Quickstart

Sign up as a content owner and add your domain. You verify ownership by serving a .well-known/openattribution.json file (or a DNS TXT record). Once verified you get an API key that looks like oat_pub_..., scoped to write telemetry for that domain. Keep it handy for step 2.

The same key, with read scope, is what powers your dashboard - so you query your own telemetry through the API too.

The open source Worker detects AI bot requests at the edge and reports them. Apache 2.0, single file, no build step.

git clone https://github.com/openattribution-org/cloudflare-worker
cd cloudflare-worker
npm install

# Copy the template - you edit this next
cp wrangler.example.toml wrangler.toml

In wrangler.toml, set routes to the hostnames the Worker should run on and the zone id from your Cloudflare dashboard:

routes = [
  { pattern = "example.com/*", zone_id = "your-zone-id" }
]

[vars]
OA_TELEMETRY_ENDPOINT = "https://telemetry.openattribution.org/events"

Then store your API key as a secret (never in the toml) and deploy:

npx wrangler secret put OA_API_KEY     # paste your oat_pub_ key

npx wrangler deploy

Hit one of your own pages with a bot user agent, then open your dashboard:

curl -A "GPTBot/1.2 (+https://openai.com/gptbot)" https://example.com/

Within a few seconds you should see a content_retrieved event for that URL, with source_role: edge. After that, real AI crawlers and assistants show up on their own as they visit. Low-traffic sites see a trickle, not a stream - give it days, not minutes.