x402.twit.sh/tweets/retweeted_by
1.Catalog declaration
| Resource URL | https://x402.twit.sh/tweets/retweeted_by |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x9dba414637c611a16bea6f0796bfcbcbdc410df8 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-10-01 01:03 UTC / 2026-11-16 01:30 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-13 16:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-11-11 13:40 UTC | GET | pass | 402 | 246 ms | — |
| 2026-11-09 04:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-11-06 22:40 UTC | GET | pass | 402 | 231 ms | — |
| 2026-11-04 16:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-11-01 16:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-10-30 16:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-10-28 22:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-10-27 00:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-10-25 06:40 UTC | GET | pass | 402 | 2046 ms | — |
| 2026-10-23 04:40 UTC | GET | pass | 402 | 2026 ms | — |
| 2026-10-21 16:40 UTC | GET | pass | 402 | 2217 ms | — |
| 2026-10-20 10:30 UTC | GET | pass | 402 | 221 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 278 ms | — |
3.L1 — real purchases
14 of 14 paid attempts settled on-chain, and 14 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 11-12 15:322026-11-12 15:32 UTC | settled (nonce-bound) | 200 | 0x340596f5…46ea | Base | 2040 ms |
| 10000 units (≈ $0.01 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
| 11-07 18:022026-11-07 18:02 UTC | settled (nonce-bound) | 200 | 0x9cb17e91…2e8e | Base | 1696 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 11-06 15:322026-11-06 15:32 UTC | settled (nonce-bound) | 200 | 0x4b3c862a…94c8 | Base | 1988 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 11-04 21:322026-11-04 21:32 UTC | settled (nonce-bound) | 200 | 0x542f9615…81f6 | Base | 1626 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 11-01 18:022026-11-01 18:02 UTC | settled (nonce-bound) | 200 | 0x06e99029…c884 | Base | 1712 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-31 12:022026-10-31 12:02 UTC | settled (nonce-bound) | 200 | 0xc8a3c0e8…2dea | Base | 1812 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-29 21:322026-10-29 21:32 UTC | settled (nonce-bound) | 200 | 0x990c22c1…c256 | Base | 1451 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-28 18:022026-10-28 18:02 UTC | settled (nonce-bound) | 200 | 0xfbcfc8a4…d7d9 | Base | 1991 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-26 23:322026-10-26 23:32 UTC | settled (nonce-bound) | 200 | 0x5800f8ef…cf12 | Base | 1273 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-25 17:312026-10-25 17:31 UTC | settled (nonce-bound) | 200 | 0x7af5b49a…eebf | Base | 2121 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-24 15:322026-10-24 15:32 UTC | settled (nonce-bound) | 200 | 0x90ba6ce4…f02e | Base | 1389 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-23 12:022026-10-23 12:02 UTC | settled (nonce-bound) | 200 | 0x4122cf69…e52d | Base | 1383 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-22 09:312026-10-22 09:31 UTC | settled (nonce-bound) | 200 | 0x92fdadeb…dc49 | Base | 1309 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-21 00:012026-10-21 00:01 UTC | settled (nonce-bound) | 200 | 0xa5f8cf12…9a77 | Base | 1764 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 14/14 settled · 14 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/9b4214ca-077d-40e5-8eff-ef57652c97bd)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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.