Cloro for AI agents
Cloro pulls structured data out of Google Search and AI assistant answers, letting a team extract search results programmatically instead of scraping manually. 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 Cloro.
Search Google for a query
Search Google for a query and get back structured results instead of raw HTML.
Extract an AI assistant's answer
Extract a specific AI assistant's answer to a query for competitive research.
Check remaining credits
Check remaining credits before submitting a large batch of search extraction tasks.
10 Cloro actions, graded by risk.
Every Cloro action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
8Look things up. Allowed by default.
- cloro.get_creditsGet Credits
- cloro.search_googleSearch Google
- cloro.get_async_taskGet Async Task
- cloro.list_us_statesList US States
- cloro.get_async_queue_statusGet Async Queue Status
- cloro.list_supported_countriesList Supported Countries
- cloro.extract_ai_answerExtract AI Answer
- cloro.extract_google_ai_mode_answerExtract Google AI Mode Answer
write
2Create and change things. Allow, or ask the user first.
- cloro.submit_async_taskSubmit Async Task
- cloro.submit_async_task_batchSubmit Async Task Batch
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Cloro in three steps.
- 01Your users connect CloroThey add their Cloro api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “submit Async Task” can wait for the user to approve.
- 03Any agent can actYour agent calls Cloro through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('cloro', { read: 'allow', write: 'ask', // submit_async_task destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Cloro connects.
Users add their Cloro 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 Cloro 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 Cloro from any agent.
More web data and scraping apps.
Cloro and Arc0, answered.
Can I use Cloro with Claude, ChatGPT or Cursor?
Yes. Connect Cloro 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 Cloro actions you allow.
How do users connect Cloro?
Users add their Cloro 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 Cloro actions can my agent take?
10 in total: 8 read, 2 write and 0 destructive, such as “submit Async Task”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Cloro?
Yes. Allow read actions and deny writes in the Cloro policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Cloro too?
Yes. The same Cloro connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Cloro into your agent.
Your users connect Cloro once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan