2s.io/api/gov/osha-violations
1.Catalog declaration
| Resource URL | https://2s.io/api/gov/osha-violations |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x2b6d4988db4723e6908db86ab2b8dfbc51fc32c5 |
| Declared price (base units) | 3000 |
| Catalog status | delisted (since 2026-09-26 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-25 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-25 22:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 541 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 102 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 32 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 686 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 632 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 284 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 50 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 256 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 (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 |
|---|---|---|---|---|
| 08-27 12:302026-08-27 12:30 UTC | settled (amount + payee) | 200 | 0x25712499…7eeb | 4934 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-20 12:542026-08-20 12:54 UTC | settled (amount + payee) | 200 | 0x0205867d…9552 | 12471 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 09:542026-08-14 09:54 UTC | settled (amount + payee) | 200 | 0x4792f298…6b39 | 3359 ms |
| 3000 units (≈ $0.003 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/e75c0bf7-6ccb-416e-bb44-431419cd42e4)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-26 | 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.