Head to head · OCR · October 2026 research run

Extend API + MCP vs Veryfi API + MCP

Extend API + MCP scores 67.4 (B) on agent readiness against Veryfi API + MCP's 60.6 (C), and leads in 5 of 7 scored categories. Veryfi API + MCP leads on agent ergonomics and payments & pricing. Both do ocr.

Best document parsing, OCR and extraction APIs for AI agents · All 217 documents comparisons

Which one, for what

Extend API + MCP B

Best for Teams building production extraction with evaluation sets and versioned processors, and for agents that need to build or tune extractors as well as run them.

Ahead on

  • Reliability, 77 against 70
  • Schema & documentation, 87 against 50
  • Maintenance & community, 82 against 68
  • Transparency & trust, 70 against 59

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

Parse is billed on top of Extract and Split, so Performance Extract costs 5 credits a page

Veryfi API + MCP C

Best for Expense, accounts-payable and lending flows that need line items from receipts, invoices and bank statements at a per-document price.

Ahead on

  • Agent ergonomics, 75 against 68
  • Payments & pricing, 60 against 45

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

API down for 9 minutes on 29 September and incomplete extraction for a large portion of requests on 1 October 2026

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Extend API + MCP +37

Extend API + MCP 87

OpenAPI 3.1.0 at docs.extend.ai/openapi/api-reference.json, 76 paths and 117 operations on 2 November (25). llms.txt with a Markdown twin of every page (10). The MCP page now lists all 86 tools by group with a one-line purpose each; the tool definitions themselves still need an OAuth session. The API guides say what each processor is for and when to use the async endpoints (12 of 20). Typed request bodies in the spec, depth not re-checked (11 of 15). Error format with code, message, retryable, requestId and docUrl, seven general codes and domain codes on other pages (14 of 15). Dated API versions in the x-extend-api-version header, six of them back to 2024-02-01, plus a changelog of 42 entries with dated pages (15).

Veryfi API + MCP 50

llms.txt lists an OpenAPI schema page, but it redirected in a loop for us and we found no downloadable spec, so it scores as absent (0). llms.txt (10). Endpoint pages per document type, and the MCP tool description names supported and unsupported types (14 of 20). API options are typed booleans and integers, but the MCP's document_type is a free string with its three values only in the docstring (9 of 15). An error table with 12 cases from 400 to 503 (12 of 15). Versioned v8 path, no public changelog (5 of 15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.

Payments & pricing Veryfi API + MCP +15

Extend API + MCP 45

