Skip to main content
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 03:57 UTC · reused for up to 5 min

agents.x402stock.xyz

78 Base listings. By the latest purchase of each: 30 delivered · 15 failed on the seller's side · 7 on vet402's side · 26 not yet bought. Latest purchase: 2026-09-27 12:02 UTC.

1.Your listings

Base listings of this seller, most recent purchase first
ListingLatest purchaseResultWhose side
agents.x402stock.xyz/api/v1/perps/predicted-fundingGET2026-09-27 12:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x28d54105…da22In export.csv?days=2: the row with attempted_at 2026-09-27T12:02:38Z and resource_key agents.x402stock.xyz/api/v1/perps/predicted-funding.Earlier: 2026-09-12 18:00 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/xstocksGET2026-09-27 12:01 UTCdelivered—
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 0xe71588cb…cfd9In export.csv?days=2: the row with attempted_at 2026-09-27T12:01:58Z and resource_key agents.x402stock.xyz/api/v1/xstocks.Earlier: 2026-09-14 00:01 UTC vet402's wallet was out of USDC (vet402's side) · 2026-09-02 01:02 UTC delivered · 2026-08-26 12:35 UTC delivered
agents.x402stock.xyz/api/v1/treasury-yieldsGET2026-09-27 12:01 UTCdelivered—
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 0x0cb38fb3…4100In export.csv?days=2: the row with attempted_at 2026-09-27T12:01:50Z and resource_key agents.x402stock.xyz/api/v1/treasury-yields.Earlier: 2026-09-21 06:02 UTC No answer to the paid request (seller's side) · 2026-09-13 00:02 UTC vet402's wallet was out of USDC (vet402's side) · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/hip3/dexsGET2026-09-27 06:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xf6eede7c…e7ebIn export.csv?days=2: the row with attempted_at 2026-09-27T06:02:32Z and resource_key agents.x402stock.xyz/api/v1/hip3/dexs.Earlier: 2026-09-12 12:09 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/form-144GET2026-09-27 06:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x908fabad…1896In export.csv?days=2: the row with attempted_at 2026-09-27T06:02:13Z and resource_key agents.x402stock.xyz/api/v1/form-144.Earlier: 2026-09-12 12:09 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/splits-calendarGET2026-09-27 06:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x2cb33766…f4c4In export.csv?days=2: the row with attempted_at 2026-09-27T06:02:09Z and resource_key agents.x402stock.xyz/api/v1/splits-calendar.Earlier: 2026-09-12 12:10 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/money-supplyGET2026-09-27 06:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x7acf072d…d683In export.csv?days=2: the row with attempted_at 2026-09-27T06:01:49Z and resource_key agents.x402stock.xyz/api/v1/money-supply.Earlier: 2026-09-12 18:01 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/gdpGET2026-09-27 00:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x11f86f12…eec7In export.csv?days=3: the row with attempted_at 2026-09-27T00:02:24Z and resource_key agents.x402stock.xyz/api/v1/gdp.Earlier: 2026-09-12 12:09 UTC delivered · 2026-08-31 12:10 UTC delivered
agents.x402stock.xyz/api/v1/conditionsGET2026-09-26 18:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xfed1915f…5498In export.csv?days=3: the row with attempted_at 2026-09-26T18:02:26Z and resource_key agents.x402stock.xyz/api/v1/conditions.Earlier: 2026-09-12 12:09 UTC delivered · 2026-08-29 12:09 UTC delivered
agents.x402stock.xyz/api/v1/ticker-typesGET2026-09-20 18:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x3a8afaf9…e74aIn export.csv?days=9: the row with attempted_at 2026-09-20T18:02:22Z and resource_key agents.x402stock.xyz/api/v1/ticker-types.Earlier: 2026-09-12 12:09 UTC delivered · 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/fear-greed/liquidityGET2026-09-17 15:23 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xaca47122…7f63In export.csv?days=12: the row with attempted_at 2026-09-17T15:23:55Z and resource_key agents.x402stock.xyz/api/v1/fear-greed/liquidity.Earlier: 2026-09-10 12:09 UTC delivered · 2026-08-29 12:08 UTC delivered
agents.x402stock.xyz/api/v1/fear-greed/cryptoGET2026-09-17 15:23 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x4c3977f4…44f6In export.csv?days=12: the row with attempted_at 2026-09-17T15:23:52Z and resource_key agents.x402stock.xyz/api/v1/fear-greed/crypto.Earlier: 2026-09-10 19:01 UTC delivered · 2026-08-31 12:09 UTC delivered
agents.x402stock.xyz/api/v1/congress-tradesGET2026-09-17 15:23 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xd3cf8d8c…84a6In export.csv?days=12: the row with attempted_at 2026-09-17T15:23:20Z and resource_key agents.x402stock.xyz/api/v1/congress-trades.Earlier: 2026-09-11 12:08 UTC delivered · 2026-09-05 07:00 UTC delivered
agents.x402stock.xyz/api/v1/trending/redditGET2026-09-16 18:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x6bc57eec…1b9eIn export.csv?days=13: the row with attempted_at 2026-09-16T18:02:00Z and resource_key agents.x402stock.xyz/api/v1/trending/reddit.Earlier: 2026-09-10 12:09 UTC delivered · 2026-08-29 12:08 UTC delivered
agents.x402stock.xyz/api/v1/grouped-dailyGET2026-09-16 18:01 UTCTook the payment, then refused the inputseller'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 0x52ced541…9fc3 · held as settled_4xxIn export.csv?days=13: the row with attempted_at 2026-09-16T18:01:47Z and resource_key agents.x402stock.xyz/api/v1/grouped-daily.Earlier: 2026-09-10 07:01 UTC Took the payment, then refused the input (seller's side) · 2026-09-02 00:03 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/market-pulseGET2026-09-14 00:01 UTCvet402's wallet was out of USDCvet402'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:14Z and resource_key agents.x402stock.xyz/api/v1/market-pulse.Earlier: 2026-08-30 12:09 UTC delivered
agents.x402stock.xyz/api/v1/compareGET2026-09-14 00:01 UTCvet402's wallet was out of USDCvet402'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:06Z and resource_key agents.x402stock.xyz/api/v1/compare.Earlier: 2026-08-31 12:09 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/macroGET2026-09-14 00:01 UTCvet402's wallet was out of USDCvet402'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:02Z and resource_key agents.x402stock.xyz/api/v1/macro.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/fdaGET2026-09-14 00:00 UTCvet402's wallet was out of USDCvet402'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:00:52Z and resource_key agents.x402stock.xyz/api/v1/fda.Earlier: 2026-09-02 00:05 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/trendingGET2026-09-14 00:00 UTCvet402's wallet was out of USDCvet402'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:00:51Z and resource_key agents.x402stock.xyz/api/v1/trending.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:35 UTC delivered
agents.x402stock.xyz/api/v1/prediction-marketsGET2026-09-14 00:00 UTCvet402's wallet was out of USDCvet402'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:00:27Z and resource_key agents.x402stock.xyz/api/v1/prediction-markets.Earlier: 2026-09-01 12:08 UTC No answer to the paid request (seller's side) · 2026-08-25 12:54 UTC No answer to the paid request (seller's side)
agents.x402stock.xyz/api/v1/inflationGET2026-09-13 00:02 UTCvet402's wallet was out of USDCvet402'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=17: the row with attempted_at 2026-09-13T00:02:31Z and resource_key agents.x402stock.xyz/api/v1/inflation.Earlier: 2026-08-31 12:09 UTC delivered
agents.x402stock.xyz/api/v1/screenerGET2026-09-12 18:02 UTCAsks for its own login or keyseller'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: settled · HTTP 403 · tx 0x6b09c486…4bf5 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:02:14Z and resource_key agents.x402stock.xyz/api/v1/screener.Earlier: 2026-09-03 01:02 UTC Asks for its own login or key (seller's side)
agents.x402stock.xyz/api/v1/newsGET2026-09-12 18:02 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xd6274e1e…9966In export.csv?days=17: the row with attempted_at 2026-09-12T18:02:11Z and resource_key agents.x402stock.xyz/api/v1/news.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:35 UTC delivered
agents.x402stock.xyz/api/v1/full-market-snapshotGET2026-09-12 18:01 UTCAsks for its own login or keyseller'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: settled · HTTP 403 · tx 0xf593fa5f…c6f0 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:01:51Z and resource_key agents.x402stock.xyz/api/v1/full-market-snapshot.Earlier: 2026-08-29 12:08 UTC Asks for its own login or key (seller's side)
agents.x402stock.xyz/api/v1/gainersGET2026-09-12 18:01 UTCAsks for its own login or keyseller'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: settled · HTTP 403 · tx 0xdc019733…7876 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:01:43Z and resource_key agents.x402stock.xyz/api/v1/gainers.Earlier: 2026-08-29 12:09 UTC Asks for its own login or key (seller's side)
agents.x402stock.xyz/api/v1/losersGET2026-09-12 18:01 UTCAsks for its own login or keyseller'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: settled · HTTP 403 · tx 0xa553f69d…1efa · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:01:38Z and resource_key agents.x402stock.xyz/api/v1/losers.Earlier: 2026-08-29 12:09 UTC Asks for its own login or key (seller's side)
agents.x402stock.xyz/api/v1/gov-awardsGET2026-09-12 18:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xf732dbe1…0622In export.csv?days=17: the row with attempted_at 2026-09-12T18:01:28Z and resource_key agents.x402stock.xyz/api/v1/gov-awards.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/cotGET2026-09-12 18:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x9735f623…166fIn export.csv?days=17: the row with attempted_at 2026-09-12T18:01:25Z and resource_key agents.x402stock.xyz/api/v1/cot.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/archiveGET2026-09-12 18:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x87f18028…9081In export.csv?days=17: the row with attempted_at 2026-09-12T18:01:19Z and resource_key agents.x402stock.xyz/api/v1/archive.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/pceGET2026-09-12 18:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xd571cb0a…a9e9In export.csv?days=17: the row with attempted_at 2026-09-12T18:01:09Z and resource_key agents.x402stock.xyz/api/v1/pce.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/energyGET2026-09-12 18:00 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x8151b079…7ea8In export.csv?days=17: the row with attempted_at 2026-09-12T18:00:57Z and resource_key agents.x402stock.xyz/api/v1/energy.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/fda/shortagesGET2026-09-12 18:00 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xdb34e556…c48fIn export.csv?days=17: the row with attempted_at 2026-09-12T18:00:47Z and resource_key agents.x402stock.xyz/api/v1/fda/shortages.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/filing-searchGET2026-09-12 18:00 UTCTook the payment, then refused the inputseller'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 0x8e9ab4d1…7371 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:00:37Z and resource_key agents.x402stock.xyz/api/v1/filing-search.Earlier: 2026-09-02 00:05 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/unified-snapshotGET2026-09-12 18:00 UTCTook the payment, then refused the inputseller'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 0x0484bc3d…2504 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T18:00:35Z and resource_key agents.x402stock.xyz/api/v1/unified-snapshot.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:35 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/calendar/fomcGET2026-09-12 18:00 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xec618690…ae7dIn export.csv?days=17: the row with attempted_at 2026-09-12T18:00:31Z and resource_key agents.x402stock.xyz/api/v1/calendar/fomc.Earlier: 2026-09-01 12:08 UTC delivered · 2026-08-25 12:54 UTC delivered
agents.x402stock.xyz/api/v1/calendarGET2026-09-12 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x42fad869…ab29In export.csv?days=17: the row with attempted_at 2026-09-12T12:09:53Z and resource_key agents.x402stock.xyz/api/v1/calendar.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/national-debtGET2026-09-12 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x18ed1160…e48bIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:48Z and resource_key agents.x402stock.xyz/api/v1/national-debt.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/exchange-ratesGET2026-09-12 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xcc7e3586…fd2fIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:45Z and resource_key agents.x402stock.xyz/api/v1/exchange-rates.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:35 UTC delivered
agents.x402stock.xyz/api/v1/news-sentimentGET2026-09-12 12:09 UTCTook the payment, then refused the inputseller'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 0x548cf196…9534 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:42Z and resource_key agents.x402stock.xyz/api/v1/news-sentiment.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:35 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/gov-contractsGET2026-09-12 12:09 UTCTook the payment, then refused the inputseller'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 0xa125cf3d…29bd · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:35Z and resource_key agents.x402stock.xyz/api/v1/gov-contracts.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:35 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/private-stocksGET2026-09-12 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xc6e04400…b43cIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:25Z and resource_key agents.x402stock.xyz/api/v1/private-stocks.Earlier: 2026-09-02 00:05 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/solana/jlpGET2026-09-12 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xeb60fc83…b018In export.csv?days=17: the row with attempted_at 2026-09-12T12:09:06Z and resource_key agents.x402stock.xyz/api/v1/solana/jlp.Earlier: 2026-09-02 00:04 UTC delivered · 2026-08-26 12:36 UTC delivered
agents.x402stock.xyz/api/v1/framesGET2026-09-12 12:09 UTCTook the payment, then refused the inputseller'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 0x5b472072…fa58 · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:09:01Z and resource_key agents.x402stock.xyz/api/v1/frames.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/clinical-trialsGET2026-09-12 12:08 UTCTook the payment, then refused the inputseller'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 0x32e4f73f…b4ef · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:08:58Z and resource_key agents.x402stock.xyz/api/v1/clinical-trials.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/patentsGET2026-09-12 12:08 UTCTook the payment, then refused the inputseller'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 0xf6ffc3be…354e · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:08:54Z and resource_key agents.x402stock.xyz/api/v1/patents.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-26 12:36 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/regulatoryGET2026-09-12 12:08 UTCTook the payment, then refused the inputseller'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 0x72205f8e…cdad · held as settled_4xxIn export.csv?days=17: the row with attempted_at 2026-09-12T12:08:51Z and resource_key agents.x402stock.xyz/api/v1/regulatory.Earlier: 2026-09-02 00:04 UTC Took the payment, then refused the input (seller's side) · 2026-08-25 12:54 UTC Took the payment, then refused the input (seller's side)
agents.x402stock.xyz/api/v1/avg-interest-ratesGET2026-09-10 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x201f514c…f464In export.csv?days=19: the row with attempted_at 2026-09-10T12:09:40Z and resource_key agents.x402stock.xyz/api/v1/avg-interest-rates.Earlier: 2026-09-01 12:08 UTC delivered · 2026-08-25 12:54 UTC delivered
agents.x402stock.xyz/api/v1/tickersGET2026-09-10 12:09 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x3c2ecb6e…665dIn export.csv?days=19: the row with attempted_at 2026-09-10T12:09:23Z and resource_key agents.x402stock.xyz/api/v1/tickers.Earlier: 2026-09-02 00:03 UTC delivered · 2026-08-26 12:35 UTC delivered
agents.x402stock.xyz/api/v1/basisGET2026-09-06 07:01 UTCdelivered—
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xcf1267d0…85f7In export.csv?days=23: the row with attempted_at 2026-09-06T07:01:07Z and resource_key agents.x402stock.xyz/api/v1/basis.

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.