Skip to main content
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:06 UTC · reused for up to 5 min

squeezeos-api.onrender.com

32 Base listings. By the latest purchase of each: 5 delivered · 6 failed on the seller's side · 0 on vet402's side · 21 not yet bought. Latest purchase: 2026-09-26 18:01 UTC.

1.Your listings

Base listings of this seller, most recent purchase first
ListingLatest purchaseResultWhose side
squeezeos-api.onrender.com/api/fx/convertGET2026-09-26 18:01 UTCAnswered 2xx, but the payment was not confirmedseller's side
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=3: the row with attempted_at 2026-09-26T18:01:26Z and resource_key squeezeos-api.onrender.com/api/fx/convert.Earlier: 2026-09-05 01:02 UTC Answered 2xx, but the payment was not confirmed (seller's side)
squeezeos-api.onrender.com/api/x/searchGET2026-09-23 12:02 UTCAnswered 2xx, but the payment was not confirmedseller's side
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=6: the row with attempted_at 2026-09-23T12:02:06Z and resource_key squeezeos-api.onrender.com/api/x/search.Earlier: 2026-09-15 23:51 UTC Answered 2xx, but the payment was not confirmed (seller's side) · 2026-09-06 01:00 UTC Answered 2xx, but the payment was not confirmed (seller's side)
squeezeos-api.onrender.com/api/utility/creditsGET2026-09-23 12:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x9aafdf8e…499aIn export.csv?days=6: the row with attempted_at 2026-09-23T12:01:29Z and resource_key squeezeos-api.onrender.com/api/utility/credits.
squeezeos-api.onrender.com/api/fred/series/UNRATEGET2026-09-07 12:08 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x9955581a…23fbIn export.csv?days=22: the row with attempted_at 2026-09-07T12:08:26Z and resource_key squeezeos-api.onrender.com/api/fred/series/UNRATE.
squeezeos-api.onrender.com/api/quick/headline/AAPLGET2026-09-07 07:00 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x7cf6698d…5030In export.csv?days=22: the row with attempted_at 2026-09-07T07:00:57Z and resource_key squeezeos-api.onrender.com/api/quick/headline/AAPL.
squeezeos-api.onrender.com/api/enrich/domainGET2026-09-06 07:01 UTCAnswered 2xx, but the payment was not confirmedseller's side
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=23: the row with attempted_at 2026-09-06T07:01:12Z and resource_key squeezeos-api.onrender.com/api/enrich/domain.
squeezeos-api.onrender.com/api/fx/creditsGET2026-09-06 01:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x386c3e61…3a06In export.csv?days=24: the row with attempted_at 2026-09-06T01:02:17Z and resource_key squeezeos-api.onrender.com/api/fx/credits.
squeezeos-api.onrender.com/api/web/read-markdownGET2026-09-06 01:01 UTCAnswered 2xx, but the payment was not confirmedseller's side
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=24: the row with attempted_at 2026-09-06T01:01:52Z and resource_key squeezeos-api.onrender.com/api/web/read-markdown.
squeezeos-api.onrender.com/api/truth/verify/AAPLGET2026-09-06 01:01 UTCNo answer to the paid requestseller's side
What we saw: vet402 signed the payment and the paid request got no HTTP answer in time (timeout, 408 or a closed connection).What to fix: Make the paid route answer within a few seconds; look for slow upstream calls or cold starts. (a server change)Recorded: settled · HTTP — · tx 0x608e817c…5157In export.csv?days=24: the row with attempted_at 2026-09-06T01:01:32Z and resource_key squeezeos-api.onrender.com/api/truth/verify/AAPL.
squeezeos-api.onrender.com/api/geo/creditsGET2026-09-06 01:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x0cf3c250…6f37In export.csv?days=24: the row with attempted_at 2026-09-06T01:01:30Z and resource_key squeezeos-api.onrender.com/api/geo/credits.
squeezeos-api.onrender.com/api/market/snapshotGET2026-09-06 01:00 UTCAnswered 2xx, but the payment was not confirmedseller's side
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=24: the row with attempted_at 2026-09-06T01:00:57Z and resource_key squeezeos-api.onrender.com/api/market/snapshot.
squeezeos-api.onrender.com/api/cascade/signalGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/fred/series/CPIAUCSLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/ftd/cycle/GMEGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/ftd/etf-basket/XRTGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/ftd/ratio/GMEGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/ftd/series/GMEGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/ftd/threshold-listGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/iam/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/memory/recallGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/quick/quote/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/quick/searchGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/scanGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/signals/365/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/signals/741/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/signals/full/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/signals/triplelock/AAPLGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/web/creditsGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/web/extract-onceGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/web/research/creditsGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/web/research/onceGETnot yet bought——
vet402 has not bought this listing yet.
squeezeos-api.onrender.com/api/x402/settlement/creditsGETnot yet bought——
vet402 has not bought this listing yet.

2.How to read this

Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. The transaction link opens the settlement on Basescan. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.