rentcast.x402.paywithlocus.com
6 Base listings. By the latest purchase of each: 3 delivered · 1 failed on the seller's side · 1 on vet402's side · 1 not yet bought. Latest purchase: 2026-09-26 12:01 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| rentcast.x402.paywithlocus.com/rentcast/propertiesPOST | 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 0x302d5e11…435bIn export.csv?days=3: the row with attempted_at 2026-09-26T12:01:51Z and resource_key rentcast.x402.paywithlocus.com/rentcast/properties.Earlier: 2026-09-17 15:27 UTC delivered · 2026-09-11 06:02 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-04 09:24 UTC vet402 did not send the declared request body (vet402's side) | |||
| rentcast.x402.paywithlocus.com/rentcast/rental-listing-by-idPOST | 2026-09-21 06: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 404 · no tx · held as unsettled_4xxIn export.csv?days=8: the row with attempted_at 2026-09-21T06:00:48Z and resource_key rentcast.x402.paywithlocus.com/rentcast/rental-listing-by-id. | |||
| rentcast.x402.paywithlocus.com/rentcast/rent-estimatePOST | 2026-09-20 00:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x4c239221…687cIn export.csv?days=10: the row with attempted_at 2026-09-20T00:02:07Z and resource_key rentcast.x402.paywithlocus.com/rentcast/rent-estimate. | |||
| rentcast.x402.paywithlocus.com/rentcast/marketsPOST | 2026-09-09 07: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: settle_failed · HTTP 400 · no tx · held as unsettled_4xxIn export.csv?days=20: the row with attempted_at 2026-09-09T07:00:32Z and resource_key rentcast.x402.paywithlocus.com/rentcast/markets. | |||
| rentcast.x402.paywithlocus.com/rentcast/random-propertiesPOST | 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 0x9b439134…2c1cIn export.csv?days=23: the row with attempted_at 2026-09-06T19:01:09Z and resource_key rentcast.x402.paywithlocus.com/rentcast/random-properties. | |||
| rentcast.x402.paywithlocus.com/rentcast/rental-listingsPOST | 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.