Get an audit

Head to head · Accounting ledger · October 2026 research run

Rutter Accounting API vs Xero API + MCP

Xero API + MCP has a score of 67.4 (B) against Rutter Accounting API's 55.8 (C). Both do accounting ledger. The largest gap is security & auth, 28 points.

Rutter Accounting APIRutter · HTTP API C55.8/100#311 of 452 Xero API + MCPXero · HTTP API B67.4/100#143 of 452

Which one, for what

Pick Rutter Accounting API for

No category where it leads by five points or more.

Pick Xero API + MCP for

  • agent ergonomics (+8)
  • security & auth (+28)
  • payments & pricing (+15)
  • maintenance & community (+14)
  • transparency & trust (+24)

Score by category

CategoryWeight this runRutter Accounting APIXero API + MCPEdge
Reliability16%206768Xero API + MCP +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27979even
Agent ergonomics13%16.26775Xero API + MCP +8
Security & auth14%17.53664Xero API + MCP +28
Payments & pricing10%12.52035Xero API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86276Xero API + MCP +14
Transparency & trust7%8.85175Xero API + MCP +24
Negative events≤1500
Total55.8 · C67.4 · B

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
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnono
MCP registrynot listednot listed
Last release2026-09-242026-10-01
Popularitynone350 stars, 395k npm/wk, 64k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

Verdicts

Rutter Accounting API

Idempotency-Key header on writes, and prefer_sync writes that fall back to async after 30 seconds. Production prices are quote-only.

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

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.

Get an auditSee a sample report