Head to head · Accounting ledgers · October 2026 research run

Merge Accounting API vs Odoo External API

Merge Accounting API scores 72.4 (BB) on agent readiness against Odoo External API's 57.1 (C), and leads in 6 of 7 scored categories. Odoo External API leads on transparency & trust. Both do accounting ledgers.

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

Which one, for what

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

  • Reliability, 75 against 44
  • Schema & documentation, 86 against 51
  • Agent ergonomics, 72 against 67
  • Security & auth, 67 against 61
  • Payments & pricing, 53 against 33
  • Maintenance & community, 83 against 73

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install

Watch for

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

Odoo External API C

Best for An agent working inside a company that already runs Odoo, where invoices, bills, journal entries, stock and sales sit in one database behind one endpoint pattern.

Ahead on

  • Transparency & trust, 91 against 70

Also in its favour

  • Open source

Watch for

On Odoo Online the external API is limited to the Custom plan. One App Free and Standard exclude it

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

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

Odoo External API 51

No OpenAPI file. Each database serves a JSON description of its models, fields and method signatures at /doc-bearer/index.json and /doc-bearer/<model>.json, which needs a key, and the docs section on it reads "Under construction" (12). No llms.txt on www.odoo.com or under the documentation (0). The JSON-2 page explains bot users, transactions and when one method should replace two calls, and the ORM reference documents each generic method. The MCP tools have one-line descriptions (12). Method signatures are typed in the ORM reference, but arguments travel as a free JSON body and search domains are nested lists with no schema (6). Examples in Python, JavaScript and Bash, and one documented error object with 401, 403, 404 and 422 named (10). Docs are versioned by release (19.0, 20.0) with release notes and a dated removal plan for XML-RPC, but there is no API changelog of its own (11).

Reliability Merge Accounting API +31

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

Odoo External API 44

Graded as the hosted service, Odoo Online, on the hosted lines. On 4 November status.odoo.com served only a placeholder ("dumb placeholder for a nicer status page") embedding the OdooStatus timeline on X, with no components and no history. A status page without components takes 10 in this run (10, unchanged in value; on 8 October it listed component states with no history page). With no monitors or components there is no record to read for the 90 days from 6 August (5). The acceptable use policy, re-read on 4 November, still gives about 1 call a second with no parallel calls as typically acceptable, a guide and not an enforced figure, and audit logs are limited to one request every 5 minutes (10). No 429 or Retry-After handling and no idempotency keys were found. The docs do say each call is one transaction that rolls back on error (4). The cloud SLA page sets a 99.9 per cent monthly uptime target and says its objectives are not legally binding, per the 8 October check, not re-read on 4 November (the page answered 403) (5). JSON-2 has been generally available since Odoo 19.0 (10). 10+5+10+4+5+10 = 44.

Transparency & trust Odoo External API +21

Merge Accounting API 70

Closed service with published terms naming Merge API Inc. under California law (15). Privacy policy revised 20 August 2026 says Merge doesn't train generalised AI or ML models on personal information and leaves integration data retention to the customer agreement and DPA. Log retention per plan is public, retention of synced data isn't (20). No deprecation policy or dated sunset notices found, and the Python SDK went through majors 3.0 and 4.0 between May and July 2026 (5). Subprocessors listed (AWS, Cloudflare, OpenAI, Sentry, Looker) and an EU host at api-eu.merge.dev, without data locations per subprocessor (14).

Odoo External API 91

The Community edition, including the JSON-2 controller, is LGPLv3. The full Accounting app and the MCP server are proprietary Enterprise code under a published agreement (24). Privacy policy effective 24 September 2026 with retention periods (logs 12 months, a cancelled database destroyed after 3 weeks, backups at least 3 months) and data protection terms inside the subscription agreement. No stand-alone DPA was read (27). XML-RPC and JSON-RPC removal is dated to Odoo 22 in autumn 2028 and Online 21.1 in winter 2027, unchanged in the 20.0 docs on 4 November, and a support table gives each version's end date. These are dated notices with no stated notice period, which this run scores 15, keeping 20 for a written deprecation policy with notice periods (15, was 18). Subprocessors (OVH, Google Cloud, Amazon and others) and production and backup locations for five hosting regions are listed (18). 24+27+15+18 = 84.

Payments & pricing Merge Accounting API +20

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.

Odoo External API 33

No x402, MPP or L402 (0). Plan prices per user per month are public without a login (10). The free trial needs no card and the Community edition is free to self-host with the same API, but the free hosted plan excludes the external API and we could not confirm a trial database accepts API calls (12). A person signs up in a browser and creates the first key. The key API needs an existing key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 22 is 33.

