api.solenrich.com/entrypoints/perps-cross-venue-funding/invoke
1.Catalog declaration
| Resource URL | https://api.solenrich.com/entrypoints/perps-cross-venue-funding/invoke |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 66Qvhr1xnwqbCT36KfHfZF1JpoWdmCQ3uFYTN335CGXe |
| Declared price (base units) | 15000 |
| Catalog status | active |
| First seen / last seen | 2026-08-24 02:00 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | POST | pass | 402 | 119 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 88 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 139 ms | — |
| 2026-10-14 03:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 370 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 84 ms | — |
| 2026-10-10 15:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-10-09 15:40 UTC | POST | pass | 402 | 100 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 324 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 140 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 222 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 314 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 87 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 195 ms | — |
| 2026-10-01 16:40 UTC | POST | pass | 402 | 90 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 234 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 309 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 223 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 96 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 159 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 194 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 108 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 415 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 266 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 84 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 133 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.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 10-06 12:002026-10-06 12:00 UTC | settled (nonce-bound) | 200 | 4XTXEL5oov…1CRS | 2256 ms |
| 15000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-30 09:302026-09-30 09:30 UTC | settled (nonce-bound) | 200 | XsX4FYtDVV…4tLL | 3627 ms |
| 15000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-24 06:002026-09-24 06:00 UTC | settled (nonce-bound) | 200 | qWbj1RuVBS…SYQg | 2224 ms |
| 15000 units (≈ $0.01 USDC) · L2 no_declarationWhose 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/7b9c83f1-7a60-4ac0-9c1f-65dff8d257fa)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.