Amazon Textract vs Mindee API

Amazon Textract

IAM policies limit a credential to single operations, CloudTrail logs every call, and page prices start at $1.50 per 1,000 in US East. Multipage files need S3 and an asynchronous job. Text detection covers six languages. Under the AWS Service Terms AWS may store and use documents to improve the service unless an AI services opt-out policy is set.

Mindee API

Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored. Every call needs a model_id created in the web platform first.

Amazon Textract

1. Sign with SigV4 for service textract at textract.<region>.amazonaws.com, or call aws textract detect-document-text. The AWS CLI can't send image bytes, so reference an S3 object
2. Use StartDocumentTextDetection or StartDocumentAnalysis for any PDF or TIFF of more than one page, pass a ClientRequestToken, then page Get calls with NextToken (1,000 blocks at most each)
3. Fetch results within 7 days of starting a job, or set OutputConfig to write them to your own S3 bucket
4. Request only the FeatureTypes you need. Forms cost $50 per 1,000 pages against $15 for tables or queries in US East
5. Back off on ProvisionedThroughputExceededException (HTTP 400) and ThrottlingException (HTTP 500). Neither carries Retry-After, and default quotas are 1 call a second in most Regions
6. Set the AI services opt-out policy on the AWS organisation before sending customer documents

Mindee API

1. Create the model in the Mindee app and store its model_id; the API can't create one for you
2. Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
3. Send Authorization: $MINDEE_API_KEY with no Bearer prefix
4. Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
5. Keep schemas to 25 fields or fewer, the documented recommendation