Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 07:10 UTC · reused for up to 5 min

vet402Sellers · What to fix firstMethodology

x402-factory.com: x402 purchase results on Base, latest attempt 2026-09-24

205 Base listings. Latest result about the seller at each listing: 51 delivered · 0 failed on the seller's side · 13 with no such result among the attempts shown · 141 not tried yet. This counts, for each listing, the newest purchase that delivered or the newest failure on the seller's side. Attempts on vet402's side, not bought, not sorted, or awaiting on-chain verification are skipped.

By the latest attempt at each listing, whatever it was: 49 delivered · 0 failed on the seller's side · 7 on vet402's side · 8 not sorted (vet402 cannot show the failure was not its own) · 141 not tried yet.

Latest attempt: 2026-09-24 12:02 UTC. This page read the ledger at 2026-09-29 07:10 UTC and reuses that read for up to 5 min.

1.Your listings

x402-factory.com/v1/contracts/awards/dhsGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xb062281c…9677In export.csv?days=42: the row with attempted_at 2026-08-19T12:13:12Z and resource_key x402-factory.com/v1/contracts/awards/dhs.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/docGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x68ba5260…1f02In export.csv?days=42: the row with attempted_at 2026-08-19T12:13:11Z and resource_key x402-factory.com/v1/contracts/awards/doc.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/dodGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xa11e1f7e…cd06In export.csv?days=42: the row with attempted_at 2026-08-19T12:13:09Z and resource_key x402-factory.com/v1/contracts/awards/dod.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/dotGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x7375dfc7…2176In export.csv?days=42: the row with attempted_at 2026-08-19T12:13:08Z and resource_key x402-factory.com/v1/contracts/awards/dot.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/hhsGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x27def999…eb7dIn export.csv?days=42: the row with attempted_at 2026-08-19T12:13:06Z and resource_key x402-factory.com/v1/contracts/awards/hhs.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/nasaGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x9010aca0…f9faIn export.csv?days=42: the row with attempted_at 2026-08-19T12:13:05Z and resource_key x402-factory.com/v1/contracts/awards/nasa.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/usdaGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x238bf809…fbd4In export.csv?days=42: the row with attempted_at 2026-08-19T12:13:03Z and resource_key x402-factory.com/v1/contracts/awards/usda.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/contracts/awards/vaGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xf1aa69ba…21abIn export.csv?days=42: the row with attempted_at 2026-08-19T12:13:02Z and resource_key x402-factory.com/v1/contracts/awards/va.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/edgar/events/acquisitionsGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x2c1b473a…0ffdIn export.csv?days=42: the row with attempted_at 2026-08-19T12:13:01Z and resource_key x402-factory.com/v1/edgar/events/acquisitions.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/edgar/events/bankruptcyGET
Latest attempt
2026-08-19 12:13 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xde28a0de…114eIn export.csv?days=42: the row with attempted_at 2026-08-19T12:13:00Z and resource_key x402-factory.com/v1/edgar/events/bankruptcy.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/edgar/events/material-agreementGET
Latest attempt
2026-08-19 12:12 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x06b733c4…6feaIn export.csv?days=42: the row with attempted_at 2026-08-19T12:12:58Z and resource_key x402-factory.com/v1/edgar/events/material-agreement.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/edgar/watch/proxy-watchGET
Latest attempt
2026-08-17 12:48 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc0b0f1d7…505aIn export.csv?days=44: the row with attempted_at 2026-08-17T12:48:38Z and resource_key x402-factory.com/v1/edgar/watch/proxy-watch.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/energy/:regionGET
Latest attempt
2026-08-17 12:48 UTC
Result
vet402 did not send the declared query
Whose side
vet402's side
Decision API now: · the full answer
What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; there has been no attempt since.The 402 terms vet402 signed: vet402 signed: exact · 0.05 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded, path parameters declared, not filled. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.05 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 attempt; vet402 signed a payment, not settled on-chain): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=44: the row with attempted_at 2026-08-17T12:48:32Z and resource_key x402-factory.com/v1/energy/:region.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/aviation/delay-risk/:iataGET
Latest attempt
2026-08-17 12:48 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
Decision API now: · the full answer
What we saw: vet402 signed the payment and the paid request got a 4xx other than 402, with no settlement receipt and no transaction on the row. No money moved, and vet402 cannot rule out that its own request was the problem (held_reason unsettled_4xx), so this page does not count the row as the seller's fault. 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.Last result about the seller: none among the attempts shown. The latest attempt is not sorted; there has been no attempt since.The 402 terms vet402 signed: vet402 signed: exact · 0.02 USDC · payTo 0xcc42…305f. Input sent: body not recorded, query not recorded, path parameters declared, not filled. The listing's maxTimeoutSeconds is 120; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.02 USDC · payTo 0xcc42…305f · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault. If the request was meant to succeed, declare the input in the listing (body or query) with example values that work as written.Before 2026-09-27 23:27 UTC, vet402 did not add query parameters to paid requests on Base; this listing declares optional ones.Recorded (L1 attempt; vet402 signed a payment, not settled on-chain): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 400 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=44: the row with attempted_at 2026-08-17T12:48:31Z and resource_key x402-factory.com/v1/aviation/delay-risk/:iata.
After a fixEmail me when this result changes Dispute this purchase
x402-factory.com/v1/alerts/fire-weatherGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/alerts/floodGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/alerts/hurricaneGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/alerts/severeGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/ATLGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/BOSGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/CLTGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/DENGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/DFWGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/DTWGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/EWRGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/FLLGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/IAHGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/JFKGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/LASGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/LAXGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/LGAGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/MCOGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/MIAGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/MSPGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/PHXGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/SEAGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/aviation/delay-risk/SFOGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/board/:category/deltaGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/board/climateGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/calendar/deltaGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/climate-events/probabilityGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/contracts/awards/deltaGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/contracts/awards/doeGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/:seriesGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/building-permitsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/calendarGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/core-cpiGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/core-pceGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/cpiGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes
x402-factory.com/v1/econ/dashboard/deltaGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result: “Recorded (L1 paid purchase)” when the payment settled on-chain, and “signed, not settled on-chain” when it did not. A row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It is cautious for the payer: it leaves out the attempts that show vet402's fault, are held, or took no payment, and counts the rest, so it can say WARN or BLOCK for a listing whose failures this page leaves not sorted. The codes that decided the answer come first, each with one sentence on what it means for that listing (reason codes). “After a fix” gives the earliest date vet402's regular sweep can buy the listing again, where the rules let it be worked out, and the links to be told of a change or to dispute a row. 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?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.