Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:21 UTC · reused for up to 5 min
quotient-api-gateway.onrender.com
14 Base listings. By the latest purchase of each: 3 delivered · 5 failed on the seller's side · 2 on vet402's side · 4 not yet bought. Latest purchase: 2026-09-27 12:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| quotient-api-gateway.onrender.com/api/v1/signals/featuredGET | 2026-09-27 12:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 200 · tx 0x57227ebf…45b1In export.csv?days=2: the row with attempted_at 2026-09-27T12:01:26Z and resource_key quotient-api-gateway.onrender.com/api/v1/signals/featured.Earlier: 2026-09-21 06:02 UTC delivered · 2026-09-14 18:00 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-08 12:07 UTC delivered | |||
| quotient-api-gateway.onrender.com/api/v1/marketsGET | 2026-09-23 18:02 UTC | No answer to the paid request | seller'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: settle_failed · HTTP — · no txIn export.csv?days=6: the row with attempted_at 2026-09-23T18:02:23Z and resource_key quotient-api-gateway.onrender.com/api/v1/markets.Earlier: 2026-09-17 15:23 UTC No answer to the paid request (seller's side) · 2026-09-11 12:07 UTC No answer to the paid request (seller's side) | |||
| quotient-api-gateway.onrender.com/api/v1/x/searchPOST | 2026-09-22 12:09 UTC | No answer to the paid request | seller'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: settle_failed · HTTP — · no txIn export.csv?days=7: the row with attempted_at 2026-09-22T12:09:01Z and resource_key quotient-api-gateway.onrender.com/api/v1/x/search. | |||
| quotient-api-gateway.onrender.com/api/v1/markets/mispricedGET | 2026-09-22 12:08 UTC | No answer to the paid request | seller'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: settle_failed · HTTP — · no txIn export.csv?days=7: the row with attempted_at 2026-09-22T12:08:07Z and resource_key quotient-api-gateway.onrender.com/api/v1/markets/mispriced. | |||
| quotient-api-gateway.onrender.com/api/v1/signalsGET | 2026-09-21 18:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The latest purchase delivered. An earlier purchase listed below did not.Recorded: settled · HTTP 200 · tx 0x45d9e1cd…37deIn export.csv?days=8: the row with attempted_at 2026-09-21T18:01:06Z and resource_key quotient-api-gateway.onrender.com/api/v1/signals.Earlier: 2026-09-15 12:08 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-09 07:02 UTC delivered · 2026-09-02 07:00 UTC delivered | |||
| quotient-api-gateway.onrender.com/api/v1/markets/lookupGET | 2026-09-21 06:02 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 422 · no tx · held as unsettled_4xxIn export.csv?days=8: the row with attempted_at 2026-09-21T06:02:30Z and resource_key quotient-api-gateway.onrender.com/api/v1/markets/lookup.Earlier: 2026-09-12 12:08 UTC The paid request was refused as invalid (seller's side) · 2026-09-04 19:00 UTC The paid request was refused as invalid (seller's side) | |||
| quotient-api-gateway.onrender.com/api/v1/portfolioGET | 2026-09-18 00:02 UTC | The paid request was refused as invalid | seller's side |
What we saw: vet402 signed the payment and the paid request got 400, 404, 415 or 422; the payment did not settle. Since 2026-09-16 23:25 UTC vet402 sends the request body the seller's 402 declares (an empty JSON body when it declares none), and since 2026-09-27 23:27 UTC it adds the query parameters the seller's 402 declares on Base.What to fix: Declare the input in the listing (body or query) with example values that work as written. (a listing or config change)Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded: settle_failed · HTTP 422 · no tx · held as unsettled_4xxIn export.csv?days=12: the row with attempted_at 2026-09-18T00:02:05Z and resource_key quotient-api-gateway.onrender.com/api/v1/portfolio. | |||
| quotient-api-gateway.onrender.com/api/v1/assetsGET | 2026-09-15 23:50 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x82a6232b…491aIn export.csv?days=14: the row with attempted_at 2026-09-15T23:50:50Z and resource_key quotient-api-gateway.onrender.com/api/v1/assets.Earlier: 2026-09-05 01:01 UTC delivered | |||
| quotient-api-gateway.onrender.com/api/v1/latestGET | 2026-09-14 12:08 UTC | vet402's wallet was out of USDC | vet402's side |
What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 402 · no tx · held as payer_unfundedIn export.csv?days=15: the row with attempted_at 2026-09-14T12:08:25Z and resource_key quotient-api-gateway.onrender.com/api/v1/latest.Earlier: 2026-09-04 19:00 UTC delivered | |||
| quotient-api-gateway.onrender.com/api/v1/assets/searchGET | 2026-09-14 00:01 UTC | vet402's wallet was out of USDC | vet402's side |
What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 402 · no tx · held as payer_unfundedIn export.csv?days=16: the row with attempted_at 2026-09-14T00:01:15Z and resource_key quotient-api-gateway.onrender.com/api/v1/assets/search.Earlier: 2026-09-05 07:01 UTC The paid request was refused as invalid (seller's side) | |||
| quotient-api-gateway.onrender.com/api/v1/markets/searchGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| quotient-api-gateway.onrender.com/api/v1/price-outlooksGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| quotient-api-gateway.onrender.com/api/v1/sourcesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| quotient-api-gateway.onrender.com/api/v1/x/profilePOST | not 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.