Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:10 UTC · reused for up to 5 min
cryptyx.ai
60 Base listings. By the latest purchase of each: 6 delivered · 2 failed on the seller's side · 5 on vet402's side · 47 not yet bought. Latest purchase: 2026-09-23 00:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| cryptyx.ai/api/market-pulseGET | 2026-09-23 00: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 0x356352c3…64b5In export.csv?days=7: the row with attempted_at 2026-09-23T00:01:15Z and resource_key cryptyx.ai/api/market-pulse. | |||
| cryptyx.ai/api/v1/harness/watchlistGET | 2026-09-16 18: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 0x51aba082…3956In export.csv?days=13: the row with attempted_at 2026-09-16T18:00:03Z and resource_key cryptyx.ai/api/v1/harness/watchlist. | |||
| cryptyx.ai/api/asset/regimeGET | 2026-09-15 06:00 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=14: the row with attempted_at 2026-09-15T06:00:30Z and resource_key cryptyx.ai/api/asset/regime. | |||
| cryptyx.ai/api/v1/harness/first-everGET | 2026-09-14 06:00 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-14T06:00:28Z and resource_key cryptyx.ai/api/v1/harness/first-ever. | |||
| cryptyx.ai/api/asset/asymmetryGET | 2026-09-13 18: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-13T18:01:49Z and resource_key cryptyx.ai/api/asset/asymmetry.Earlier: 2026-09-04 19:02 UTC vet402 did not send the declared query (vet402's side) | |||
| cryptyx.ai/api/funding-rateGET | 2026-09-13 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=16: the row with attempted_at 2026-09-13T12:08:10Z and resource_key cryptyx.ai/api/funding-rate.Earlier: 2026-09-03 07:01 UTC vet402 did not send the declared query (vet402's side) | |||
| cryptyx.ai/api/v1/harness/evaluationsGET | 2026-09-12 12:08 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xa0b14abf…f0ccIn export.csv?days=17: the row with attempted_at 2026-09-12T12:08:02Z and resource_key cryptyx.ai/api/v1/harness/evaluations. | |||
| cryptyx.ai/api/ai/signalsGET | 2026-09-11 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: settled · HTTP — · tx 0x95e38b6b…1a01In export.csv?days=18: the row with attempted_at 2026-09-11T18:02:17Z and resource_key cryptyx.ai/api/ai/signals.Earlier: 2026-09-04 12:08 UTC No answer to the paid request (seller's side) | |||
| cryptyx.ai/api/signals/activeGET | 2026-09-10 19: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 0xea055d95…8fb9In export.csv?days=19: the row with attempted_at 2026-09-10T19:00:44Z and resource_key cryptyx.ai/api/signals/active. | |||
| cryptyx.ai/api/signals/evalGET | 2026-09-09 07:01 UTC | vet402 did not send the declared query | vet402's side |
What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing marks some of them as required. The seller refused the request with 400 or 422.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=20: the row with attempted_at 2026-09-09T07:01:06Z and resource_key cryptyx.ai/api/signals/eval. | |||
| cryptyx.ai/api/market-pulse/regimeGET | 2026-09-06 19: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 0x12fc174c…0f51In export.csv?days=23: the row with attempted_at 2026-09-06T19:01:56Z and resource_key cryptyx.ai/api/market-pulse/regime. | |||
| cryptyx.ai/api/v1/ai/trade-ideasGET | 2026-09-06 07:00 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=23: the row with attempted_at 2026-09-06T07:00:44Z and resource_key cryptyx.ai/api/v1/ai/trade-ideas. | |||
| cryptyx.ai/api/x402/healthGET | 2026-09-04 09:25 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xee65aa5c…a388In export.csv?days=25: the row with attempted_at 2026-09-04T09:25:55Z and resource_key cryptyx.ai/api/x402/health. | |||
| cryptyx.ai/api/ai/metricsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset-factorsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset-regimesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/active-signalsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/metric-healthGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/peer-clusterGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/regime-contextGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/signal-eventsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/thesisGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/thesis-journalGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/top-predictorsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/asset/top-setupsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/assetsGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/intelligence/queryPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/iv-surfaceGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-historyGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/composite-breakdownGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/convictionGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/divergencesGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/factor-cross-sectionGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/hero-timelineGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/regime-divergenceGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/market-pulse/temporal-layersGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/metrics/previewGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/metrics/slicerPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/metrics/slicer/compositePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/metrics/slicer/scanGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/backtestPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/catalogGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/attributionGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/backtestPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/breadthGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/customPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/heatmapGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/composite/momentumGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/explainGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| cryptyx.ai/api/signals/forkPOST | 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.