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

vet402Sellers · What to fix firstMethodology

api.carbon-cashmere.de: x402 purchase results on Base, latest attempt 2026-09-26

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

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

1.Your listings

api.carbon-cashmere.de/v1/bittensor-derivatives/network-fundamentalsGET
Latest attempt
2026-09-26 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.02 USDC · payTo 0xf8b2…f2ee. 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.02 USDC · payTo 0xf8b2…f2ee · nonce 0x76fb…d248 · 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 0xc6d23bf3…e269In export.csv?days=4: the row with attempted_at 2026-09-26T18:02:18Z and resource_key api.carbon-cashmere.de/v1/bittensor-derivatives/network-fundamentals.Dispute this purchase Email me when this result changes
Earlier attempts
1. 2026-09-17 06:00 UTC · delivered · no failure (delivered)settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x84476992…edd5
  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.02 USDC · payTo 0xf8b2…f2ee. 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 0xf8b2…f2ee · nonce 0x5030…0219 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.
  Dispute this purchase
api.carbon-cashmere.de/v1/btc-derivatives/blocks-rangeGET
Latest attempt
2026-09-17 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.02 USDC · payTo 0xf8b2…f2ee. 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 0xf8b2…f2ee · nonce 0xd5c4…54a9 · 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 0x97b58d09…88ebIn export.csv?days=14: the row with attempted_at 2026-09-17T00:01:20Z and resource_key api.carbon-cashmere.de/v1/btc-derivatives/blocks-range.Dispute this purchase Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/fee-estimateGET
Latest attempt
2026-09-12 06:00 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.03 USDC · payTo 0xf8b2…f2ee. 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 0xf8b2…f2ee · nonce 0x6ec3…84c8 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xd27e3df0…51ceIn export.csv?days=19: the row with attempted_at 2026-09-12T06:00:57Z and resource_key api.carbon-cashmere.de/v1/kaspa-derivatives/fee-estimate.Dispute this purchase Email me when this result changes
api.carbon-cashmere.de/v1/subtensor-derivatives/block-metricsGET
Latest attempt
2026-09-09 12:08 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.02 USDC · payTo 0xf8b2…f2ee. 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 0xf8b2…f2ee · nonce 0x8ff4…3d01 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x53ab4f7b…8670In export.csv?days=21: the row with attempted_at 2026-09-09T12:08:03Z and resource_key api.carbon-cashmere.de/v1/subtensor-derivatives/block-metrics.Dispute this purchase Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/dag-stateGET
Latest attempt
2026-09-07 12:10 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.02 USDC · payTo 0xf8b2…f2ee. 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 0xf8b2…f2ee · nonce 0x2b32…eb3e · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Decision API now: · the full answerRecorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xe347adc4…4967In export.csv?days=23: the row with attempted_at 2026-09-07T12:10:00Z and resource_key api.carbon-cashmere.de/v1/kaspa-derivatives/dag-state.Dispute this purchase Email me when this result changes
api.carbon-cashmere.de/v1/bittensor-derivatives/alpha-price-history/:netuidGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/bittensor-derivatives/alpha-pricesGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/bittensor-derivatives/registration-cost-historyGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/bittensor-derivatives/subnet/:netuid/emission-trendGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/bittensor-derivatives/subnet/:netuid/metagraphGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/blocks/:heightGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/coinbase-messagesGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/diversityGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/fee-curveGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/mempool-pressureGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/btc-derivatives/ordinals-flowGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/blocks/:block_hashGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/diversityGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/fee-regimeGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/mempool-pulseGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/mining-economicsGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/kaspa-derivatives/recent-blocksGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/subtensor-derivatives/evm-activityGET
Latest attempt
not tried yet
Result
—
Whose side
—
vet402 has not tried to buy this listing yet.Email me when this result changes
api.carbon-cashmere.de/v1/subtensor-derivatives/transfer-flowGET
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.