api.vextorium.com/sol-saldos-pago
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://api.vextorium.com/sol-saldos-pago |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0xb9f06d2734b7e9d7b21b64c4d8b95bd774b71acf |
| Declared price (base units) | 4000 |
| Catalog status | delisted (since 2026-10-26 01:31 UTC) |
| First seen / last seen | 2026-09-28 01:02 UTC / 2026-10-17 01:03 UTC |
| Catalog-reported calls / payers (30d) | 6 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-25 00:40 UTC | POST | fail | 503 | 216 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-22 22:40 UTC | POST | fail | 503 | 185 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-21 13:40 UTC | POST | fail | 503 | 192 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-19 22:40 UTC | POST | fail | 503 | 203 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-18 13:40 UTC | POST | fail | 503 | 184 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-17 04:40 UTC | POST | fail | 503 | 2503 ms | no_402HTTP 503 instead of 402 to an unpaid POST. |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 1006 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 392 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 144 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 297 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 176 ms | — |
| 2026-10-08 13:40 UTC | POST | pass | 402 | 300 ms | — |
| 2026-10-07 13:40 UTC | POST | pass | 402 | 210 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 165 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 2082 ms | — |
| 2026-10-03 13:40 UTC | POST | pass | 402 | 190 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 2275 ms | — |
| 2026-10-01 22:40 UTC | POST | fail | 530 | 35 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 306 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 287 ms | — |
| 2026-09-29 13:40 UTC | POST | pass | 402 | 448 ms | — |
| 2026-09-28 16:40 UTC | POST | pass | 402 | 461 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 727 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 vet402's 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.
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 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
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 |
|---|---|---|---|---|---|
| 10-13 12:002026-10-13 12:00 UTC | settled (nonce-bound) | 200 | 0x2b61b456…5c55 | Base | 5762 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
| 10-07 03:302026-10-07 03:30 UTC | settled (nonce-bound) | 200 | 0xf1fa19b1…bb41 | Base | 4758 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
| 09-30 03:302026-09-30 03:30 UTC | settled (nonce-bound) | 200 | 5Dkyydhk7j…597c | Solana | 5800 ms |
| 4000 units (≈ $0.004 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
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/2ff666dd-173f-4f7e-be9f-0df01ea205c1)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | delisted | {"status":"active"} | {"status":"delisted"} |
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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.