Skip to content

Connect an AI agent

An agent that can send HTTP requests, Claude Code or Codex for example, can work with Lobbe through the API. It learns the routes from Lobbe’s OpenAPI document and sends each request with a token you made for it.

  • Make the agent a token of its own, with only the scopes its work needs and, if it spends minutes, a daily cap. See Tokens and scopes.
  • Keep Developer mode on. While it is off, every request the agent sends answers 403 DEVELOPER_MODE_OFF: see Developer mode.
Terminal window
export LOBBE_TOKEN=lobbe_…
# Then tell your agent:
# Use the Lobbe API at https://app.lobbe.ai/api/v1 with the bearer token in $LOBBE_TOKEN.
# Its OpenAPI document: https://app.lobbe.ai/api/v1/openapi.json
# Ask for a meeting's status no more than once a minute.

Put the token in LOBBE_TOKEN, in the environment the agent runs in. Then give the agent the lines after # Then tell your agent:, in its instructions or at the start of a conversation. They name the variable, never the token itself. In the app, Connections › Agents shows the same lines.

  • The OpenAPI document, https://app.lobbe.ai/api/v1/openapi.json: every route, its fields and its errors. Reading it needs no token. Each operation also says which scopes it needs (x-lobbe-scopes), whether it spends minutes (x-lobbe-spends) and its rate limit (x-lobbe-rate-limit). These docs serve the same document at /openapi.json.
  • These docs, as Markdown. llms.txt lists every page with a link to its Markdown, and llms-full.txt holds every page in one file; those two files are in English. Each page, in either language, is also Markdown at its own address, with .md in place of the trailing slash: https://docs.lobbe.ai/guides/lifecycle.md or https://docs.lobbe.ai/fa/guides/lifecycle.md. The two home pages are the exception: https://docs.lobbe.ai/index.md and https://docs.lobbe.ai/fa/index.md.

The lines above name the OpenAPI document only. For the agent to read the guides too, add https://docs.lobbe.ai/llms.txt to what you tell it.

Tell the agent these as well:

  • Ask for a meeting’s status no more than once a minute. Most meetings are done within a few minutes. To follow many meetings, read the events feed instead. On a 429, wait the seconds Retry-After gives.
  • At NAMING, give the person naming.url, and don’t guess the speakers’ names. The link opens the meeting’s speaker naming in the app, for its owner, and the Lobbe’s decisions and action items then carry real names. Skip naming only when the person says to: see Speaker naming.
  • Get the price before an Ask. The quote is free. Send the Ask with maxMinutes set to the quote’s minutes, so it never costs more than that. Every answer spends minutes, a refusal included: see Ask a meeting.
  • Send an Idempotency-Key with each request that spends, made once and kept for every retry of that request, so a retry never pays twice: see Idempotency and retries.
  • Never print the token. Read it from $LOBBE_TOKEN. Never echo it, put it in a URL, write it to a file or a log, or quote it in an answer: see Keep it safe.
  • On 403 DEVELOPER_MODE_OFF, stop and tell the person. The owner has turned Developer mode off, which pauses every token of the account, and retrying can’t help until it is back on: see Errors.

A Lobbe MCP server and a CLI are coming. Until then, an agent connects through the OpenAPI document.