Head to head · Accounting ledgers · October 2026 research run

FreeAgent API vs Xero API + MCP

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

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

Which one, for what

FreeAgent API C

Best for An agent doing the books for a UK freelancer or small limited company, especially one already banking with NatWest.

Ahead on

  • Reliability, 85 against 68

Watch for

No OAuth scopes, so a token can do anything the authorising user can

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

  • Schema & documentation, 79 against 50
  • Agent ergonomics, 75 against 55
  • Security & auth, 64 against 44
  • Payments & pricing, 53 against 45
  • Maintenance & community, 76 against 60

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 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.

Schema & documentation Xero API + MCP +29

FreeAgent API 50

No OpenAPI or other machine-readable spec (0). No llms.txt or Markdown docs. The HTML is server-rendered and reads cleanly to a plain fetch, which the checklist doesn't score (0). Each resource page explains purpose and workflow, such as invoices created as drafts and moved by transition endpoints (14). Attribute tables give types, required markers and enums such as invoice status values (12). JSON and XML request and response examples on every page, but no error body format or error catalogue (9). Dated API changelog and a versioning guide (15).

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

Agent ergonomics Xero API + MCP +20

FreeAgent API 55

Responses sized by per_page (default 25, maximum 100), view filters such as open, overdue and last_N_months, and nested items off unless asked. No field selection (15). Link headers for prev, next, first and last, X-Total-Count, updated_since and sort (20). Only the 429 path is documented, not the error bodies an agent has to recover from (8). No idempotency keys or safe-retry guidance. Invoices start as drafts, which makes a duplicate visible before it goes out (5). Defaults are sensible, but there's no official SDK in any language (7).

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

Security & auth Xero API + MCP +20

FreeAgent API 44

OAuth 2.0 authorisation code, one-hour access tokens, refresh tokens that rotate on each refresh, and a client secret rotation guide. No scopes, so a token can do whatever the authorising user can (22). No read-only mode. Invoices are drafts until a transition endpoint marks them sent, which works as a confirmation step (5). Returns the business's own records plus bank descriptions and contact text from third parties, with no injection guidance (3). No per-app audit log or API activity view found (0). Valid security.txt to April 2027, a disclosure policy with discretionary rewards and Cyber Essentials Plus. No ISO 27001 or SOC 2 found (14).

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

Reliability FreeAgent API +17

FreeAgent API 85

Statuspage at status.freeagent.com with history back to September 2024 (20). Nothing between the scheduled database maintenance on 17 June and the next one, posted on 29 October for 22:00 to 23:00 GMT on 4 November, so the 90 days from 6 August are clean (30). 120 requests a minute and 3,600 an hour per user, plus 15 token refreshes a minute (15). 429 with Retry-After 60, a request to back off before retrying, and an X-RateLimit-Test header that drops the sandbox to 5 a minute so a client can rehearse the back-off. No guidance on retrying writes and no idempotency keys (10). No SLA found (0). 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).

Maintenance & community Xero API + MCP +16

FreeAgent API 60

Last dated API change on 7 October 2026, employee and employer pension percentages on the Payroll endpoint (30). Five dated entries in the 90 days from 6 August (17 August, 20 August, 1 September, 5 October, 7 October) (20). Closed service with a public changelog and a developer discussion group at api-discuss.freeagent.com that isn't official support (10). No official SDKs and no MCP server (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).

Payments & pricing Xero API + MCP +8

FreeAgent API 45

No x402, MPP or L402 (0). The API is free under section 4.1 of the terms with 30 days' notice before any fee, and a live company needs a subscription with public prices (£33 a month for a limited company, half for the first six months). We scored it as plan-only pricing (10). Free sandbox account at signup.sandbox.freeagent.com and a 30-day product trial (20). Browser signup and a developer app registration (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Score by category

CategoryWeightFreeAgent APIXero API + MCPEdge
Reliability16%8568FreeAgent API +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5079Xero API + MCP +29
Agent ergonomics13%5575Xero API + MCP +20
Security & auth14%4464Xero API + MCP +20
Payments & pricing10%4553Xero API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6076Xero API + MCP +16
Transparency & trust7%7472FreeAgent API +2
Negative events≤1500
TotalC 59.1/100B 69.4/100

Facts side by side

FactFreeAgent APIXero API + MCP
KindHTTP APIHTTP API
VendorFreeAgentXero
Hosted endpointhttps://api.freeagent.com/v2https://api.xero.com/api.xro/2.0
TransportsHTTPHTTP, stdio
AuthOAuthOAuth
PricingYour planFreemium
x402nono
LicencenoneMIT
Tools exposednone51
Read-only variant documentednono
llms.txtnono
Last release2026-10-072026-10-01
Terms last updated2025-02-282025-12-04
Privacy policy last updatedcouldn't be read2025-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 benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone350 stars, 395k npm/wk, 64k PyPI/wk
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Xero API + MCP higher.

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

FreeAgent API

Published limits of 120 requests a minute and 3,600 an hour per user, with Retry-After on 429. No OAuth scopes, so a token can do anything the authorising user can.

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

FreeAgent API

  1. Store the new refresh token from every refresh response. The old one stops working
  2. Create the invoice, then PUT /v2/invoices/:id/transitions/mark_as_sent. A draft isn't visible to the customer
  3. Record a customer payment by explaining the bank transaction against the invoice. There's no invoice payments endpoint
  4. Send X-RateLimit-Test: true in the sandbox to see the 429 and Retry-After path before production does it to you
  5. Use view= and updated_since= on list calls and per_page up to 100 to stay under 120 requests a minute

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

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

Do FreeAgent API and Xero API + MCP need an API key?

Both use an OAuth sign-in.

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

Yes. FreeAgent API has a hosted endpoint at https://api.freeagent.com/v2 and Xero API + MCP at https://api.xero.com/api.xro/2.0.

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