# LlamaParse API + MCP vs Reducto API + MCP

> Reducto API + MCP has a score of 63.2 (B) against LlamaParse API + MCP's 59.6 (C). Both do docs parse. The largest gap is reliability, 17 points. Category scores, facts, verdicts and agent notes side by side.

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

Reducto API + MCP has a score of 63.2 (B) against LlamaParse API + MCP's 59.6 (C). Both do docs parse. The largest gap is reliability, 17 points.

- LlamaParse API + MCP: grade C, 59.6/100, rank #262 of 452. Markdown https://www.anchorterminal.com/tools/llamaparse.md · JSON https://www.anchorterminal.com/api/v1/tools/llamaparse.json
- Reducto API + MCP: grade B, 63.2/100, rank #207 of 452. Markdown https://www.anchorterminal.com/tools/reducto.md · JSON https://www.anchorterminal.com/api/v1/tools/reducto.json

## Which one, for what

Pick LlamaParse API + MCP for security & auth (+13), payments & pricing (+10), transparency & trust (+10).

Pick Reducto API + MCP for reliability (+17), agent ergonomics (+12).

## Score by category

| Category | Weight | LlamaParse API + MCP | Reducto API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 72 | Reducto API + MCP +17 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 80 | LlamaParse API + MCP +2 |
| Agent ergonomics | 13% (16.2 this run) | 72 | 84 | Reducto API + MCP +12 |
| Security & auth | 14% (17.5 this run) | 48 | 35 | LlamaParse API + MCP +13 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | LlamaParse API + MCP +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 80 | even |
| Transparency & trust | 7% (8.8 this run) | 70 | 60 | LlamaParse API + MCP +10 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **59.6 · C** | **63.2 · B** | |

## Facts side by side

| Fact | LlamaParse API + MCP | Reducto API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | LlamaIndex | Reducto |
| Hosted endpoint | `https://api.cloud.llamaindex.ai/api/v2` | `https://platform.reducto.ai` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | none |
| Tools exposed | 26 | 9 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-08 | 2026-09-11 |
| Popularity | 4.3k stars, 125k npm/wk, 767k PyPI/wk | 342k npm/wk, 1.1M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 4/5 (2) |

## Verdicts

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

**Reducto API + MCP.** Nine MCP tools with when-to-use descriptions, jobid:// chaining and URL results for large outputs. Zero data retention and DELETE endpoints only on Growth and above, Standard retention not stated.

## Before you call either

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

### Reducto API + MCP

1. Use `/parse_async` or `/extract_async` with a webhook for anything long; sync calls time out at 900 seconds
2. Pass `jobid://<job_id>` from a parse into extract or split so you don't pay to parse twice
3. Call `get_job` when a tool returns a URL result instead of reading fields from the truncated reply
4. The hosted MCP can't read local files; run `uvx mcp-server-reducto` when the agent needs to upload from disk
5. Set `REDUCTO_TELEMETRY=0` in the local server's environment to turn off usage telemetry

## Other comparisons with LlamaParse API + MCP or Reducto API + MCP

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