api.monpham.work/v1/twitter/search
1.Catalog declaration
| Resource URL | https://api.monpham.work/v1/twitter/search |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x7eebd75b116a553e02cbaca28cfbd47bc411e6b1 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-18 01:06 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 13:40 UTC | GET | pass | 402 | 1066 ms | — |
| 2026-10-15 15:40 UTC | GET | fail | 530 | 168 ms | no_402HTTP 530 instead of 402 to an unpaid GET. |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 2782 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 2426 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 826 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 805 ms | — |
| 2026-10-09 15:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 978 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 980 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 1202 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 1116 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 960 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 781 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 1007 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 868 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 1154 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 2412 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 1047 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 940 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 959 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 1370 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 1099 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 747 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 778 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 2224 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 879 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 468 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 341 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 2314 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 292 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 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 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 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.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
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 the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-11 18:022026-09-11 18:02 UTC | settled (nonce-bound) | 200 | 0x61037cce…38f2 | Base | 2673 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
| 09-03 12:072026-09-03 12:07 UTC | settled (amount + payee) | 200 | 0x89c3d2aa…0d30 | Base | 1997 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/9d17b568-dc00-41c9-8fbd-ce345e13ab2d)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-21 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-16 | 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.