gateway.sanfoundation.com/x402/v1/agents
1.Catalog declaration
| Resource URL | https://gateway.sanfoundation.com/x402/v1/agents |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x16b5fe729f2ca544b309844f75e8429ab45151ae |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-10-06 01:01 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-05 22:40 UTC | GET | fail | 404 | 279 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 616 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 417 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 363 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 2296 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 224 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 185 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-26 00:012026-09-26 00:01 UTC | settled (nonce-bound) | 200 | 0x4f767334…9bd6 | Base | 2510 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered)Stage: delivered | |||||
| 09-19 18:002026-09-19 18:00 UTC | settled (nonce-bound) | 200 | 0x873bb2a5…7fe5 | Base | 2376 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered)Stage: delivered | |||||
| 09-13 00:002026-09-13 00:00 UTC | settled (nonce-bound) | 200 | 0x83d3c4bd…1ea9 | Base | 2394 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered)Stage: delivered | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/6df0f511-353f-427f-81c0-cef9e8d263dd)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | delisted | {"status":"active"} | {"status":"delisted"} |
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.