Head to head · Invoicing · October 2026 research run

FreeAgent API vs Invoice Ninja API

FreeAgent API scores 59.1 (C) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 2 of 7 scored categories. Invoice Ninja API leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do invoicing.

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 41
  • Transparency & trust, 74 against 63

Also in its favour

  • No incidents deducted, where Invoice Ninja API loses 6 points for them

Watch for

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

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

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

Watch for

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

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 FreeAgent API +44

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

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.

Maintenance & community Invoice Ninja 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).

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.

Schema & documentation Invoice Ninja API +16

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

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.

Transparency & trust FreeAgent API +11

FreeAgent API 74

Closed service with API terms v2.1 dated 28 February 2025, under Scots law, naming FreeAgent Central Limited, SC316774 (15). A privacy hub with a general notice, a customer DPA, a subprocessor list and a GDPR page, and API terms that bar clients from keeping data longer than the function needs. The landing page gives no retention periods (20). Dated changelog and a versioning guide, and the terms promise email notice of material changes but set no deprecation period (8). Subprocessor list published. We didn't read the locations (12).

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.

Security & auth Invoice Ninja API +9

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

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.

Payments & pricing Invoice Ninja 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.

Invoice Ninja API 53

No x402, MPP or L402 (0). Hosted plan prices are public, Pro $14 a month, Enterprise $18 to $300, Premium Business from $280 a year (10). Hosted Free (5 clients, no card) has no REST API, but self-hosting is free with every feature, which we counted at three quarters (15). The public demo at demo.invoiceninja.com takes the token TOKEN with no signup, though it's a shared demo, not your own company (10). 0 + 10 + 15 + 10 = 35. 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 APIInvoice Ninja APIEdge
Reliability16%8541FreeAgent API +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5066Invoice Ninja API +16
Agent ergonomics13%5560Invoice Ninja API +5
Security & auth14%4453Invoice Ninja API +9
Payments & pricing10%4553Invoice Ninja API +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6083Invoice Ninja API +23
Transparency & trust7%7463FreeAgent API +11
Negative events≤150-6
TotalC 59.1/100D 51.4/100

Facts side by side

FactFreeAgent APIInvoice Ninja API
KindHTTP APIHTTP API
VendorFreeAgentInvoice Ninja
Hosted endpointhttps://api.freeagent.com/v2https://invoicing.co/api/v1
TransportsHTTPHTTP
AuthOAuthAPI key
PricingYour planFreemium
x402nono
LicencenoneElastic License 2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-072026-10-18
Terms last updated2025-02-28not read yet
Privacy policy last updatedcouldn't be readnot read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone10k stars
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

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.

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

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

Questions

Which is better for AI agents, FreeAgent API or Invoice Ninja API?

FreeAgent API scores 59.1 (C) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 2 of 7 scored categories. Invoice Ninja API leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community.

Do FreeAgent API and Invoice Ninja API need an API key?

FreeAgent API uses an OAuth sign-in. Invoice Ninja API needs an API key.

Can an agent call FreeAgent API and Invoice Ninja API without installing anything?

Yes. FreeAgent API has a hosted endpoint at https://api.freeagent.com/v2 and Invoice Ninja API at https://invoicing.co/api/v1.

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