api.cryptoetfsentinel.com/v1/agent/issuers
1.Catalog declaration
| Resource URL | https://api.cryptoetfsentinel.com/v1/agent/issuers |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x169bf49c6ee5a179190121ab8d180b50e31683d1 |
| Declared price (base units) | 1000000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 13:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-10-19 22:40 UTC | GET | pass | 402 | 401 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 416 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 2259 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 488 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 448 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 476 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 2241 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 2150 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 409 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 852 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 819 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 637 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 480 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 1156 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 640 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 711 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 480 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 449 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 368 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-07 07:002026-09-07 07:00 UTC | settled (nonce-bound) | 200 | 0x5ad760b2…ec9e | Base | 1392 ms |
| 1000000 units (≈ $1.00 USDC) · L2 not_checked (recorded mismatch)Whose 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/19862903-bffd-45b0-9a7e-b5c2a1687dd0)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.