api-v2.ixs.finance/x402/vaults
1.Catalog declaration
| Resource URL | https://api-v2.ixs.finance/x402/vaults |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe341add833f9d62082e97ea260baa6546cd09f73 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 13:40 UTC | GET | pass | 402 | 1225 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 1039 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 910 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 3070 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 1083 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 1009 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 851 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 1099 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 920 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 908 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 898 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 853 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 433 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 1019 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 1186 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 979 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 1656 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 912 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 1399 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 1385 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 900 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 946 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 1017 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 1161 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 851 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 887 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 950 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 1470 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 1073 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 1194 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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 |
|---|---|---|---|---|
| 09-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 200 | 0x9bc26ff2…0be8 | 2547 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-31 12:072026-08-31 12:07 UTC | settled (amount + payee) | 200 | 0x3aa69f82…c765 | 2419 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-24 23:352026-08-24 23:35 UTC | settled (amount + payee) | 200 | 0x4613232e…2991 | 2510 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 10:092026-08-14 10:09 UTC | settled (amount + payee) | 200 | 0xd4f32faa…31d1 | 2822 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/09b33db2-8ce0-44bb-9d3b-6bf8a67f1ae4)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.