LlamaParse API + MCP vs Nanonets API + MCP

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

Nanonets API + MCP

Extraction API returns Markdown, CSV or JSON, with named fields or a JSON schema. No public changelog and no dated release in the last 90 days.

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

Nanonets API + MCP

1. Use the extraction API at extraction-api.nanonets.com, not app.nanonets.com, unless you already have a trained model
2. Pass a JSON schema in json_options when downstream code needs fixed field names
3. Use the async extract endpoints for long documents and poll /api/v1/extract/results/{record_id}
4. On a 429, wait 30 seconds and double the delay each retry
5. Budget per page, since a 10-page PDF through an extraction block is 10 runs