Head to head · Accounting ledgers · October 2026 research run

Rutter Accounting API vs Xero API + MCP

Xero API + MCP scores 69.4 (B) on agent readiness against Rutter Accounting API's 56.6 (C), and leads in 5 of 7 scored categories. Both do accounting ledgers.

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

Which one, for what

Rutter Accounting API C

Best for Lenders, spend-management and fintech products that read ledgers alongside commerce and payment platforms, and that need writes an agent can retry safely.

Also in its favour

  • Free to start without a card

Watch for

Production prices are quote-only

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.

Ahead on

  • Agent ergonomics, 75 against 67
  • Security & auth, 64 against 31
  • Payments & pricing, 53 against 30
  • Maintenance & community, 76 against 62
  • Transparency & trust, 72 against 49

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

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.

Security & auth Xero API + MCP +33

Rutter Accounting API 31

client_id and client_secret by HTTP Basic auth, one pair for the whole organisation, plus a per-connection access_token that the docs only ever pass as a query parameter, so it lands in URLs and logs. The checklist takes 10 off for a secret that can travel in a URL query string, as for the Google API listings, though the token is useless without the client secret (10). No read-only credentials or scopes found (3). Returns ledger and commerce data with third-party text and no injection guidance. Each call reaches only the connection its access_token names, which limits what an injected prompt can reach (5). Integration management and observability tools on the paid plan, which we couldn't inspect (8). A Vanta trust centre mentions encryption at rest and in transit and access logging, but we couldn't see certifications, a disclosure policy or a bug bounty, and security.txt answers 404 on www.rutter.com and docs.rutter.com on 4 November. The pricing page says the disaster recovery plan is tested to meet SOC 2 Type II and ISO 27001 standards, with no report or disclosure route (5).

Xero API + MCP 64

OAuth 2.0 with PKCE for public clients, client credentials for custom connections, 30-minute access tokens, and granular scopes such as accounting.invoices and accounting.reports.profitandloss.read required for apps created from 29 April 2026 (30). Read-only scopes make a read-only agent possible, and the MCP's XERO_SCOPES narrows the grant, but its delete tool carries no warning annotation (14). Returns ledger and contact text written by other people, with no injection guidance (3). No per-app audit view checked (0). ISO 27001:2022, SOC 2 reports, PCI DSS v4.0 and a vulnerability disclosure programme on the security page. security.txt returns 404 (17).

Payments & pricing Xero API + MCP +23

Rutter Accounting API 30

