Tokens
Track, visualize, and compete on AI coding assistant token usage across Claude Code, Cursor, OpenCode, Codex, Gemini, Kimi, and Qwen. The Kardashev Scale for AI Devs.
Tracking AI traffic and agent activity on the public internet
DataTypeScript · CSSGitHub @eshin087OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Tracking autonomous AI agents on the public internet: a live report and data explorer
Loading the full README. The saved excerpt is shown below.
An observatory of AI traffic and agent activity across external public sources, with the original Agents → destinations animation, multi-year census line graphs and a daily GitHub heatmap.
Each source covers a different part of the internet; counts cannot be added into a whole-internet AI activity total. Source classifications and attribution evidence stay attached to each measurement. Local visitor tracking and dashboards are retired; existing history is not deleted.Read the full README ↗How much of the public internet is now AI agents, measured from public sources that can be checked.
Live at gcdtracker.vercel.app.
It follows crawlers reading the web, coding agents opening pull requests on GitHub, and automated edits to Wikipedia, OpenStreetMap and public forums. Each number stays tied to the source it came from and to the rule used to attribute it to an agent, so the site never adds unlike things into one "AI share of the internet".
Everyone has an opinion on how much of the web is bots now, and almost nobody shows their evidence. I wanted a place where the counts, the attribution rules and the gaps in coverage are all visible on the same page, so that a reader can judge the claim rather than take it.
| Area | Evidence |
|---|---|
| Traffic | Cloudflare Radar snapshots, AI crawler-purpose shares and sampled robots.txt policy |
| Social publishing | Bounded Bluesky and Mastodon samples, disclosure text signals, separate automation flags and coverage |
| GitHub | GH Archive observations, documented bot accounts, branch-name signals, watched repositories |
| Wikipedia and Commons | Platform filters, disclosed heuristics, bot activity, files added to tracked AI categories |
| Maps | Capped overlapping OSM creation-time samples with deduplication |
| Forums | Platform-reported public activity on Moltbook |
| Tooling | Package downloads, MCP registry entries, quoted external series |
| Before & After and Notes | Historical context; time correlation does not establish causation |
The census view puts multi-year series side by side, such as Wikipedia pageviews by user, spider and automated traffic, with model launches marked for context:
A claimed crawler name, branch prefix, edit filter or platform assertion does not prove model authorship. Public HTML, JSON and CSV use explicit field allowlists; raw IP addresses are never persisted, and saved bookmarks stay in the reader's browser. Local visitor tracking is retired; historical summaries remain available, and some detailed records expire under the retention policy.
Tech: Next.js 16, React 19, TypeScript, Tailwind 4, Drizzle with Neon, Vercel.
npm ci
npm run dev
npm run lint
npm run typecheck
npm test
npm run build
Without a configured database, the site renders an explicit offline state.
Code: MIT. Project data exports: CC BY 4.0, subject to underlying source rights. Quoted sources retain their publishers' licences; Radar data has its own licence. Fonts: SIL OFL. Public third-party metadata links to its source; inclusion implies no endorsement or finding of misconduct.
Do not report suspected vulnerabilities in a public issue. Use GitHub private vulnerability reporting or contact the repository owner privately. Never include credentials, private request evidence, or production data in a report.