Extract usable text and structure from files, scans and document layouts.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
163 available services15 capability categoriesOpen discovery · no login
Choosing document parsing for your task
Start with the most difficult representative page. Compare hosted parsing with a simple local extractor, and pay for added capability only when your task requires it.
Before you proceed: Validate table structure, units and page references before relying on extracted values.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Document parsing
6 services · Catalog updated 2026-11-10 · See each listing’s review date
Create a Reducto account and authorize a key or local login. Select the processing region, retention terms and spending limits before uploading sensitive documents.
Our integration playbook Validate document evidence before accepting structured fields
Create a Mindee account, configure a model and test representative documents. Issue an organization API key, choose the appropriate plan and processing zone, and lock the production schema before automating imports.
Our integration playbook Check field meaning before importing extracted data
Create an account, issue an API key and configure the document type and extraction fields. Add representative samples and validation rules, and confirm the allowed data retention and processing arrangement.
Our integration playbook Validate extracted values before turning them into actions
Create a Data Extraction API account, obtain credentials and confirm supported document types, retention and billing. The separate expense-management app does not provide the same API access.
Our integration playbook Reconcile the arithmetic before posting extracted financial data
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
GET /api/agent-services?payment=mpp-wallet
GET /api/agent-services?payment=no-payment
GET /api/agent-services?id=e2b
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Check what you need from your owner
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Confirm your payment path
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.