Documentation

Everything you need to integrate Sealed for AI into your pipeline. Five minutes to first seal.

Quickstart (5 minutes)

# Install
pip install sealed-for-ai      # Python 3.11+
# or
npm install @epochquant/sealed-for-ai   # Node 18+ / Bun / Workers

# Get a free key at https://ai.epochpay.today
export SEALED_AI_KEY=sk-ai-...

# Seal your first artifact
python -c "
from sealed_for_ai import SealedAIClient
import hashlib
c = SealedAIClient()
r = c.seal(
    artifact_kind='llm_output',
    subject='my first sealed AI output',
    payload_sha256=hashlib.sha256(b'hello').hexdigest(),
)
print('Verifier:', r.verifier_url)
"

Five integration patterns

LLM output

Seal every text completion. Most common attach point.

artifact_kind="llm_output"

RAG response

Bind the (question, retrieved doc IDs, answer) tuple. Auditor can re-verify citations.

artifact_kind="rag_response"

Agent action

Seal the decision BEFORE executing the tool. Survives execution failures.

artifact_kind="agent_action"

Training slice

Freeze the slice manifest + hyperparameters before training starts. Strongest "what trained this model" defense.

artifact_kind="training_slice"

Evaluation run

Seal the (eval suite, model, scores) tuple. Re-verifiable months later.

artifact_kind="eval_run"

Pipeline chain

Multi-step? Use chain_prev to bind each seal to the previous one's hash.

chain_prev=prior.full_hash

API reference

Method	Path	Purpose
POST	`/api/seal`	Mint a sealed receipt
GET	`/api/verify/{seal_id}`	Look up a seal by ID
GET	`/api/healthz`	Liveness probe
GET	`/api/openapi.json`	OpenAPI 3.0.3 spec

Auth: Authorization: Bearer sk-ai-.... CORS enabled on all /api/* paths.

POST /api/seal

POST /api/seal HTTP/1.1
Authorization: Bearer sk-ai-...
Content-Type: application/json

{
  "artifact_kind": "llm_output",
  "subject": "Generated for customer 42",
  "payload_sha256": "9f3c...e1",
  "metadata": { "model": "claude-opus-4-7" },
  "retention_years": 7,
  "chain_prev": null
}

Response:

{
  "ok": true,
  "seal_id": "EP-DKAP-A5C2F07B...",
  "full_hash": "a5c2f07b...8983",
  "verifier_url": "https://chain.epochcoreqcs.com/v1/verify?hash=...&full=1",
  "qr_target": "https://seal.epochpay.today/v/...",
  "sealed_at": "2026-05-17T03:06:44.774Z",
  "retention_until": "2033-05-17T03:06:44.774Z",
  "watermark": "EPOCHCORE™_DKAP_CEO_...",
  "seal_algorithm": "SHA-256",
  "signature_algorithm": "Ed25519+ML-DSA-87",
  "authentication_basis": "SEC-17a-4"
}

Errors

Status	Meaning
400	Validation error
401	Missing/invalid bearer token
429	Plan limit or rate limit exceeded
502	Upstream broker unavailable (retryable)

SDKs

Python

pip install sealed-for-ai

Python 3.11+. Sync + async clients.

TypeScript

npm install @epochquant/sealed-for-ai

Node 18+, Bun, Cloudflare Workers, Deno, browsers.

curl

POST /api/seal

No SDK needed — see the OpenAPI spec.

Compliance

Sealed for AI is engineered to satisfy provenance, retention, and tamper-evidence requirements across four regimes:

SEC 17 CFR § 240.17a-4 — non-rewriteable retention, serialized records, third-party verification
FINRA Rule 4370 — independent-of-vendor record access via on-chain anchor
SOC 2 (TSC 100) — Security, Availability, Processing Integrity, Confidentiality, Privacy
EU AI Act — Articles 12, 13, 14, 50 (record-keeping, transparency, oversight, content disclosure)

For procurement / vendor security questionnaires: lead with the verifier URL on a real seal. The math is the evidence.

→ Try the interactive verifier
→ See pricing tiers
→ Talk to us about Enterprise