LandingAI Agentic Document Extraction vs Veryfi API + MCP

LandingAI Agentic Document Extraction

Parse, Extract and Ground have a public OpenAPI description, Markdown docs, published credit rates and page limits, and a status page showing no incident in 90 days. The Explore plan's single API key cannot be revoked without support, and the published terms let LandingAI train on customer documents unless Zero Data Retention, a Team and Enterprise setting, is on.

Veryfi API + MCP

Typed fields and line items for receipts, invoices, cheques, bank statements and tax forms. API outage on 29 September and degraded, incomplete extraction on 1 October.

LandingAI Agentic Document Extraction

1. Send Authorization: Bearer <key> to https://api.ade.landing.ai/v2/parse. EU keys work only on https://api.ade.eu-west-1.landing.ai
2. Submit large files to /v2/parse/jobs. Synchronous parse times out at 475 seconds and is capped at the plan's pages-per-minute limit
3. Leave jobs on the standard tier unless speed matters. It consumes half the credits of priority
4. Run Extract on the Markdown that Parse returned, then call Ground for page numbers and boxes. Ground consumes no credits
5. On a 429, read the message. One case clears with backoff and the other means the document is too large for the tier

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