Wachete for AI agents
Wachete tracks changes on web pages and sends notifications, used by teams monitoring competitor sites, prices, or listings for updates. 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 Wachete.
Create a watcher for a page
Set up monitoring on a URL to get notified when its content changes.
Get a watcher's change history
Pull the recorded history of changes for a watcher, a read-only report.
Confirm before deleting a watcher
Check with the user before deleting a watcher, since its change history goes with it.
11 Wachete actions, graded by risk.
Every Wachete action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- wachete.get_watcherGet watcher by ID
- wachete.list_watchersList watchers
- wachete.get_data_historyGet Data History
- wachete.get_crawler_pagesGet crawler pages
- wachete.get_folder_contentGet folder content
- wachete.list_notificationsList notifications
write
3Create and change things. Allow, or ask the user first.
- wachete.create_watcherCreate Watcher
- wachete.create_update_folderCreate or update folder
- wachete.move_items_to_folderMove Items to Folder
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- wachete.delete_folderDelete folder
- wachete.delete_watcherDelete watcher
Wachete in three steps.
- 01Your users connect WacheteThey add their Wachete api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Watcher” can wait for the user, and “delete folder” can be denied outright.
- 03Any agent can actYour agent calls Wachete through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('wachete', { read: 'allow', write: 'ask', // create_watcher destructive: 'deny', // delete_folder }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Wachete connects.
Users add their Wachete 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 Wachete 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 Wachete from any agent.
Wachete and Arc0, answered.
Can I use Wachete with Claude, ChatGPT or Cursor?
Yes. Connect Wachete 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 Wachete actions you allow.
How do users connect Wachete?
Users add their Wachete 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 Wachete actions can my agent take?
11 in total: 6 read, 3 write and 2 destructive, such as “create Watcher”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Wachete?
Yes. Actions like “delete folder” 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 Wachete too?
Yes. The same Wachete connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Wachete into your agent.
Your users connect Wachete 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