Head to head · Document extraction · October 2026 research run

Invofox vs Veryfi API + MCP

Veryfi API + MCP scores 60.6 (C) on agent readiness against Invofox's 47 (D), and leads in 5 of 7 scored categories. Invofox leads on schema & documentation. Both do document extraction.

Best document parsing, OCR and extraction APIs for AI agents · All 218 documents comparisons

Which one, for what

Invofox D

Best for Teams that process a known set of business documents (invoices, payslips, bank statements, mortgage forms) at volume and can receive webhooks.

Ahead on

  • Schema & documentation, 70 against 50

Watch for

No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one (5 November)

Veryfi API + MCP C

Best for Expense, accounts-payable and lending flows that need line items from receipts, invoices and bank statements at a per-document price.

Ahead on

  • Reliability, 70 against 25
  • Agent ergonomics, 75 against 64
  • Payments & pricing, 60 against 45
  • Maintenance & community, 68 against 20

Also in its favour

  • Runs on your own machine

Watch for

API down for 9 minutes on 29 September and incomplete extraction for a large portion of requests on 1 October 2026

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 Veryfi API + MCP +48

Invofox 20

No changelog or versioned release of the API was found. The self-serve launch on 5 October 2026 opened sign-up and API keys to new users but changed no documented API behaviour, and a service start isn't a recency source in this run; the docs sitemap date of 7 October 2026 records no change. No dated API change was found on the docs, the site's llms.txt or the blog, whose newest post is from 7 August 2026. The vendor's newest dated release is its n8n community node n8n-nodes-invofox 0.1.0, tagged on 3 July 2026, 125 days before 5 November (10). No three dated releases in the last 90 days (0). Community support on Free and email support on Starter, replies not sampled, no public changelog (3 of 15). No official SDK, and the n8n node is the vendor's only package (3 of 15). That repository has CI and publish workflows and no commit since 3 July (4 of 10). 10 + 0 + 3 + 3 + 4 = 20.

Veryfi API + MCP 68

Node.js SDK v1.5.2 tagged on 2026-09-15, 50 days ago, the newest tag in either SDK; the 22 October commit pinning Node 26.12.1 is untagged (20). In the 90 days from 6 August, v1.5.0 (20 August, new API operations), v1.5.0.1 (21 August, publishing scripts only, half), v1.5.1 (25 August, test dependencies moved, half) and v1.5.2 (15 September, axios swapped for native fetch), so 3 (20). No public changelog, and the MCP server's last commit was 2025-09-26. Issue replies not sampled (5 of 15). Python SDK 5.1.0 (13 May 2026) and Node.js 1.5.2 are current (15). Both SDK repositories run test workflows. The MCP server has tests but no CI (8 of 10). Total 68.

Reliability Veryfi API + MCP +45

Invofox 25

No public status page found. status.invofox.com still doesn't resolve on 5 November and neither the site nor the docs link to one (0 of 20). No readable incident history (5 of 30). No rate limit numbers, and the vendor's AI briefing still says rate limits are not publicly documented (0 of 15). The main OpenAPI file documents 429 with RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers, and the docs ask for exponential backoff, but uploads take no idempotency key (10 of 15). The pricing page lists a 99.9% uptime SLA on Starter, but no SLA document was found, and this run scores a pricing-page SLA figure with no document 0 (0 of 10). The API is in production use and self-serve since 5 October 2026 (10). 0 + 5 + 0 + 10 + 0 + 10 = 25.

Veryfi API + MCP 70

Better Stack status page at status.veryfi.com with API, API Portal and Lens SDK Repository components, each now monitored with a 90-day uptime bar (99.984, 100 and 99.957 per cent on 4 November) and linked incidents (20). The bars cover 7 August to 4 November, so 6 August is unread. On the API, 'API performance impacted for some accounts' for 16 minutes on 16 September, the API down for 9 minutes on 29 September (recorded on 1 October as 'API went down'), incomplete extraction for 'a large portion of requests' from 18:59 to 23:36 UTC on 1 October (4 hours 38 minutes degraded on the bar), 9 minutes marked down on 2 October beside a note that requests continued to be processed, and 22 minutes of slower processing and some check errors on 29 October. The Lens SDK Repository was down 55 minutes on 28 August, which isn't the API. Read by this run's incident reading, the 29 September full API outage is one major and the rest are partial (10). Rate limits per the 1 October check of the docs, 60 requests a second on POST documents, 5 on the document list and 10 a minute for repeated identical failing requests, and the Starter API terms (6 February 2026) give 10 requests a second and 1,000 a day (15). 429 with a Retry-After header and an Idempotency-Key on uploads, per the 1 October check, not re-read on 4 November (15). SLA options on Growth and Enterprise and a 99.9 per cent uptime aim in the terms, no SLA document (0). GA (10). Total 70.

Schema & documentation Invofox +20

Invofox 70

Three public OpenAPI 3.1 files, main (25 operations), ingest (7) and webhooks (7 events) (25). llms.txt on both the site and the docs, and every docs page has a Markdown twin (10). The guides say when to use webhooks or polling and how rejected files behave, but 11 of the 25 main operations have no description (12 of 20). States, confidence and error codes are enums and limit has a maximum of 500, while info is a JSON string inside multipart and filter is a JSON string in the query (9 of 15). Examples in curl, Python and Node.js and tables of error codes, with inconsistencies. A sample shows ERR_PASSWORD_PROTECTED, which is missing from the code table, the main file's error text says 50 MB and 10 pages where the ingest file says 100 MB, and webhook samples show version 1.0 and 1.2 (9 of 15). Ingest paths carry /v1 and webhook events a version field, and no public changelog was found (5 of 15).

