onchainpulse.theaslangroupllc.com/api/token-safety
1.Catalog declaration
| Resource URL | https://onchainpulse.theaslangroupllc.com/api/token-safety |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc |
| Declared price (base units) | 15000 |
| Catalog status | active |
| First seen / last seen | 2026-08-22 01:53 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 473 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 616 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 190 ms | — |
| 2026-10-04 10:30 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-27 10:30 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 138 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
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 |
|---|---|---|---|---|
| 10-18 03:312026-10-18 03:31 UTC | settled (nonce-bound) | 200 | 04895B0B43…8CED | 6570 ms |
| 15000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-10 05:002026-10-10 05:00 UTC | settled (nonce-bound) | 200 | 0x67a901c5…ca2a | 2183 ms |
| 15000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/90b0565f-6fd1-4a4b-a49f-c72860e98044)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.