x402-agents-production.up.railway.app/funding-rates
1.Catalog declaration
| Resource URL | https://x402-agents-production.up.railway.app/funding-rates |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6592eb8ef820abc092e8c3474fb2042dffccedc7 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 22:40 UTC | GET | pass | 402 | 296 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 579 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 270 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 2482 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 468 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 2257 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 323 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 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.
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-30 15:312026-09-30 15:31 UTC | settled (nonce-bound) | 200 | 0x3ad26024…ccfb | 2170 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-06 07:012026-09-06 07:01 UTC | settled (nonce-bound) | 200 | 0x6340ca34…44d0 | 3085 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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/898e9480-eea7-4bcc-8977-784e35bc99ee)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.