SearchAPI for AI agents
SearchAPI is a hosted connector that runs configured search engine queries under a plan with request quotas, giving an agent one endpoint for web search results. 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 SearchAPI.
Run a light Google search
Executes a quick Google-style search query and returns the top results for a topic.
Check remaining quota before searching
Confirms the plan's request quota still has room before running another batch of searches.
Search only configured engines
Runs a query only against the search engines already configured for the account, a fixed and read-only scope.
1 SearchAPI actions, graded by risk.
Every SearchAPI action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
1Create and change things. Allow, or ask the user first.
- searchapi.google_search_lightGoogle search light
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
SearchAPI in three steps.
- 01Your users connect SearchAPIThey sign in to SearchAPI on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “google search light” can wait for the user to approve.
- 03Any agent can actYour agent calls SearchAPI through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('searchapi', { read: 'allow', write: 'ask', // google_search_light destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How SearchAPI connects.
SearchAPI runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches SearchAPI through the same endpoint, policies and audit log as every other app.
The same SearchAPI 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
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use SearchAPI from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore web data and scraping apps.
SearchAPI and Arc0, answered.
Can I use SearchAPI with Claude, ChatGPT or Cursor?
Yes. Connect SearchAPI 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 SearchAPI actions you allow.
How do users connect SearchAPI?
SearchAPI runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches SearchAPI through the same endpoint, policies and audit log as every other app.
Which SearchAPI actions can my agent take?
1 in total: 0 read, 1 write and 0 destructive, such as “google search light”. Your policies decide which of them each agent may call.
Can I make my agent read-only in SearchAPI?
Yes. Allow read actions and deny writes in the SearchAPI policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call SearchAPI too?
Yes. The same SearchAPI connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug SearchAPI into your agent.
Your users connect SearchAPI once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan