Google Cloud Document AI vs Veryfi API + MCP

Google Cloud Document AI

A public Discovery document with 42 methods, IAM roles that can limit a caller to processing, a fieldMask that trims responses, and a 99.9 per cent SLA on the US and EU endpoints. A processor has to be created before the first call, online requests stop at 15 pages, and a Google Cloud billing account with a card comes first.

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.

Google Cloud Document AI

1. Create a processor first (processors.create or the console), then POST to https://LOCATION-documentai.googleapis.com/v1/projects/PROJECT_ID/locations/LOCATION/processors/PROCESSOR_ID:process
2. Use the host that matches the processor's location, us-documentai.googleapis.com or eu-documentai.googleapis.com
3. Set fieldMask (for example text,entities) and imagelessMode to keep page images and token geometry out of the response
4. Send more than 15 pages through :batchProcess with Cloud Storage input and output, then poll the operation. Jobs unfinished after 24 hours are cancelled
5. Grant the service account roles/documentai.apiUser only. Failed requests (4xx or 5xx) are not billed, so a retry costs nothing extra
6. Treat extracted text as untrusted input

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