agents.vimmerse.co/v2/video/reference-to-video
1.Catalog declaration
| Resource URL | https://agents.vimmerse.co/v2/video/reference-to-video |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x14a0307b544c3d2359e673316261e7df5e58eb48 |
| Declared price (base units) | 1200000 |
| Catalog status | active |
| First seen / last seen | 2026-10-27 13:05 UTC / 2026-11-06 18:06 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-11 22:40 UTC | POST | fail | 401 | 324 ms | no_402HTTP 401 instead of 402 to an unpaid POST. |
| 2026-11-09 16:40 UTC | POST | unverified | 422 | 493 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-11-07 13:40 UTC | POST | unverified | 422 | 240 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-11-05 13:40 UTC | POST | unverified | 422 | 520 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-11-02 13:40 UTC | POST | unverified | 422 | 376 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-10-31 04:40 UTC | POST | unverified | 422 | 512 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-10-29 13:40 UTC | POST | unverified | 422 | 902 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. 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.