Skip to main content
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-11-05 12:47 UTC. Refreshed after a view, so the first view after a quiet period can be older.

toll402.dev: x402 purchase results on Base, latest attempt 2026-11-05

28 Base listings. Latest result about the seller at each listing: 10 delivered · 0 failed on the seller's side · 2 with no such result among the attempts shown · 16 with no Base purchase. This counts, for each listing, the newest Base purchase that delivered or the newest Base 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: 10 delivered · 0 failed on the seller's side · 0 on vet402's side · 2 not sorted (vet402 cannot show the failure was not its own) · 16 with no Base purchase.

Latest attempt: 2026-11-05 06:02 UTC. This page read the ledger at 2026-11-05 12:47 UTC and reuses that read for up to 5 min. The first view after a quiet period can show an older read.

Withdrawn from the catalog

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count. These routes are not in the counts above.

Rows marked census or retest were bought to give this seller a row of its own, to buy again after a failure on vet402's side, or to read again a listing whose latest delivery missed declared keys.

1.Your listings

  1. toll402.dev/v1/t/cui_gt_validatePOST
    Latest attempt
    2026-11-05 06:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: asking… · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-02 22:46 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 22:46 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0xc837…65a7 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x346d0f97…8f81In export.csv?days=2: the row with attempted_at 2026-11-05T06:02:35Z and resource_key toll402.dev/v1/t/cui_gt_validate.
    After a fixNext purchase by vet402: Not before 2026-11-11 06:02 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  2. toll402.dev/v1/t/cui_ro_validatePOST
    Latest attempt
    2026-10-29 00:01 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: asking… · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-02 13:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 13:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x2fdb…e428 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xccbe889b…92f0In export.csv?days=9: the row with attempted_at 2026-10-29T00:01:58Z and resource_key toll402.dev/v1/t/cui_ro_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-04 00:01 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  3. toll402.dev/v1/t/cvr_dk_validatePOST
    Latest attempt
    2026-10-28 09:32 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-02 16:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 16:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x0e32…97c7 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x3e8bf5df…5e76In export.csv?days=10: the row with attempted_at 2026-10-28T09:32:33Z and resource_key toll402.dev/v1/t/cvr_dk_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-11-03 09:32 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  4. toll402.dev/v1/biz/verifyPOST
    Latest attempt
    2026-10-04 18:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 22:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 22:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.01 USDC · payTo 0x318d…3dbe. Input sent: body declared, query empty. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x318d…3dbe · nonce 0x19be…6d13 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.The latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xec54ee09…2591 · bought by the retestIn export.csv?days=33: the row with attempted_at 2026-10-04T18:02:07Z and resource_key toll402.dev/v1/biz/verify.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-10 18:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
    Earlier attempts
    1. 2026-09-10 19: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 recordedBefore 2026-09-16 23:25:55 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: exact · 0.01 USDC · payTo 0x318d…3dbe. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x318d…3dbe · nonce 0x460f…aeb7 · 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
  5. toll402.dev/v1/fxGET
    Latest attempt
    2026-09-30 15:30 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-10-28 16:40 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x1e6a…e600 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x7cab4694…d226In export.csv?days=37: the row with attempted_at 2026-09-30T15:30:53Z and resource_key toll402.dev/v1/fx.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-30 15:30 UTC (this listing has 3 or more settled purchases, so it is bought at most once every 30 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
    Earlier attempts
    1. 2026-09-24 12:01 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x19baf010…f107
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0xbb3e…7bcb · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-09-18 06:01 UTC · delivered · no failure (delivered)settled (vet402 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xc87fbb08…1ed6
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x03af…4f06 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  6. toll402.dev/v1/t/cpr_dk_validatePOST
    Latest attempt
    2026-09-25 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-05 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-10 04:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0xc781…0270 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x780625ad…01cbIn export.csv?days=43: the row with attempted_at 2026-09-25T00:02:06Z and resource_key toll402.dev/v1/t/cpr_dk_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-10-01 00:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  7. toll402.dev/v1/t/cpf_cnpj_validatePOST
    Latest attempt
    2026-09-24 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-05 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-10 04:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.002 USDC · payTo 0x318d…3dbe. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.002 USDC · payTo 0x318d…3dbe · nonce 0xf82d…2a38 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x048652d6…2733In export.csv?days=44: the row with attempted_at 2026-09-24T00:02:26Z and resource_key toll402.dev/v1/t/cpf_cnpj_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-30 00:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  8. toll402.dev/v1/t/siret_validatePOST
    Latest attempt
    2026-09-22 06:01 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-02 22:47 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 22:47 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x573c…cd86 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x0b8d8a19…249aIn export.csv?days=46: the row with attempted_at 2026-09-22T06:01:15Z and resource_key toll402.dev/v1/t/siret_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-28 06:01 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  9. toll402.dev/v1/t/cin_in_validatePOST
    Latest attempt
    2026-09-19 12:08 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 13:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 13:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0xbcc7…ae6e · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0x98c67fe8…3ebdIn export.csv?days=49: the row with attempted_at 2026-09-19T12:08:25Z and resource_key toll402.dev/v1/t/cin_in_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-25 12:08 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  10. toll402.dev/v1/t/fn_at_validatePOST
    Latest attempt
    2026-09-19 00:02 UTC
    Result
    delivered
    Whose side
    no failure (delivered)
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 13:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 13:40 UTC (within 120 hours of the last).
    What vet402 saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body declared, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0x5e3d…6090 · 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 re-read the transfer on-chain in that chain's pinned settlement asset) · HTTP 200 · tx 0xd3bf8da2…2105In export.csv?days=49: the row with attempted_at 2026-09-19T00:02:36Z and resource_key toll402.dev/v1/t/fn_at_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-25 00:02 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  11. toll402.dev/v1/t/jsonld_extractPOST

    On 2026-09-16 12:08 UTC, vet402 signed a payment and the paid request answered HTTP 502. This row is not counted against the seller (not sorted: vet402 unproven). If HTTP 502 is unexpected, check the route's logs, and the next purchase by vet402 is not before 2026-09-22 12:08 UTC, with no booked time. After that it depends on the daily budget and the order of demand.

    Latest attempt
    2026-09-16 12:08 UTC
    Result
    No record of the input vet402 sent
    Whose side
    not sorted: vet402 unproven
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 22:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 22:40 UTC (within 120 hours of the last).
    What vet402 saw: This purchase is from before vet402 recorded the body and the query it sent on each paid request (the query on Base since 2026-09-27 23:27:16 UTC), so it cannot show that it sent the input the listing declares. This page does not count the row as the seller's fault.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: exact · 0.003 USDC · payTo 0x318d…3dbe. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0x318d…3dbe · nonce 0xa055…8526 · validBefore not recorded.Answer to the paid request: HTTP 502 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault.Not shown for this row: vet402 has no record of the input it sent.Recorded (L1 attempt, vet402 signed a payment, not settled on-chain): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 502 · no txIn export.csv?days=52: the row with attempted_at 2026-09-16T12:08:45Z and resource_key toll402.dev/v1/t/jsonld_extract.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-22 12:08 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  12. toll402.dev/v1/t/orgnr_se_validatePOST

    On 2026-09-10 07:01 UTC, vet402 signed a payment and the paid request answered HTTP 502. This row is not counted against the seller (not sorted: vet402 unproven). If HTTP 502 is unexpected, check the route's logs, and the next purchase by vet402 is not before 2026-09-16 07:01 UTC, with no booked time. After that it depends on the daily budget and the order of demand.

    Latest attempt
    2026-09-10 07:01 UTC
    Result
    No record of the input vet402 sent
    Whose side
    not sorted: vet402 unproven
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-10-10 12:40 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    What vet402 saw: This purchase is from before vet402 recorded the body and the query it sent on each paid request (the query on Base since 2026-09-27 23:27:16 UTC), so it cannot show that it sent the input the listing declares. This page does not count the row as the seller's fault.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: exact · 0.001 USDC · payTo 0x318d…3dbe. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 300. vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.001 USDC · payTo 0x318d…3dbe · nonce 0xdff6…6c80 · validBefore not recorded.Answer to the paid request: HTTP 502 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: This page does not count it as the seller's fault.Not shown for this row: vet402 has no record of the input it sent.Recorded (L1 attempt, vet402 signed a payment, not settled on-chain): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 502 · no txIn export.csv?days=58: the row with attempted_at 2026-09-10T07:01:18Z and resource_key toll402.dev/v1/t/orgnr_se_validate.
    After a fixNext purchase by vet402: The regular sweep can pick this listing again since 2026-09-16 07:01 UTC (a listing is bought at most once every 6 days). When it does depends on the daily budget and the order of demand, so there is no booked date.Email me when this result changesDispute this purchaseA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  13. toll402.dev/v1/listingsPOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-05 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  14. toll402.dev/v1/lookupPOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-05 10:30 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  15. toll402.dev/v1/provenancePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (price_mismatch) at 2026-11-02 22:46 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 22:46 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  16. toll402.dev/v1/readGET
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  17. toll402.dev/v1/t/latam_tax_id_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  18. toll402.dev/v1/t/mst_vn_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  19. toll402.dev/v1/t/pan_in_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 06:41 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 06:41 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  20. toll402.dev/v1/t/partita_iva_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  21. toll402.dev/v1/t/ppsn_ie_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-05 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-10 04:40 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  22. toll402.dev/v1/t/rfc_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  23. toll402.dev/v1/t/rodne_cislo_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  24. toll402.dev/v1/t/rrn_be_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-04 13:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-09 13:40 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  25. toll402.dev/v1/t/rsin_nl_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-02 22:46 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-07 22:46 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  26. toll402.dev/v1/t/siren_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): fail (timeout) at 2026-10-04 10:31 UTC. The next probe is due. Probes run oldest first, so there is no booked time.
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  27. toll402.dev/v1/t/unit_convertPOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-05 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-10 04:40 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
  28. toll402.dev/v1/t/vat_at_validatePOST
    Latest attempt
    not tried on Base yet
    Result
    not tried on Base yet
    Whose side
    not tried on Base yet
    Decision API now: · the full answer
    Latest L0 check (the 402 to an unpaid request): pass at 2026-11-05 04:40 UTC. Probes run oldest first, so there is no booked time. The next one usually comes by 2026-11-10 04:40 UTC (within 120 hours of the last).
    No Base purchase is on this listing.
    After a fixEmail me when this result changesDispute this recordA dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

2.How to read this

Each listing shows its latest Base attempt and up to four earlier Base attempts. Result and Whose side follow that Base attempt. A purchase on another chain is listed under Other chains, with the chain name, time, status, HTTP status, and a transaction link when one was recorded. The record page shows that purchase in the Payment chain column. 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 “attribution under review” while that review runs. The review has no set date. 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 when the purchase is on Base. “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 reads the same sorting as this page: a failure counts against the seller only when this page puts it on the seller's side. A paid attempt that took payment and did not deliver is a WARN, and two or more of them on the seller's side since the last delivery are the only way a failed purchase makes it a BLOCK; a listing whose failures this page leaves not sorted gets at most a WARN from them. An L0 check that is unverified (not probed yet, or not measurable) is a WARN, not a BLOCK. The codes that decided the answer come first, each with the meaning from the reason-code table (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. The time filled in is the latest Base attempt when that listing has a Base purchase. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.