Exa for AI agents
Exa is a search and data extraction API that helps teams gather and structure information from websites and documents, used by developers building research and retrieval tools. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Exa.
Search the web for sources
Run a search to find sources relevant to a research question a user asked.
Pull content from a URL
Get the contents of a specific URL to summarize it without a manual visit.
Read-only research task checks
Get a research task's status as a read-only step before pulling its finished output.
20 Exa actions, graded by risk.
Every Exa action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
11Look things up. Allowed by default.
- exa.get_eventGet Event
- exa.get_api_keyGet API Key
- exa.list_eventsList events
- exa.find_similarFind similar (Deprecated)
- exa.get_researchGet Research Task
- exa.list_importsList imports
- exa.get_agent_runGet Agent Run
- exa.list_researchList research tasks
- exa.list_webhooksList webhooks
- exa.get_contents_actionGet contents from URLs or document IDs
- exa.searchSearch
write
7Create and change things. Allow, or ask the user first.
- exa.create_importCreate Import
- exa.create_websetCreate Webset
- exa.update_importUpdate import
- exa.create_monitorCreate a Monitor
- exa.create_researchCreate Research Task
- exa.create_agent_runCreate Agent Run
- exa.answerGenerate an answer
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- exa.delete_importDelete import
- exa.delete_websetDelete webset
Exa in three steps.
- 01Your users connect ExaThey add their Exa api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Import” can wait for the user, and “delete import” can be denied outright.
- 03Any agent can actYour agent calls Exa through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('exa', { read: 'allow', write: 'ask', // create_import destructive: 'deny', // delete_import }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Exa connects.
Users add their Exa api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Exa connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Exa from any agent.
Exa and Arc0, answered.
Can I use Exa with Claude, ChatGPT or Cursor?
Yes. Connect Exa to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Exa actions you allow.
How do users connect Exa?
Users add their Exa api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Exa actions can my agent take?
20 in total: 11 read, 7 write and 2 destructive, such as “create Import”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Exa?
Yes. Actions like “delete import” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Exa too?
Yes. The same Exa connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Exa into your agent.
Your users connect Exa once, under your brand. Your agent gets 20 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan