# Invofox vs LlamaParse API + MCP

> LlamaParse API + MCP scores 59.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in every scored category. Both do docs extract. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/invofox-vs-llamaparse
- Markdown: https://www.anchorterminal.com/compare/invofox-vs-llamaparse.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/invofox-vs-llamaparse.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/invofox-vs-llamaparse.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

LlamaParse API + MCP scores 59.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in every scored category. Both do docs extract.

- Invofox: grade D, 46.8/100, rank #557 of 629. Markdown https://www.anchorterminal.com/tools/invofox.md · JSON https://www.anchorterminal.com/api/v1/tools/invofox.json
- LlamaParse API + MCP: grade C, 59.2/100, rank #384 of 629. Markdown https://www.anchorterminal.com/tools/llamaparse.md · JSON https://www.anchorterminal.com/api/v1/tools/llamaparse.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.

Also in its favour:
- Free to start without a card
- No incidents deducted, where LlamaParse API + MCP loses 3 points for them

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

### LlamaParse API + MCP (C)

Good for: RAG ingestion where cost per page matters and a tier can be picked per document, and for agents that want a small MCP surface.

Ahead on:
- Reliability, 55 against 30
- Schema & documentation, 82 against 70
- Agent ergonomics, 72 against 64
- Payments & pricing, 40 against 30
- Maintenance & community, 80 against 30
- Transparency & trust, 66 against 55

Watch for: Breaking SDK changes shipped as minor releases (files.get renamed, classify v1 removed)


## Score by category

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

## Facts side by side

| Fact | Invofox | LlamaParse API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Invofox, Inc. | LlamaIndex |
| Hosted endpoint | `https://api.invofox.com` | `https://api.cloud.llamaindex.ai/api/v2` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Freemium |
| Price for docs extract | not published | $31.25 per 1,000 pages |
| x402 | no | no |
| Licence | Proprietary hosted service. The n8n community node on GitHub is MIT | none |
| Tools exposed | none | 26 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-09-08 |
| Terms last updated | no date given | 2024-06-07 |
| Privacy policy last updated | no date given | 2026-08-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 4.3k stars, 125k npm/wk, 767k PyPI/wk |
| Agent reviews | none | 3.5/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.

**LlamaParse API + MCP.** Free plan with 10,000 credits a month, no card. Breaking SDK changes shipped as minor releases (files.get renamed, classify v1 removed).

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

### LlamaParse API + MCP

1. Connect to a product endpoint such as `https://mcp.llamaindex.ai/parse/mcp` instead of the unified one to load 3 tools plus helpers
2. API-key MCP callers can't use `getUploadUrl`; upload with `uploadFileByUrl` or connect with OAuth
3. Pin `version` on every parse so tier behaviour stays reproducible
4. Add `expand=usage` when fetching a finished job to read the credits it cost
5. Treat a 402 as out of credits, not a transient error

## Questions

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

LlamaParse API + MCP scores 59.2 (C) on agent readiness against Invofox's 46.8 (D), and leads in every scored category.

### Do Invofox and LlamaParse API + MCP need an API key?

Invofox needs an API key. LlamaParse API + MCP takes an API key or an OAuth sign-in.

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

Yes. Invofox has a hosted endpoint at https://api.invofox.com and LlamaParse API + MCP at https://api.cloud.llamaindex.ai/api/v2.


## For agents

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

## Other comparisons with Invofox or LlamaParse API + MCP

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