Google Cloud Document AI vs Invofox

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.

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.

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

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