Head to head · Accounting ledgers · October 2026 research run

FreeAgent API vs Merge Accounting API

Merge Accounting API scores 72.4 (BB) 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 75

Watch for

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

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

  • Schema & documentation, 86 against 50
  • Agent ergonomics, 72 against 55
  • Security & auth, 67 against 44
  • Payments & pricing, 53 against 45
  • Maintenance & community, 83 against 60

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

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

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 Merge Accounting API +36

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

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

Security & auth Merge Accounting API +23

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

Merge Accounting API 67

Production and test API keys plus an X-Account-Token per linked account, so one token reaches one customer. Merge holds the platform OAuth tokens, and the agent never sees them (22). Scopes to limit common models and fields, field-level on Professional and above. No read-only key documented (12). Ledger text from third parties comes back unfiltered with no injection guidance, and the per-account token limits what an injected prompt can reach (5). Request logs kept 3 days on Launch, 30 on Professional and 90 or more on Enterprise (12). SOC 2 Type 2, ISO 27001:2022, a penetration test report and a responsible-disclosure programme on trust.merge.dev. security.txt 404, no bug bounty found (16).

Maintenance & community Merge Accounting API +23

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

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

Agent ergonomics Merge Accounting API +17

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

Merge Accounting API 72

expand, include_remote_data and remote_fields are opt-in, page_size and modified_after trim reads, no field selection (18). Cursor pagination with created_after, modified_after and type filters on lists (20). Write responses carry warnings and errors from the platform, with logs in debug mode (14). No idempotency keys found for writes, and the SDKs retry 409 by default, so a timed-out POST needs a check before a retry (5). The meta endpoint says which fields a platform needs, and official SDKs cover Python, Node and others (15).

Reliability FreeAgent API +10

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

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

Payments & pricing Merge Accounting API +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.

Merge Accounting API 53

No x402, MPP or L402 (0). Launch is $650 a month for 10 production linked accounts plus $65 for each one after, a published marginal price per account. Professional and Enterprise are on contract (15). The first 3 production linked accounts are free with no card (20). Browser signup and a Merge Link flow per customer (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 APIMerge Accounting APIEdge
Reliability16%8575FreeAgent API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5086Merge Accounting API +36
Agent ergonomics13%5572Merge Accounting API +17
Security & auth14%4467Merge Accounting API +23
Payments & pricing10%4553Merge Accounting API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6083Merge Accounting API +23
Transparency & trust7%7470FreeAgent API +4
Negative events≤1500
TotalC 59.1/100BB 72.4/100

Facts side by side

FactFreeAgent APIMerge Accounting API
KindHTTP APIHTTP API
VendorFreeAgentMerge
Hosted endpointhttps://api.freeagent.com/v2https://api.merge.dev/api/accounting/v1
TransportsHTTPHTTP
AuthOAuthAPI key
PricingYour planFreemium
x402nono
LicencenoneMIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-072026-10-05
Terms last updated2025-02-28no date given
Privacy policy last updatedcouldn't be read2026-08-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone15 stars, 201k npm/wk, 235k PyPI/wk
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Merge Accounting API 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.

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.

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

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

Questions

Which is better for AI agents, FreeAgent API or Merge Accounting API?

Merge Accounting API scores 72.4 (BB) 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 Merge Accounting API need an API key?

FreeAgent API uses an OAuth sign-in. Merge Accounting API needs an API key.

Can an agent call FreeAgent API and Merge Accounting API without installing anything?

Yes. FreeAgent API has a hosted endpoint at https://api.freeagent.com/v2 and Merge Accounting API at https://api.merge.dev/api/accounting/v1.

Other comparisons with FreeAgent API or Merge Accounting API

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.