Search api for AI agents
Search API is a real-time SERP API that runs search engine queries and returns structured results, handling proxy rotation and CAPTCHAs for the caller. 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 Search api.
Run a search query
Executes a search engine query and returns structured results such as organic listings and ads.
Pull a cached search result
Retrieves a previously run search result by its ID instead of paying for a fresh query.
Check account info before a run
Reads the account's plan and remaining quota before running another batch of searches.
5 Search api actions, graded by risk.
Every Search api action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- search_api.get_locationsGet Locations
- search_api.get_account_infoGet Account Info
- search_api.get_cached_search_by_idGet Cached Search by ID
- search_api.get_cached_search_html_by_idGet Cached Search HTML by ID
- search_api.searchSearch
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Search api in three steps.
- 01Your users connect Search apiThey add their Search api api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Search api through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('search_api', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Search api connects.
Users add their Search api 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 Search api 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 Search api from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore web data and scraping apps.
Search api and Arc0, answered.
Can I use Search api with Claude, ChatGPT or Cursor?
Yes. Connect Search api 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 Search api actions you allow.
How do users connect Search api?
Users add their Search api 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 Search api actions can my agent take?
5 in total: 5 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Search api?
Yes. Allow read actions and deny writes in the Search api policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Search api too?
Yes. The same Search api connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Search api into your agent.
Your users connect Search api once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan