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

vet402Sellers · What to fix firstMethodology

agent.massive.com: x402 purchase results on Base, as of 2026-09-28

23 Base listings. By the latest attempt at each: 2 delivered · 0 failed on the seller's side · 1 on vet402's side · 1 not sorted (vet402 cannot show the failure was not its own) · 19 not tried yet. Latest attempt: 2026-09-28 00:01 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: 4 delivered · 0 failed on the seller's side · 0 with no such result among the attempts shown.

1.Your listings

agent.massive.com/stocks/filings/vX/risk-factorsGET
Latest attempt
2026-09-28 00:01 UTC
Result
Server error on the paid request
Whose side
not sorted: one failure so far
What we saw: vet402 signed the payment and the paid request got a 5xx.Last result about the seller: delivered on 2026-09-21 18:02 UTC. The latest attempt is not sorted; vet402 has not bought this listing again since.The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x525f…21e6. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xba30…34e3 · validBefore not recorded.Answer to the paid request: HTTP 502 · Content-Type application/json · no PAYMENT-RESPONSE recorded.What to fix: Nothing is counted against the seller. vet402 puts a failure on the seller's side only after it sees one at this listing on two different days (UTC). If this one is real: Check the route's logs: the handler or its upstream failed on the paid request.Recorded (L1 paid purchase): settle_failed (vet402 signed a payment and got no settlement receipt back) · HTTP 502 · no txIn export.csv?days=3: the row with attempted_at 2026-09-28T00:01:46Z and resource_key agent.massive.com/stocks/filings/vX/risk-factors.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-21 18:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xb2eb9161…5ca2
  What vet402 recorded
  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 0x525f…21e6. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x8435…4f42 · 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-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 recorded
  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).The 402 terms vet402 paid: vet402 signed: exact · 0.01 USDC · payTo 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xdd0f…9b42 · validBefore not recorded.Answer to the paid request: HTTP 402 · Content-Type application/json · no PAYMENT-RESPONSE recorded.
  Dispute this purchase
3. 2026-09-05 07:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x60c9b30c…34ac
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xdeef…06cf · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
agent.massive.com/stocks/filings/10-K/vX/sectionsGET
Latest attempt
2026-09-26 00: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.01 USDC · payTo 0x525f…21e6. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x0ecc…dafc · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x915b03fd…cb21In export.csv?days=5: the row with attempted_at 2026-09-26T00:01:16Z and resource_key agent.massive.com/stocks/filings/10-K/vX/sections.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-19 18:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x8fa6e8fa…5c51
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x587f…9e43 · 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-13 00:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x8257ea94…7f08
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x3cb2…7318 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
agent.massive.com/stocks/filings/8-K/vX/textGET
Latest attempt
2026-09-23 12: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.01 USDC · payTo 0x525f…21e6. Input sent: body none, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x1c3d…c668 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x30a0294c…4282In export.csv?days=7: the row with attempted_at 2026-09-23T12:01:43Z and resource_key agent.massive.com/stocks/filings/8-K/vX/text.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-17 00:02 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc8bfb673…4f5d
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xce7a…6d43 · 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-10 19:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x21cba633…b802
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0x5d8e…9a17 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
agent.massive.com/stocks/filings/vX/form-3GET
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 07:00 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.01 USDC · payTo 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xed6d…3561 · 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.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:04Z and resource_key agent.massive.com/stocks/filings/vX/form-3.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-05 07:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x767acca1…4f62
  What vet402 recorded
  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 0x525f…21e6. Input sent: body not recorded, query not recorded. The listing's maxTimeoutSeconds is 60; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0x525f…21e6 · nonce 0xb82c…557d · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
agent.massive.com/stocks/filings/8-K/vX/disclosuresGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/stocks/filings/vX/13-FGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/stocks/filings/vX/form-4GET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/stocks/filings/vX/indexGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/stocks/taxonomies/vX/disclosuresGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/stocks/taxonomies/vX/risk-factorsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v1/indicators/ema/:stockTickerGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v1/indicators/macd/:stockTickerGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v1/indicators/rsi/:stockTickerGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v1/indicators/sma/:stockTickerGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v1/open-close/:stocksTicker/:dateGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/aggs/grouped/locale/us/market/stocks/:dateGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/aggs/ticker/:stocksTicker/range/:multiplier/:timespan/:from/:toGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/reference/newsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/snapshot/locale/us/markets/stocks/:directionGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/snapshot/locale/us/markets/stocks/tickersGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v2/snapshot/locale/us/markets/stocks/tickers/:stocksTickerGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v3/reference/tickersGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
agent.massive.com/v3/reference/tickers/:tickerGET
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.