Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-15 · 1 day ago

x402.twit.sh/users/followers

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402.twit.sh/users/followers
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x9dba414637c611a16bea6f0796bfcbcbdc410df8
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-11-16 01:30 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-10-012026-11-15
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-15 13:40 UTCGETpass402578 ms—
2026-11-12 04:40 UTCGETpass402106 ms—
2026-11-10 04:40 UTCGETpass402131 ms—
2026-11-07 22:40 UTCGETpass402240 ms—
2026-11-05 16:40 UTCGETpass4022093 ms—
2026-11-02 16:40 UTCGETpass402147 ms—
2026-10-31 16:40 UTCGETpass402117 ms—
2026-10-29 16:40 UTCGETpass402370 ms—
2026-10-27 16:40 UTCGETpass402414 ms—
2026-10-26 00:40 UTCGETpass402276 ms—
2026-10-23 22:40 UTCGETpass402184 ms—
2026-10-22 13:40 UTCGETpass4022072 ms—
2026-10-20 22:40 UTCGETpass402382 ms—
2026-10-19 13:40 UTCGETpass402504 ms—
2026-10-17 22:40 UTCGETpass402216 ms—
2026-10-16 15:40 UTCGETpass402510 ms—
2026-10-15 03:40 UTCGETpass402466 ms—
2026-10-13 21:40 UTCGETpass402690 ms—
2026-10-12 15:40 UTCGETpass402788 ms—
2026-10-11 15:40 UTCGETpass402344 ms—
2026-10-10 15:40 UTCGETpass402471 ms—
2026-10-09 12:40 UTCGETpass402165 ms—
2026-10-08 04:40 UTCGETpass402263 ms—
2026-10-07 04:40 UTCGETpass402121 ms—
2026-10-06 13:40 UTCGETpass402181 ms—
2026-10-04 22:40 UTCGETpass402164 ms—
2026-10-04 04:40 UTCGETpass402404 ms—
2026-10-03 13:40 UTCGETpass402272 ms—
2026-10-02 13:40 UTCGETpass402274 ms—
2026-10-01 16:40 UTCGETpass402207 ms—

3.L1 — real purchases

25 of 25 paid attempts settled on-chain, and 25 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).
25/25(20 cells, proportional)
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
11-12 18:02settled (nonce-bound)2000x0b0980cb…6570Base2037 ms
10000 units (≈ $0.01 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered
11-07 18:02settled (nonce-bound)2000xe243fe90…ce0aBase1770 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
11-06 15:32settled (nonce-bound)2000x6c2ea7a1…6103Base2095 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
11-04 21:32settled (nonce-bound)2000x341ab6e1…38b0Base2374 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
11-01 18:02settled (nonce-bound)2000x367d1ff3…b115Base2309 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-31 12:02settled (nonce-bound)2000x4e19d7fb…e707Base1931 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-29 21:32settled (nonce-bound)2000xaf7a65d9…1f46Base1757 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-28 18:02settled (nonce-bound)2000x6b8c52a8…7103Base2221 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-26 23:32settled (nonce-bound)2000x4bc4119a…0659Base1837 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-25 17:31settled (nonce-bound)2000x505521cf…750eBase2334 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-24 15:32settled (nonce-bound)2000x7792aec4…bbf5Base2774 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-23 12:02settled (nonce-bound)2000xed5b37ca…6773Base1578 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-22 09:31settled (nonce-bound)2000xa0f74016…2fbbBase1901 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-20 21:31settled (nonce-bound)2000x60934dd9…7bbbBase1693 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-19 18:01settled (nonce-bound)2000xadf90be6…089dBase1684 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-18 15:31settled (nonce-bound)2000x6c72b633…2454Base2712 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-11 23:01settled (nonce-bound)2000x8fa27c32…47b4Base1986 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-10 20:30settled (nonce-bound)2000xe5328a99…91f5Base1856 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-09 17:00settled (nonce-bound)2000xcdc2bf46…b491Base1966 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-08 12:01settled (nonce-bound)2000xe2e3efc4…d011Base1935 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 25/25 settled · 25 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.

vet402: 25 of 25 paid attempts settled with an on-chain receipt, and 25 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (x402.twit.sh · measured 2026-11-12)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/b325650a-212b-47cf-80c7-9076cf5200a2.svg)](https://vet402.com/observatory/e/b325650a-212b-47cf-80c7-9076cf5200a2)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-29settle_drop{"calls30d":428}{"calls30d":1}
2026-09-13relisted{"status":"delisted"}{"status":"active"}
2026-08-30delisted{"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

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.

20–2,000 characters · 0 so far