agentpaystore.com/duke/api/query
1.Catalog declaration
| Resource URL | https://agentpaystore.com/duke/api/query |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x367f1b3d8ca90d1e087481a9a40d585bf3451a03 |
| Declared price (base units) | 150000 |
| Catalog status | active |
| First seen / last seen | 2026-08-30 01:02 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 13:40 UTC | POST | pass | 402 | 420 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 204 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 95 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 349 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 139 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 288 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 472 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 170 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 262 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 83 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 489 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 147 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 100 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 224 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 229 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 282 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 247 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 121 ms | — |
| 2026-09-09 14:40 UTC | POST | pass | 402 | 84 ms | — |
| 2026-09-08 23:40 UTC | POST | pass | 402 | 154 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
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.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-05 07:012026-09-05 07:01 UTC | settle_failed | 402 | — | 223 ms |
| 150000 units (≈ $0.15 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
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. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.
About the purchase at 2026-09-05T07:01:36Z (UTC). The form starts with that time; add what you saw instead.