twitter.use.x402atlas.com/community-details
1.Catalog declaration
| Resource URL | https://twitter.use.x402atlas.com/community-details |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x51d577c8cbb8b3fb1ba0ce31c7923cc27a07f78b |
| Declared price (base units) | 6000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 530 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 2071 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 27 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 39 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 50 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 42 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 1994 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 15 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 7 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 18 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 1897 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 128 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
L2 mismatch- the response lacked 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-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0x310a8ca7…3aef | 789 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 08-30 12:082026-08-30 12:08 UTC | settled (amount + payee) | 200 | 0xd5d90d40…7536 | 670 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-23 12:432026-08-23 12:43 UTC | settled (amount + payee) | 200 | 0x0c8e6c92…237c | 689 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-16 12:502026-08-16 12:50 UTC | settled (amount + payee) | 200 | 0x10948443…9fae | 7902 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/6d02df57-5c4b-4ddd-9ee0-fb684fb123c8)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.