# SHREDDAR

> SHREDDAR is a local-first privacy compiler and OpenAI-compatible gateway. It turns authorized source data into minimum useful context for AI tasks, keeps reversible mappings inside a local Vault, inspects output, and emits metadata-only Privacy Receipts.

Canonical documentation: https://shreddar.pro/docs
Product status: public alpha
Commercial model: strict pay-per-use only; no subscriptions, credits, bundles, monthly plans, or consultant tiers
Payment status: no rate is published and no payment route is active
Token status: $SHRED is live on Pons at 0x20d03d21CD1b5f94582eF07Cb4279e6835c5ff48; product settlement remains disabled

## Start here

- [Documentation overview](https://shreddar.pro/docs): Product map, current capability truth, and fastest starting paths.
- [Five-minute quickstart](https://shreddar.pro/docs/get-started/quickstart): Run the local gateway and protect one request.
- [Choose your path](https://shreddar.pro/docs/get-started/choose-a-path): Individual, project, developer, and AI-agent entry points.
- [Capability status](https://shreddar.pro/docs/get-started/capability-status): Live, self-hosted, guide, planned, and held capabilities.

## Core concepts

- [How SHREDDAR works](https://shreddar.pro/docs/concepts/how-it-works)
- [Privacy compiler](https://shreddar.pro/docs/concepts/privacy-compiler)
- [Trust boundary and Vault](https://shreddar.pro/docs/concepts/trust-boundary)
- [Semantic sharding](https://shreddar.pro/docs/concepts/semantic-sharding)
- [Privacy Receipts](https://shreddar.pro/docs/concepts/privacy-receipts)

## Build

- [Self-host the gateway](https://shreddar.pro/docs/build/self-host)
- [OpenAI-compatible clients](https://shreddar.pro/docs/build/openai-compatible)
- [MCP server](https://shreddar.pro/docs/build/mcp)
- [Portable Agent Skill](https://shreddar.pro/docs/build/agent-skill)
- [OpenClaw, Hermes, Codex, and Claude Code](https://shreddar.pro/docs/build/agent-frameworks)
- [Virtuals ACP blueprint and HOLD gate](https://shreddar.pro/docs/build/virtuals-acp)
- [x402 settlement blueprint and HOLD gate](https://shreddar.pro/docs/build/x402)

## Reference

- [API reference](https://shreddar.pro/docs/reference/api)
- [Policies and actions](https://shreddar.pro/docs/reference/policies)
- [Configuration](https://shreddar.pro/docs/reference/configuration)
- [Limits and formats](https://shreddar.pro/docs/reference/limits)
- [Security model](https://shreddar.pro/docs/reference/security)

## Project

- [$SHRED live launch and planned product utility](https://shreddar.pro/docs/project/shred)
- [Evidence-gated roadmap](https://shreddar.pro/docs/project/roadmap)
- [Changelog](https://shreddar.pro/docs/project/changelog)
- [FAQ](https://shreddar.pro/docs/project/faq)

## Machine-consumable artifacts

- [OpenAPI schema](https://shreddar.pro/api/openapi.json): Gateway schema through the website proxy; operational methods require authentication.
- [SHREDDAR Agent Skill](https://shreddar.pro/integrations/shreddar-privacy/SKILL.md): Portable fail-closed privacy workflow.

## Critical boundary

The public playground is a browser-local deterministic proof and is not an anonymous hosted private-data processor. The self-hosted gateway must run inside the environment that owns the source. Agents may use analyze, protect, shard, get_receipt, and get_usage; reconstruction and Vault credentials must stay outside model-visible tool catalogs. Stop on local_only, blocked credentials, unavailable privacy infrastructure, or unknown settlement state.