api.402rates.com/v1/rwa/yields
1.Catalog declaration
| Resource URL | https://api.402rates.com/v1/rwa/yields |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf567cfe0fdb87a1d6ca330e3f30f0d3da0f7cb98 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 7 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 04:40 UTC | GET | pass | 402 | 659 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 461 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 543 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 819 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 1617 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 663 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 504 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 864 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 700 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 926 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 629 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 392 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 607 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 431 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (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 mismatch- the response lacked 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-03 19:012026-09-03 19:01 UTC | settled (amount + payee) | 200 | 0x802f6ec8…a5ef | 1955 ms |
| 30000 units (≈ $0.03 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/2ff8b0f9-1545-4992-a613-c9e8df74d7e2)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.