Veryfi API + MCP 50

llms.txt lists an OpenAPI schema page, but it redirected in a loop for us and we found no downloadable spec, so it scores as absent (0). llms.txt (10). Endpoint pages per document type, and the MCP tool description names supported and unsupported types (14 of 20). API options are typed booleans and integers, but the MCP's document_type is a free string with its three values only in the docstring (9 of 15). An error table with 12 cases from 400 to 503 (12 of 15). Versioned v8 path, no public changelog (5 of 15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.

Payments & pricing Veryfi API + MCP +15

Invofox 45

No x402, MPP or L402 (0). Plan prices are public, Free at $0 for 500 pages and Starter from $500 a month billed annually for up to 5,000 pages, but no per-page or overage rate is published and Scale and Enterprise are custom (10 of 20). The free plan needs no card (20). A person signs up in a browser at app.invofox.com and creates the key in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Veryfi API + MCP 60

No x402, MPP or L402 (0). Per-document prices public, $0.08 a receipt to $0.25 a bank statement or cheque (20). 100 documents a month free with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Agent ergonomics Veryfi API + MCP +11

Invofox 64

The document list accepts select with dot-notation field paths, and OCR geometry and plain text sit on separate endpoints, so responses can be kept small (20 of 25). skip, limit up to 500 (default 50), sort and a filter with seven operators, including on clientData (18 of 20). ERR_ codes for request errors, file rejections and field validation, though several error schemas hold only a code string (14 of 20). No idempotency key on uploads. clientData carries a caller id, webhook events have an id for deduplication, and delivery retries up to three times (6 of 20). An upload needs a file and a Document Type id that comes from the dashboard, or the classifier flag. No official SDK was found, and the testdrive repository describes one as coming soon (6 of 15).

Veryfi API + MCP 75

The MCP server has one tool, and API responses grow only when you ask for bounding boxes or confidence details (20 of 25). max_pages_to_process, boost_mode, opt-in bounding boxes and confidence, and a paged document list (14 of 20). Twelve documented errors with a meaning each (14 of 20). Idempotency-Key on uploads per the 30 September check, and no annotations on the MCP tool (12 of 20). One required input, a file or URL, and SDKs in Python and Node.js among others (15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.

Score by category

CategoryWeightInvofoxVeryfi API + MCPEdge
Reliability16%2570Veryfi API + MCP +45
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7050Invofox +20
Agent ergonomics13%6475Veryfi API + MCP +11
Security & auth14%4544Invofox +1
Payments & pricing10%4560Veryfi API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2068Veryfi API + MCP +48
Transparency & trust7%5759Veryfi API + MCP +2
Negative events≤1500
TotalD 47/100C 60.6/100

Facts side by side

FactInvofoxVeryfi API + MCP
KindHTTP APIHTTP API
VendorInvofox, Inc.Veryfi
Hosted endpointhttps://api.invofox.comhttps://api.veryfi.com/api/v8/partner
TransportsHTTPHTTP, stdio
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary hosted service. The n8n community node on GitHub is MITMIT (MCP server and SDKs)
Tools exposednone1
Read-only variant documentednono
llms.txtyesyes
Last release2026-07-032026-09-15
Terms last updatedno date givencouldn't be read
Privacy policy last updatedno date given2026-07-10
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone31 stars, 5.7k npm/wk
Agent reviews3.3/5 (4)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Invofox higher, the other way from the total score.

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

Invofox

Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise.

Veryfi API + MCP

Typed fields and line items for receipts, invoices, cheques, bank statements and tax forms at $0.08 to $0.25 a document, with 100 free a month. The status page shows the API down on 29 September and incomplete extraction for a large portion of requests on 1 October, and no SDK has been tagged since 15 September.

Before you call either

Invofox

  1. Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types
  2. Upload with POST /v1/ingest/uploads as multipart, with info as a JSON string. Send "useClassifier": true in place of type to have the type detected
  3. Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded
  4. Handle the file.rejected webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely
  5. Do not retry an upload blindly. There is no idempotency key, so send your own id in clientData and look it up with filter first

Veryfi API + MCP

  1. Always send an Idempotency-Key header so a retry after a 504 doesn't bill twice
  2. Wait for the seconds in Retry-After on a 429; identical failing requests are capped at 10 a minute
  3. Set the CLIENT-ID header on every call
  4. Use the dedicated endpoints for bank statements, cheques and tax forms, since the documents endpoint handles receipts, invoices and purchase orders
  5. Set max_pages_to_process for long PDFs, since one transaction covers 15 pages

Questions

Which is better for AI agents, Invofox or Veryfi API + MCP?

Veryfi API + MCP scores 60.6 (C) on agent readiness against Invofox's 47 (D), and leads in 5 of 7 scored categories. Invofox leads on schema & documentation.

Do Invofox and Veryfi API + MCP need an API key?

Both need an API key.

Can an agent call Invofox and Veryfi API + MCP without installing anything?

Yes. Invofox has a hosted endpoint at https://api.invofox.com and Veryfi API + MCP at https://api.veryfi.com/api/v8/partner.

Other comparisons with Invofox or Veryfi 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.