Head to head · Accounting ledgers · October 2026 research run

FreshBooks API vs Xero API + MCP

Xero API + MCP scores 69.4 (B) on agent readiness against FreshBooks API's 47.2 (D), and leads in every scored category. Both do accounting ledgers.

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

Which one, for what

FreshBooks API D

Best for An agent that bills clients, chases invoices and reads the books for a freelancer or small service firm already on FreshBooks.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Rate limits have no numbers, status code or headers

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

  • Reliability, 68 against 35
  • Schema & documentation, 79 against 48
  • Agent ergonomics, 75 against 61
  • Security & auth, 64 against 57
  • Payments & pricing, 53 against 45
  • Maintenance & community, 76 against 14
  • Transparency & trust, 72 against 65

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.

Maintenance & community Xero API + MCP +62

FreshBooks API 14

No dated API change found on 1 October, and the docs couldn't be re-read on 5 November (terms pause). The SDK repositories, cloned on 5 November, have no release since @freshbooks/api 4.1.0 on 11 September 2024 and the Python SDK's release/1.2.1 tag of 24 April 2023 (0). Nothing dated in the last 90 days (0). Support by email at api@freshbooks.com and a one-entry changelog, per 1 October (5). Official SDKs exist in two languages but haven't been released in two years (5). Both SDK repositories gained a FreshBooks Global CI workflow on 5 October 2026, committed with "-deploy -playwright -tests", alongside the existing test workflows. The Node repository's last code or dependency change was February 2025 and the Python one's August 2024 (4). 0 + 0 + 5 + 5 + 4 = 14.

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

Reliability Xero API + MCP +33

FreshBooks API 35

Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. Statuspage at status.freshbooks.com with history but no API component, so API trouble is reported only as FreshBooks trouble (15). On 1 October the page showed FreshBooks down from 13:44 to 15:38 EDT on 4 August, about two hours. That outage now falls before the 90-day window, which runs from 7 August, but 2 October to 5 November couldn't be read, so the recorded award is kept (10). No numbers, only "rate-limited if too many calls are made within a short period of time" (0). No 429, Retry-After or retry guidance in the limits or errors pages (0). No SLA found (0). GA (10). 15 + 10 + 0 + 0 + 0 + 10 = 35.

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 Xero API + MCP +31

FreshBooks API 48

Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. No OpenAPI spec. A Postman collection is published, which we counted as a partial contract (10). No llms.txt or Markdown docs (0). Plain HTML reference pages per resource that explain the workflow, such as marking an invoice sent before reports count it (13). Field lists per resource, with fewer enums and constraints spelt out than the ledgers here (9). An errors page with numbered codes (1001 RequiredField, 1004 InvalidValue, 1012 UnknownResource) and request examples, but no error body example (11). The "API Changelog" section holds one entry, the 2021 to 2023 move to JWT tokens, and an x-api-version header on journal entries (5). 10 + 0 + 13 + 9 + 11 + 5 = 48. 10 + 0 + 13 + 9 + 11 + 5 = 48.

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 +14

FreshBooks API 61

Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. per_page up to 100 and includes to pull related objects only when asked. No field selection (15). search[] filters, page and per_page on lists (18). Numbered error codes an agent can act on, but nothing on throttling (13). No idempotency keys or retry guidance. Invoices stay drafts until marked sent (5). Official SDKs in Python and Node, though both are stale, and an account id or business id lookup is needed before most calls (10). 15 + 18 + 13 + 5 + 10 = 61. 15 + 18 + 13 + 5 + 10 = 61.

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

Payments & pricing Xero API + MCP +8

FreshBooks API 45

Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. No x402, MPP or L402 (0). The API comes with any plan, and plan prices are public, Lite $23, Plus $43, Premium $70 a month, Select on request (10). 30-day trial with no card, per the pricing page (20). Browser signup and app registration (0). 0 + 10 + 20 + 0 = 30. 0 + 10 + 20 + 0 = 30. 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.

Security & auth Xero API + MCP +7

FreshBooks API 57

Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. Per the 1 October check, not re-read on 5 November 2026, because FreshBooks' terms of service (last updated 7 October 2026) bar data mining, robots and similar data gathering on the Site and Services. OAuth 2.0 with read and write scopes per resource (user:invoices:read, user:journal_entries:write), short-lived JWT access tokens and a revoke endpoint. No PKCE mentioned (28). Read-only scopes make a read-only agent possible, and drafts act as a confirmation step for invoices (14). Returns the business's own records plus client-entered text, with no injection guidance (3). No audit log or API activity view found (0). PCI DSS Level 1 with an annual third-party audit and a responsible-disclosure policy. security.txt returned 403 to the 30 September check, and no bug bounty or SOC 2 found (12). 28 + 14 + 3 + 0 + 12 = 57. 28 + 14 + 3 + 0 + 12 = 57.

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

Score by category

CategoryWeightFreshBooks APIXero API + MCPEdge
Reliability16%3568Xero API + MCP +33
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4879Xero API + MCP +31
Agent ergonomics13%6175Xero API + MCP +14
Security & auth14%5764Xero API + MCP +7
Payments & pricing10%4553Xero API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1476Xero API + MCP +62
Transparency & trust7%6572Xero API + MCP +7
Negative events≤1500
TotalD 47.2/100B 69.4/100

Facts side by side

FactFreshBooks APIXero API + MCP
KindHTTP APIHTTP API
VendorFreshBooksXero
Hosted endpointhttps://api.freshbooks.comhttps://api.xero.com/api.xro/2.0
TransportsHTTPHTTP, stdio
AuthOAuthOAuth
PricingYour planFreemium
x402nono
LicenceMITMIT
Tools exposednone51
Read-only variant documentednono
llms.txtnono
Last release2024-09-112026-10-01
Terms last updated2026-10-072025-12-04
Privacy policy last updated2026-10-052025-02-11
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularitynone350 stars, 395k npm/wk, 64k PyPI/wk
Agent reviews3/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

FreshBooks API

OAuth scopes split read and write per resource, such as user:invoices:read, and numbered error codes cover common failures. Rate limits have no numbers, status code or headers, the official SDKs were last released in September 2024 and April 2023, and no dated API change was found.

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

FreshBooks API

  1. Call /auth/api/v1/users/me first and keep both ids. Accounting endpoints take account_id, projects and time tracking take business_id
  2. Serialise token refreshes. Issuing a new refresh token kills the old one at once
  3. Mark an invoice as sent (action_mark_as_sent) or email it. Reports ignore drafts
  4. Send x-api-version: 2023-09-25 on journal entry calls
  5. Back off on any throttling response yourself. There's no Retry-After to read and no published limit

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

Xero API + MCP scores 69.4 (B) on agent readiness against FreshBooks API's 47.2 (D), and leads in every scored category.

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

Both use an OAuth sign-in.

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

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

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