AgenstryBot

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-01 04:28:51Z to 2026-09-01 04:28:51Z UTC.

AgenstryBot/0.3.0 (+https://agenstry.com/bot)

6 request(s) from 1 distinct address(es), 6 distinct path(s), first seen 2026-09-01 04:28:51Z, last seen 2026-09-01 04:28:51Z UTC. 1 separate visit(s), counting a gap of more than 30 minutes as a new one.

The user-agent strings, exactly as they arrived

user-agentrequestsaddressesfirst seenlast seen
AgenstryBot/0.3.0 (+https://agenstry.com/bot)612026-09-01 04:28:51Z2026-09-01 04:28:51Z

What it asked for, in the order it asked

First request to each path, oldest first.

#pathat (UTC)status
1/robots.txt2026-09-01 04:28:51Z200
2/.well-known/agent-card.json2026-09-01 04:28:51Z200
3/a2a2026-09-01 04:28:51Z200
4/.well-known/x4022026-09-01 04:28:51Z404
5/.well-known/mpp2026-09-01 04:28:51Z404
6/.well-known/payment-manifest2026-09-01 04:28:51Z404

Everything it asked for

pathrequestsstatus codesfirstlast
/.well-known/agent-card.json1200×12026-09-01 04:28:51Z2026-09-01 04:28:51Z
/.well-known/mpp1404×12026-09-01 04:28:51Z2026-09-01 04:28:51Z
/.well-known/payment-manifest1404×12026-09-01 04:28:51Z2026-09-01 04:28:51Z
/.well-known/x4021404×12026-09-01 04:28:51Z2026-09-01 04:28:51Z
/a2a1200×12026-09-01 04:28:51Z2026-09-01 04:28:51Z
/robots.txt1200×12026-09-01 04:28:51Z2026-09-01 04:28:51Z

What it asked for that did not exist

path it asked forwhat it gotfirst askedsince then
/.well-known/x402404×12026-09-01 04:28:51Zanswers 200 since 2026-09-01 05:29:00Z
/.well-known/mpp404×12026-09-01 04:28:51Zstill absent
/.well-known/payment-manifest404×12026-09-01 04:28:51Zstill absent

What it got, and what it sent

Status codes
200×3, 404×3
Accept headers
application/json
Bytes served
18999
Attributed to a channel
none — it arrived at a plain path
Our instrument classed it
crawler×6 — 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://agenstry.com/bot 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/agenstrybot.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

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-01 04:28:51Z to 2026-09-01 04:28:51Z 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.