ident.halowerk.com/v1/sms-receive
1.Catalog declaration
| Resource URL | https://ident.halowerk.com/v1/sms-receive |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 6000 |
| Catalog status | active |
| First seen / last seen | 2026-08-26 01:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | POST | pass | 402 | 720 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 352 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 396 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 372 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 325 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 332 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 335 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 409 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 470 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 463 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 337 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 2348 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 381 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 370 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 469 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 440 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 624 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-22 11:25 UTC | POST | pass | 402 | 326 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 333 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-09 11:24 UTC | POST | fail | 400 | 389 ms | no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail. |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 394 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 |
|---|---|---|---|---|
| 09-30 03:312026-09-30 03:31 UTC | settled (nonce-bound) | 200 | 0xeb116783…d485 | 3530 ms |
| 6000 units (≈ $0.006 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/e3ddf1e8-0050-4634-80ae-f741fe13b0cd)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | 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.