Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-28 03:54 UTC · reused for up to 5 min
api.locus.report
96 Base listings. By the latest purchase of each: 4 delivered · 4 failed on the seller's side · 11 on vet402's side · 77 not yet bought. Latest purchase: 2026-09-28 00:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| api.locus.report/api/locus-place-reportPOST | 2026-09-28 00: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: settle_failed · HTTP — · no txIn export.csv?days=2: the row with attempted_at 2026-09-28T00:02:34Z and resource_key api.locus.report/api/locus-place-report.Earlier: 2026-09-11 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-three-property-buyer-comparisonPOST | 2026-09-27 00:02 UTC | vet402's own limits | vet402's side |
What we saw: vet402 did not pay: the price was over its per-purchase ceiling, its budget for the day was used up, its operator halted spending, or the 402 named vet402's own receiving address.What to fix: Nothing for the seller to fix.This failure was on vet402's side, not the seller's.Recorded: over_cap · HTTP — · no txIn export.csv?days=3: the row with attempted_at 2026-09-27T00:02:00Z and resource_key api.locus.report/api/locus-three-property-buyer-comparison.Earlier: 2026-09-17 18:02 UTC vet402's own limits (vet402's side) · 2026-09-11 12:07 UTC vet402's own limits (vet402's side) | |||
| api.locus.report/api/locus-owner-cost-reviewPOST | 2026-09-26 18: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 0xb1784be1…7c78In export.csv?days=3: the row with attempted_at 2026-09-26T18:02:21Z and resource_key api.locus.report/api/locus-owner-cost-review.Earlier: 2026-09-15 18:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-09 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-rental-operations-briefPOST | 2026-09-26 18: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 0x5d5b556f…c985In export.csv?days=3: the row with attempted_at 2026-09-26T18:02:03Z and resource_key api.locus.report/api/locus-rental-operations-brief.Earlier: 2026-09-15 18:01 UTC vet402 did not send the declared request body (vet402's side) · 2026-09-09 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-large-site-satellite-changePOST | 2026-09-26 18: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 0x97838b83…cd45In export.csv?days=3: the row with attempted_at 2026-09-26T18:01:35Z and resource_key api.locus.report/api/locus-large-site-satellite-change.Earlier: 2026-09-17 18:02 UTC delivered · 2026-09-11 06:01 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-practitioner-readPOST | 2026-09-24 18: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=5: the row with attempted_at 2026-09-24T18:00:54Z and resource_key api.locus.report/api/locus-practitioner-read. | |||
| api.locus.report/api/locus-solar-property-screenPOST | 2026-09-23 00:01 UTC | Answered 2xx, but the payment was not confirmed | seller's side |
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=7: the row with attempted_at 2026-09-23T00:01:45Z and resource_key api.locus.report/api/locus-solar-property-screen. | |||
| api.locus.report/api/locus-insurance-contextPOST | 2026-09-20 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 0xabecfc3f…c55aIn export.csv?days=10: the row with attempted_at 2026-09-20T00:01:00Z and resource_key api.locus.report/api/locus-insurance-context. | |||
| api.locus.report/api/locus-permit-closeout-checkPOST | 2026-09-15 23:51 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:51:32Z and resource_key api.locus.report/api/locus-permit-closeout-check.Earlier: 2026-09-09 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-air-quality-historyPOST | 2026-09-15 23:50 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:50:38Z and resource_key api.locus.report/api/locus-air-quality-history.Earlier: 2026-09-09 07:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-parcel-lookupPOST | 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:55Z and resource_key api.locus.report/api/locus-parcel-lookup.Earlier: 2026-09-09 01:00 UTC vet402 did not send the declared request body (vet402's side) | |||
| api.locus.report/api/locus-parcel-setPOST | 2026-09-13 00:01 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=17: the row with attempted_at 2026-09-13T00:01:44Z and resource_key api.locus.report/api/locus-parcel-set. | |||
| api.locus.report/api/locus-property-taxPOST | 2026-09-13 00:01 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=17: the row with attempted_at 2026-09-13T00:01:36Z and resource_key api.locus.report/api/locus-property-tax. | |||
| api.locus.report/api/locus-place-report-batchPOST | 2026-09-11 06:01 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=18: the row with attempted_at 2026-09-11T06:01:46Z and resource_key api.locus.report/api/locus-place-report-batch. | |||
| api.locus.report/api/locus-evaluation-packetPOST | 2026-09-11 06:01 UTC | Answered 2xx, but the payment was not confirmed | seller's side |
What we saw: The paid request got a 2xx, but no settlement receipt came back, so the payment could not be confirmed as settled.What to fix: Settle the payment and return the PAYMENT-RESPONSE header with the 2xx. (a server change)Recorded: delivered_no_receipt · HTTP 200 · no txIn export.csv?days=18: the row with attempted_at 2026-09-11T06:01:42Z and resource_key api.locus.report/api/locus-evaluation-packet. | |||
| api.locus.report/api/locus-data-center-watchPOST | 2026-09-11 06:01 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=18: the row with attempted_at 2026-09-11T06:01:34Z and resource_key api.locus.report/api/locus-data-center-watch. | |||
| api.locus.report/api/locus-property-flyerPOST | 2026-09-11 06:01 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=18: the row with attempted_at 2026-09-11T06:01:19Z and resource_key api.locus.report/api/locus-property-flyer. | |||
| api.locus.report/api/locus-valuation-challengePOST | 2026-09-11 01: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=19: the row with attempted_at 2026-09-11T01:00:31Z and resource_key api.locus.report/api/locus-valuation-challenge. | |||
| api.locus.report/api/locus-transaction-follow-upPOST | 2026-09-09 07:01 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:01:06Z and resource_key api.locus.report/api/locus-transaction-follow-up. | |||
| api.locus.report/api/locus-appeal-windowPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-area-crime-reportPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-assessment-positionPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-before-you-signPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-capital-projectsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-cleanup-sitesPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-cmbs-loan-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-cmbs-maturity-wallPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-coastal-overlaysPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-comps-briefPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-development-casesPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-drinking-water-violationsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-electricity-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-environmental-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-environmental-history-lookupPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-environmental-records-screenPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-fair-market-rentsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-fema-eventsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-flood-gaugesPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-flood-premium-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-flood-zonePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-fraud-alert-pointerPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-governing-districtsPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-groundwater-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-homeowners-insurance-contextPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-house-price-indexPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-housing-stockPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-housing-supply-balancePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-landslide-diligencePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-local-legislationPOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
| api.locus.report/api/locus-local-policy-briefPOST | 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.