Waggle

What this client asked www.pathwren.workers.dev for, when, and what it got. Every number below is from this host's own server-side request log, 2026-09-02 04:15:47Z to 2026-09-02 05:35:58Z UTC.

Waggle/1.0 (+https://waggle.zone)

11 request(s) from 3 distinct address(es), 9 distinct path(s), first seen 2026-09-02 04:15:47Z, last seen 2026-09-02 05:35:58Z UTC. 2 separate visit(s), counting a gap of more than 30 minutes as a new one, median 80.2 minutes between them.

The user-agent strings, exactly as they arrived

user-agentrequestsaddressesfirst seenlast seen
Waggle/1.0 (+https://waggle.zone)1132026-09-02 04:15:47Z2026-09-02 05:35:58Z

What it asked for, in the order it asked

First request to each path, oldest first.

#pathat (UTC)status
1/a2a/.well-known/agent-card.json2026-09-02 04:15:47Z404
2/a2a/.well-known/agent.json2026-09-02 04:15:47Z404
3/mcp/triage/.well-known/agent-card.json2026-09-02 04:15:58Z404
4/mcp/triage/.well-known/agent.json2026-09-02 04:15:59Z404
5/.well-known/agent-card.json2026-09-02 04:16:03Z200
6/apis.json/.well-known/agent-card.json2026-09-02 04:16:06Z404
7/apis.json/.well-known/agent.json2026-09-02 04:16:06Z404
8/.well-known/api-catalog/.well-known/agent-card.json2026-09-02 04:16:15Z404
9/.well-known/api-catalog/.well-known/agent.json2026-09-02 04:16:15Z404

Everything it asked for

pathrequestsstatus codesfirstlast
/.well-known/agent-card.json3200×32026-09-02 04:16:03Z2026-09-02 05:35:58Z
/.well-known/api-catalog/.well-known/agent-card.json1404×12026-09-02 04:16:15Z2026-09-02 04:16:15Z
/.well-known/api-catalog/.well-known/agent.json1404×12026-09-02 04:16:15Z2026-09-02 04:16:15Z
/a2a/.well-known/agent-card.json1404×12026-09-02 04:15:47Z2026-09-02 04:15:47Z
/a2a/.well-known/agent.json1404×12026-09-02 04:15:47Z2026-09-02 04:15:47Z
/apis.json/.well-known/agent-card.json1404×12026-09-02 04:16:06Z2026-09-02 04:16:06Z
/apis.json/.well-known/agent.json1404×12026-09-02 04:16:06Z2026-09-02 04:16:06Z
/mcp/triage/.well-known/agent-card.json1404×12026-09-02 04:15:58Z2026-09-02 04:15:58Z
/mcp/triage/.well-known/agent.json1404×12026-09-02 04:15:59Z2026-09-02 04:15:59Z

What it asked for that did not exist

path it asked forwhat it gotfirst askedsince then
/a2a/.well-known/agent-card.json404×12026-09-02 04:15:47Zanswers 200 since 2026-09-02 06:00:31Z
/a2a/.well-known/agent.json404×12026-09-02 04:15:47Zanswers 200 since 2026-09-02 06:00:31Z
/mcp/triage/.well-known/agent-card.json404×12026-09-02 04:15:58Zstill absent
/mcp/triage/.well-known/agent.json404×12026-09-02 04:15:59Zstill absent
/apis.json/.well-known/agent-card.json404×12026-09-02 04:16:06Zstill absent
/apis.json/.well-known/agent.json404×12026-09-02 04:16:06Zstill absent
/.well-known/api-catalog/.well-known/agent-card.json404×12026-09-02 04:16:15Zstill absent
/.well-known/api-catalog/.well-known/agent.json404×12026-09-02 04:16:15Zstill absent

What it got, and what it sent

Status codes
404×8, 200×3
Accept headers
application/json
Bytes served
37055
Attributed to a channel
none — it arrived at a plain path
Our instrument classed it
agent×11 — that is our classifier's label from the user-agent, not the operator's, and it has been wrong before.

How to verify it is really them

Not observed. This client publishes no address list we could read and no reverse-DNS convention we could test, so the user-agent is the only identity it has here — and a user-agent is a claim, not a proof. Anyone can send this string.

What it publishes about you afterwards

Not observed. We have not seen this client publish a grade, a listing or a record about this host anywhere, and we make no claim that it does or does not.

Its own documentation

It names https://waggle.zone in its own user-agent. That is the operator's own claim about itself; we neither endorse nor verify what is on it.

This page as data

curl -s https://www.pathwren.workers.dev/bot/waggle.json
curl -s https://www.pathwren.workers.dev/data/observed-clients.json   # every client, one request

JSON · markdown · all clients seen here · index as JSON · check a crawler yourself, no key

Method, and what this page will not say

Rows come from a server-side log written before anything is served, so clients that run no JavaScript are counted exactly like browsers. The window is the whole life of the log, 2026-09-02 04:15:47Z to 2026-09-02 05:35:58Z UTC, and it is stated on every number because a count without a window is not a fact. Addresses are stored as salted hashes and counted, never printed. Our own checks send X-Self: 1 and are excluded, together with every request the analyst flagged as one of our own agents reaching for a URL through a model provider's fetch tool (the numbers are on the index). Nothing here is a claim about intent: where this page does not know something it says not observed.