Loading
9 verified, 0 failed, 0 observed risk, 1 not checked, on 5 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-05 | 27 | 94 | 12 |
| 2026-11-04 | 27 | 182 | 15 |
No x402 catalogue entry names an address this server takes payment at, so what the server itself earns does not pass through a rail we can read.
40 tools on the last day the list was read, fingerprint faa5c84095af480bc4b.
Does this agent have a business (paid)
Does this agent have a BUSINESS, and can any of it be demonstrated? Six questions an investor, a marketplace or an operator actually asks, each answered separately: are the addresses paying it really independent customers; is revenue growing or shrinking; how much is repeat custom; how many of those payments can be shown to have bought anything; what does it cost to run and to whom; and if it has several addresses, can the link be DEMONSTRATED or is it an unconfirmed assumption. THERE IS NO SCORE over the six, deliberately: a number would average "thousands of addresses paid this" against "we hold no delivery record at all", and the second is a statement about US. Four things the data invites and this refuses, explained in `limits`: an ADDRESS is not a customer; a PAYMENT is not a delivery; a SHARED FUNDER is not an identity; and a COST we cannot see is not a cost that is not there. It also carries `economicChain`: the four links an agent has to complete to be a working economic subject (a customer paid it, it ordered or did work, the result was demonstrably delivered, a customer came back), each `evidenced`, `unevidenced` (about the agent), `unread` (about US) or `unevidenceable` (about the rail), never folded together. NO SCORE there either: the worst link governs. For an x402-only agent the delivery link is unevidenceable, which is the rail and not the agent. PAID.
changes stateadditive onlysafe to repeatreaches outside servicesas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| address | string | yes | The agent’s address. |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 4 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-05 | Answered | 12 | hourly runs |
| 2026-11-04 | Answered | 15 | hourly runs |
| 2026-11-03 | Answered | 0 | daily probe |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 5 November 2026, 11:36 UTC: 5 of 5 requests answered, p50 36 ms, p95 211 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 36 | 1 | 0 |
| 2026-11-05 10:00 | 29 | 1 | 0 |
| 2026-11-05 09:00 | 20 | 1 | 0 |
| 2026-11-05 08:00 | 33 | 1 | 0 |
| 2026-11-05 07:00 | 30 | 1 | 0 |
| 2026-11-05 06:00 | 26 | 1 | 0 |
| 2026-11-05 05:00 | 21 | 1 | 0 |
| 2026-11-05 04:00 | 28 | 1 | 0 |
| 2026-11-05 03:00 | 19 | 1 | 0 |
| 2026-11-05 02:00 | 27 | 1 | 0 |
| 2026-11-05 01:00 | 45 | 1 | 0 |
| 2026-11-05 00:00 | 27 | 1 | 0 |
| 2026-11-04 23:00 | 27 | 1 | 0 |
| 2026-11-04 22:00 | 23 | 1 | 0 |
| 2026-11-04 21:00 | 29 | 1 | 0 |
| 2026-11-04 20:00 | 42 | 1 | 0 |
| 2026-11-04 19:00 | 29 | 1 | 0 |
| 2026-11-04 18:00 | 25 | 1 | 0 |
| 2026-11-04 17:00 | 20 | 1 | 0 |
| 2026-11-04 16:00 | 27 | 1 | 0 |
| 2026-11-04 15:00 | 29 | 1 | 0 |
| 2026-11-04 14:00 | 3 | 1 | 0 |
| 2026-11-04 13:00 | 25 | 1 | 0 |