api.solenrich.com/entrypoints/consensus-signal/invoke
1.Catalog declaration
| Resource URL | https://api.solenrich.com/entrypoints/consensus-signal/invoke |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 66Qvhr1xnwqbCT36KfHfZF1JpoWdmCQ3uFYTN335CGXe |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-24 02:00 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 8 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-10-17 22:40 UTC | POST | pass | 402 | 589 ms | — |
| 2026-10-16 15:40 UTC | POST | pass | 402 | 379 ms | — |
| 2026-10-15 03:40 UTC | POST | pass | 402 | 389 ms | — |
| 2026-10-13 21:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-10-12 15:40 UTC | POST | pass | 402 | 2082 ms | — |
| 2026-10-11 15:40 UTC | POST | pass | 402 | 206 ms | — |
| 2026-10-10 12:40 UTC | POST | pass | 402 | 121 ms | — |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 728 ms | — |
| 2026-10-08 04:40 UTC | POST | pass | 402 | 236 ms | — |
| 2026-10-07 04:40 UTC | POST | pass | 402 | 103 ms | — |
| 2026-10-06 13:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-10-04 22:40 UTC | POST | pass | 402 | 174 ms | — |
| 2026-10-04 04:40 UTC | POST | pass | 402 | 200 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 149 ms | — |
| 2026-10-02 13:40 UTC | POST | pass | 402 | 147 ms | — |
| 2026-10-01 16:40 UTC | POST | pass | 402 | 83 ms | — |
| 2026-09-30 22:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-30 04:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 209 ms | — |
| 2026-09-27 10:30 UTC | POST | pass | 402 | 167 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 81 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-16 11:24 UTC | POST | pass | 402 | 209 ms | — |
| 2026-09-12 11:24 UTC | POST | pass | 402 | 80 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-04 11:24 UTC | POST | pass | 402 | 194 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's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-12 05:002026-10-12 05:00 UTC | settled (nonce-bound) | 200 | 4W4F4Yu1F6…kLhh | 1706 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-06 03:382026-10-06 03:38 UTC | settled (nonce-bound) | 200 | PCQNWeN4VF…GuJL | 2768 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-29 12:002026-09-29 12:00 UTC | settled (nonce-bound) | 200 | 5LZxqyFRZ2…7aem | 2675 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 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/a62edee0-7153-47c1-9f4f-0db1ea9aa4ba)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.