DocsOpen appApp

PRODUCT UTILITY / STRICT PAYG

ONE JOB.
ONE OUTPUT.
ONE RECEIPT.

SHREDDAR turns sensitive text and documents into smaller, purpose-bounded context before AI systems, agents, or tools receive it. People and machines pay for completed privacy work—not access time.

OPEN THE APP ↗SEE $SHRED TERMS →
COMMERCIAL MODEL
PAY AS YOU GO
UNIT OF SALE
COMPLETED OUTPUT
TOKEN
OPTIONAL / PRE-LAUNCH
WALLET IN PRODUCT
NONE
A private SHREDDAR document is separated into bounded task routes before sparse protected context reaches external intelligence
UTILITY / 01SELL THE RESULT. MINIMIZE THE EXPOSURE.
One use, one posted price, one completed output, one receipt.No subscriptionsNo prepaid creditsNo bundlesNo consultant tiers
01 / WHAT THE PRODUCT DOES

A privacy layer
for every caller.

Live behavior and roadmap behavior are labeled separately. A protocol name is not evidence that its adapter or payment route is already operational.

01LIVE ALPHA

TEXT + DOCUMENT TOOLS

Detect, minimize, pseudonymize, generalize, conceptualize, block, and preview protected context before it reaches another system.

PRICED UNITOne locally protected text or supported file result
02AVAILABLE SELF-HOSTED

AI + API GATEWAY

Place an OpenAI-compatible boundary in front of a configured model so only policy-approved context is forwarded.

PRICED UNITOne protected inference with its Privacy Receipt
03PLANNED

AI AGENTS

Give an autonomous agent a bounded privacy step before it invokes a model, API, database, or external tool.

PRICED UNITOne completed privacy operation for one agent task
04PLANNED

MCP TOOLS

Expose analyze, protect, SHARD, and receipt functions as typed tools with explicit input and output schemas.

PRICED UNITOne completed MCP tool result
05PLANNED

VIRTUALS ACP

Offer a bounded SHREDDAR service through an agent-commerce job lifecycle with a defined deliverable and acceptance state.

PRICED UNITOne accepted and completed privacy job
06HELD

x402

Return a machine-readable price, verify payment, perform one operation, and attach settlement plus privacy evidence to the result.

PRICED UNITOne paid HTTP resource response
02 / SERVICE CONTRACT

From request
to verified result.

Every commercial adapter must preserve the same bounded unit even when the caller, payment rail, or workload size changes.

  1. 01

    REQUEST

    Caller states the bounded job and supplies authorized source context.

  2. 02

    QUOTE

    The route exposes one price for one defined result.

  3. 03

    SHRED

    SHREDDAR minimizes and transforms context inside the trusted boundary.

  4. 04

    DELIVER

    The caller receives the protected result or completed inference.

  5. 05

    RECEIPT

    Privacy and payment evidence remain distinct and independently inspectable.

REFERENCE PROTOCOLSMCP SPECIFICATION ↗x402 DOCUMENTATION ↗VIRTUALS ACP PLAYBOOK ↗
03 / REVENUE STREAMS

Six routes.
One PAYG rule.

Revenue is earned only when a defined output is completed and its payment settles. Roadmap routes remain projections until code, pricing, settlement, and recovery controls are verified.

BUYERCHANNELPRICED OUTPUTSETTLEMENTSTATUS
INDIVIDUAL USERWalletless PAYGOne protected text, document, or inference resultTokenless payment first; optional wallet settlement only after implementationPLANNED
AI AGENT / APIMetered endpointOne protect, infer, inspect, and receipt operationAPI-native payment or future $SHRED routePLANNED
MCP CLIENTTyped privacy toolOne successful tool result returned to the callerPer-call quote with receipt referencePLANNED
ACP AGENTBounded service jobOne accepted deliverable under the job termsACP-compatible job settlementPLANNED
x402 CLIENTHTTP 402 resourceOne verified and fulfilled HTTP responsePayment-signature verification and settlement responseHELD
PROJECT / TEAMMetered project runEach completed file or result at a posted volume rateConsolidated invoice and receipts; no prepaid package or bundlePLANNED
PROJECT-SCALE USAGEMore volume changes the posted rate—not the unit of sale.

Posted per-output volume schedules and consolidated reporting; no prepaid package or committed bundle. Each file or result stays metered and traceable.

04 / REVENUE ACCOUNTING

Keep every value
in its own ledger.

Product demand, protocol fees, treasury activity, and token-market activity answer different questions. SHREDDAR will not collapse them into one profit claim.

01

PRODUCT REVENUE

Count only settled customer payments for completed SHREDDAR outputs.

02

CREATOR-FEE RECEIPTS

Track realized 2% $SHRED creator-fee receipts separately if the Pons launch occurs and trades settle.

03

TREASURY PROCEEDS

Record any later reserve sale as treasury proceeds with transaction, cost basis, and use—not as product revenue.

04

MARKET ACTIVITY

Price, volume, market value, wallet count, and unrealized holdings are never reported as revenue or profit.

05 / OPTIONAL TOKEN RAIL

Product utility first.
$SHRED second.

If launched, $SHRED can become one optional settlement asset for these individually priced outputs. Tokenless PAYG remains available, and neither the website nor app adds a wallet connection.

FULL $SHRED PAGE →
UTILITY ≠ GUARANTEED DEMAND

These routes describe a product and revenue strategy, not current volume, guaranteed adoption, token value, or investment return. Only the browser-local proof and self-hostable gateway are available in the alpha; MCP, ACP, x402, wallet settlement, and paid production routes are not live.

READ THE TECHNICAL SPECIFICATION →