Colter Lens

TL;DR: Register a site with colter lens https://mystore.com, deploy the edge worker, then use colter lens status, alerts, protocols, report, and export to monitor live AI agent traffic. Lens is the runtime view of what agents actually do after launch.

What Lens Tracks

• agent traffic volume
• protocol health
• signature verification
• funnel progression
• session drill-downs
• alerts and exports

Lens leads with observable traffic quality. It does not invent revenue. Revenue attribution appears when cart and order events are connected; before that, any dollar impact is labeled as an estimate based on observed traffic and benchmark assumptions.

Quick Start

Register the site:

colter lens https://mystore.com

Or via the API:

curl -X POST https://agenticcom.ai/api/v1/lens/sites \
  -H "Authorization: Bearer $COLTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://mystore.com"}'

Deploy the worker:

cd workers/lens-edge
npm install
npx wrangler secret put COLTER_API_KEY
npx wrangler deploy

Ship server logs when an edge worker is not available:

curl -X POST https://agenticcom.ai/api/v1/lens/ingest-logs \
  -H "Authorization: Bearer $COLTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "lens_site_id",
    "format": "json",
    "logs": "{\"timestamp\":\"2026-05-20T10:15:00Z\",\"method\":\"GET\",\"path\":\"/products/widget\",\"status\":200,\"user_agent\":\"GPTBot\"}"
  }'

Coverage Modes

Lens is designed to capture agent HTTP requests, including crawlers that never execute JavaScript. Use the collection mode that gives Colter request-level visibility:

Mode	Coverage	Captures non-JS crawlers?	Use when
Edge worker	Full request-level telemetry	Yes	The store domain is on Cloudflare or can run an edge worker
Server-log ingestion	Full, delayed telemetry	Yes	The merchant can ship web server/CDN logs
Beacon	Partial browser-like telemetry	No	Edge/log collection is unavailable and you only need JS-executing agent signals

Beacon mode is a fallback. It cannot see most direct crawler requests because crawlers usually do not run storefront JavaScript.

Data Minimization

Lens records agent-classified request metadata, not page bodies or prompts. Stored paths and referrers are sanitized before persistence: query strings, URL fragments, usernames, and passwords are stripped, while host/path attribution is preserved for source and journey reporting. Raw IP addresses are not stored; Cloudflare deployments can include country, ASN, and bot-score fields.

For product pages, Lens stores the product path handle, such as /products/widget -> widget, so Product Intelligence can rank agent interest without storing page content or customer data.

Capture Health

The scheduled Lens health check compares Cloudflare-known AI crawler volume against known or signed request-level Lens events for sites with Cloudflare analytics configured. Generic unidentified crawlers are still recorded in traffic analytics, but they do not satisfy this drift check. When Cloudflare sees known crawlers but Lens records little or no matching request-level traffic, Lens stores a capture-health snapshot and opens a capture_drift alert.

This protects against silent failures such as a disabled Worker route, stale ingestion key, stopped log pipeline, or beacon-only install being mistaken for full coverage.

Core CLI

Register:

colter lens https://mystore.com --json

Status:

colter lens status --url https://mystore.com --period 7d --json

Alerts:

colter lens alerts --site-id <id> --status open --json

Protocol health:

colter lens protocols --site-id <id> --json

Report:

colter lens report --site-id <id> --period 7d --json

Export:

colter lens export --site-id <id> --type traffic --period 7d --format csv --out lens-traffic.csv

Deploy:

colter lens deploy --url https://mystore.com --cf-account-id <id> --cf-api-token <token>

Dashboard Areas

Area	What it answers
Traffic overview	Which agents are visiting and in what volume
Verification quality	Which agent requests are signed, trusted, unverified, or suspicious
Protocol health	Which readiness surfaces are up or down
Journey funnel	Where agents drop off
Session explorer	What happened in one session
Attribution	Which agent sessions tie to carts and orders when order events are connected
Estimates	Benchmark-based upside from observed traffic, always labeled as estimates
Alerts	What changed and what needs action
Portfolio	How multiple sites compare

Free Tier Access

• Free Lens sites get deterministic traffic monitoring for one site with up to 30 days of history until the first 500 agent visits.
• After 500 visits, free ingestion accepts calls but stops recording additional events until the site upgrades.
• LLM insights, manual analysis, journey analytics, protocol health dashboards, exports, external alerts, portfolio views, and webhooks require a paid plan.
• Pro and Agency plans keep their existing 30-day and 90-day history windows.

Authenticated API

Lens endpoints require a session cookie or Authorization: Bearer $COLTER_API_KEY.

Useful endpoints:

• POST /api/v1/lens/sites
• POST /api/v1/lens/deploy-worker
• POST /api/v1/lens/ingest
• POST /api/v1/lens/ingest-logs
• POST /api/v1/lens/order-event
• GET /api/v1/lens/traffic
• GET /api/v1/lens/journeys
• GET /api/v1/lens/protocols
• GET /api/v1/lens/alerts
• GET /api/v1/lens/export
• POST /api/v1/lens/revenue-webhook

POST /api/v1/lens/order-event and POST /api/v1/lens/revenue-webhook are the order-data hooks that make measured revenue attribution possible. Without those events, Lens still reports traffic, verification, protocol health, journeys, paths, products, alerts, and clearly labeled estimates.

Alert Types

• protocol_down
• protocol_recovered
• score_drop
• capture_drift
• signature_failure
• new_agent
• x402_down
• x402_recovered
• acp_checkout_down
• acp_checkout_recovered

Notes

• Lens pricing and limits follow the current Pricing page.
• Lens is for live monitoring; use Check, Test, and Verify for setup and validation work.

Next Steps

• Getting Started
• API Reference
• Fix
• Verify
• Agent Detection