Persistent snapshots and semantic change detection over the open web. Stream durable state to your agents through APIs, webhooks, and MCP-shaped integrations—without owning the scraper fleet.
await cambio.watch.create({
url: "https://docs.vendor.com/api/releases",
mode: "semantic", // or "deterministic"
intent: "breaking changes, deprecations, auth flow updates",
interval: "15m",
retention: "90d",
webhook: "https://api.yours.dev/v1/agents/web-memory",
});Why Cambio
Selectors rot after every redesign. Your agents read stale DOM or break mid-run. Cambio owns extraction and normalization so downstream tools get stable, versioned facts—not one-off HTML.
Cron + fetch scales poorly and burns tokens on unchanged bytes. Cambio keeps a temporal record and only emits events when your policy says the world crossed a threshold worth acting on.
Timestamps, trackers, and layout noise drown signal. Cambio evaluates semantic deltas against your intent so orchestrators, queues, and MCP tools react to durable change—not pixel churn.
How it works
POST a URL, how often to sample, how long to retain snapshots, and what counts as material change—in prose or structured rules.
POST /v1/watches
Authorization: Bearer sk_live_•••
{
"url": "https://docs.vendor.com/reference/auth",
"intent": "schema + auth-flow changes our agents must know about",
"interval": "10m",
"retention": "90d",
"webhook": "https://api.yours.dev/hooks/cambio"
}Cambio runs the data plane: fetch, normalize, store versions, and score deltas against your intent so noise never becomes an event.
// Cambio snapshots the URL on a schedule, stores
// durable versions, and evaluates deltas with your policy:
//
// "Given the last committed snapshot, did anything
// matching the intent materially change?"
//
// Most ticks produce no event. Your stack wakes only when
// the web's state crosses a semantic threshold—webhook,
// queue, or MCP tool call downstream.Get structured payloads with snapshot lineage—wire webhooks to queues, agents, or MCP-exposed tools. Your code stays event-driven.
POST https://api.yours.dev/hooks/cambio
{
"watch_id": "wch_8f2a",
"url": "https://docs.vendor.com/reference/auth",
"detected_at": "2026-05-10T14:22:08Z",
"snapshot_id": "snap_3k9m",
"previous_snapshot_id": "snap_3k8p",
"change": {
"type": "auth_flow_update",
"summary": "OAuth scopes table expanded; PKCE now required",
"before": { "pkce": "optional" },
"after": { "pkce": "required" }
},
"confidence": 0.96
}Programmable surface
Mix semantic intent with deterministic guards. Cambio materializes durable web state so orchestrators, queues, and MCP servers subscribe to the same event contract.
Describe what matters in natural language—Cambio maps it to evaluation so agents consume human-readable summaries, not raw DOM noise.
Need hard guarantees? Pin selectors, JSON paths, or hashes. Get typed diffs and replayable snapshots for tests, CI gates, and compliance.
No cron mesh, residential proxies, or headless farms. Scheduling, backoff, capture, and storage are Cambio primitives—not glue in your repo.
Tune sampling cadence, retention windows, and concurrency budgets. Rate limits and retries stay inside the platform boundary.
Use cases
Cambio is the persistence and change layer between HTTP origins and your agents, services, and event fabric—not a dashboard for passive alerts.
Pin vendor API references; stream breaking changes into codegen, eval harnesses, or on-call bots with cited snapshots.
Let LangGraph / Temporal / custom workers consume Cambio events as first-class tasks instead of bespoke scraper maintenance.
Push structured deltas to Kafka, SQS, or HTTPS endpoints—idempotent keys and snapshot lineage for exactly-once style handling.
Rehydrate prior page state for debugging agent drift, regression tests, or compliance evidence without rebuilding crawl archives.
Track legal and security pages with durable history so risk teams and autonomous monitors align on what changed, when.
Trigger embedding refreshes only when monitored sources materially move—keep vector stores aligned with the live web.
Pricing
Early access
We onboard teams building agent runtimes, data planes, and automation first. Share the workflows you want to wire—API, webhook, or MCP—and we route you into the right beta wave.