agent402.tools/v1/rerank
1.Catalog declaration
| Resource URL | https://agent402.tools/v1/rerank |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-20 01:30 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 62 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | POST | pass | 402 | 344 ms | — |
| 2026-10-04 10:30 UTC | POST | pass | 402 | 98 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 114 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 85 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 233 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 138 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 109 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 191 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 of those also returned a 2xx response (delivered). 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 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_claimed- the seller returned a receipt that vet402 has not re-read on-chain yet.
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 10-20 15:302026-10-20 15:30 UTC | settle_claimed | 200 | 0x6fa321ba…dbcd | 3654 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: not sorted: awaiting on-chain verification | ||||
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.