curatoria.dev

diagnostics / buyer dogfood

Debug paid delivery, not the primary buying path.

Curatoria's primary path is agent-first: an agent reads the catalog, confirms the exact payment challenge, pays, saves the file locally, and reports proof. This browser page stays as a support surface for testing catalog, payment, and byte-preserving delivery behavior. The wallet approves payment only; the downloaded file belongs in your browser's download folder, never in the wallet.

Intended agent proof

  1. Read /.well-known/design-catalog.json and choose a paid asset.
  2. Request its paid route and verify the 402 amount, resource, network, and payTo.
  3. Pay with an agent wallet, fetch the paid response as raw bytes, and write those bytes to a local path.
  4. Report saved path, byte count, MIME type, SHA-256, and payment transaction.
  5. For this browser flow, save the generated receipt beside the PSD, then run node --require ts-node/register scripts/verify-browser-download.ts --receipt <receipt.json> --file <actual-saved.psd> --receipt-id <id> --product <product> --transaction <tx> --entitlement-fingerprint <sha256>. Copy the four identity values from the confirmation/receipt. A browser collision rename is allowed only when the supplied identity and bytes match.