Skip to main content

SWT3 AI Witness SDK: cryptographic attestation for AI inference

Project description

Witness your AI, don't just run it. Cryptographic provenance for LLMs with zero data retention.

swt3-ai

SWT3 AI Witness SDK:continuous, cryptographic attestation for AI systems. Prove your models are running approved weights, safety guardrails are active, inferences are traceable, and fairness thresholds are met. All without your prompts or responses ever leaving your infrastructure.

Built on the SWT3 Protocol, the same cryptographic witnessing layer trusted for federal compliance (NIST 800-53, CMMC, FedRAMP).

See It Work in 10 Seconds

No API keys. No account. No network calls.

pip install swt3-ai
python -m swt3_ai.demo

You'll see the full SWT3 witnessing pipeline: hash, extract, clear, anchor, verify — all running locally. When you're ready for production, keep reading.

Three Lines of Code

from swt3_ai import Witness
from openai import OpenAI

witness = Witness(
    endpoint="https://sovereign.tenova.io",
    api_key="axm_live_...",
    tenant_id="YOUR_ENCLAVE",
)
client = witness.wrap(OpenAI())

# That's it. Every inference is now witnessed.
response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Summarize this contract..."}],
)
# response is untouched, use it exactly as before
print(response.choices[0].message.content)

No code changes. No performance impact. No data leakage.

Quick Start (Try It Locally)

Want to see the SDK work before connecting to a live endpoint? Use factor_handoff to write witness anchors to local JSON files — no account needed.

from swt3_ai import Witness
from openai import OpenAI

witness = Witness(
    endpoint="https://sovereign.tenova.io",
    api_key="test",                # any string — handoff runs before network flush
    tenant_id="LOCAL_TEST",
    factor_handoff="file",         # write anchors to ./swt3-handoff/ as JSON
)
client = witness.wrap(OpenAI())

response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "What is the EU AI Act?"}],
)
print(response.choices[0].message.content)

# Check ./swt3-handoff/ — you'll see a JSON file per inference with:
#   - SHA-256 fingerprint
#   - Model ID, latency, token count
#   - Clearing level applied
#   - Full factor data for independent verification

When you're ready for production, book a 14-day assessment to get your tenant ID and API key. Point the SDK at your enclave and every inference is witnessed, anchored, and verifiable.

What Happens Per Inference

  1. Intercept: The SDK wraps your AI client transparently
  2. Hash: Prompts and responses are SHA-256 hashed locally
  3. Extract: Model version, latency, token count, guardrail status captured as numeric factors
  4. Clear: Raw text is purged from the wire payload (configurable clearing level)
  5. Anchor: Factors are batched and flushed to the SWT3 Witness Ledger in the background
  6. Return: Your original response returns untouched, zero added latency

The result: an immutable, cryptographic proof that your AI followed the rules, without the auditor ever needing to see the sensitive data.

Supported Providers

Provider Client Status
OpenAI openai.OpenAI Supported
Anthropic anthropic.Anthropic Supported
AWS Bedrock bedrock-runtime Planned
Azure OpenAI openai.AzureOpenAI Planned
Ollama / vLLM Local models Planned

OpenAI

from swt3_ai import Witness
from openai import OpenAI

witness = Witness(endpoint="...", api_key="axm_...", tenant_id="...")
client = witness.wrap(OpenAI())

response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "Hello"}],
)

Anthropic

from swt3_ai import Witness
from anthropic import Anthropic

witness = Witness(endpoint="...", api_key="axm_...", tenant_id="...")
client = witness.wrap(Anthropic())

message = client.messages.create(
    model="claude-sonnet-4-20250514",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Hello"}],
)

Clearing Levels

The Clearing Engine controls what leaves your infrastructure. Your code always gets the full response. Clearing only affects the wire payload sent to the witness ledger.

Level Name What's on the wire Use case
0 Analytics Hashes + factors + model ID + provider + guardrail names Internal analytics, non-sensitive workloads
1 Standard Hashes + factors + model ID + provider metadata Default. Production SaaS, enterprise apps
2 Sensitive Hashes + factors + model ID only Healthcare, legal, PII-adjacent workloads
3 Classified Numeric factors only. Model ID hashed. No metadata. Defense, classified environments, air-gapped
# Level 2: Sensitive, no provider names, no guardrail names on the wire
witness = Witness(
    endpoint="...",
    api_key="axm_...",
    tenant_id="...",
    clearing_level=2,
)

At Level 1+, raw prompts and responses never leave your infrastructure. Only SHA-256 hashes and numeric factors travel on the wire. This satisfies both GDPR Article 17 (right to erasure) and EU AI Act Article 12 (record-keeping) simultaneously.

What Gets Witnessed

Each inference produces anchors for these AI procedures:

Procedure Domain What it proves
AI-INF.1 Inference Prompt and response were captured (provenance)
AI-INF.2 Inference Latency within threshold (detects model swaps)
AI-MDL.1 Model Deployed model matches approved hash (integrity)
AI-MDL.2 Model Model version identifier recorded (tracking)
AI-GRD.1 Guardrail Required safety filters were active (enforcement)
AI-GRD.2 Safety No refusal or content filter triggered (content safety)

Each procedure maps to both NIST AI RMF functions and EU AI Act articles. When a CISO looks at the ledger, they don't see "inference captured." They see "Article 12 Compliance: Verified."

Resilience (Flight Recorder)

The SDK never blocks your inference call. Witnessing happens in a background thread.

