Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:06 UTC · reused for up to 5 min
api.xynaptic.io
110 Base listings. By the latest purchase of each: 5 delivered · 7 failed on the seller's side · 0 on vet402's side · 98 not yet bought. Latest purchase: 2026-09-27 18:00 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| api.xynaptic.io/v1/intermodal-compareGET | 2026-09-27 18:00 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server 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: settled · HTTP 400 · tx 0x45b3e802…b13f · held as settled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T18:00:41Z and resource_key api.xynaptic.io/v1/intermodal-compare. | |||
| api.xynaptic.io/v1/train-statusGET | 2026-09-27 12:00 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server 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: settled · HTTP 400 · tx 0x13debee5…a431 · held as settled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T12:00:47Z and resource_key api.xynaptic.io/v1/train-status. | |||
| api.xynaptic.io/v1/crypto-riskGET | 2026-09-26 12:00 UTC | Server error on the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got a 5xx.What to fix: Check the route's logs: the handler or its upstream failed on the paid request. (a server change)Recorded: settled · HTTP 503 · tx 0x89e48858…1634In export.csv?days=3: the row with attempted_at 2026-09-26T12:00:41Z and resource_key api.xynaptic.io/v1/crypto-risk. | |||
| api.xynaptic.io/v1/crypto-tokenomicsGET | 2026-09-25 12:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xef378c54…0718In export.csv?days=4: the row with attempted_at 2026-09-25T12:01:03Z and resource_key api.xynaptic.io/v1/crypto-tokenomics. | |||
| api.xynaptic.io/v1/news-worldGET | 2026-09-25 12:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xe0806f11…393aIn export.csv?days=4: the row with attempted_at 2026-09-25T12:00:53Z and resource_key api.xynaptic.io/v1/news-world. | |||
| api.xynaptic.io/v1/crypto-onchainGET | 2026-09-24 18:01 UTC | Server error on the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got a 5xx.What to fix: Check the route's logs: the handler or its upstream failed on the paid request. (a server change)Recorded: settled · HTTP 503 · tx 0xb45647e3…dc30In export.csv?days=5: the row with attempted_at 2026-09-24T18:01:19Z and resource_key api.xynaptic.io/v1/crypto-onchain. | |||
| api.xynaptic.io/v1/connection-riskGET | 2026-09-24 12:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server 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: settled · HTTP 400 · tx 0x019be44f…9bee · held as settled_4xxIn export.csv?days=5: the row with attempted_at 2026-09-24T12:01:32Z and resource_key api.xynaptic.io/v1/connection-risk. | |||
| api.xynaptic.io/v1/rail-trip-briefGET | 2026-09-24 12:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server 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: settled · HTTP 400 · tx 0xe1ff3400…3b7e · held as settled_4xxIn export.csv?days=5: the row with attempted_at 2026-09-24T12:01:30Z and resource_key api.xynaptic.io/v1/rail-trip-brief. | |||
| api.xynaptic.io/v1/station-departuresGET | 2026-09-24 12:01 UTC | Took the payment, then refused the input | seller's side |
What we saw: The payment settled on-chain, and then the paid request got 400, 404, 415 or 422: the route took the payment before it checked the input, so the buyer paid for a refused request. When the seller declared a body, or a required query, that vet402 was not yet sending, the row is on vet402's side instead.What to fix: Check the input before you settle, so an invalid request is refused without taking the payment; and declare the input in the listing with example values that work as written. (a server 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: settled · HTTP 400 · tx 0x00d13b65…2151 · held as settled_4xxIn export.csv?days=5: the row with attempted_at 2026-09-24T12:01:23Z and resource_key api.xynaptic.io/v1/station-departures. | |||
| api.xynaptic.io/v1/crypto-brief-liveGET | 2026-09-24 12:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x238a3670…8613In export.csv?days=5: the row with attempted_at 2026-09-24T12:01:20Z and resource_key api.xynaptic.io/v1/crypto-brief-live. | |||
| api.xynaptic.io/v1/news-techGET | 2026-09-24 00:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xa636d977…4d5fIn export.csv?days=6: the row with attempted_at 2026-09-24T00:00:33Z and resource_key api.xynaptic.io/v1/news-tech. | |||
| api.xynaptic.io/v1/aoGET | 2026-09-23 12:00 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xbae88cc6…44f8In export.csv?days=6: the row with attempted_at 2026-09-23T12:00:37Z and resource_key api.xynaptic.io/v1/ao. | |||
| api.xynaptic.io/v1/ai-bankGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/ai-energyGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/ai-healthGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/ai-industryGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/ai-insuranceGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/airport-situationGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/aviation-newsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/battery-arbitrageGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/commodity-priceGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-brief-liveGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-changesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-compareGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-financialGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-international-profileGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-international-searchGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-kybGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-monitorGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-networkGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-newsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-peopleGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-profileGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-relationshipGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/company-searchGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-briefGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-correlationGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-deep-trading-analysisGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-defiGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-derivativesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-gas-feesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-historicalGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-marketGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-newsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-orderflowGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-priceGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-screenerGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-trading-analysisGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/crypto-validateGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.xynaptic.io/v1/energy-brief-liveGET | 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.