Skip to main content
vet402
Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 06:51 UTC · reused for up to 5 min
vet402Sellers · What to fix firstMethodology

apiacre.com: x402 purchase results on Base, latest attempt 2026-09-27

74 Base listings. Latest result about the seller at each listing: 3 delivered · 0 failed on the seller's side · 16 with no such result among the attempts shown · 55 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: 3 delivered · 0 failed on the seller's side · 16 on vet402's side · 55 not tried yet.

Latest attempt: 2026-09-27 18:02 UTC. This page read the ledger at 2026-09-29 06:51 UTC and reuses that read for up to 5 min.

1.Your listings

  1. apiacre.com/v1/data/current-weatherPOST
    Latest attempt
    2026-09-27 18: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 0xa0bf…869b. 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 0xa0bf…869b · nonce 0x96c5…30a9 · 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 0x338e5d36…aab5In export.csv?days=3: the row with attempted_at 2026-09-27T18:02:15Z and resource_key apiacre.com/v1/data/current-weather.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-13 06:01 UTC · vet402's wallet was out of USDC · vet402's sidesettle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))
      What vet402 recordedBetween 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).The 402 terms vet402 signed: vet402 signed: exact · 0.001 USDC · payTo 0xa0bf…869b. 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 0xa0bf…869b · nonce 0x6cfa…116e · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
      Dispute this purchase
    2. 2026-09-04 07: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 422 · 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 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 0xa0bf…869b. 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 0xa0bf…869b · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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
  2. apiacre.com/v1/research/sec-company-evidencePOST
    Latest attempt
    2026-09-25 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.01 USDC · payTo 0xa0bf…869b. 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.01 USDC · payTo 0xa0bf…869b · nonce 0x0059…a264 · 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 answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x2d7b1786…186dIn export.csv?days=5: the row with attempted_at 2026-09-25T12:02:20Z and resource_key apiacre.com/v1/research/sec-company-evidence.Dispute this purchaseEmail me when this result changes
  3. apiacre.com/v1/crypto/base-network-statusPOST
    Latest attempt
    2026-09-22 06:01 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 0xa0bf…869b. 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 0xa0bf…869b · nonce 0x8e24…464b · 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 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 0x424cf8e2…0871In export.csv?days=9: the row with attempted_at 2026-09-22T06:01:43Z and resource_key apiacre.com/v1/crypto/base-network-status.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-15 23:49 UTC · Not bought: server error before payment · not bought: vet402 did not payno_402 (the unpaid request did not get a 402, so nothing was paid) · HTTP — (unpaid answer 522) · no tx
      What vet402 recordedThe unpaid request got a 5xx, so there was no 402 to pay and vet402 did not pay.The 402 vet402 saw: The unpaid request got HTTP 522, not a 402.
      Dispute this purchase
    2. 2026-09-09 19:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5f9b3f40…797e
      What vet402 recordedPaid; 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 0xa0bf…869b. 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 0xa0bf…869b · nonce 0x94f5…1c2c · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  4. apiacre.com/v1/data/us-address-geocodePOST
    Latest attempt
    2026-09-15 00:00 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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.005 USDC · payTo 0xa0bf…869b. 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.005 USDC · payTo 0xa0bf…869b · nonce 0x3db9…0404 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=16: the row with attempted_at 2026-09-15T00:00:42Z and resource_key apiacre.com/v1/data/us-address-geocode.Dispute this purchaseEmail me when this result changes
  5. apiacre.com/v1/crypto/base-account-statusPOST
    Latest attempt
    2026-09-13 12:08 UTC
    Result
    vet402's wallet was out of USDC
    Whose side
    vet402's side
    What we saw: Between 2026-09-13 00:00 and 2026-09-15 23:49 UTC, vet402's Base payer wallet had run out of USDC. The seller refused a payment that had nothing behind it (402 or 5xx).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.003 USDC · payTo 0xa0bf…869b. 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 0xa0bf…869b · nonce 0xe29a…ae80 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.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 402 · no tx · held as payer_unfunded (a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15))In export.csv?days=17: the row with attempted_at 2026-09-13T12:08:59Z and resource_key apiacre.com/v1/crypto/base-account-status.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-03 12:07 UTC · vet402 did not send the declared request body · vet402's sidesettle_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)
      What vet402 recordedBefore 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.003 USDC · payTo 0xa0bf…869b. 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 0xa0bf…869b · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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
  6. apiacre.com/v1/research/wikidata-organization-searchPOST
    Latest attempt
    2026-09-07 01:00 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.015 USDC · payTo 0xa0bf…869b. 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.015 USDC · payTo 0xa0bf…869b · nonce 0x0e1f…2a59 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=24: the row with attempted_at 2026-09-07T01:00:37Z and resource_key apiacre.com/v1/research/wikidata-organization-search.Dispute this purchaseEmail me when this result changes
  7. apiacre.com/v1/research/crossref-work-searchPOST
    Latest attempt
    2026-09-07 01:00 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.008 USDC · payTo 0xa0bf…869b. 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.008 USDC · payTo 0xa0bf…869b · nonce 0x4345…a13a · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=24: the row with attempted_at 2026-09-07T01:00:26Z and resource_key apiacre.com/v1/research/crossref-work-search.Dispute this purchaseEmail me when this result changes
  8. apiacre.com/v1/data/contractPOST
    Latest attempt
    2026-09-06 07:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.035 USDC · payTo 0xa0bf…869b. 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.035 USDC · payTo 0xa0bf…869b · nonce 0x5c45…ec76 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=24: the row with attempted_at 2026-09-06T07:02:15Z and resource_key apiacre.com/v1/data/contract.Dispute this purchaseEmail me when this result changes
  9. apiacre.com/v1/research/organization-evidencePOST
    Latest attempt
    2026-09-06 07:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.1 USDC · payTo 0xa0bf…869b. 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.1 USDC · payTo 0xa0bf…869b · nonce 0x8e58…0760 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=24: the row with attempted_at 2026-09-06T07:02:14Z and resource_key apiacre.com/v1/research/organization-evidence.Dispute this purchaseEmail me when this result changes
  10. apiacre.com/v1/data/reverse-geocodePOST
    Latest attempt
    2026-09-06 07:01 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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 0xa0bf…869b. 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.002 USDC · payTo 0xa0bf…869b · nonce 0xca25…0476 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=24: the row with attempted_at 2026-09-06T07:01:54Z and resource_key apiacre.com/v1/data/reverse-geocode.Dispute this purchaseEmail me when this result changes
  11. apiacre.com/v1/research/lei-entity-searchPOST
    Latest attempt
    2026-09-06 01:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.01 USDC · payTo 0xa0bf…869b. 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 0xa0bf…869b · nonce 0x019e…38cf · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-06T01:02:07Z and resource_key apiacre.com/v1/research/lei-entity-search.Dispute this purchaseEmail me when this result changes
  12. apiacre.com/v1/crypto/base-contract-inspectPOST
    Latest attempt
    2026-09-05 19:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.005 USDC · payTo 0xa0bf…869b. 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.005 USDC · payTo 0xa0bf…869b · nonce 0xfd60…421d · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T19:02:16Z and resource_key apiacre.com/v1/crypto/base-contract-inspect.Dispute this purchaseEmail me when this result changes
  13. apiacre.com/v1/crypto/base-gas-estimatePOST
    Latest attempt
    2026-09-05 19:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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 0xa0bf…869b. 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.004 USDC · payTo 0xa0bf…869b · nonce 0x1969…1f21 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T19:02:15Z and resource_key apiacre.com/v1/crypto/base-gas-estimate.Dispute this purchaseEmail me when this result changes
  14. apiacre.com/v1/data/schemaorg-normalizePOST
    Latest attempt
    2026-09-05 19:01 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.02 USDC · payTo 0xa0bf…869b. 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.02 USDC · payTo 0xa0bf…869b · nonce 0x40bb…d45b · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T19:01:50Z and resource_key apiacre.com/v1/data/schemaorg-normalize.Dispute this purchaseEmail me when this result changes
  15. apiacre.com/v1/research/sec-filing-signalsPOST
    Latest attempt
    2026-09-05 12:09 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.05 USDC · payTo 0xa0bf…869b. 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.05 USDC · payTo 0xa0bf…869b · nonce 0xf4e8…cb9c · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T12:09:59Z and resource_key apiacre.com/v1/research/sec-filing-signals.Dispute this purchaseEmail me when this result changes
  16. apiacre.com/v1/research/sec-insider-transactionsPOST
    Latest attempt
    2026-09-05 12:09 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.03 USDC · payTo 0xa0bf…869b. 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.03 USDC · payTo 0xa0bf…869b · nonce 0x2ee0…5dba · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T12:09:25Z and resource_key apiacre.com/v1/research/sec-insider-transactions.Dispute this purchaseEmail me when this result changes
  17. apiacre.com/v1/web/robots-sitemapPOST
    Latest attempt
    2026-09-05 12:07 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.025 USDC · payTo 0xa0bf…869b. 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.025 USDC · payTo 0xa0bf…869b · nonce 0x4530…fd53 · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T12:07:45Z and resource_key apiacre.com/v1/web/robots-sitemap.Dispute this purchaseEmail me when this result changes
  18. apiacre.com/v1/web/full-auditPOST
    Latest attempt
    2026-09-05 07:02 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.25 USDC · payTo 0xa0bf…869b. 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.25 USDC · payTo 0xa0bf…869b · nonce 0xb8c4…7ffc · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T07:02:09Z and resource_key apiacre.com/v1/web/full-audit.Dispute this purchaseEmail me when this result changes
  19. apiacre.com/v1/web/accessibility-auditPOST
    Latest attempt
    2026-09-05 07:01 UTC
    Result
    vet402 did not send the declared request body
    Whose side
    vet402's side
    What we saw: Before 2026-09-16 23:25 UTC, vet402 sent an empty JSON body on paid POST requests, even when the listing declares a body. The seller refused it with 400, 415 or 422, and the payment did not settle (a payment that settled is under "Charged, then refused an input vet402 had not sent").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.05 USDC · payTo 0xa0bf…869b. 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.05 USDC · payTo 0xa0bf…869b · nonce 0x8a50…990e · validBefore not recorded.Answer to the paid request: HTTP 422 · Content-Type application/problem+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 request body.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=25: the row with attempted_at 2026-09-05T07:01:43Z and resource_key apiacre.com/v1/web/accessibility-audit.Dispute this purchaseEmail me when this result changes
  20. apiacre.com/v1/advertising/pixel-claimPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  21. apiacre.com/v1/commerce/product-pricePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  22. apiacre.com/v1/crypto/address-inspectPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  23. apiacre.com/v1/crypto/base-account-snapshotPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  24. apiacre.com/v1/crypto/base-block-inspectPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  25. apiacre.com/v1/crypto/base-contract-readPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  26. apiacre.com/v1/crypto/base-event-logsPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  27. apiacre.com/v1/crypto/base-transaction-inspectPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  28. apiacre.com/v1/crypto/base-usdc-transfersPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  29. apiacre.com/v1/crypto/calldata-decodePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  30. apiacre.com/v1/crypto/typed-data-hashPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  31. apiacre.com/v1/data/cleanPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  32. apiacre.com/v1/data/convertPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  33. apiacre.com/v1/data/deduplicatePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  34. apiacre.com/v1/data/ecb-fx-referencePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  35. apiacre.com/v1/data/json-repairPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  36. apiacre.com/v1/data/place-geocodePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  37. apiacre.com/v1/data/profilePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  38. apiacre.com/v1/data/schemaPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  39. apiacre.com/v1/data/schema-validatePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  40. apiacre.com/v1/data/timezone-convertPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  41. apiacre.com/v1/data/us-weather-forecastPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  42. apiacre.com/v1/data/vin-decodePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  43. apiacre.com/v1/data/worldbank-snapshotPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  44. apiacre.com/v1/developer/code-change-reviewPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  45. apiacre.com/v1/developer/code-metricsPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  46. apiacre.com/v1/developer/dependency-auditPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  47. apiacre.com/v1/developer/license-auditPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  48. apiacre.com/v1/developer/openapi-auditPOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  49. apiacre.com/v1/developer/openapi-test-generatePOST
    Latest attempt
    not tried yet
    Result
    —
    Whose side
    —
    vet402 has not tried to buy this listing yet.Email me when this result changes
  50. apiacre.com/v1/developer/secret-scanPOST
    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.