Skip to main content
The Worker connector works on every Cloudflare plan with Workers. It sits on your route, passes each request to your origin unchanged, and, when the request comes from an AI agent, reports it to Quotable after the response is on its way.
If your zone is on Cloudflare Enterprise, use Cloudflare Logpush instead. Logpush is out of band and measures response time; the Worker runs on every request of its route.

How the Worker protects your site

  • Fail open. Telemetry is sent with ctx.waitUntil() after the origin response is returned. A failure is swallowed and never changes the response.
  • No body access. The Worker never reads or clones the response body.
  • Batched. Agent requests are collected for up to 2 seconds, or until 50 are waiting, and sent as one report. One report per batch instead of one per request keeps a busy site well inside the delivery limit.
  • Bounded. Each report has a time budget (3 seconds by default, 5 at most).
  • Circuit breaker. After 5 consecutive failed reports, the Worker stops reporting for 60 seconds, so an outage on our side costs you nothing but skipped reports. Authentication errors (4xx) don’t open the breaker.
  • One hostname. The Worker only reports requests for the hostname you bind it to.

What it measures

Every field except response time. Response size is read from the content-length header, so streamed responses without it report no size. The Worker only reports requests whose user agent matches one of the recognized AI agents. The list is built into each Worker version, so download the latest version to pick up agents added later.

Set up

1

Create the source in Quotable

In Agent Analytics, select Connect source, choose Cloudflare Worker and select Generate credentials. Copy the token, the endpoint URL and the AGENT_ANALYTICS_HOSTNAME value.
2

Download the Worker

Select Download Worker template. You get a single module file, quotable-agent-analytics-worker-v1.3.0.mjs.
3

Configure Wrangler

Create a wrangler.toml next to the file. Replace the hostname, zone and endpoint with your own values:
wrangler.toml
4

Store the token as a secret

Never put the token in wrangler.toml. Store it as a Worker secret:
Paste the aa_live_… token when prompted.
5

Deploy

6

Confirm delivery

Run the self-test below, then select Check now in Quotable. The source turns active on the first AI agent request to your site.

Settings

If one of the three required bindings is missing, the Worker passes traffic through and reports nothing.

Volume limit

A Worker source accepts up to 6,000 reports per 5-minute window, about 20 per second. Version 1.2.0 and later send up to 50 agent requests per report, so the limit is far above what a single site’s AI agent traffic produces. Earlier versions send one report per agent request; update to the latest version if you see 429 responses. Batches are kept per Worker instance, in memory. If Cloudflare stops an instance before its batch is sent, that batch is lost; with the 2-second default this is rare. Above the limit, reports are refused with 429 and the circuit breaker pauses reporting. If that happens, set AGENT_ANALYTICS_SAMPLE_RATE below 1, or use Cloudflare Logpush, which sends batches of up to 1,000 records.

Self-test

Check that the token works and see which version is installed:
The self-test stores nothing. It’s limited to 30 calls per 5 minutes per IP address. A wrong, rotated or disconnected token returns 401.

Update or roll back

When upgrade_available is true, download the template again from the wizard, replace the module file, update main in wrangler.toml and run npx wrangler deploy. To go back to the previous deployment without downtime, run npx wrangler rollback.

Rotate the token

  1. Rotate the token in Quotable. The old token stops working immediately.
  2. Run npx wrangler secret put AGENT_ANALYTICS_TOKEN with the new token.
Reports sent in between are refused with 401. They don’t open the circuit breaker.

Disconnect

Remove the route or delete the Worker in Cloudflare, then disconnect the source in Quotable.

Troubleshooting

Next steps

Cloudflare Logpush

The out-of-band option for Enterprise zones.

How verification works

The Worker sends the visitor IP from cf-connecting-ip for verification.
Last modified on November 18, 2026