Head to head · Invoicing · October 2026 research run

Invoice Ninja API vs Xero API + MCP

Xero API + MCP scores 69.4 (B) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 5 of 7 scored categories. Invoice Ninja API leads on maintenance & community. Both do invoicing.

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

Which one, for what

Invoice Ninja API D

Best for An agent that quotes, invoices, chases and records payments for a small business, or for anyone who wants the billing system on their own server.

Ahead on

  • Maintenance & community, 83 against 76

Watch for

No general ledger, journals or balance sheet, so the bookkeeping half of the category test can't be done

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 41
  • Schema & documentation, 79 against 66
  • Agent ergonomics, 75 against 60
  • Security & auth, 64 against 53
  • Transparency & trust, 72 against 63

Also in its favour

  • Runs on your own machine
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where Invoice Ninja API loses 6 points for them

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.

Reliability Xero API + MCP +27

Invoice Ninja API 41

Oh Dear status page watching invoiceninja.com and invoicing.co, with no component for the API itself; it now links an incident history page (15). The history page lists one event, invoiceninja.com down for one minute on 29 October 2026, and doesn't say how far back it reaches, so the 90-day record isn't established and the line keeps 5. The docs give no numbers. The source sets 1,000 requests a minute per IP and per token on the hosted service, 20 a minute on report exports and no limit when self-hosted, counted at half as on 1 October (8). 429 appears only as a row in the error table, with no backoff or retry guidance (3, the 1 October partial). No SLA, and the terms say Invoice Ninja "strives to ensure maximum uptime" (0). GA (10). 15 + 5 + 8 + 3 + 0 + 10 = 41.

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

Agent ergonomics Xero API + MCP +15

Invoice Ninja API 60

per_page (default 20), include for related objects and status and client filters, no field selection (15). page, per_page, sort, filter and status on index routes, plus bulk endpoints for actions across many ids (20). Laravel 422 validation errors name the field, but the docs only show the generic table (12). No idempotency keys. ?mark_sent=true and ?send_email=true are opt-in, so a plain create stays a draft (5). Official SDK in PHP only, Go from the community. Two headers on every call, X-API-TOKEN and X-Requested-With (8). 15 + 20 + 12 + 5 + 8 = 60.

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

Schema & documentation Xero API + MCP +13

Invoice Ninja API 66

OpenAPI 3 spec in the repository with 379 operations and a demo server, last edited 15 October 2026, though its info version still reads 5.12.55 while the app is at 5.13.49 (23). No llms.txt (404 on the docs host) or Markdown docs (0). Path descriptions explain the chained query parameters and actions such as mark_sent, but rarely when to use one route over another (12). Typed schemas in the components, with allowed values often given in prose ("a comma separated list of invoice status strings") rather than enums (10). curl and PHP examples on each path and a generic status-code table (11). Tagged releases, the API fixed at /api/v1, no API changelog of its own (10). 23 + 0 + 12 + 10 + 11 + 10 = 66.

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

Security & auth Xero API + MCP +11

Invoice Ninja API 53

API tokens per user, created and revoked under Settings, Account Management, Integrations, in a header and never a URL. No per-token scopes (20). No read-only token. Invoices stay drafts unless the call asks otherwise (5). Returns client and product text that other people wrote, and stored XSS advisories came through invoice line items, product notes and the terms field, with no injection guidance for API consumers (3). Activity log and an activities report export (10). SECURITY.md with a disclosure email, advisories published on GitHub, and a SOC 2 page (Security, Availability, Confidentiality and Processing Integrity, report under NDA on request) with a PCI-DSS claim. The page names neither the SOC 2 type nor the auditor. No security.txt or bug bounty (15, as brex). 20 + 5 + 3 + 10 + 15 = 53.

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

Transparency & trust Xero API + MCP +9

Invoice Ninja API 63

