Extend API + MCP vs Mindee API

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.

Mindee API

Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored. Every call needs a model_id created in the web platform first.

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

Mindee API

1. Create the model in the Mindee app and store its model_id; the API can't create one for you
2. Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
3. Send Authorization: $MINDEE_API_KEY with no Bearer prefix
4. Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
5. Keep schemas to 25 fields or fewer, the documented recommendation