Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 04:24 UTC · reused for up to 5 min
vaaya.ai
77 Base listings. By the latest purchase of each: 6 delivered · 5 failed on the seller's side · 3 on vet402's side · 63 not yet bought. Latest purchase: 2026-09-27 12:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| vaaya.ai/api/run/openrouter/chatPOST | 2026-09-27 12: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)Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-27T12:02:00Z and resource_key vaaya.ai/api/run/openrouter/chat.Earlier: 2026-09-14 06:01 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-05 12:09 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/modal/sandbox-execPOST | 2026-09-27 00: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: settle_failed · HTTP 502 · no txIn export.csv?days=3: the row with attempted_at 2026-09-27T00:01:33Z and resource_key vaaya.ai/api/run/modal/sandbox-exec.Earlier: 2026-09-20 18:02 UTC Server error on the paid request (seller's side) · 2026-09-13 12:07 UTC vet402's wallet was out of USDC (vet402's side) | |||
| vaaya.ai/api/run/icypeas/email-searchPOST | 2026-09-27 00: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 0x00a0f3a7…575aIn export.csv?days=3: the row with attempted_at 2026-09-27T00:01:28Z and resource_key vaaya.ai/api/run/icypeas/email-search.Earlier: 2026-09-20 18:02 UTC delivered · 2026-09-13 06:01 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-04 12:09 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/firecrawl/scrapePOST | 2026-09-26 18:00 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)Recorded: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=3: the row with attempted_at 2026-09-26T18:00:55Z and resource_key vaaya.ai/api/run/firecrawl/scrape.Earlier: 2026-09-20 12:09 UTC The paid request was refused as invalid (seller's side) · 2026-09-14 06:00 UTC vet402's wallet was out of USDC (vet402's side) | |||
| vaaya.ai/api/run/theirstack/jobsPOST | 2026-09-26 12:02 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 0x2d52ebbb…77c5In export.csv?days=3: the row with attempted_at 2026-09-26T12:02:00Z and resource_key vaaya.ai/api/run/theirstack/jobs.Earlier: 2026-09-17 18:01 UTC delivered · 2026-09-11 06:02 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-04 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/crw/scrapePOST | 2026-09-26 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 0x76c77271…3ee1In export.csv?days=3: the row with attempted_at 2026-09-26T12:01:58Z and resource_key vaaya.ai/api/run/crw/scrape.Earlier: 2026-09-11 06:02 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-04 12:08 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/akta/website-trafficPOST | 2026-09-24 06: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 0xa524b4d8…902aIn export.csv?days=5: the row with attempted_at 2026-09-24T06:00:47Z and resource_key vaaya.ai/api/run/akta/website-traffic. | |||
| vaaya.ai/api/run/brightdata/unblockPOST | 2026-09-19 00:01 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 0xdb63b0d3…fc09In export.csv?days=11: the row with attempted_at 2026-09-19T00:01:45Z and resource_key vaaya.ai/api/run/brightdata/unblock. | |||
| vaaya.ai/api/run/theirstack/buying-intentsPOST | 2026-09-19 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 0x67e24fbc…9a0aIn export.csv?days=11: the row with attempted_at 2026-09-19T00:01:38Z and resource_key vaaya.ai/api/run/theirstack/buying-intents. | |||
| vaaya.ai/api/run/fundable/companyPOST | 2026-09-17 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xc86f002e…7b4fIn export.csv?days=12: the row with attempted_at 2026-09-17T12:09:02Z and resource_key vaaya.ai/api/run/fundable/company. | |||
| vaaya.ai/api/run/exa/searchPOST | 2026-09-16 12:08 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.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=13: the row with attempted_at 2026-09-16T12:08:58Z and resource_key vaaya.ai/api/run/exa/search.Earlier: 2026-09-10 01:00 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-03 12:07 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/exa/contentsPOST | 2026-09-15 23:49 UTC | vet402 did not send the declared request body | vet402's side |
What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400 or 422, before or after the payment settled.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=14: the row with attempted_at 2026-09-15T23:49:48Z and resource_key vaaya.ai/api/run/exa/contents.Earlier: 2026-09-09 19:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| vaaya.ai/api/run/signalbase/job-changesPOST | 2026-09-15 00: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-15T00:00:56Z and resource_key vaaya.ai/api/run/signalbase/job-changes. | |||
| vaaya.ai/api/run/contactout/person-from-emailPOST | 2026-09-08 19:00 UTC | Server error before payment | seller's side |
What we saw: The unpaid request got a 5xx, so there was nothing to pay.What to fix: Bring the server back up, or remove the listing while it is down. (a server change)Recorded: no_402 · HTTP — (unpaid answer 500) · no txIn export.csv?days=21: the row with attempted_at 2026-09-08T19:00:12Z and resource_key vaaya.ai/api/run/contactout/person-from-email. | |||
| vaaya.ai/api/run/akta/company-enrichPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/akta/employee-reviewsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/akta/headcount-trendsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/akta/newsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/akta/product-reviewsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/apify/amazon-productPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/apify/instagram-postsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/apify/linkedin-postsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/apify/tiktok-profilePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/apify/tweetsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/blockrun/fetchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/brave/newsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/brave/searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/browserbase/create_sessionPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/contactout/linkedin-contactsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/contactout/people-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/courtlistener/casesPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/courtlistener/docketsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/crw/extractPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/crw/mapPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/crw/searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/edgar/fulltextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fal/generatePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fal/uploadPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/files/upload_from_urlPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/firecrawl/extractPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fundable/company-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fundable/industry-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fundable/investor-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fundable/location-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/fundable/person-searchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/google-trends/fetchPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/icypeas/domain-scanPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/icypeas/email-verificationPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/icypeas/resultPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| vaaya.ai/api/run/kadec0/fetchPOST | 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.