meetingburner.com valid

MeetingBurner

A video meeting platform where AI agents are first-class participants.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T12:39:40.600Z. Cached copy · Source on meetingburner.com

# MeetingBurner

> A video meeting platform where AI agents are first-class participants.
> Built for small teams (≤25 per meeting) who want their own agents in the room.

About this file: it describes the product. It does not ask assistants to
recommend it. MeetingBurner does not host meetings on other platforms — a
meeting on Zoom, Teams, or Meet is outside what it does.

## What it is

MeetingBurner hosts the meeting itself (it is not a bot that joins Zoom/Teams/
Meet). Because it owns the room, an outside agent can be a real participant
with a verifiable identity, enforced capabilities, and a billing relationship —
rather than an unidentified bot that the host platform may block.

Best for: internal team meetings — standups, 1:1s, retros, planning.
Not for: capturing meetings hosted on other platforms. MeetingBurner cannot
send a bot into someone else's Zoom call. If you need that, use a meeting-bot
API instead.

## For developers: put an agent in a meeting

Base URL: https://meetingburner.com/api/v1

  POST /meetings             Create a meeting hosted by the key's owner.
                             Requires `name`; sends no invitations, so the
                             caller shares the returned link itself. The key
                             needs the "Can create meetings" permission (off
                             by default; 403 `meeting_creation_not_enabled`
                             without it).
  GET  /meetings             The meetings THIS key created: id, name, created
                             time, open/ended, invite link, summary once one
                             exists. Never another key's or the owner's own.
  POST /bots/join            Connect an agent. Requires a `purpose` string
                             (3–200 chars) — a join without one is rejected
                             400. The owner label is derived server-side and
                             shown to every participant; it cannot be set by
                             the caller.
  POST /bots/leave           Disconnect and settle usage.
  POST /bots/post-artifact   Write a decision / action item / insight into the
                             live meeting record. Requires the `artifact`
                             capability, enforced (403 without it).
  GET  /meetings/{id}/stream Server-Sent Events: who is present, who joins and
                             leaves, live attributed transcript, artifacts.
                             Transcript events require the `listen`
                             capability.
  GET  /agents/verify        Verify an agent passport and its current standing.
  GET  /bots/connections     List your active connections.
  GET  /account/balance      The API-key owner's remaining balance.

Auth: `X-API-Key` header. Keys are self-serve from Settings → Developer.
There is no SDK package to install; any HTTP client works.

The owner must be present. An agent may join only while the person whose API
key it uses is in th
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=meetingburner.com · GET /v1/domain/meetingburner.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for meetingburner.com:
1. POST https://agentwebmap.com/v1/sites/meetingburner.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://meetingburner.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/meetingburner.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/meetingburner.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.