PulseGate / Arrivals
Agent Highway
Agents acting for a person first, then the crawlers. One ray is one request, and every row says how we recognised it.
Traffic by lane
Core 7 · Acting for a person
3 of 131,201 IP-verified requests today12 of 50,980 self-declared requests today
Cores 4–6 · Search crawlers …
Today 18,710 IP-verified · 13,494 self-declared
- … in the latest reading2.2% of today's requests with this proofClaude-SearchBotAnthropicIP-verifiedReq/s…TrendShare2.2%
- … in the latest reading0.62% of today's requests with this proofPerplexityBotPerplexityIP-verifiedReq/s…TrendShare0.62%
- Others · 3PetalBot, OAI-SearchBot, YouBotCore 6, 3 more identities in this lane …
Cores 1–3 · Training crawlers …
Today 112,488 IP-verified · 37,474 self-declared
- … in the latest reading56.4% of today's requests with this proofAmazonbotAmazonself-declaredReq/s…TrendShare56.4%
- … in the latest reading16.2% of today's requests with this proofClaudeBotAnthropicIP-verifiedReq/s…TrendShare16.2%
- Others · 2Meta-ExternalAgent, BytespiderCore 3, 2 more identities in this lane …
Parked at the gate
Today: 10 · see allUnverified or turned away 16 unverified claims · 1,340 IP-verified and 9 self-declared requests turned away today
One ray is one request we served, on a core of its lane. It rises onto the cable about 30 seconds after the request reached us and passes the gate 5 seconds later. Counts are exact; where the moment of a request within its reading is not known, it is placed at random.
IP-verified self-declared acting for a personUnverified and turned-away requests are counted, not drawn.Trends fill from when you opened the page.
Runs started today 111 IP-verified · 49 self-declared · Requests since 9 Oct 852,459 IP-verified · 283,438 self-declaredToday is 14 Oct 2026 from 00:00 UTC; the month is counted since 9 Oct, when counting began. Both stay partial until they close. IP-verified and self-declared are counted apart and never added together.
Connect your agent
Read the index the way this page counts you: as a named visitor.
- MCP
https://www.pulsegate.ai/api/mcpStreamable HTTP, no key and no account.- HTTP
GET /api/search?q=…&format=jsonEach candidate links to its record and the sources we read.
The documented endpoints, their limits and the terms are on Access terms. OpenAPI · llms.txt
Acting for a person
Agents that run inside a person's own browser look like Chrome to us and are not counted here.
No arrivals since 15:58 UTC
ChatGPT
ChatGPT
MCP client
MCP client
MCP client
Google-Read-Aloud5 requests
MCP client2 requests
MCP client
ChatGPT
MCP client
MCP client
ChatGPT
Search crawlers
Fetch pages so an assistant or a search engine can answer with them.
YouBot
PerplexityBot802 requests
OAI-SearchBot20 requests
PerplexityBot
PerplexityBot
PerplexityBot11 requests
YouBot
OAI-SearchBot
OAI-SearchBot
YouBot
Claude-SearchBot2,926 requests
YouBot
PetalBot93 requests
YouBot
YouBot
YouBot
Training crawlers
Fetch pages to train models.
Meta-ExternalAgent2 requests
ClaudeBot3,480 requests
ClaudeBot1,337 requests
ClaudeBot5,271 requests
ClaudeBot9 requests
ClaudeBot3,244 requests
ClaudeBot3,232 requests
ClaudeBot2,793 requests
ClaudeBot1,902 requests
Meta-ExternalAgent4 requests
Meta-ExternalAgent
Meta-ExternalAgent
Meta-ExternalAgent
Meta-ExternalAgent6,537 requests
Bytespider2,154 requests
Amazonbot28,774 requests
Times are UTC. A row is one run: one name with no pause longer than 5 minutes, ending at 00:00 UTC. ×N counts its requests.
Unproven and turned away today (UTC): 16 requests claimed an AI name we could not verify · our daily limits turned away 1,340 IP-verified and 9 self-declared requests.
How the cable is drawn
One ray is one request we served. Between two readings of the board, about 15 seconds apart, each run adds the requests it made; a run that started inside that window adds all of them. Each of those requests is a ray on its lane's core of the cable, passing the gate at the moment it reached us. Where that moment is not known within the window, it is placed at random, so the counts are exact and the moments are approximate.
The cable has seven cores. Core 7, by the gate's right leg, carries agents acting for a person, in amber; cores 4 to 6 carry search crawlers and cores 1 to 3 training crawlers: each lane's two busiest identities when you opened the page have a core of their own, and the third core carries the rest of the lane. A ray that only named itself is three points of light; a verified one is a single streak.
Rays rise onto the cable about 30 seconds behind live, so the cable never shows a moment we have not counted yet. When a reading is late the cable waits; when updates are delayed no new ray starts and the cable empties. Requests from runs not listed on the board are drawn too, on the third core of their lane — for agents acting for a person, on core 7. Unverified claims and requests our limits turned away are counted on a line of their own, and not drawn.
When an agent acting for a person passes the gate, its card stays beside it for the rest of the day. A crawler too fast to draw ray by ray travels in trains, and the page says how many requests one ray stands for.
How we recognise visitors
The first column holds visitors acting for a person: chat assistants fetching a page someone asked about, and user-triggered fetchers such as read-aloud services. The other two hold crawlers, which fetch on their operator's schedule rather than for one person.
IP-verified means the request came from an address its operator publishes for that name, checked when the request reached us.
Self-declared means the visitor named itself in its User-Agent and nothing confirmed it. It is shown with that label and never added to the verified figures.
A request that claims an AI name from an address its operator does not publish is not shown under that name. It is counted on the line under the board.
What one row is
One row is one run: the same name with no pause longer than 5 minutes, ending at 00:00 UTC. ×N is the number of requests in the run.
A column shows at most sixteen runs and at most eight of each proof, so self-declared visitors cannot push IP-verified ones off the board.
A request has no goodbye, so a run never leaves the board. After 5 minutes without a request its row keeps the time the run started and adds “Last seen” with the time of its last request; a screen reader also hears the span between the two.
What we cannot see
Responses that Cloudflare serves from its cache never reach our servers, so they are not on this board.
Requests for robots.txt and llms.txt are not recorded.
Agents that run inside a person's own browser send the same signals as Chrome. We cannot tell them from people, so we do not count them.
No page per visitor
This board is the only place a visitor appears. We do not publish a page for each crawler or agent.