If the witness endpoint is unreachable (network outage, air-gapped deployment), payloads move to a dead-letter queue instead of being dropped. When connectivity is restored, the backlog drains automatically with exponential backoff.

witness = Witness(
    endpoint="...",
    api_key="axm_...",
    tenant_id="...",
    buffer_size=50,       # flush every 50 anchors
    flush_interval=10.0,  # or every 10 seconds
    max_retries=5,        # retry 5 times before dead-lettering
)

# Check dead-letter status
print(f"Pending: {witness.pending}")

Configuration

Parameter Default Description
endpoint required Witness endpoint URL
api_key required API key (axm_* prefix)
tenant_id required Your enclave identifier
clearing_level 1 Clearing level (0-3)
buffer_size 10 Flush after N anchors
flush_interval 5.0 Flush after N seconds
timeout 10.0 HTTP timeout for flush
max_retries 3 Retry count before dead-letter
latency_threshold_ms 30000 AI-INF.2 latency threshold
guardrails_required 0 AI-GRD.1 required guardrail count
guardrail_names [] Names of active guardrails
factor_handoff None "file" to enable local factor export
factor_handoff_path None Directory for factor handoff files

Factor Handoff (Clearing Level 2+)

At Clearing Level 2 or 3, some or all verifiable data is stripped from the wire before it reaches the witness endpoint. The Factor Handoff ensures your factors are safely written to a local directory before clearing proceeds. If the write fails, the payload is not transmitted.

witness = Witness(
    endpoint="https://sovereign.tenova.io",
    api_key="axm_live_...",
    tenant_id="YOUR_ENCLAVE",
    clearing_level=3,
    factor_handoff="file",
    factor_handoff_path="/secure/vault/factors/",
)

Each anchor gets its own JSON file (named by fingerprint) containing the full uncleared factors and metadata needed for independent re-verification. Files are written with 0600 permissions.

For the full protocol specification, see the Factor Handoff Protocol.

Custom Pipelines

For non-standard LLM integrations, use the decorator or manual API:

@witness.inference()
def my_custom_llm(prompt: str) -> str:
    # Your custom inference logic
    return result

# Or manual recording
from swt3_ai.types import InferenceRecord
from swt3_ai.fingerprint import sha256_truncated

record = InferenceRecord(
    model_id="my-model-v2",
    model_hash=sha256_truncated("my-model-v2"),
    prompt_hash=sha256_truncated(prompt),
    response_hash=sha256_truncated(response),
    latency_ms=elapsed_ms,
    provider="custom",
)
witness.record(record)

Installation

pip install swt3-ai

# With provider extras
pip install swt3-ai[openai]
pip install swt3-ai[anthropic]
pip install swt3-ai[all]

Regulatory Coverage

The SWT3 AI Witnessing Profile maps to:

  • EU AI Act: Articles 9, 10, 12, 13, 14, 53, 72
  • NIST AI RMF: GOVERN, MAP, MEASURE, MANAGE (10 subcategories)
  • ISO 42001: Annex A AI management controls
  • NIST 800-53: SI-7 (integrity), AU-2/AU-3 (audit), AC controls

AI Witness-as-a-Service

SWT3 AI Witness is available as a managed service through Axiom Sovereign Engine:

Tier Retention Key Features Price
Open 7 days SDK, dashboard, public verify Free
Pro 90 days + AI conformity exports, regulatory reports $499/mo
Enclave 1 year + OSCAL, Gate API, attestations, webhook feeds $9,500/mo
Sovereign Custom + White-glove ATO sprint, mock assessment, on-prem Book Assessment

890+ downloads across npm and PyPI. 151 procedures. 13 frameworks. Patent pending.

Ready to Witness Your AI?

Get an API key and start witnessing in under 10 minutes:

Documentation


Support the Standard

If you believe AI systems should prove they followed the rules, give us a star. Every star signals that the industry is ready for an accountability standard.


SWT3: Sovereign Witness Traceability. We don't run your models. We witness them.

TeNova: Defining the AI Accountability Standard. One protocol. Zero Integrity Debt. Total Sovereignty.

SWT3 and Sovereign Witness Traceability are trademarks of Tenable Nova LLC. Patent pending. Apache 2.0 licensed.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

swt3_ai-0.2.5.tar.gz (24.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

swt3_ai-0.2.5-py3-none-any.whl (30.9 kB view details)

Uploaded Python 3

File details

Details for the file swt3_ai-0.2.5.tar.gz.

File metadata

  • Download URL: swt3_ai-0.2.5.tar.gz
  • Upload date:
  • Size: 24.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for swt3_ai-0.2.5.tar.gz
Algorithm Hash digest
SHA256 152ff5ae9213386d1198d4badaaab1f5d7d7eb313c357045ee36bea64451e980
MD5 aeb94103a2d2bcde8fa82d6282e4ad8e
BLAKE2b-256 cf182de08dc4eb4d64cbce2002867401879f5d1a3554360e23065bdb41197917

See more details on using hashes here.

File details

Details for the file swt3_ai-0.2.5-py3-none-any.whl.

File metadata

  • Download URL: swt3_ai-0.2.5-py3-none-any.whl
  • Upload date:
  • Size: 30.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for swt3_ai-0.2.5-py3-none-any.whl
Algorithm Hash digest
SHA256 ec450ee6b899faef1775ddb2b0e1715ee77f048610f231da3bf379050f8d3b49
MD5 2a7fcddb500569c70ff8b265b40da93d
BLAKE2b-256 f5aaa5aafd8db169e9fd9a9e46fa6ee4741d05723feadc62df1f1db89a60f517

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page