dicta-notes.com
5 Base listings. By the latest purchase of each: 3 delivered · 1 failed on the seller's side · 0 on vet402's side · 1 not yet bought. Latest purchase: 2026-09-08 01:02 UTC.
1.Your listings
| Listing | Latest purchase | Result | Whose side |
|---|---|---|---|
| dicta-notes.com/routes/x402/stt-session/30POST | 2026-09-08 01:02 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0x694f4a17…338dIn export.csv?days=22: the row with attempted_at 2026-09-08T01:02:16Z and resource_key dicta-notes.com/routes/x402/stt-session/30. | |||
| dicta-notes.com/routes/x402/stt-session/15POST | 2026-09-07 12:09 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xbf773238…2e6aIn export.csv?days=22: the row with attempted_at 2026-09-07T12:09:21Z and resource_key dicta-notes.com/routes/x402/stt-session/15. | |||
| dicta-notes.com/routes/x402/transcribe-longPOST | 2026-09-07 07:02 UTC | No answer to the paid request | seller's side |
What we saw: vet402 signed the payment and the paid request got no HTTP answer in time (timeout, 408 or a closed connection).What to fix: Make the paid route answer within a few seconds; look for slow upstream calls or cold starts. (a server change)Recorded: settle_failed · HTTP — · no txIn export.csv?days=22: the row with attempted_at 2026-09-07T07:02:15Z and resource_key dicta-notes.com/routes/x402/transcribe-long. | |||
| dicta-notes.com/routes/x402/stt-session/5POST | 2026-09-06 19:01 UTC | delivered | — |
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.Recorded: settled · HTTP 200 · tx 0xc4a9ac98…32abIn export.csv?days=23: the row with attempted_at 2026-09-06T19:01:29Z and resource_key dicta-notes.com/routes/x402/stt-session/5. | |||
| dicta-notes.com/routes/x402/transcribePOST | not yet bought | — | — |
| vet402 has not bought this listing yet. | |||
2.How to read this
Each listing shows its latest purchase on Base and up to four earlier ones. Whose side says where the failure came from: the seller's answer or listing, or vet402 itself. A row held (held_reason in the export) is not counted against the seller in the delivered numbers, because vet402 cannot rule out that its request was the problem. 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?
Open the listing's record (the link in the first column) and use “Dispute this record” there. Say which purchase and what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.