api.solenrich.com/entrypoints/wallet-graph/invoke
1.Catalog declaration
| Resource URL | https://api.solenrich.com/entrypoints/wallet-graph/invoke |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 66Qvhr1xnwqbCT36KfHfZF1JpoWdmCQ3uFYTN335CGXe |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-24 02:00 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 363 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 2052 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 310 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 303 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 2168 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 244 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 196 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 160 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 406 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 275 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 229 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 214 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 519 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 586 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 449 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 130 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 152 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 221 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 90 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.
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 |
|---|---|---|---|---|
| 10-04 21:302026-10-04 21:30 UTC | settled (nonce-bound) | 200 | 4eWyECznv9…EMXe | 3960 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-28 18:002026-09-28 18:00 UTC | settled (nonce-bound) | 200 | 4i61TXfy4c…bFgR | 3192 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-22 12:072026-09-22 12:07 UTC | settled (nonce-bound) | 200 | 27winxacgP…a5G4 | 3629 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 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/52b6e462-ce1b-428d-b07a-0c082e18658e)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.