Head to head · Accounting ledgers · October 2026 research run

Merge Accounting API vs Xero API + MCP

Merge Accounting API scores 72.4 (BB) on agent readiness against Xero API + MCP's 69.4 (B), and leads in 4 of 7 scored categories. Both do accounting ledgers.

Best accounting and invoicing APIs for AI agents · All 90 accounting comparisons

Which one, for what

Merge Accounting API BB

Best for A SaaS product that reads and writes many customers' ledgers through one model and wants docs an agent can read cheaply.

Ahead on

  • Reliability, 75 against 68
  • Schema & documentation, 86 against 79
  • Maintenance & community, 83 against 76

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Launch jumps from free to $650 a month at the fourth linked account

Xero API + MCP B

Best for An agent keeping the books for UK, Australian or New Zealand businesses, or any team that wants read-only scopes and long deprecation notice.

Also in its favour

  • Runs on your own machine

Watch for

Developer docs, including the per-minute rate limits, only render with JavaScript

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Merge Accounting API +7

Merge Accounting API 75

Status page on Sorry with components for the Unified API, Merge Link, data syncing and Agent Handler, per the 1 October check (20). status.merge.dev's robots.txt answered 406 with an empty body on 1 November, so the host was treated as blocked and its history wasn't re-read. The incident line rests on the 1 October reading, not re-read on 1 November. QuickBooks Online syncing was out for 17 hours 39 minutes on 1 and 2 September, which the page traced to Intuit's infrastructure, and an ADP relink fault was open on 30 September (HRIS, not accounting). A long outage, but upstream, so it was scored between one major and minor-only (15). 100, 400 or 600 requests a minute per linked account by plan, unchanged on 1 November (15). The docs say nothing about 429, Retry-After or retrying writes. The official SDKs retry 429, 408 and 409 with Retry-After and exponential backoff (5). Uptime SLA on Enterprise (10). GA (10).

Xero API + MCP 68

Statuspage at status.xero.com with product and region components, none of them the API (20). Since 3 August the history lists tax-authority connections (HMRC, ATO, Inland Revenue), US payroll through Gusto, Partner Hub, subscriptions, third-party outages and scheduled maintenance. None names the API. The longest whole-product incidents were errors navigating Xero after logging in for about an hour on 28 October (labelled critical, component Xero Platform and Settings) and intermittent errors for some customers for 2 hours 24 minutes on 26 and 27 October, both read from their text as the web app, not the API (20). Daily limits per organisation are published on the pricing page (1,000 on Starter, 5,000 above). The minute and concurrency limits are on a JavaScript-only page we couldn't read (10). The OpenAPI spec puts an Idempotency-Key parameter on 101 operations. 429 and Retry-After handling sits on the unreadable limits page (8). No SLA found (0). GA (10).

Schema & documentation Merge Accounting API +7

Merge Accounting API 86

OpenAPI spec for accounting published as JSON at docs.merge.dev/openapi/accounting.json (25). llms.txt with about 70 links, every docs page available as .md (10). Docs explain each common model and point writers to the meta endpoint for per-platform required fields, though not when to avoid a route (15). Typed models with enums such as ACCOUNTS_PAYABLE and ACCOUNTS_RECEIVABLE and typed expand values (13). Write responses document model, warnings, errors and debug logs, but llms.txt lists no errors page (10). Weekly dated changelog and semver SDKs, with the API fixed at /v1 and no deprecation notices (13).

Xero API + MCP 79

OpenAPI specs for accounting, payroll, assets, files, bank feeds, projects and more in XeroAPI/Xero-OpenAPI, 235 operations in accounting alone (25). No llms.txt, and developer docs return "This app works with JavaScript enabled" to a fetch (0). MCP descriptions name the tool to call first ("can be obtained from the list-accounts tool") and explain ACCREC and ACCPAY, but don't say when not to use a tool (15). Zod schemas with enums, and enums throughout the spec (13). Examples in the spec, a summarizeErrors option for batch writes, and the MCP maps 401, 403, 404 and 429 to plain messages (11). Spec tagged 19.1.0 on 1 October and a dated developer changelog with deprecation dates (15).

Maintenance & community Merge Accounting API +7

Merge Accounting API 83

