DOCS/BUILD
HOLD7 MIN READUPDATED 03 SEP 2026

BUILD / 07

Machine payments should be as bounded as the data.

The planned x402 settlement boundary, token-meter quote, and current HOLD state.
SHREDDAR plans to quote individual privacy operations over HTTP, with larger inputs costing more. The current alpha exposes a status route only: payment is disabled, no amount is requested, and no settlement occurs.
LIVE STATUS ROUTE

Inspect the hold state

CURLbash
curl -H "Authorization: Bearer $SHREDDAR_API_KEY" \
  http://127.0.0.1:8787/v1/payments/x402
PLANNED FLOW

Quote → authorize → verify → process → receipt

  1. 01

    METER

    Derive an input-context token count before private processing begins.

  2. 02

    QUOTE

    Return a deterministic per-use amount using the publicly posted rate and rounding rule.

  3. 03

    AUTHORIZE

    The caller signs or submits the protocol-defined payment payload to the exact verified destination.

  4. 04

    VERIFY

    Reconcile the payment state once. Never blindly retry after a timeout that may have settled.

  5. 05

    PROCESS

    Run one bounded operation only after payment evidence is valid.

  6. 06

    RECEIPT

    Link the quote, payment evidence, metered use, and Privacy Receipt without recording source content.

ACTIVATION GATE

Evidence required before enabled true

  • Posted $SHRED or tokenless PAYG rate with currency, precision, and expiry.
  • Verified chain, asset contract, recipient, facilitator, and network fees.
  • Idempotent verification and settlement plus unknown-state recovery.
  • Quote and payment receipt tests for minimum, maximum, replay, expiry, and partial failure.
  • Project-specific legal and accounting treatment.
SHREDDAR DOCSYOUR DOC. YOUR DATA. YOUR CONTROL.

Public alpha documentation. Capability labels describe implementation state, not certification or guaranteed suitability.