State of agent traffic · October 2026
What visits a developer-tools site, counted first-hand.
One site that invites agents, every request classified against the Atlas registry, identity claims checked against what operators publish, rolled up nightly. This edition covers 2026-09-28 to 2026-10-08 and updates every night.
Markdown · JSON · Daily data
Findings
- 01Over 11 days, 2026-09-28 to 2026-10-08, overwing.ai answered 49,293 requests from 579 distinct User-Agent strings, about 521 distinct clients a day.
- 02Registered agents made 11.7% of requests. Software that names itself but is in no registry made 54.4%, generic HTTP libraries 21%, and browsers 7.6%.
- 0346 registered agents were seen. The ten busiest made 86.1% of agent requests; the busiest was Agent402 with 2,621 requests on 11 of 11 days.
- 04By purpose, Search / retrieval index 68.5%, Training / bulk crawl 16.2%, Other / undocumented 14.3% of agent requests.
- 053,247 agent requests claimed an identity that could be checked against the operator's published IP ranges, reverse DNS or signing keys: 176 (5.4%) were confirmed, 2 contradicted the claim, and the rest could not be confirmed either way.
- 06Among discovery files, automated clients asked most for the MCP endpoint (12,708), x402 payment terms (12,352), .well-known discovery files (7,578), the OpenAPI document (1,947).
- 07Of 13,904 requests with a recorded answer, 17.5% were refused with a client error other than a payment request.
- 08In the last seven days 463 distinct User-Agent strings were seen; 241 (52.1%) had not appeared earlier in the period. The registry holds 312 published agents, with 0 self-named strings waiting for review.
- 09On the readiness panel, 29 developer-tool sites were checked in the latest week: the median score was 67 of 100, 93.1% publish llms.txt, 37.9% have a hosted MCP endpoint that answers, and 0 score 90 or more.
Who sends the requests
| Kind of client | Requests | Share | Distinct User-Agents |
|---|---|---|---|
| Registered agents | 5,770 | 11.7% | 63 |
| Software that names itself but is not in the registry | 26,813 | 54.4% | 453 |
| Generic HTTP libraries | 10,340 | 21% | 46 |
| Browsers | 3,744 | 7.6% | 1 |
| Overwing SDKs and tools | 1,597 | 3.2% | 15 |
| Requests with no User-Agent | 1,029 | 2.1% | 1 |
The busiest registered agents
| Agent | Operator | Purpose | Days | Requests | Share | Identity |
|---|---|---|---|---|---|---|
| Agent402 | Agent402 | Search / retrieval index | 11 | 2,621 | 45.4% | 0 of 1534 verified |
| BrickBlueBot | brick.blue | Search / retrieval index | 10 | 627 | 10.9% | 0 of 405 verified |
| Meta-ExternalAgent | Meta | Training / bulk crawl | 6 | 440 | 7.6% | 0 of 188 verified |
| ClaudeBot | Anthropic | Training / bulk crawl | 11 | 294 | 5.1% | 0 of 164 verified |
| AgenstryBot | Agenstry | Search / retrieval index | 10 | 285 | 4.9% | 0 of 165 verified |
| forum-labs-trust-prober | Forum Labs | Other / undocumented | 11 | 223 | 3.9% | 0 of 76 verified |
| GolemreachTrustBot | Golemreach | Other / undocumented | 9 | 136 | 2.4% | 0 of 96 verified |
| Amazonbot | Amazon | Training / bulk crawl | 10 | 123 | 2.1% | 73 of 73 verified |
| agentprobe | agentprobe.org | Other / undocumented | 10 | 118 | 2% | 0 of 72 verified |
| x402watch | x402watch | Other / undocumented | 11 | 100 | 1.7% | 0 of 61 verified |
By purpose
| Purpose | Agents | Requests | Share |
|---|---|---|---|
| Search / retrieval index | 17 | 3,955 | 68.5% |
| Training / bulk crawl | 7 | 932 | 16.2% |
| Other / undocumented | 13 | 823 | 14.3% |
| User-triggered fetcher | 5 | 33 | 0.6% |
| Autonomous / browser agent | 3 | 20 | 0.3% |
| Coding agent | 1 | 7 | 0.1% |
What automated clients asked for
| Asked for | Requests |
|---|---|
| the MCP endpoint | 12,708 |
| x402 payment terms | 12,352 |
| .well-known discovery files | 7,578 |
| the REST API | 6,358 |
| HTML pages | 2,130 |
| the OpenAPI document | 1,947 |
| the A2A endpoint | 1,051 |
| robots.txt | 707 |
| llms.txt | 463 |
| the sitemap | 172 |
| markdown versions of pages | 83 |
How ready developer tools are
Week by week, with every measure: /atlas/readiness. Check your own site: /beacon.
Method
Every request to overwing.ai is classified against the Atlas registry and rolled up nightly by day and User-Agent, with addresses hashed and no request bodies kept. Identity is checked against IP ranges, reverse DNS and signing keys the operator publishes. Registered agents are counted by registry agent; everything else by User-Agent string. One site, so the shares describe a developer-tools site that invites agents, not the web. The readiness panel is the same Beacon check run weekly on a fixed list of developer-tool sites.
Cite as: Overwing Atlas, State of agent traffic, October 2026, overwing.ai/atlas/traffic, data to 2026-10-08. The daily rows behind it are free at /api/v1/atlas/sightings; the registry at /atlas.