raptor-base-yields.vercel.app/v1/yields
1.Catalog declaration
| Resource URL | https://raptor-base-yields.vercel.app/v1/yields |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1e84f1f4e83ddfc91f8d5298b0cf49da34d041a6 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-26 01:39 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 8 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 16:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-10-18 22:40 UTC | GET | fail | 502 | 246 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 286 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 289 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 1844 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-29 04:40 UTC | GET | fail | 502 | 103 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 815 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-24 22:40 UTC | GET | fail | 502 | 189 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 261 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 207 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 parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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-16 18:012026-09-16 18:01 UTC | settled (nonce-bound) | 200 | 0xe651a90b…869f | 1807 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0xa53005b4…30c5 | 1250 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 19:012026-09-02 19:01 UTC | settled (amount + payee) | 200 | 0x6a2c58c6…207c | 2093 ms |
| 10000 units (≈ $0.01 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/c857b090-24b1-4b08-b5c1-1d872bb5dc82)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.