Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-16 · 2 days ago

squeezeos-api.onrender.com/api/fx/convert

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://squeezeos-api.onrender.com/api/fx/convert
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-25 01:58 UTC / 2026-11-18 16:05 UTC
Catalog-reported calls / payers (30d)11 / 7

2.Probe history

2026-10-022026-11-16
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-16 22:40 UTCGETpass402327 ms—
2026-11-13 16:40 UTCGETpass402297 ms—
2026-11-11 04:40 UTCGETpass402183 ms—
2026-11-09 04:40 UTCGETpass402162 ms—
2026-11-06 22:40 UTCGETpass402616 ms—
2026-11-04 16:40 UTCGETpass402142 ms—
2026-11-01 16:40 UTCGETpass402159 ms—
2026-10-30 16:40 UTCGETfail502131 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-28 16:40 UTCGETpass402142 ms—
2026-10-27 00:40 UTCGETpass402148 ms—
2026-10-25 06:40 UTCGETpass402130 ms—
2026-10-23 04:40 UTCGETpass402127 ms—
2026-10-21 16:40 UTCGETpass402192 ms—
2026-10-20 04:40 UTCGETpass402212 ms—
2026-10-18 16:40 UTCGETpass402190 ms—
2026-10-17 13:40 UTCGETpass402241 ms—
2026-10-15 21:40 UTCGETpass402196 ms—
2026-10-14 15:40 UTCGETpass402244 ms—
2026-10-13 03:40 UTCGETpass402254 ms—
2026-10-12 03:40 UTCGETpass402305 ms—
2026-10-11 03:40 UTCGETpass402314 ms—
2026-10-10 03:40 UTCGETpass402720 ms—
2026-10-08 16:40 UTCGETpass402101 ms—
2026-10-07 16:40 UTCGETpass402269 ms—
2026-10-06 16:40 UTCGETpass4021391 ms—
2026-10-05 22:40 UTCGETpass402126 ms—
2026-10-04 13:40 UTCGETpass402130 ms—
2026-10-03 16:40 UTCGETpass402203 ms—
2026-10-02 22:40 UTCGETpass402146 ms—
2026-10-02 04:40 UTCGETpass402157 ms—

3.L1 — real purchases

3 of 5 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 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.

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.
delivered_no_receipt
the paid request answered 200 without a settlement receipt.
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 in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
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.
Stage signed
vet402 signed a paid request. vet402 has not settled it on chain yet, or settlement failed, or the seller returned goods without a receipt.
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).
3/5
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
10-21 18:02settled (nonce-bound)2000xb26aad3a…24efBase5242 ms
1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-09 20:31settled (nonce-bound)2000xc17ba69c…412bBase2709 ms
1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
10-02 21:31settled (nonce-bound)2000x4c64f9fa…eaaeBase3192 ms
1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered
09-26 18:01delivered_no_receipt200—Base488 ms
1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: not sorted: no chargeStage: signed
09-05 01:02delivered_no_receipt200—Base492 ms
1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: not sorted: no chargeStage: signed

Add this badge to your docs

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/5 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.

vet402: 3 of 5 paid attempts settled with an on-chain receipt, and 3 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (squeezeos-api.onrender.com · measured 2026-10-21)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/baff3a71-dd79-4ead-94e5-4d69ee635273.svg)](https://vet402.com/observatory/e/baff3a71-dd79-4ead-94e5-4d69ee635273)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-07relisted{"status":"delisted"}{"status":"active"}
2026-09-06delisted{"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. 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.

20–2,000 characters · 0 so far