proxy.suverse.io/v1/swap/base/quote
1.Catalog declaration
| Resource URL | https://proxy.suverse.io/v1/swap/base/quote |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x4261701a4ddf4625ebfa80ceefb5b3b2b5453b2e |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-11-19 18:06 UTC |
| Catalog-reported calls / payers (30d) | 9 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-17 13:40 UTC | POST | pass | 402 | 794 ms | — |
| 2026-11-14 13:40 UTC | POST | pass | 402 | 403 ms | — |
| 2026-11-11 16:40 UTC | POST | pass | 402 | 346 ms | — |
| 2026-11-09 16:40 UTC | POST | pass | 402 | 488 ms | — |
| 2026-11-07 13:40 UTC | POST | pass | 402 | 480 ms | — |
| 2026-11-05 04:40 UTC | POST | pass | 402 | 540 ms | — |
| 2026-11-02 04:40 UTC | POST | pass | 402 | 383 ms | — |
| 2026-10-31 04:40 UTC | POST | pass | 402 | 391 ms | — |
| 2026-10-29 04:40 UTC | POST | pass | 402 | 361 ms | — |
| 2026-10-27 13:40 UTC | POST | pass | 402 | 368 ms | — |
| 2026-10-25 15:40 UTC | POST | pass | 402 | 613 ms | — |
| 2026-10-23 16:40 UTC | POST | pass | 402 | 442 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 491 ms | — |
| 2026-10-20 13:40 UTC | POST | pass | 402 | 351 ms | — |
| 2026-10-18 22:40 UTC | POST | pass | 402 | 514 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 592 ms | — |
| 2026-10-16 12:40 UTC | POST | pass | 402 | 466 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 361 ms | — |
| 2026-10-13 15:40 UTC | POST | pass | 402 | 410 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 425 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 345 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 327 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 2446 ms | — |
| 2026-10-07 22:40 UTC | POST | pass | 402 | 460 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 470 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 201 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 214 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 223 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 306 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 0 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
4 of those paid attempts are held as inconclusive rather than counted against this seller (4 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
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.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
settled_4xx- held_reason in the export: the payment settled, then the paid request got a 4xx.
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.
Stage inconclusive- vet402 holds the row because the paid HTTP response was 4xx, or vet402's payer wallet was unfunded in a recorded window. vet402 keeps the row public in its own stage, apart from delivered and not_delivered.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-16 12:092026-09-16 12:09 UTC | settled (nonce-bound) | 400 | 0x052e84f6…86bd | Base | 1613 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sentStage: inconclusive | |||||
| 09-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 400 | 0x7947c44c…9d5c | Base | 2094 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sentStage: inconclusive | |||||
| 08-27 12:322026-08-27 12:32 UTC | settled (amount + payee) | 400 | 0x2c2f20f1…ea73 | Base | 2393 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sentStage: inconclusive | |||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 400 | 0x8e4bb970…b156 | Base | 2031 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sentStage: inconclusive | |||||
Add this badge to your docs
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 0 delivered · 4 inconclusive 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/8c04061f-20a1-4f51-a089-8704b602a14c)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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.