Skip to content

API keys, OAuth, revocation, permissions, and limits

MCP credentials belong to your user, but each credential binds one ledger. Tools run only in that ledger’s data. They do not see other memberships.

Create keys at Settings → API keys. Choose the ledger at creation. The full tl_ value is shown once. The table shows a prefix, created date, last used, and active or disabled. Revoke a key from that row.

Use a key for Claude Code or any client that sends Authorization: Bearer tl_....

Claude.ai, Claude Desktop, and ChatGPT (Developer mode connector) complete OAuth in the browser. The consent screen binds one ledger. Revoke a grant at Settings → Connected apps. That drops that app’s access to that ledger.

/mcp never accepts the website session cookie.

  • Free ledger. Read tools only. Writes return a Pro-feature message, not a broken connection.
  • Pro ledger, owner or editor. Read and write.
  • Viewer. Read only, even on a Pro ledger.
  • Future-dated journeys. Pro only, on top of write access.

Daily quota is per ledger plan and is shared by every API key and OAuth grant bound to that ledger.

  • Free. 100 MCP requests per day
  • Pro. 5,000 MCP requests per day

A short per-minute burst limit sits on top. Unauthenticated /mcp attempts also have a per-IP limit. Hitting a limit returns an error that names the reset time.

  • Revoke one key or one connected app in Settings.
  • Changing your password revokes all API keys and all OAuth grants. Reconnect afterward.
  • Treat keys as passwords. Rotate when they show up in a transcript you would not share.