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

api.linkedpanda.com: x402 purchase results on Base, as of 2026-09-29

10 Base listings. By the latest attempt at each: 2 delivered · 0 failed on the seller's side · 5 on vet402's side · 1 awaiting on-chain verification · 1 not sorted (vet402 cannot show the failure was not its own) · 1 not tried yet. Latest attempt: 2026-09-29 03:32 UTC. Leaving out attempts that failed on vet402's side, were not bought, or are not sorted, the latest result that says something about the seller is: 5 delivered · 0 failed on the seller's side · 4 with no such result among the attempts shown.

Rows marked census or retest were bought to give this seller a row of its own, or to buy again after a failure on vet402's side.

1.Your listings

  1. api.linkedpanda.com/agent/v1/companies/enrichPOST
    Latest attempt
    2026-09-29 03:32 UTC
    Result
    awaiting on-chain verification
    Whose side
    not sorted: awaiting on-chain verification
    What we saw: The seller returned a settlement receipt, and vet402 has not confirmed that transaction on-chain yet. Until it is confirmed or refuted, this purchase is neither delivered nor failed.Last result about the seller: none among the attempts shown. The latest purchase is awaiting on-chain verification; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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.05 USDC · payTo 0xe740…cf46 · nonce 0x8d01…1c87 · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settle_claimed (the seller returned a receipt that vet402 has not re-read on-chain yet) · HTTP 201 · tx 0x0645f6a1…7d62 · bought by the retestIn export.csv?days=2: the row with attempted_at 2026-09-29T03:32:20Z and resource_key api.linkedpanda.com/agent/v1/companies/enrich.Dispute this purchaseEmail me when this result changes
  2. api.linkedpanda.com/agent/v1/profiles/enrichGET
    Latest attempt
    2026-09-24 12:01 UTC
    Result
    vet402 did not send the declared query
    Whose side
    vet402's side
    What we saw: Before 2026-09-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.Last result about the seller: none among the attempts shown. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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.05 USDC · payTo 0xe740…cf46 · nonce 0x1517…5638 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.In export.csv this row's held_reason is unsettled_4xx (the paid request got a 4xx with no settlement receipt and no transaction). This page names the cause the row shows: vet402 did not send the declared query.This failure was on vet402's side, not the seller's.Recorded (L1 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=6: the row with attempted_at 2026-09-24T12:01:55Z and resource_key api.linkedpanda.com/agent/v1/profiles/enrich.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-18 00:01 UTC · vet402 did not send the declared query · 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-27 23:27 UTC, vet402 did not add the query parameters the seller's 402 declares to paid requests on Base, and this listing declares them (example values, or required names). The seller refused the request with 400 or 422.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0x5905…962f · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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 query.
      Dispute this purchase
  3. api.linkedpanda.com/agent/v1/profiles/postsPOST
    Latest attempt
    2026-09-22 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 201.The 402 terms vet402 paid: vet402 signed: exact · 0.25 USDC · payTo 0xe740…cf46. 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.25 USDC · payTo 0xe740…cf46 · nonce 0x814f…7eb1 · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.The latest purchase delivered. An earlier attempt listed below did not.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0xcbdafe64…f271In export.csv?days=8: the row with attempted_at 2026-09-22T12:09:47Z and resource_key api.linkedpanda.com/agent/v1/profiles/posts.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-15 23:49 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 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 paid: vet402 signed: exact · 0.25 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0xfea1…48b2 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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. 2026-09-09 19:01 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 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 paid: vet402 signed: exact · 0.25 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0xd091…3e0d · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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
  4. api.linkedpanda.com/agent/v1/profiles/emailPOST
    Latest attempt
    2026-09-15 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 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0x8ee2…4368 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This 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=15: the row with attempted_at 2026-09-15T12:08:40Z and resource_key api.linkedpanda.com/agent/v1/profiles/email.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-09 01: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 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 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0x28f5…e9ee · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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. 2026-09-02 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 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 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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. api.linkedpanda.com/agent/v1/profiles/searchPOST
    Latest attempt
    2026-09-15 06: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: delivered on 2026-09-08 19:01 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce 0xa482…d8e8 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This 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=15: the row with attempted_at 2026-09-15T06:00:55Z and resource_key api.linkedpanda.com/agent/v1/profiles/search.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-08 19:01 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x5ef46f34…2647
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce 0x3a69…b404 · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-08-27 12:30 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x6ba6dd07…2351
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    3. 2026-08-20 12:54 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x0907c146…02f9
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    4. 2026-08-14 09:54 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0xef5c6c54…9bd1
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  6. api.linkedpanda.com/agent/v1/ads/searchPOST
    Latest attempt
    2026-09-14 06:01 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: delivered on 2026-09-05 12:09 UTC. The latest attempt failed on vet402's side; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0xfa2b…e0c3 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing for the seller to fix.This 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-14T06:01:15Z and resource_key api.linkedpanda.com/agent/v1/ads/search.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-05 12:09 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x9e56688e…3edd
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0x84b6…2369 · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  7. api.linkedpanda.com/agent/v1/companies/searchPOST
    Latest attempt
    2026-09-12 18:02 UTC
    Result
    vet402 cannot show its wallet held the price
    Whose side
    not sorted: vet402 unproven
    What we saw: This purchase is from before vet402 checked its wallet's balance before signing (2026-09-16 23:25 UTC), and the balance rebuilt from the wallet's on-chain transfers does not show that it held the price at the time. The row is not counted against the seller.Last result about the seller: delivered on 2026-09-01 12:08 UTC. The latest attempt is not sorted; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce 0x7b5f…1b03 · validBefore not recorded.Answer to the paid request: HTTP 500 · Content-Type application/json; charset=utf-8 · no PAYMENT-RESPONSE recorded.What to fix: Nothing is counted against the seller.Not shown for this row: vet402 cannot show its wallet held the price at signing; vet402 has no record of the input it sent.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 500 · no txIn export.csv?days=18: the row with attempted_at 2026-09-12T18:02:04Z and resource_key api.linkedpanda.com/agent/v1/companies/search.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-09-01 12:08 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x682d20f8…33e8
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-08-25 12:53 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0xd9ba9b1c…f73b
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.3 USDC · payTo 0xe740…cf46. 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.3 USDC · payTo 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  8. api.linkedpanda.com/agent/v1/jobs/searchPOST
    Latest attempt
    2026-09-10 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 201.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0xc479…f30e · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x82887c8c…60f8In export.csv?days=20: the row with attempted_at 2026-09-10T12:09:08Z and resource_key api.linkedpanda.com/agent/v1/jobs/search.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-08-31 12:07 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x9339ace4…8fcf
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    2. 2026-08-24 23:34 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0xc83c2c90…a8ea
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
    3. 2026-08-17 12:47 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 201 · tx 0x8b013db5…8628
      What vet402 recordedPaid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 201.The 402 terms vet402 paid: vet402 signed: exact · 0.05 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 201 · Content-Type application/json; charset=utf-8 · PAYMENT-RESPONSE: success true, names a transaction.
      Dispute this purchase
  9. api.linkedpanda.com/agent/v1/geo-idPOST
    Latest attempt
    2026-09-10 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 paid: vet402 signed: exact · 0.01 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce 0x8a54…1853 · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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.This 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=20: the row with attempted_at 2026-09-10T07:02:19Z and resource_key api.linkedpanda.com/agent/v1/geo-id.Dispute this purchaseEmail me when this result changes
    Earlier attempts
    1. 2026-08-31 12:08 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 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 paid: vet402 signed: exact · 0.01 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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. 2026-08-24 23:34 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 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 paid: vet402 signed: exact · 0.01 USDC · payTo 0xe740…cf46. 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 0xe740…cf46 · nonce not recorded · validBefore not recorded.Answer to the paid request: HTTP 400 · Content-Type application/json; charset=utf-8 · 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
  10. api.linkedpanda.com/agent/v1/profiles/:linkedinIdPOST
    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. 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.