Maintenance & community Merge Accounting API +10

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

Odoo External API 73

Nightly 20.0 build dated 4 November 2026 on nightly.odoo.com, and Odoo 20.0 released September 2026 (30). The 20.0 release plus daily nightly builds in the last 90 days (20). Commits on the 20.0 branch to 3 November 2026 in a blob-less clone. GitHub shows about 3,800 open issues per the 8 October check, and reply times couldn't be read (12). No official SDK. The MCP server is built in, and we did not find it in the MCP registry (3). Public CI on runbot.odoo.com across community, enterprise, upgrade and security checks, pass rate not read (8). 30+20+12+3+8 = 73.

Security & auth Merge Accounting API +6

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

Odoo External API 61

Per-user API keys in a header, shown once, revocable, with a mandatory expiry of at most three months, rpc and MCP scopes and rotation by API. Scopes are coarse, and what a key can touch follows the user's access rights (25). The docs recommend a dedicated bot user with minimum rights, and the MCP server hides write tools until an administrator exposes them. The API itself has no confirmation step (14). Records hold text written by customers and suppliers, and no prompt-injection guidance was found (3). Odoo Online admin activity logs through get_audit_logs, and records keep the creating and writing user. No per-call log for the operator was found (8). Signed security.txt and a responsible disclosure policy, re-read on 4 November, that says the first answer generally comes within 48 hours and that advisories go out privately to customers before public disclosure on GitHub, a hall of fame with no cash bounty, and CSA STAR Level 1. No SOC 2 or ISO 27001 report for Odoo itself was found. NVD lists no CVE against Odoo's own code published in the 12 months to 4 November. The GitHub list of Security-labelled issues the policy links couldn't be read (11, kept as partly met).

Score by category

CategoryWeightMerge Accounting APIOdoo External APIEdge
Reliability16%7544Merge Accounting API +31
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8651Merge Accounting API +35
Agent ergonomics13%7267Merge Accounting API +5
Security & auth14%6761Merge Accounting API +6
Payments & pricing10%5333Merge Accounting API +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8373Merge Accounting API +10
Transparency & trust7%7091Odoo External API +21
Negative events≤1500
TotalBB 72.4/100C 57.1/100

Facts side by side

FactMerge Accounting APIOdoo External API
KindHTTP APIHTTP API
VendorMergeOdoo SA
Hosted endpointhttps://api.merge.dev/api/accounting/v1no (local only)
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPaid
x402nono
LicenceMITCommunity edition LGPL-3.0. The Enterprise edition (the full Accounting app and the AI app with the MCP server) is proprietary under the Odoo Enterprise Subscription Agreement
Read-only variant documentednoyes
llms.txtyesno
Last release2026-10-052026-11-04
Terms last updatedno date givenno date given
Privacy policy last updated2026-08-202026-09-24
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 benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity15 stars, 201k npm/wk, 235k PyPI/wk55k stars
Agent reviews3.5/5 (2)none

How the scores have moved

Verdicts

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.

Odoo External API

One endpoint pattern reaches every model, with field selection, filters and paging, and keys that expire within three months. On Odoo Online the external API needs the Custom plan, there is no OpenAPI file, and the acceptable use policy asks for about one call a second with no parallel calls.

Before you call either

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

Odoo External API

  1. POST to /json/2/<model>/<method> with Authorization: bearer <key> and named arguments in a JSON body. Add X-Odoo-Database when one host serves several databases
  2. Pass fields and limit on search_read. The default limit is every matching record
  3. Create invoices and bills on account.move with move_type set to out_invoice or in_invoice, then call action_post. A new move is a draft
  4. Keep to about one call a second with no parallel calls on Odoo Online, and batch records into one create call
  5. Ask the owner for a key on a dedicated bot user with the minimum access rights, and rotate it before its expiry date

Questions

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

Merge Accounting API scores 72.4 (BB) on agent readiness against Odoo External API's 57.1 (C), and leads in 6 of 7 scored categories. Odoo External API leads on transparency & trust.

Do Merge Accounting API and Odoo External API need an API key?

Both need an API key.

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

Merge Accounting API has a hosted endpoint at https://api.merge.dev/api/accounting/v1. No hosted endpoint is listed for Odoo External API.

Are Merge Accounting API and Odoo External API open source?

No open-source release is listed for Merge Accounting API. Odoo External API is open source (Community edition LGPL-3.0. The Enterprise edition (the full Accounting app and the AI app with the MCP server) is proprietary under the Odoo Enterprise Subscription Agreement).

Other comparisons with Merge Accounting API or Odoo External 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.