Extend API + MCP vs Nanonets API + MCP

Extend API + MCP

Hosted MCP with OAuth scoped to workspaces and to test or production, and a tools filter with nine groups. Parse is billed on top of Extract, Split and Classify, so Performance Extract costs 5 credits a page.

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.

Extend API + MCP

1. Connect with https://mcp.extend.ai/mcp?tools=parse,extract,files to keep the schema small
2. Every MCP call names a workspace and TEST or PRODUCTION; start in TEST
3. Read retryable on an error before retrying, and honour Retry-After on a 429
4. Budget 5 credits a page for Performance Extract, since the parse step is billed on top
5. Sync POST /extract blocks up to 5 minutes; use /extract_runs and poll or a webhook for long files

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