Colter Lens

Name: Colter
Author: Colter

Ongoing observed agent-traffic monitoring used when the Recommendation Audit or a technical workflow needs production evidence.

TL;DR: Register a site with colter lens https://mystore.com, configure a collection method, then use colter lens status, alerts, protocols, report, and export to review the signals Colter actually recorded.

Lens is a Monitor capability inside the Recommendation Audit, not a separate starting product. It answers traffic and journey questions; it does not by itself show that an answer engine recommended a product.

What Lens Tracks

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

Order events can be matched to available activity records when those events are connected. A match does not show that a recorded visit caused an order or revenue. Do not present benchmark estimates as measured merchant outcomes.

Quick Start

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

Use the collection mode that fits the merchant's infrastructure and describe only the records it can supply:

Mode	Coverage	Captures non-JS crawlers?	Use when
Edge worker	Request-level telemetry on the configured route	Yes	The store domain can run the Colter worker on the relevant routes
Server-log ingestion	Records present in the supplied logs	Yes, when present in those logs	The merchant can ship the relevant 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

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
Activity matching	Which recorded sessions are linked to carts and orders by the current matching rules
Alerts	What changed and what needs action
Portfolio	How multiple sites compare

Plan Limits

Monitoring history, store counts, and feature access follow the current Pricing page and the plan terms confirmed through Shopify. Do not infer an entitlement from an old Lens, visit-cap, or trial description.

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 stable order-event hooks used for activity matching. The API may return legacy matching labels such as direct, assisted, or influenced; those labels do not establish commercial causation.

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; start merchant recommendation questions with the Recommendation Audit, and use Check, Test, and Verify for supporting technical evidence.