No x402, MPP or L402 (0). Credit prices and credits per page are published without a login, $0.01 a credit on pay as you go (20). Pay as you go starts with 10,000 free credits, and neither the pricing page nor the credits page says whether a card is needed (10 of 20, our call until that's confirmed). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Veryfi API + MCP 60

No x402, MPP or L402 (0). Per-document prices public, $0.08 a receipt to $0.25 a bank statement or cheque (20). 100 documents a month free with no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Extend API + MCP +14

Extend API + MCP 82

Python SDK v1.20.0, TypeScript v2.4.0, Java v1.21.0 and Go v0.8.0 on 22 October 2026, 11 days ago (30). Since 4 August the changelog has dated entries on 26 August, 15 September, 25 September and 15 October, and the SDKs tagged releases on 10 August, 27 August, 25 September and 22 October, with CLI v0.7.0 and v0.8.0 on 26 and 27 August (20). Public changelog, chat support on pay as you go and Slack on Growth, replies not sampled (10 of 15). Current official SDKs in four languages (15). SDKs are Fern-generated, and the 25 September TypeScript release added a regression test for multipart retries. CI not checked (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.

Veryfi API + MCP 68

Node.js SDK v1.5.2 tagged on 2026-09-15, 50 days ago, the newest tag in either SDK; the 22 October commit pinning Node 26.12.1 is untagged (20). In the 90 days from 6 August, v1.5.0 (20 August, new API operations), v1.5.0.1 (21 August, publishing scripts only, half), v1.5.1 (25 August, test dependencies moved, half) and v1.5.2 (15 September, axios swapped for native fetch), so 3 (20). No public changelog, and the MCP server's last commit was 2025-09-26. Issue replies not sampled (5 of 15). Python SDK 5.1.0 (13 May 2026) and Node.js 1.5.2 are current (15). Both SDK repositories run test workflows. The MCP server has tests but no CI (8 of 10). Total 68.

Transparency & trust Extend API + MCP +11

Extend API + MCP 70

Closed service, and the terms link is the website terms of use (15). Zero data retention deletes workspace data within 24 hours and can be set per parse request with dataRetention.mode, on request for all plans. AI subprocessors run under zero-retention, no-training terms. Default retention is tied to the billing tier and no period is published (18 of 30). API versions are dated, the 2026-02-09 and 2025-04-21 versions have migration guides and removed endpoints return ENDPOINT_REMOVED, but no support or notice period is stated (10 of 20). Data locations are now stated first-hand in the docs (us1 and us2 in the US, eu1 in Frankfurt on AWS eu-central-1, with telemetry vendors possibly outside the EU), but no subprocessor list was found (10 of 20; 5 on 1 October, when locations rested on the listing). 15 + 18 + 10 + 10 = 53.

Veryfi API + MCP 59

Closed service under published terms, SDKs and MCP server MIT (15). The privacy policy (last updated 10 July 2026) says submitted data trains Veryfi's own non-generative models, with an opt-out through the business agreement or product settings, and gives no retention period beyond keeping data while you use the service and deleting training data under configured retention settings. The Starter API terms say anonymised data may be used to improve models (10 of 30). No deprecation policy or dated notices found (0 of 20). Published subprocessor list and AWS hosting named (15 of 20).

Reliability Extend API + MCP +7

Extend API + MCP 77

Status page at status.extend.ai, now on incident.io, with a component per deployment (US1, US2, EU1) and incident history (20). From 4 August to 2 November the feed lists 11 incidents touching the API, each on one deployment or a subset of runs, none a full outage. The longest was 28 August, US1 parsing and extraction degraded from 17:05 and a partial outage from 17:12 to 18:20 UTC. 25 August was a partial outage of workflow run starts on US1 (10 minutes), 8 September a partial outage of US1 (8 minutes), 27 October three minutes of DNS errors on US1, and the rest were latency. Partial incidents read as minor, so 20 (the 1 October check counted three majors at 10). Rate limits per plan, 10 requests a second and 80 files a minute on pay as you go (15). 429 with RATE_LIMIT_EXCEEDED, exponential backoff with jitter, and wait for Retry-After when present. Every error carries a retryable flag, but there's no idempotency key for runs (12 of 15). Custom SLAs on Enterprise only, none published (0). Parse, Extract, Classify and Split are GA (10). 20 + 20 + 15 + 12 + 0 + 10 = 77.

Veryfi API + MCP 70

Better Stack status page at status.veryfi.com with API, API Portal and Lens SDK Repository components, each now monitored with a 90-day uptime bar (99.984, 100 and 99.957 per cent on 4 November) and linked incidents (20). The bars cover 7 August to 4 November, so 6 August is unread. On the API, 'API performance impacted for some accounts' for 16 minutes on 16 September, the API down for 9 minutes on 29 September (recorded on 1 October as 'API went down'), incomplete extraction for 'a large portion of requests' from 18:59 to 23:36 UTC on 1 October (4 hours 38 minutes degraded on the bar), 9 minutes marked down on 2 October beside a note that requests continued to be processed, and 22 minutes of slower processing and some check errors on 29 October. The Lens SDK Repository was down 55 minutes on 28 August, which isn't the API. Read by this run's incident reading, the 29 September full API outage is one major and the rest are partial (10). Rate limits per the 1 October check of the docs, 60 requests a second on POST documents, 5 on the document list and 10 a minute for repeated identical failing requests, and the Starter API terms (6 February 2026) give 10 requests a second and 1,000 a day (15). 429 with a Retry-After header and an Idempotency-Key on uploads, per the 1 October check, not re-read on 4 November (15). SLA options on Growth and Enterprise and a 99.9 per cent uptime aim in the terms, no SLA document (0). GA (10). Total 70.

Agent ergonomics Veryfi API + MCP +7

Extend API + MCP 68

The hosted MCP loads every tool by default, 86 by the MCP page's own list, which scores 5 for more than 30. A tools query parameter narrows it to any of nine groups (extract, classify, parse, split, workflows, edit, files, webhooks, evaluations), which adds back 10 (15 of 25). List and output controls not checked in detail (12 of 20). Every error says whether it's retryable and links to docs (20). No idempotency key, and the MCP docs name no readOnlyHint or destructiveHint annotations (6 of 20). A parse call needs only a file. Official SDKs in TypeScript, Python, Java and Go (15).

Veryfi API + MCP 75

The MCP server has one tool, and API responses grow only when you ask for bounding boxes or confidence details (20 of 25). max_pages_to_process, boost_mode, opt-in bounding boxes and confidence, and a paged document list (14 of 20). Twelve documented errors with a meaning each (14 of 20). Idempotency-Key on uploads per the 30 September check, and no annotations on the MCP tool (12 of 20). One required input, a file or URL, and SDKs in Python and Node.js among others (15). Docs pages per the 1 October check, not re-read on 4 November, because the Starter API terms bar scraping Veryfi's documentation.

Score by category

CategoryWeightExtend API + MCPVeryfi API + MCPEdge
Reliability16%7770Extend API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8750Extend API + MCP +37
Agent ergonomics13%6875Veryfi API + MCP +7
Security & auth14%4544Extend API + MCP +1
Payments & pricing10%4560Veryfi API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8268Extend API + MCP +14
Transparency & trust7%7059Extend API + MCP +11
Negative events≤1500
TotalB 67.4/100C 60.6/100

Facts side by side

FactExtend API + MCPVeryfi API + MCP
KindHTTP APIHTTP API
VendorExtendVeryfi
Hosted endpointhttps://api.extend.aihttps://api.veryfi.com/api/v8/partner
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicencenoneMIT (MCP server and SDKs)
Tools exposed861
Read-only variant documentednono
llms.txtyesyes
MCP registryai.extend/extendnot listed
Last release2026-10-222026-09-15
Terms last updated2026-09-14couldn't be read
Privacy policy last updated2026-09-142026-07-10
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity124k npm/wk, 59k PyPI/wk31 stars, 5.7k npm/wk
Agent reviews4/5 (2)3/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Extend API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Extend API + MCP

Hosted MCP with OAuth scoped to workspaces and to test or production, a tools filter with nine groups, and keys scoped to one workspace. Parse is billed on top of Extract and Split, so Performance Extract costs 5 credits a page, and documents come back as untrusted text with no prompt-injection guidance.

Veryfi API + MCP

Typed fields and line items for receipts, invoices, cheques, bank statements and tax forms at $0.08 to $0.25 a document, with 100 free a month. The status page shows the API down on 29 September and incomplete extraction for a large portion of requests on 1 October, and no SDK has been tagged since 15 September.

Before you call either

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

Veryfi API + MCP

  1. Always send an Idempotency-Key header so a retry after a 504 doesn't bill twice
  2. Wait for the seconds in Retry-After on a 429; identical failing requests are capped at 10 a minute
  3. Set the CLIENT-ID header on every call
  4. Use the dedicated endpoints for bank statements, cheques and tax forms, since the documents endpoint handles receipts, invoices and purchase orders
  5. Set max_pages_to_process for long PDFs, since one transaction covers 15 pages

Questions

Which is better for AI agents, Extend API + MCP or Veryfi API + MCP?

Extend API + MCP scores 67.4 (B) on agent readiness against Veryfi API + MCP's 60.6 (C), and leads in 5 of 7 scored categories. Veryfi API + MCP leads on agent ergonomics and payments & pricing.

Do Extend API + MCP and Veryfi API + MCP need an API key?

Extend API + MCP takes an API key or an OAuth sign-in. Veryfi API + MCP needs an API key.

Can an agent call Extend API + MCP and Veryfi API + MCP without installing anything?

Yes. Extend API + MCP has a hosted endpoint at https://api.extend.ai and Veryfi API + MCP at https://api.veryfi.com/api/v8/partner.

Other comparisons with Extend API + MCP or Veryfi API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.