blockrun.ai/api/v1/modal/sandbox/create
1.Catalog declaration
| Resource URL | https://blockrun.ai/api/v1/modal/sandbox/create |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xe9030014f5dae217d0a152f02a043567b16c1abf |
| Declared price (base units) | 11000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 11 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 421 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 166 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 518 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 238 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 481 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 285 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 332 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 185 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 64 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 290 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 203 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 122 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 124 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 697 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 68 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 1735 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 344 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 94 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 65 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 1625 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 151 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 465 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 99 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 86 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 match- the response had the fields the listing's output schema declares.
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 |
|---|---|---|---|---|
| 09-16 18:012026-09-16 18:01 UTC | settled (nonce-bound) | 200 | 0x73732e20…d893 | 2572 ms |
| 11000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 07:022026-09-10 07:02 UTC | settled (nonce-bound) | 200 | 0xe71fd533…13a4 | 2584 ms |
| 11000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 07:022026-09-02 07:02 UTC | settled (amount + payee) | 200 | 0xb26fbaab…e4e7 | 2395 ms |
| 11000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/132e564c-66e4-44eb-834c-f6efec052c39)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.