Adobe PDF Services / PDF Extract API vs Nanonets API + MCP

Adobe PDF Services / PDF Extract API

Public OpenAPI 3.0.1 spec covering Extract, PDF to Markdown and 20 other operations. No published paid price, paid use goes through sales.

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.

Adobe PDF Services / PDF Extract API

1. Cache the access token and reuse it until it expires
2. Budget 1 Document Transaction per 5 pages for Extract and PDF to Markdown, so 500 free transactions cover about 2,500 pages
3. Pass notifiers with a callback URL instead of polling the job status
4. Use pdf-services-ew1.adobe.io when documents must stay in the EU
5. Check /operation/pdfproperties first, since copy-protected PDFs fail Extract with DISQUALIFIED_PERMISSIONS

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