API v1
Connect as an AI agent
Discovery files, markdown docs, OpenAPI, WebMCP, and how to call the ledger API.
Start with GET /llms.txt. It is the map. Follow links to markdown pages instead of scraping HTML. This origin does not host a Streamable HTTP MCP server — import OpenAPI into a bridge (AnythingMCP) or call REST directly. Use the curated tool set described in MCP tool design.
Discovery URLs
| URL | What it is |
|---|---|
| /llms.txt | Curated markdown map (llmstxt.org) |
| /llms-full.txt | Full docs corpus for RAG |
| /index.md | Product overview in markdown |
| /skill.md | Agent playbook: auth, curated tools, workflows |
| /developers/guides/audit-log.md | How writes appear in Log for humans |
| /agents.txt | Capability announcement (skills + WebMCP pages) |
| /agents.json | Structured companion to agents.txt |
| /.well-known/api-catalog | RFC 9727 API catalog (OpenAPI + ontology) |
| /openapi.json | OpenAPI 3 spec with x-mcp annotations (public) |
| /api/v1/ontology.jsonld | JSON-LD ontology (public) |
Every HTML docs page has a .md twin (e.g. /developers/quickstart.md) and a rel=alternate Link header. Send Accept: text/markdown on /developers to receive markdown.
Call the API
Authorization: Bearer bb_live_<token>- Create a token in Settings → MCP access
- read lists ledger data; propose-write creates approval-queue items (audit-logged in Log)
- Prefer categoryCode (5100) over display names
- Use limit≤50 on list calls
- Never auto-post journal entries — POST /api/v1/proposals/journal-entry
- Write clear reason/confidence/evidence — humans see them in Approvals and Log
WebMCP
Browser agents that support WebMCP can call in-page tools on /, /developers, /dashboard, /ledger, and /log. Tools are read-only discovery and same-origin navigation. They do not return ledger or audit rows — use the REST API for data; do not scrape Log.
WebMCP is a Chrome origin trial (149–156) via document.modelContext.registerTool. Verified in Chrome 152 with chrome://flags/#enable-webmcp-testing (or --enable-features=WebMCPTesting). Cursor's embedded browser does not ship it — tools no-op when modelContext is missing. This page shows live registration status when the API is present.
Checking WebMCP in this browser…