# Invofox vs Veryfi API + MCP

> Veryfi API + MCP scores 55.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in 5 of 7 scored categories. Invofox leads on schema & documentation and security & auth. Both do docs extract. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/invofox-vs-veryfi
- Markdown: https://www.anchorterminal.com/compare/invofox-vs-veryfi.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/invofox-vs-veryfi.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/invofox-vs-veryfi.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Veryfi API + MCP scores 55.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in 5 of 7 scored categories. Invofox leads on schema & documentation and security & auth. Both do docs extract.

- Invofox: grade D, 46.8/100, rank #641 of 722. Markdown https://www.anchorterminal.com/tools/invofox.md · JSON https://www.anchorterminal.com/api/v1/tools/invofox.json
- Veryfi API + MCP: grade C, 55.2/100, rank #514 of 722. Markdown https://www.anchorterminal.com/tools/veryfi.md · JSON https://www.anchorterminal.com/api/v1/tools/veryfi.json

## Which one, for what

### Invofox (D)

Good 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
- Security & auth, 45 against 40

Watch for: No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one

### Veryfi API + MCP (C)

Good 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, 55 against 30
- Agent ergonomics, 75 against 64
- Payments & pricing, 40 against 30
- Maintenance & community, 78 against 30

Also in its favour:
- Runs on your own machine

Watch for: API outage on 29 September and degraded, incomplete extraction on 1 October


## Score by category

| Category | Weight | Invofox | Veryfi API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 30 | 55 | Veryfi API + MCP +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 50 | Invofox +20 |
| Agent ergonomics | 13% (16.2 this run) | 64 | 75 | Veryfi API + MCP +11 |
| Security & auth | 14% (17.5 this run) | 45 | 40 | Invofox +5 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Veryfi API + MCP +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 30 | 78 | Veryfi API + MCP +48 |
| Transparency & trust | 7% (8.8 this run) | 55 | 58 | Veryfi API + MCP +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **46.8 · D** | **55.2 · C** | |

## Facts side by side

| Fact | Invofox | Veryfi API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Invofox, Inc. | Veryfi |
| Hosted endpoint | `https://api.invofox.com` | `https://api.veryfi.com/api/v8/partner` |
| Transports | HTTP | HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service. The n8n community node on GitHub is MIT | MIT (MCP server and SDKs) |
| Tools exposed | none | 1 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-09-15 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | 2026-07-10 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 31 stars, 5.7k npm/wk, 17k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## 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. API outage on 29 September and degraded, incomplete extraction on 1 October.

## 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 55.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in 5 of 7 scored categories. Invofox leads on schema & documentation and security & auth.

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/invofox-vs-veryfi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/invofox-vs-veryfi.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "invofox", "b": "veryfi"}`. From a terminal: `anchor compare invofox veryfi`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/invofox.json and https://www.anchorterminal.com/api/v1/tools/veryfi.json

## Other comparisons with Invofox or Veryfi API + MCP

- [Adobe PDF Services / PDF Extract API vs Veryfi API + MCP](https://www.anchorterminal.com/compare/adobe-pdf-extract-vs-veryfi.md)
- [Extend API + MCP vs Veryfi API + MCP](https://www.anchorterminal.com/compare/extend-vs-veryfi.md)
- [Invofox vs OpenDocRouter](https://www.anchorterminal.com/compare/invofox-vs-opendocrouter.md)
- [LlamaParse API + MCP vs Veryfi API + MCP](https://www.anchorterminal.com/compare/llamaparse-vs-veryfi.md)
- [Mindee API vs Veryfi API + MCP](https://www.anchorterminal.com/compare/mindee-vs-veryfi.md)
- [Mistral OCR API vs Veryfi API + MCP](https://www.anchorterminal.com/compare/mistral-ocr-vs-veryfi.md)
- [Nanonets API + MCP vs Veryfi API + MCP](https://www.anchorterminal.com/compare/nanonets-vs-veryfi.md)
- [OpenDocRouter vs Veryfi API + MCP](https://www.anchorterminal.com/compare/opendocrouter-vs-veryfi.md)
- [Reducto API + MCP vs Veryfi API + MCP](https://www.anchorterminal.com/compare/reducto-vs-veryfi.md)
- [Unstructured API + MCP vs Veryfi API + MCP](https://www.anchorterminal.com/compare/unstructured-vs-veryfi.md)
- [Adobe PDF Services / PDF Extract API vs Invofox](https://www.anchorterminal.com/compare/adobe-pdf-extract-vs-invofox.md)
- [Extend API + MCP vs Invofox](https://www.anchorterminal.com/compare/extend-vs-invofox.md)
- [Invofox vs LlamaParse API + MCP](https://www.anchorterminal.com/compare/invofox-vs-llamaparse.md)
- [Invofox vs Mindee API](https://www.anchorterminal.com/compare/invofox-vs-mindee.md)
- [Invofox vs Mistral OCR API](https://www.anchorterminal.com/compare/invofox-vs-mistral-ocr.md)
- [Invofox vs Nanonets API + MCP](https://www.anchorterminal.com/compare/invofox-vs-nanonets.md)
- [Invofox vs Reducto API + MCP](https://www.anchorterminal.com/compare/invofox-vs-reducto.md)
- [Invofox vs Unstructured API + MCP](https://www.anchorterminal.com/compare/invofox-vs-unstructured.md)