Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 02:32 UTC · reused for up to 5 min
api.aidress.ai
12 Base listings. By the latest purchase of each: 2 delivered · 4 failed on the seller's side · 2 on vet402's side · 4 not yet bought. Latest purchase: 2026-09-28 00:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| api.aidress.ai/pay/agent_ottoai_crypto_newsGET | 2026-09-28 00:01 UTC | Asks for its own login or key | seller's side |
What we saw: The request got 401 or 403 (before or after payment).What to fix: Let the x402 payment be enough: answer 402 to an unpaid request and the data to a paid one. (a server change)Recorded: settle_failed · HTTP 401 · no tx · held as unsettled_4xxIn export.csv?days=2: the row with attempted_at 2026-09-28T00:01:35Z and resource_key api.aidress.ai/pay/agent_ottoai_crypto_news.Earlier: 2026-09-21 18:00 UTC Asks for its own login or key (seller's side) · 2026-09-15 12:08 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-09 01:01 UTC delivered · 2026-09-02 12:07 UTC Server error on the paid request (seller's side) | |||
| api.aidress.ai/pay/agent_edgar_apitoll_cloudGET | 2026-09-17 12:53 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 0x1cb45d40…6755In export.csv?days=12: the row with attempted_at 2026-09-17T12:53:47Z and resource_key api.aidress.ai/pay/agent_edgar_apitoll_cloud.Earlier: 2026-09-11 12:09 UTC delivered · 2026-09-02 12:08 UTC Server error on the paid request (seller's side) | |||
| api.aidress.ai/pay/agent_exa_aiPOST | 2026-09-16 00:00 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: settled · HTTP 400 · tx 0x18b9d3f9…1384 · held as settled_4xxIn export.csv?days=14: the row with attempted_at 2026-09-16T00:00:42Z and resource_key api.aidress.ai/pay/agent_exa_ai.Earlier: 2026-08-26 12:35 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.aidress.ai/pay/agent_agentres_devPOST | 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:53Z and resource_key api.aidress.ai/pay/agent_agentres_dev. | |||
| api.aidress.ai/pay/agent_api_dev_v2_ixs_financeGET | 2026-09-10 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 0x94adc9a3…91feIn export.csv?days=19: the row with attempted_at 2026-09-10T12:09:35Z and resource_key api.aidress.ai/pay/agent_api_dev_v2_ixs_finance.Earlier: 2026-08-27 12:31 UTC delivered · 2026-08-20 12:56 UTC delivered · 2026-08-14 09:57 UTC delivered | |||
| api.aidress.ai/pay/agent_voidfeed_aiGET | 2026-09-03 19: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 500 · tx 0x39196fed…fa04In export.csv?days=26: the row with attempted_at 2026-09-03T19:01:38Z and resource_key api.aidress.ai/pay/agent_voidfeed_ai. | |||
| api.aidress.ai/pay/agent_tick_hugen_tokyoGET | 2026-09-03 01: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 500 · tx 0x65795351…b580In export.csv?days=27: the row with attempted_at 2026-09-03T01:01:28Z and resource_key api.aidress.ai/pay/agent_tick_hugen_tokyo. | |||
| api.aidress.ai/pay/agent_printmoneylab_comGET | 2026-09-01 12:08 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 500 · tx 0x827788ac…6172In export.csv?days=28: the row with attempted_at 2026-09-01T12:08:12Z and resource_key api.aidress.ai/pay/agent_printmoneylab_com.Earlier: 2026-08-25 12:53 UTC delivered · 2026-08-19 12:12 UTC delivered | |||
| api.aidress.ai/pay/agent_blockrun_aiGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.aidress.ai/pay/agent_compute_lonestaroracle_xyzGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.aidress.ai/pay/agent_launches_lonestaroracle_xyzGET | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.aidress.ai/pay/agent_pro_api_coingecko_comGET | 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.