booaip.vercel.app/api/feargreed
1.Catalog declaration
| Resource URL | https://booaip.vercel.app/api/feargreed |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcd6b6d99b7751ff30b68fa1365488eb73fa7cefa |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 04:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 56 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 2226 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 2053 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 2071 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 519 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 232 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 93 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 462 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 231 ms | — |
| 2026-09-13 16:40 UTC | POST | fail | 500 | 115 ms | no_402HTTP 500 instead of 402 to an unpaid POST. |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 162 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 match- the response had the 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-21 18:022026-09-21 18:02 UTC | settled (nonce-bound) | 200 | 0x3eb02e20…14c5 | 1036 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-12 00:022026-09-12 00:02 UTC | settled (nonce-bound) | 200 | 0xa432efff…c6d9 | 884 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-04 01:022026-09-04 01:02 UTC | settled (amount + payee) | 200 | 0xde58578e…a815 | 1058 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/51848d88-db7e-493b-b686-bc15ebf55280)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.