api.slamai.dev/token/price
1.Catalog declaration
| Resource URL | https://api.slamai.dev/token/price |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0xd85096faec1ac03075667b4c1a1661f5623bf111 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 13:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 740 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 482 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 589 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 487 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 516 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 416 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 815 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 593 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 565 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 538 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 406 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 514 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 296 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 859 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 414 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 471 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 359 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 269 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 no_declaration- the listing declares no output schema to check the response against.
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-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0xc75de229…02e7 | 1247 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-01 12:082026-09-01 12:08 UTC | settled (amount + payee) | 200 | 0x2025ea72…5ef4 | 1509 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-25 12:542026-08-25 12:54 UTC | settled (amount + payee) | 200 | 0xfdfced4f…94e6 | 1040 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose 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/0cb38b1f-2dd0-43c8-9079-e37c2fac41d1)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | 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
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.