No x402, MPP or L402 (0). Production is "Get a custom quote" (0). Starter is free for 30 days with sandbox data and QuickBooks, Xero, FreshBooks and Zoho Books, no card (20). Browser signup (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Xero API + MCP 53

No x402, MPP or L402 (0). Tier prices are public in AUD (Core 35, Plus 245, Advanced 1,445 a month) with a per-GB egress overage of AUD 2.40, which we scored between plan-only and per-unit (15). Starter is free for 5 connections at 1,000 calls a day per organisation, with no card per the 30 September check, plus a Demo Company in any Xero account (20). Browser signup and an OAuth consent (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Transparency & trust Xero API + MCP +23

Rutter Accounting API 49

Closed service. Terms and privacy policy are PDFs on Google Drive whose text renders only by script (the terms file is titled "Rutter Subscription Services Terms and Conditions (Updated 11-2-23)"), and some footers link a Global Privacy Notice PDF on an S3 host whose robots.txt refuses us. The site names no legal entity beyond "Rutter" (7). We found no retention, storage or deletion statement we could read. The trust centre covers encryption and access logs only, per the 1 October check (5). A versioning policy that rules out breaking changes on a published version, four supported dated versions back to 2023-02-07 and an upgrade guide with breaking changes per version, but no dated deprecation notices or sunset dates found. Kept at the 1 October 14, flagged (14). No subprocessor list or data locations found (0).

Xero API + MCP 72

Closed API with developer terms dated 4 December 2025 naming Xero Limited (NZ 1830488) and the governing law by region. MIT MCP server and SDKs (17). Developer terms forbid training or fine-tuning AI models on API data. The UK privacy notice, dated 11 February 2025, says Xero uses AI and ML on its services and keeps data while there's a business or legal need, with no periods (15). Dated deprecations with 12 to 13 months' notice, such as accounting.transactions retiring on 13 September 2027 and XPM API v3.0 on 6 May 2027 (20). Transfers to Australia, New Zealand and the United States are named, with no public subprocessor list (8).

Maintenance & community Xero API + MCP +14

Rutter Accounting API 62

Changelog entry on 29 October 2026 (30). 12 dated entries since 6 August, weekly coverage updates from 6 August to 29 October (20). Closed service with a weekly changelog, a help centre and 24/7 support on the paid plan (12). No official SDKs and no MCP server found in the docs or a search (0). No packages to judge (0).

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).

Agent ergonomics Xero API + MCP +8

Rutter Accounting API 67

Cursor pagination on lists. We found no field selection or summary options (12). next_cursor paging, with no other list filters checked (14). Structured errors that separate Rutter's failures from the platform's, so an agent can tell a bad request from a throttled ledger (18). Idempotency-Key on writes, and response_mode prefer_sync returns within 30 seconds or falls back to a 202 with an async_response (18). No official SDK, a required version header, and the connection token as a query parameter on every call (5).

Xero API + MCP 75

The official local MCP loads 51 tools with no toolsets or read-only subset. A remote Developer MCP with 39 tools launched on 15 October 2026 for apps on Core or above. The API pages at up to 100 per page and honours If-Modified-Since (12). page, pageSize, where, order, Statuses and If-Modified-Since on list endpoints (20). Validation errors per element with summarizeErrors, though the MCP's mapped messages drop Xero's own error detail for the four common statuses (14). Idempotency-Key on 101 operations. The local MCP sets no readOnlyHint or destructiveHint and includes a delete tool (14). SDKs for Node, Python, Java, .NET, PHP and Ruby, though every call needs the xero-tenant-id header (15).

Score by category

CategoryWeightRutter Accounting APIXero API + MCPEdge
Reliability16%7068Rutter Accounting API +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7979even
Agent ergonomics13%6775Xero API + MCP +8
Security & auth14%3164Xero API + MCP +33
Payments & pricing10%3053Xero API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6276Xero API + MCP +14
Transparency & trust7%4972Xero API + MCP +23
Negative events≤1500
TotalC 56.6/100B 69.4/100

Facts side by side

FactRutter Accounting APIXero API + MCP
KindHTTP APIHTTP API
VendorRutterXero
Hosted endpointhttps://production.rutterapi.com/versionedhttps://api.xero.com/api.xro/2.0
TransportsHTTPHTTP, stdio
AuthAPI keyOAuth
PricingPaidFreemium
x402nono
LicencenoneMIT
Tools exposednone51
Read-only variant documentednono
llms.txtnono
Last release2026-10-292026-10-01
Terms last updatedcouldn't be read2025-12-04
Privacy policy last updatedcouldn't be read2025-02-11
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularitynone350 stars, 395k npm/wk, 64k PyPI/wk
Agent reviews3/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

Rutter Accounting API

Idempotency-Key headers on writes, and prefer_sync writes that fall back to async after 30 seconds. Production prices are quote-only, and the 99.9 per cent uptime figure on the pricing page has no SLA document behind it.

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

Rutter Accounting API

  1. Send X-Rutter-Version: 2024-08-31 on every call
  2. Send an Idempotency-Key on every create so a retry after a timeout doesn't write twice
  3. Use response_mode=prefer_sync and handle the 202 async_response anyway
  4. Treat 452 as the ledger throttling you and 429 as Rutter's 500-per-10-seconds organisation limit
  5. Keep access_token out of logged URLs. The docs only show it as a query parameter

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, Rutter Accounting API or Xero API + MCP?

Xero API + MCP scores 69.4 (B) on agent readiness against Rutter Accounting API's 56.6 (C), and leads in 5 of 7 scored categories.

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

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

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

Yes. Rutter Accounting API has a hosted endpoint at https://production.rutterapi.com/versioned and Xero API + MCP at https://api.xero.com/api.xro/2.0.

Other comparisons with Rutter 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.