Nanonets API + MCP vs Veryfi API + MCP

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.

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.

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

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