Invofox vs LandingAI Agentic Document Extraction

Invofox

Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise.

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.

Invofox

1. Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types
2. Upload with POST /v1/ingest/uploads as multipart, with info as a JSON string. Send "useClassifier": true in place of type to have the type detected
3. Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded
4. Handle the file.rejected webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely
5. Do not retry an upload blindly. There is no idempotency key, so send your own id in clientData and look it up with filter first

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