Kadoa for AI agents
Kadoa is an API-first platform for creating and monitoring data extraction workflows from unstructured web sources. Teams use it to pull this data on a schedule instead of copying it by hand. 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 Kadoa.
Check a workflow's latest data
Pull the latest extracted data from a monitoring workflow to check for new listings.
Check a crawl's status
Check whether a crawl configuration's latest run has finished before pulling results.
Delete a workflow with confirmation
Delete an extraction workflow only after the owner confirms it is no longer needed.
77 Kadoa actions, graded by risk.
Every Kadoa action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
38Look things up. Allowed by default.
- kadoa.get_schemaGet Schema by ID
- kadoa.list_changesList Changes
- kadoa.list_schemasList Schemas
- kadoa.get_workflowsGet Workflows
- kadoa.list_activityList Activity Events
- kadoa.get_event_typeGet Event Type Details
- kadoa.get_event_typesGet Notification Event Types
- kadoa.get_crawl_configGet Crawl Configuration
- kadoa.get_crawl_statusGet Crawl Status
- kadoa.get_workflow_jobGet Workflow Job
- kadoa.get_all_locationsGet all locations
- kadoa.get_crawled_pagesGet Crawled Pages
- kadoa.get_validation_ruleGet Validation Rule
- kadoa.list_crawl_sessionsList Crawl Sessions
- kadoa.list_support_statesList Support States
- kadoa.get_workflow_triggerGet Workflow Trigger
write
29Create and change things. Allow, or ask the user first.
- kadoa.post_crawlStart Crawl Session
- kadoa.create_schemaCreate Schema
- kadoa.post_workflowCreate Workflow
- kadoa.update_schemaUpdate Schema
- kadoa.create_crawl_configCreate Crawl Config
- kadoa.create_support_issueCreate Support Issue
- kadoa.post_advanced_workflowCreate Advanced Workflow
- kadoa.post_notification_testSend Test Notification
- kadoa.create_workflow_triggerCreate Workflow Trigger
- kadoa.update_workflow_triggerUpdate Workflow Trigger
- kadoa.post_workflow_monitoringConfigure Workflow Monitoring
- kadoa.update_validation_configUpdate Validation Configuration
- kadoa.update_workflow_metadataUpdate Workflow Metadata
- kadoa.post_notification_settingCreate Notification Setting
- kadoa.post_webhook_subscriptionSubscribe to Webhook Events
- kadoa.create_notification_channelCreate Notification Channel
destructive
10Delete, cancel or archive. Ask first, or deny outright.
- kadoa.delete_schemaDelete Schema
- kadoa.delete_workflowDelete Workflow
- kadoa.delete_crawl_configDelete Crawl Configuration
- kadoa.delete_validation_ruleDelete Validation Rule
- kadoa.delete_workflow_triggerDelete Workflow Trigger
- kadoa.delete_all_validation_rulesDelete All Validation Rules
- kadoa.delete_notification_channelDelete Notification Channel
- kadoa.delete_validation_rules_bulkDelete Validation Rules (Bulk)
- kadoa.disable_validation_ruleDisable Validation Rule
- kadoa.unsubscribe_from_webhook_eventsUnsubscribe from Webhook Events
Kadoa in three steps.
- 01Your users connect KadoaThey add their Kadoa api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Schema” can wait for the user, and “delete Schema” can be denied outright.
- 03Any agent can actYour agent calls Kadoa through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('kadoa', { read: 'allow', write: 'ask', // create_schema destructive: 'deny', // delete_schema }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Kadoa connects.
Users add their Kadoa 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 Kadoa 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 Kadoa from any agent.
More web data and scraping apps.
Kadoa and Arc0, answered.
Can I use Kadoa with Claude, ChatGPT or Cursor?
Yes. Connect Kadoa 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 Kadoa actions you allow.
How do users connect Kadoa?
Users add their Kadoa 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 Kadoa actions can my agent take?
77 in total: 38 read, 29 write and 10 destructive, such as “create Schema”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Kadoa?
Yes. Actions like “delete Schema” 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 Kadoa too?
Yes. The same Kadoa connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Kadoa into your agent.
Your users connect Kadoa once, under your brand. Your agent gets 77 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan