Analytics and short links for the sites you generate
A site generator adds a site through the API, puts its counter into the pages it builds and reads the totals back. Each counter runs in the Cloudflare account its site is served from.
No shared footprint
Every site gets its own path, file names and snippet code, generated from a random seed, and no third-party host appears: no signature in the page, the URLs or the answers is shared by clx sites or names clx. What stays visible, plainly: a same-origin POST on each page view, answered with an empty 204, and the browser’s own API names.
Made for build pipelines
Every write takes an idempotency key: a write that went through, sent again with the same key within 24 hours, does not make its change twice. A key gets only the scopes it needs — a pipeline needs sites and reports.
Many customers, one integration
The API plan covers 50 Cloudflare accounts, 500 sites and 10,000 links with five keys; a key can be limited to some accounts and client IPs, so one customer’s key cannot reach another’s.
Works with Cloudflare Pages
The counter’s route sits on the site’s own host, beside a Pages site, and passes everything else through. The account’s use is measured daily, and the API tells you when a customer should move to Workers Paid.
Three steps in a build
Once the customer’s Cloudflare account is connected: add the site once, embed its snippet in every page, read the report when you need it. The full contract is in the API reference.
# 1. add the site (scope: sites)
curl https://clx.cx/v1/sites \
-H "Authorization: Bearer clx_…" \
-H "Idempotency-Key: build-42-example.com" \
-H "Content-Type: application/json" \
-d '{"account_id":"…","host":"example.com"}'
# → 202 { "site": { "id": "…", "snippet": { "inline": "<script>…</script>", … } } }
# 2. put snippet.inline into the <head> of every page you build
# 3. read the totals (scope: reports)
curl "https://clx.cx/v1/sites/{id}/report?period=7d" -H "Authorization: Bearer clx_…"Questions
Do my customers need their own Cloudflare accounts?
Yes: a counter runs in the account its site is served from. A customer connects it once with a bootstrap token, by hand or through your integration.
Can footprint scanners or ad blockers spot clx?
No signature in the page, the URLs or the answers is shared by clx sites or names clx, beyond the browser’s own API names. Someone watching can still see the behaviour — a same-origin POST answered with an empty 204.
Is there an SDK?
No: the API is plain HTTP with an OpenAPI contract, and AI agents have a walkthrough of their own.
What does it cost?
The API plan is switched on by request and is free for now; Workers Paid is never required.