x402-defi-signals.onrender.com/defi/funding-rates
1.Catalog declaration
| Resource URL | https://x402-defi-signals.onrender.com/defi/funding-rates |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe72b85a97a6e19413d8b80633787eda6d6237a77 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-08-14 08:39 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 158 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 131 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 933 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 74 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
L2 no_declaration- the listing declares no output schema to check the response against.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-06 01:012026-09-06 01:01 UTC | settled (nonce-bound) | 200 | 0x67c4b3d8…7bf6 | 1470 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose 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/9544156e-380d-458f-90d6-1aa48f6326f0)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.
About the purchase at 2026-09-06T01:01:06Z (UTC). The form starts with that time; add what you saw instead.