Build with an AI agent

Pointing a coding agent — Claude Code, Codex, Cursor, or anything that can fetch a URL — at TenkeyBridge is a first-class way to integrate. The entire documentation site is published in agent-readable form:

• /llms.txt — index with one-line summaries
• /llms-full.txt — every page in one file (small enough for any modern context window)

Starting prompt

Get credentials first, fill in the placeholders, then paste this into your agent from inside your app's repository:

You are integrating this application with TenkeyBridge, a QuickBooks
Online-compatible REST API for QuickBooks Desktop & Enterprise. The API base URL is
https://api.tenkeybridge.com and it is live.

Before writing any code, fetch https://docs.tenkeybridge.com/llms-full.txt and read
it — it is the entire documentation site: quickstart, authentication (OAuth2), the
entity-by-entity compatibility contract, and error codes.

Credentials for this integration:
- client_id: <CLIENT_ID>
- client_secret: <CLIENT_SECRET>
- registered redirect URI: <REDIRECT_URI>
- QuickBooks company realm ID: <REALM_ID> (pass as `realm_id` on the authorize URL)

Working rules:
1. If this app already integrates with QuickBooks Online, the core change is the
   base URL and the OAuth authorize/token URLs — reuse the existing QBO code paths.
2. Before integrating each entity, check its section of the compatibility contract
   and adapt to anything marked partial.
3. When an API call returns a Fault, look up its error code in the error-codes
   reference before retrying or changing the request.
4. If the documentation is unclear, wrong, or missing something you need, STOP and
   report it to the developer. Do not guess or work around documentation gaps.

Tool notes

• Claude Code — paste the prompt into a session, or commit it to CLAUDE.md so every session starts with it.
• Codex — put it in AGENTS.md at the repo root.
• Cursor — add it as a project rule (.cursor/rules/).

MCP

@tenkeybridge/mcp is the official MCP server: five tools (query, get, create, update, delete) over the live API, plus a compatibility-catalog resource (compat://catalog, with per-entity detail at compat://entity/{name}) so agents can check entity and field support before calling instead of learning by 400. API faults come back structured — status, code, fixes, docsUrl — so agents self-correct.

Create an OAuth client in the developer portal (see Authentication for the token flow), then add the server to your MCP host config:

{
  "mcpServers": {
    "tenkeybridge": {
      "command": "npx",
      "args": ["-y", "@tenkeybridge/mcp"],
      "env": {
        "TKB_REALM_ID": "9130350000000000",
        "TKB_CLIENT_ID": "tkb-ci-example",
        "TKB_CLIENT_SECRET": "…",
        "TKB_REFRESH_TOKEN": "…"
      }
    }
  }
}

Refresh tokens rotate — the server persists the newest pair under ~/.tenkeybridge/ (override with TKB_TOKEN_FILE) and reuses it across restarts. A static TKB_ACCESS_TOKEN and a TKB_BASE_URL override are also supported. The docs remain available to agents as llms-full.txt — no install required.