api.delx.ai/api/v1/x402/rot13
1.Catalog declaration
| Resource URL | https://api.delx.ai/api/v1/x402/rot13 |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x9f8bd9875b3e0b632a24a3a7c73f7787175e73a2 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-09-18 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-17 12:35 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-16 11:24 UTC | POST | pass | 402 | 386 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 436 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 129 ms | — |
| 2026-09-03 11:24 UTC | POST | pass | 402 | 130 ms | — |
| 2026-08-31 11:24 UTC | POST | fail | 402 | 383 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-18 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-19 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-16 | 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.