Amazon Textract vs Nanonets API + MCP

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.

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.

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

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