DOCS/CORE CONCEPTS
LIVE7 MIN READUPDATED 03 SEP 2026

CORE CONCEPTS / 05

Evidence without keeping the source.

Understand receipt fields, integrity chaining, usage meters, and verification limits.
A Privacy Receipt records what control path ran without becoming another store of sensitive prompts. It supports audit and debugging, but it is not proof that detection was perfect or that a deployment is legally compliant.
RECEIPT CONTENT

What the record contains

FIELD GROUPEXAMPLESPURPOSE
Identityrequest_id, created_atLocate one operation without source content
Executionprovider, model, software_versionName the processing path
Policypolicy_id, policy_hashPin the transformation rules
Magnitudeoriginal_characters, external_characters, reductionMeasure how much context moved
Decisionrisk_before, risk_after, route, shardsExplain the boundary outcome
Integrityprevious_hash, receipt_hash, anchor_statusDetect local record modification and preserve order
VERIFICATION

Read and verify a receipt

READbash
curl -H "Authorization: Bearer $SHREDDAR_API_KEY" \
  http://127.0.0.1:8787/v1/receipts/shr_REQUEST_ID
VERIFY CHAINbash
curl -H "Authorization: Bearer $SHREDDAR_API_KEY" \
  http://127.0.0.1:8787/v1/receipts/shr_REQUEST_ID/verify
TOKEN METER

Usage is measured; price is not invented

The alpha estimates input and external context tokens from character counts, reports tokens prevented from external use, and aggregates protected operations. The posted $SHRED rate is null, cost is null, and pricing_status remains RATE_NOT_PUBLISHED until a verified rate exists.

  • Metering unit: input_context_token.
  • Larger inputs imply larger future quotes under the planned per-use formula.
  • No subscription, credit pack, bundle, or monthly plan is permitted.
  • A cost becomes a settled fact only with a posted rate and payment receipt.
SHREDDAR DOCSYOUR DOC. YOUR DATA. YOUR CONTROL.

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