Source-available under the Elastic License 2.0, which is clear but isn't an OSI licence, so we scored between closed and open (20). The privacy policy on invoiceninja.com names eight vendors (OVH Cloud added) and a DPA, and now states one retention period (free accounts inactive for three months are deleted), and the terms (version 1.0.2, effective 1 February 2026) name Florida law. No full retention schedule or registered address, so 15 plus 3 (18). No deprecation policy found, only release notes (3). Self-hosted error reporting is opt-in by checkbox and disclosed. Vendors named without data locations (16). 20 + 18 + 3 + 16 = 57.

Xero API + MCP 72

Closed API with developer terms dated 4 December 2025 naming Xero Limited (NZ 1830488) and the governing law by region. MIT MCP server and SDKs (17). Developer terms forbid training or fine-tuning AI models on API data. The UK privacy notice, dated 11 February 2025, says Xero uses AI and ML on its services and keeps data while there's a business or legal need, with no periods (15). Dated deprecations with 12 to 13 months' notice, such as accounting.transactions retiring on 13 September 2027 and XPM API v3.0 on 6 May 2027 (20). Transfers to Australia, New Zealand and the United States are named, with no public subprocessor list (8).

Maintenance & community Invoice Ninja API +7

Invoice Ninja API 83

v5.13.49 on 18 October 2026 (30). 20 tagged releases on v5-stable since 6 August, from v5.13.30 to v5.13.49 (20). Pull requests merge within days on v5-stable. We couldn't see issue reply times from git (15). Official PHP SDK, v2.0.0 tagged on 2 November 2026 after v1.4.0 in January 2025. No MCP server (8). PHPUnit CI runs the test suite across PHP 8.2 to 8.5 on every push to v5-stable and v5-develop, plus Dependabot (10). 30 + 20 + 15 + 8 + 10 = 83.

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

Score by category

CategoryWeightInvoice Ninja APIXero API + MCPEdge
Reliability16%4168Xero API + MCP +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6679Xero API + MCP +13
Agent ergonomics13%6075Xero API + MCP +15
Security & auth14%5364Xero API + MCP +11
Payments & pricing10%5353even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8376Invoice Ninja API +7
Transparency & trust7%6372Xero API + MCP +9
Negative events≤15-60
TotalD 51.4/100B 69.4/100

Facts side by side

FactInvoice Ninja APIXero API + MCP
KindHTTP APIHTTP API
VendorInvoice NinjaXero
Hosted endpointhttps://invoicing.co/api/v1https://api.xero.com/api.xro/2.0
TransportsHTTPHTTP, stdio
AuthAPI keyOAuth
PricingFreemiumFreemium
x402nono
LicenceElastic License 2.0MIT
Tools exposednone51
Read-only variant documentednono
llms.txtnono
Last release2026-10-182026-10-01
Terms last updatednot read yet2025-12-04
Privacy policy last updatednot read yet2025-02-11
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity10k stars350 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

Invoice Ninja API

OpenAPI 3 spec with 379 operations and curl and PHP examples on each path, and a public demo token. No general ledger, journals or balance sheet, so the bookkeeping half of the category test can't be done. A September advisory on webhook request forgery was fixed in two weeks, but an August one on invoice terms has no established fix.

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

Invoice Ninja API

  1. Send X-Requested-With: XMLHttpRequest with X-API-TOKEN on every call
  2. Prototype against demo.invoiceninja.com with X-API-TOKEN: TOKEN before asking for real credentials
  3. Add ?mark_sent=true to the save to make an invoice live, or ?send_email=true to send it. A plain create is a draft
  4. Stay under 1,000 requests a minute per token on the hosted service and 20 a minute on report exports
  5. Record a supplier bill as an expense or purchase order. There's no bills resource

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

Xero API + MCP scores 69.4 (B) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 5 of 7 scored categories. Invoice Ninja API leads on maintenance & community.

Do Invoice Ninja API and Xero API + MCP need an API key?

Invoice Ninja API needs an API key. Xero API + MCP uses an OAuth sign-in.

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

Yes. Invoice Ninja API has a hosted endpoint at https://invoicing.co/api/v1 and Xero API + MCP at https://api.xero.com/api.xro/2.0.

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