Exa ↗
Search the web and retrieve page contents for your research.
Provision an API key and usage budget.
Our integration playbook
Build a research record you can audit later
INFRASTRUCTURE FOR THE AGENT ECONOMY
Find web sources for your current question.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Start with a focused query and a stopping rule. Preserve URLs with findings and inspect primary sources before turning search results into claims.
Before you proceed: More results are not automatically more independent evidence.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
13 services · Catalog updated 2026-11-10 · See each listing’s review date
Search the web and retrieve page contents for your research.
Provision an API key and usage budget.
Our integration playbook
Build a research record you can audit later
Find web information through search designed for AI agents.
Sign up for an API key; approve paid usage beyond the included allowance.
Our integration playbook
Set a research budget before expanding the search
Request cited web research and structured enrichment for your task.
Provision a Parallel API key and usage budget, or configure an authorized payment method for the separate payment gateway.
Our integration playbook
Keep the research evidence attached to each output field
Retrieve current public web data through a hosted MCP connection.
Create a Bright Data account, configure its API token and approve the public-data scope and usage budget.
Our integration playbook
Check coverage before expanding a public-data collection
Find current web sources and return evidence in a useful structure.
Provision an API key and account credits, or configure an approved funded wallet and spending policy for the documented x402 route.
Our integration playbook
Validate a citation before spending on deeper research
Retrieve web content and structured search results.
Create a ScrapingBee account, supply its API key and choose the allowed research targets and credit budget.
Our integration playbook
Validate one extraction before expanding the crawl
Search web and specialist research sources through one API.
Create a Valyu account, obtain an API key or authorize MCP sign-in, and select a plan with access to the datasets your task needs.
Our integration playbook
Keep source coverage visible throughout the research task
Retrieve structured search-engine results through an API or MCP client.
Create a SerpApi account, obtain an API key and select a search plan. Choose the engine, language and geographic settings that match the task.
Our integration playbook
Keep the search context with every result you use
Collect structured search-engine results for agent research.
Create a SERP API zone, configure an API token and choose query locales and usage limits.
Our integration playbook
Build a repeatable search-results collection
Query linked web entities and extract structured records through API or MCP.
Create a Diffbot account, authorize MCP or supply an API token, and choose a plan and query budget. Crawl access depends on the plan.
Our integration playbook
Resolve the entity before expanding a research query
Query publisher content and current information with documented agent payment options.
Choose the required publisher model and access channel. Configure an API key for the regular API, or authorize the storefront’s identity and payment route with a bounded budget.
Our integration playbook
Select the content contract before authorizing paid retrieval
Search an independent web index and retrieve source-linked context for agents.
Create an API account, complete the provider’s billing verification and issue a key. Choose a usage budget and confirm the plan’s storage rights before retaining results.
Our integration playbook
Budget the search context and verify the original claim
Search current web sources through API or MCP, with free and documented machine-payment routes.
For limited search, configure the free MCP profile without an account. For broader access, create an account and API key or authorize OAuth. For machine payments, use a compatible funded wallet and an approved spending budget.
Our integration playbook
Choose an access route and bound the retrieval cost before researching
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.