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

vet402Sellers · What to fix firstMethodology

phion.systems: x402 purchase results on Base, latest attempt 2026-09-23

123 Base listings. Latest result about the seller at each listing: 4 delivered · 0 failed on the seller's side · 9 with no such result among the attempts shown · 110 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: 4 delivered · 0 failed on the seller's side · 3 on vet402's side · 6 not sorted (vet402 cannot show the failure was not its own) · 110 not tried yet.

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

1.Your listings

phion.systems/v1/paid/attestPOST
Latest attempt
2026-09-23 12:02 UTC
Result
delivered
Whose side
no failure (delivered)
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.001 USDC · payTo 0x7bec…71e2. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x7bec…71e2 · nonce 0x2894…3010 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: asking… · the full answerThe latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x6b46fe2b…7c2dIn export.csv?days=7: the row with attempted_at 2026-09-23T12:02:42Z and resource_key phion.systems/v1/paid/attest.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-13 00:00 UTC · vet402 did not send the declared request body · vet402's sidesettle_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)
  What vet402 recorded
  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, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x7bec…71e2 · nonce 0xa77e…b585 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json · no PAYMENT-RESPONSE recorded.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 request body.
  Dispute this purchase
phion.systems/v1/paid/trust/purpose-bound-consentPOST
Latest attempt
2026-09-22 06:01 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.003 USDC · payTo 0x7bec…71e2. Input sent: body empty, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x7bec…71e2 · nonce 0x1995…e5db · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.Decision API now: asking… · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=9: the row with attempted_at 2026-09-22T06:01:09Z and resource_key phion.systems/v1/paid/trust/purpose-bound-consent.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/transaction-recoveryPOST
Latest attempt
2026-09-20 06:02 UTC
Result
delivered
Whose side
no failure (delivered)
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.01 USDC · payTo 0x7bec…71e2. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x7bec…71e2 · nonce 0xb5ef…48b7 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x2bd480e9…115bIn export.csv?days=11: the row with attempted_at 2026-09-20T06:02:19Z and resource_key phion.systems/v1/paid/transaction-recovery.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/mandates/reservePOST
Latest attempt
2026-09-20 06:02 UTC
Result
delivered
Whose side
no failure (delivered)
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.004 USDC · payTo 0x7bec…71e2. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.004 USDC · payTo 0x7bec…71e2 · nonce 0x3059…4e44 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xfcc48ada…0fbaIn export.csv?days=11: the row with attempted_at 2026-09-20T06:02:06Z and resource_key phion.systems/v1/paid/mandates/reserve.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/trust/delegation-scope-guardPOST
Latest attempt
2026-09-20 06:01 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.003 USDC · payTo 0x7bec…71e2. Input sent: body empty, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x7bec…71e2 · nonce 0x22f7…327a · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=11: the row with attempted_at 2026-09-20T06:01:35Z and resource_key phion.systems/v1/paid/trust/delegation-scope-guard.Dispute this purchase Email me when this result changes
phion.systems/v1/executePOST
Latest attempt
2026-09-17 12:09 UTC
Result
delivered
Whose side
no failure (delivered)
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.001 USDC · payTo 0x7bec…71e2. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x7bec…71e2 · nonce 0x40fe…d057 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x898bb2a2…197cIn export.csv?days=13: the row with attempted_at 2026-09-17T12:09:25Z and resource_key phion.systems/v1/execute.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/trust/company-enrichment-evidencePOST
Latest attempt
2026-09-16 12:08 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.005 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0x7bec…71e2 · nonce 0xc7a7…c432 · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.This purchase is from before 2026-09-16 23:25 UTC, when vet402 sent an empty JSON body on paid POST requests; this listing declares no body.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=14: the row with attempted_at 2026-09-16T12:08:04Z and resource_key phion.systems/v1/paid/trust/company-enrichment-evidence.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/trust/person-enrichment-evidencePOST
Latest attempt
2026-09-16 12:07 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.006 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.006 USDC · payTo 0x7bec…71e2 · nonce 0x674e…4464 · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.This purchase is from before 2026-09-16 23:25 UTC, when vet402 sent an empty JSON body on paid POST requests; this listing declares no body.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=14: the row with attempted_at 2026-09-16T12:07:44Z and resource_key phion.systems/v1/paid/trust/person-enrichment-evidence.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/trust/contact-enrichment-evidencePOST
Latest attempt
2026-09-16 12:07 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.007 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.007 USDC · payTo 0x7bec…71e2 · nonce 0xd4fc…0037 · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.This purchase is from before 2026-09-16 23:25 UTC, when vet402 sent an empty JSON body on paid POST requests; this listing declares no body.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=14: the row with attempted_at 2026-09-16T12:07:42Z and resource_key phion.systems/v1/paid/trust/contact-enrichment-evidence.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/trust/interrupted-task-recoveryPOST
Latest attempt
2026-09-15 23:49 UTC
Result
Refused, and no payment was taken
Whose side
not sorted: no charge
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; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.003 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x7bec…71e2 · nonce 0xe153…ec67 · validBefore not recorded.Answer to the paid request: HTTP 422 · 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.This purchase is from before 2026-09-16 23:25 UTC, when vet402 sent an empty JSON body on paid POST requests; this listing declares no body.Decision API now: · the full answerRecorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=15: the row with attempted_at 2026-09-15T23:49:12Z and resource_key phion.systems/v1/paid/trust/interrupted-task-recovery.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/preflight-paymentPOST
Latest attempt
2026-09-14 06:00 UTC
Result
vet402's wallet held less USDC than the price
Whose side
vet402's side
What we saw: When vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.002 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x7bec…71e2 · nonce 0x7bb1…8791 · validBefore not recorded.Answer to the paid request: HTTP 422 · 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's wallet held less USDC than the price.Decision API now: · the full answerThis failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=17: the row with attempted_at 2026-09-14T06:00:29Z and resource_key phion.systems/v1/paid/preflight-payment.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/schema-normalizePOST
Latest attempt
2026-09-14 06:00 UTC
Result
vet402's wallet held less USDC than the price
Whose side
vet402's side
What we saw: When vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x7bec…71e2 · nonce 0xa3d1…b0da · validBefore not recorded.Answer to the paid request: HTTP 422 · 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's wallet held less USDC than the price.Decision API now: · the full answerThis failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 422 · no tx · held as unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction)In export.csv?days=17: the row with attempted_at 2026-09-14T06:00:21Z and resource_key phion.systems/v1/paid/schema-normalize.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/fetch-evidencePOST
Latest attempt
2026-09-13 12:07 UTC
Result
vet402's wallet held less USDC than the price
Whose side
vet402's side
What we saw: When vet402 signed, its payer wallet held less USDC than the price, by the wallet's balance rebuilt from its own USDC transfers on-chain. The payment had nothing behind it, so the failure is on vet402's side.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 signed: vet402 signed: exact · 0.004 USDC · payTo 0x7bec…71e2. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 600; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.004 USDC · payTo 0x7bec…71e2 · nonce 0xd307…7588 · 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's wallet held less USDC than the price.Decision API now: · the full answerThis failure was on vet402's side, not the seller's.Recorded (L1 paid purchase): 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=17: the row with attempted_at 2026-09-13T12:07:59Z and resource_key phion.systems/v1/paid/fetch-evidence.Dispute this purchase Email me when this result changes
phion.systems/v1/paid/commercial/enrichPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/commercial/inferencePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/commercial/intelligencePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/commercial/searchPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/inspect-agentPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/journeys/verifyPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/asset-due-diligencePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/compliancePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/corporate-actionsPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/nav-reservePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/sanctions-screening-evidencePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/rwa/transaction-assurancePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/transaction-assurancePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/a2a-transaction-bridgePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/abandoned-tool-detectorPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-approval-relayPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-behavior-fingerprintPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-budget-guardPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-economic-graphPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-memory-provenancePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-rate-limit-negotiatorPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-reputation-evidencePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-session-continuityPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/agent-task-handoff-receiptPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/ap2-mandate-bridgePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/automated-dispute-bundlePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/autonomous-procurementPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/capability-benchmarkPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/capability-negotiation-preflightPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/capability-verificationPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/concurrency-guardPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/conflict-resolutionPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/context-provenance-labelerPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/counterparty-risk-preflightPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/cross-agent-receipt-bundlePOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/cross-protocol-receiptPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
phion.systems/v1/paid/trust/data-egress-preflightPOST
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email 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)”); 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 (API reference). 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.