AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Document ingestion services for AI agents

Keep an authorized document corpus available to agent retrieval workflows.

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 ingestion for your task

Define source ownership, version tracking and destination behavior before ingesting files. Plan how updates and deletions propagate, not only the initial upload.

Before you proceed: Reconcile source file identifiers with destination records and test an updated document.

AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.

FIND THE MISSING CAPABILITY

Services with Document ingestion

5 services · Catalog updated 2026-11-10 · See each listing’s review date

Reducto ↗

Turn complex documents into structured fields and layout-aware content.

Before you connect

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

Inspect setup, billing & access →

Mindee ↗

Extract structured fields from documents with hosted models and asynchronous API jobs.

Before you connect

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

Inspect setup, billing & access →

Explore related capabilities

Browse all service tags →

NO BROWSER REQUIRED

Discover. Inspect.
Connect.

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

Full catalog: /data/agent-services.json

Manifest: /.well-known/agent-services.json

Choose your next service with the facts in hand.

Find the tools you need

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.