Browseai for AI agents
Browse.ai is a web scraping and monitoring service that teams use to turn websites into structured data feeds and get alerted when tracked pages change. 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 Browseai.
Check a monitor's latest run
Read-only lookup of a robot's task results before deciding whether the tracked page has changed.
Run a scraping robot
Run a configured robot against a target site after the user confirms which pages to extract.
Require approval before deleting a monitor
Treat deleting a monitor or task as destructive since it stops tracking a page's changes.
11 Browseai actions, graded by risk.
Every Browseai 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.
- browseai.get_robotsGet Robots List
- browseai.get_robot_tasksGet Robot Tasks
- browseai.get_task_detailsGet Task Details
- browseai.get_system_statusGet System Status
- browseai.list_robot_webhooksList Robot Webhooks
write
4Create and change things. Allow, or ask the user first.
- browseai.create_monitorCreate Monitor
- browseai.create_webhookCreate Webhook
- browseai.run_robotRun Robot
- browseai.bulk_run_tasksBulk Run Tasks
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- browseai.delete_taskDelete a specific task
- browseai.delete_monitorDelete a specific monitor
Browseai in three steps.
- 01Your users connect BrowseaiThey add their Browseai api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Monitor” can wait for the user, and “delete a specific task” can be denied outright.
- 03Any agent can actYour agent calls Browseai through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('browseai', { read: 'allow', write: 'ask', // create_monitor destructive: 'deny', // delete_task }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Browseai connects.
Users add their Browseai 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 Browseai 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 Browseai from any agent.
More web data and scraping apps.
Browseai and Arc0, answered.
Can I use Browseai with Claude, ChatGPT or Cursor?
Yes. Connect Browseai 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 Browseai actions you allow.
How do users connect Browseai?
Users add their Browseai 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 Browseai actions can my agent take?
11 in total: 5 read, 4 write and 2 destructive, such as “create Monitor”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Browseai?
Yes. Actions like “delete a specific task” 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 Browseai too?
Yes. The same Browseai connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Browseai into your agent.
Your users connect Browseai once, under your brand. Your agent gets 11 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan