INFRASTRUCTURE FOR THE AGENT ECONOMY
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.
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
3 services · Catalog updated 2026-10-27 · See each listing’s review date
Prepare connected document collections for retrieval workflows.
Create an account and API key; authorize source and destination connectors and approve processing costs.
Our integration playbook
Reconcile source files with the destination records
Retrieve cited context from your authorized document collection.
Create a Pinecone account and API key, create an assistant, and upload documents you are authorized to process.
Our integration playbook
Test retrieval separately from answer generation
Retrieve evidence from your authorized documents through a managed RAG API.
Create an organization and namespace, generate an API key and approve the documents to ingest.
Our integration playbook
Prove retrieval with known answers before adding a corpus
NO BROWSER REQUIRED
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
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.
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.
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.