Changelog entry for the Unified API on 30 October 2026 and MergePythonClient v4.2.1 on 5 October (30). Weekly changelog entries (9, 16, 23 and 30 October for the Unified API) and two Python SDK tags since 3 August (20). Closed service with a weekly changelog, support@merge.dev and a help centre (12). Current official SDKs (Python 4.2.1, Node 4.0.4), but the official Unified API MCP server, merge-mcp, hasn't changed since 0.1.4 on 30 April 2025 (13). SDK CI and Semgrep scanning (8).

Xero API + MCP 76

Xero-OpenAPI 19.1.0 on 1 October and a dated developer changelog entry on 15 October for the remote MCP launch (30). Spec releases 16.2.0, 17.0.0, 18.0.0, 19.0.0 and 19.1.0, xero-node 19.1.0, 19.2.0 and 20.0.0, and changelog entries from 10 August to 15 October, all since 3 August (20). Closed API with a dated changelog and developer community. The local MCP repository had five commits on 26 October after none since 5 June, none of them released yet (10). Current official SDKs in six languages, but the MCP isn't in the official registry, and npm's latest was 0.0.17 from 26 May per the 1 October check (12). The MCP repository has no CI workflows (4).

Score by category

CategoryWeightMerge Accounting APIXero API + MCPEdge
Reliability16%7568Merge Accounting API +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8679Merge Accounting API +7
Agent ergonomics13%7275Xero API + MCP +3
Security & auth14%6764Merge Accounting API +3
Payments & pricing10%5353even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8376Merge Accounting API +7
Transparency & trust7%7072Xero API + MCP +2
Negative events≤1500
TotalBB 72.4/100B 69.4/100

Facts side by side

FactMerge Accounting APIXero API + MCP
KindHTTP APIHTTP API
VendorMergeXero
Hosted endpointhttps://api.merge.dev/api/accounting/v1https://api.xero.com/api.xro/2.0
TransportsHTTPHTTP, stdio
AuthAPI keyOAuth
PricingFreemiumFreemium
x402nono
LicenceMITMIT
Tools exposednone51
Read-only variant documentednono
llms.txtyesno
Last release2026-10-052026-10-01
Terms last updatedno date given2025-12-04
Privacy policy last updated2026-08-202025-02-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity15 stars, 201k npm/wk, 235k PyPI/wk350 stars, 395k npm/wk, 64k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Merge Accounting API

12 accounting platforms behind one set of common models, with writes. Launch jumps from free to $650 a month at the fourth linked account.

Xero API + MCP

Granular OAuth scopes, such as accounting.reports.profitandloss.read, required for apps created from 29 April 2026. Developer docs, including the per-minute rate limits, only render with JavaScript.

Before you call either

Merge Accounting API

  1. Call GET /invoices/meta/post for the linked account first. Required fields differ by platform
  2. Bills and sales invoices are one model. Set type to ACCOUNTS_PAYABLE or ACCOUNTS_RECEIVABLE
  3. Append .md to any docs URL for the Markdown twin
  4. Check sync_status before reading a freshly linked account. Common models fill in over the first sync
  5. Look the record up before retrying a POST that timed out. There's no idempotency key

Xero API + MCP

  1. Send xero-tenant-id on every call. The token alone doesn't name the organisation
  2. A bill is an Invoice with Type ACCPAY, a sales invoice is ACCREC. There's no separate bills endpoint
  3. Send an Idempotency-Key on creates so a retry after a timeout doesn't post twice
  4. Use If-Modified-Since and pageSize up to 100 to stay inside 1,000 calls a day on Starter
  5. Set XERO_SCOPES to read scopes only when the agent shouldn't write. The MCP still lists its write and delete tools

Questions

Which is better for AI agents, Merge Accounting API or Xero API + MCP?

Merge Accounting API scores 72.4 (BB) on agent readiness against Xero API + MCP's 69.4 (B), and leads in 4 of 7 scored categories.

Do Merge Accounting API and Xero API + MCP need an API key?

Merge Accounting API needs an API key. Xero API + MCP uses an OAuth sign-in.

Can an agent call Merge Accounting API and Xero API + MCP without installing anything?

Yes. Merge Accounting API has a hosted endpoint at https://api.merge.dev/api/accounting/v1 and Xero API + MCP at https://api.xero.com/api.xro/2.0.

Other comparisons with Merge Accounting API or Xero API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.