test.x402labs.sh/v1/scraping/scrape
1.Catalog declaration
| Resource URL | https://test.x402labs.sh/v1/scraping/scrape |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:84532 |
| Receiving address | 0x3fd04211963f79be7e5356438680542aa97b089f |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-30 01:03 UTC) |
| First seen / last seen | 2026-08-16 01:07 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 11 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 07:38 UTC | POST | unverified | 400 | 1322 ms | request_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-09-27 10:30 UTC | POST | fail | 400 | 567 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-22 11:24 UTC | POST | fail | 400 | 516 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-18 11:24 UTC | POST | fail | 400 | 230 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-16 11:24 UTC | POST | fail | 400 | 492 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-12 11:24 UTC | POST | fail | 400 | 489 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-08 11:24 UTC | POST | fail | 400 | 580 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-04 11:24 UTC | POST | fail | 400 | 593 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-01 23:14 UTC | POST | fail | 400 | 484 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-01 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-31 | 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.