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 sources and retrieve evidence for your next decision.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
FIND THE MISSING CAPABILITY
19 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
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
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
Embed content and rerank retrieved candidates through hosted models.
Obtain a Jina API key, choose a model and configure token funding for sustained usage. Decide which content may be sent to the hosted API.
Our integration playbook
Keep retrieval coverage separate from ranking quality
Search public developer documentation without an account or API key.
Configure an MCP-compatible client with the HTTPS endpoint https://mcp.algolia.com/1/docsearch/mcp. No Algolia account, application ID or API key is required.
Our integration playbook
Resolve the documentation set before trusting a code example
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
Resolve addresses and place names into geographic coordinates and context.
Create a Mapbox account and access token, configure billing and decide whether results will be stored. Confirm the workflow uses results with a Mapbox map; permanent storage requires the appropriate account setup.
Our integration playbook
Set the result-storage policy before building an address lookup workflow
Resolve addresses and coordinates using maintained open geographic data.
Create an account and API key. Choose a production plan for ongoing use, confirm request allowances and apply the provider’s attribution guidance.
Our integration playbook
Separate geographic precision from address identity
Fetch weather observations and forecasts through an agent-oriented API or MCP server.
Have the account owner authorize signup and the current terms, then store the returned account secret and data key separately. A person completes paid credit top-ups on the provider’s payment page.
Our integration playbook
Check the weather timestamp and the correct credit balance
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
Retrieve library documentation and examples for an agent’s coding task.
Connect an MCP client with OAuth or create a Context7 API key. Select allowed sources and decide whether private-repository indexing or paid overages are permitted.
Our integration playbook
Match documentation to the installed dependency before coding
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
Find scholarly works, resolve citations and inspect research connections through API or MCP.
Connect MCP and approve OpenAlex sign-in, or obtain a free API key. An agent can request a key for its owner, but the owner must click the emailed activation link before that key works.
Our integration playbook
Keep a reproducible search trail before summarizing research
Find relevant public and private technical documentation through a hosted MCP service.
Create a Ref account and connect the MCP client. Choose personal or team scope, and authorize any private documentation sources before making them available to the agent.
Our integration playbook
Check the installed version before applying a retrieved example
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
Search a maintained news corpus and group coverage into events.
Create an Event Registry / NewsAPI.ai account and API key. Choose a plan covering the required history and usage, and decide how retrieved content will be attributed and used.
Our integration playbook
Count independent sources before treating repeated coverage as corroboration
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.