Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-06 · today

vaaya.ai/api/run/modal/sandbox-create

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://vaaya.ai/api/run/modal/sandbox-create
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x7c655d3d3944bd27994dd81a036c3afb19806c40
Declared price (base units)250000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-06 07:55 UTC
Catalog-reported calls / payers (30d)7 / 2

2.Probe history

2026-09-152026-10-06
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-06 04:41 UTCPOSTfail402118 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-10-04 22:40 UTCPOSTfail40250 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-10-04 04:40 UTCPOSTfail402465 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-10-03 04:40 UTCPOSTfail402272 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-10-02 13:40 UTCPOSTfail402104 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-10-01 16:40 UTCPOSTfail402106 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-09-30 22:40 UTCPOSTfail402134 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-09-30 04:40 UTCPOSTfail402277 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-09-29 10:30 UTCPOSTfail402174 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-09-29 07:38 UTCPOSTfail402190 msprice_mismatchDeclared 250000 of 0x8335…2913; the 402 offered 50000 of 0x8335…2913.
2026-09-28 22:40 UTCPOSTfail402455 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-28 04:40 UTCPOSTfail402301 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 13:40 UTCPOSTfail4021018 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 16:40 UTCPOSTfail402163 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 22:40 UTCPOSTfail402241 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 04:40 UTCPOSTfail402285 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 13:40 UTCPOSTfail402190 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 16:40 UTCPOSTfail40274 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 22:40 UTCPOSTfail402470 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 04:40 UTCPOSTfail402432 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 13:40 UTCPOSTfail402250 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 16:40 UTCPOSTfail402253 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 22:40 UTCPOSTfail402119 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 13:40 UTCPOSTfail402114 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 16:40 UTCPOSTfail40240 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 22:40 UTCPOSTfail40297 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 04:40 UTCPOSTfail402134 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 16:40 UTCPOSTfail402279 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 16:40 UTCPOSTfail402179 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 04:40 UTCPOSTfail40297 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far

vaaya.ai/api/run/modal/sandbox-create — x402 purchase and probe record | vet402