{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/accounting.connect-books/",
    "json": "https://www.anchorterminal.com/niches/accounting.connect-books/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/accounting.connect-books/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/accounting.connect-books/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 2 | 8 | 13 | 17 | 12 |\n\n## What counts as done\n\nThe agent reaches the real company (not only a demo) through documented setup a single business can complete itself, with a read-only or object-limited grant that the tool enforces, and a second user can connect without displacing the first.\n\nMeasured, for our own tests: setup in under 30 minutes without an app review.\n\nHow agents ask for it: connect Claude to my QuickBooks; give the agent read-only access to Xero; let my bookkeeper and me both use it; make sure it cannot delete anything\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Pennylane (Pennylane SAS)**: An admin on Essentiel or above makes a company token in Settings \u003e Connectivity \u003e Developers with :readonly or :all scopes per resource and an expiry; a company can hold several tokens, one per user or integration. The hosted MCP is read-only.\n- **Zoho Books (Zoho Corporation Private Limited)**: A Self Client serves a business connecting its own organisation with no review, and scopes are per module and per action (ZohoBooks.invoices.READ), so a read-only grant is enforced. Each user authorises with their own tokens.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Apideck Accounting API + MCP (Apideck Inc. and Apideck NV/BV)**: Built for SaaS products reaching customers; a business can connect its own ledger through Vault on a 30-day trial, then $599 a month. MCP --scope read is enforced since 0.19.0 (issue 62), but the REST API key itself has no read-only grant.\n- **FreeAgent API (FreeAgent Central Limited)**: Any developer registers an app on the dashboard with no review and each user authorises their own token. There are no OAuth scopes; the only limit is authorising as a user with a lower permission level (Invoices, Bills, Banking), which is not read-only.\n- **FreshBooks API (2NDSITE Inc.)**: OAuth scopes are per object and per read or write (user:invoices:read), so a read-only grant is enforced. Only one refresh token lives per user per app, so concurrent refreshes break, and whether a private app needs no review was not found.\n- **Invoice Ninja API (Invoice Ninja LLC)**: A business creates an API token in its own settings (Settings \u003e Account Management \u003e Integrations), on hosted Pro or self-hosted, with no review. No read-only or per-object token is documented.\n- **Merge Accounting API (Merge API, Inc.)**: Aimed at SaaS products linking customers through Merge Link; a business could link its own ledger (the listing's pricing notes give 3 free linked accounts). linked-account-scopes sets model and field permissions per linked account.\n- **Odoo External API (Odoo SA)**: A user makes an API key in Preferences with a set lifetime, and the docs advise a dedicated bot user with minimum rights, which Odoo's access rights enforce. Odoo Online excludes the external API on One App Free and Standard; the Custom plan is needed.\n- **Puzzle API and MCP (Puzzle Financial Inc.)**: The hosted MCP signs in by OAuth, lets the user pick companies, is read-only by default with write as an opt-in beta, and can be revoked. That rests on the product page; no tool list or scope enforcement test is published.\n- **Xero API + MCP (Xero Limited)**: Custom Connections give one organisation its own client, and granular .read scopes are enforced by the API. Custom Connections aren't offered in Canada (acc-31) and post-29 April connections can't authenticate with the MCP's hard-coded scopes (acc-26); both open, and the MCP still lists write tools.\n\n- not this job: Codat (Codat Limited): Sold to lenders and fintechs under an order form with no self-serve signup; API keys have no scopes or read-only mode and reach every connected company.\n- not this job: QuickBooks Online API + MCP (Intuit Inc.): A business must register an Intuit OAuth app like a SaaS vendor (acc-38, no personal token), and one accounting scope covers the whole ledger including delete (acc-05). The MCP's DISABLE_WRITE flags hide tools locally; the token stays full access.\n- not this job: rotki MCP server (Rotki Solutions GmbH): Connects to the user's local rotki app, not to a company's ledger; there is no multi-user model.\n- not this job: Rutter Accounting API (Rutter): Built for lenders and fintech products: production is a sales quote, each connection's access_token rides in the query string, and no read-only scope is documented.\n\n## What stops agents finishing\n\n- only a public OAuth app works, with no personal token for a single business\n- the connector type the MCP needs is not offered in the organisation's country\n- one scope covers the whole ledger, including delete\n\n## Around it\n\nAfter: accounting.read-reports, accounting.raise-invoice, accounting.reconcile-bank.\n\n## Where this comes from\n\nWeight 17 of 100 in Accounting \u0026 invoicing: 12 of 69 use-case citations across 60 accounts, scaled to 100\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/accounting.connect-books.json, or the MCP tool get_use_case with id accounting.connect-books. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Connect an agent to one company's books with the right access",
        "url": ""
      }
    ],
    "description": "Connect an agent to one company's books with the right access: 2 companies fully do it, 8 with a limit, 13 carry the tag. Every listing in Accounting \u0026 invoicing with the reason and a source.",
    "facts": null,
    "h1": "Connect an agent to one company's books with the right access",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/accounting.connect-books/",
    "published": "",
    "section": "agents",
    "title": "Connect an agent to one company's books with the right access |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/accounting.connect-books/"
  },
  "tokens": {
    "markdown": 1550,
    "slim": 330
  },
  "version": 1
}
