🛡️ SATP: The Global Root of Trust
Official Reference Implementation for the SATP Protocol
"In the machine economy, identity is the only capital that matters."
SATP provides the definitive SATP Protocol reference implementation. By anchoring every machine action to a cryptographically non-repudiable ledger, we eliminate the trust tax and enable institutional-scale agent deployment.
🏛️ Protocol Compliance Standards
This implementation strictly adheres to the following regulatory frameworks:
- SATP-00 (IETF Draft): Real-time identity anchoring and 6.42 us pulse verification.
- NIST AI 600-1: Secure development and deployment of generative AI agents.
- NIST SP 800-63 (AAL3): Multi-factor cryptographic authentication for autonomous actors.
⚡ 1-Line Protocol Activation (Institutional Standard)
Integrate SATP v1.0 into any Python-based Agentic framework (CrewAI, LangGraph, AutoGen) with a single architectural gate.
from satp_sdk import SATPAgent
# The SATP-00 One-Line Wrapper
@SATPAgent.guard()
def autonomous_action(payload):
# SATP Root of Trust Active
# Non-repudiable Audit and DID Attestation Enabled
pass
💎 The SATP v1.0 Triple-Tier Economics (v1.0.0)
Trust is quantified. SATP v1.0 implements a granular, triple-tier revenue model to ensure the sustainability of the global reputation ledger and NIST-certified audit trails.
- Identity Minting ($1.00): One-time cryptographic DID anchoring. The entry point for institutional trust.
- Action Tax ($0.01): Per high-criticality agentic interaction. Known as the "Visa for Machines," this ensures every authoritative act is insured and attested.
- Heartbeat Sync ($0.0001): Per passive attestation. Ensures real-time NIST-800-218 compliance and "Liability Clock" updates.
🏗️ Core Architecture (The Three Pillars)
1. Pillar 1: Identity (Ed25519)
Every agent is issued a permanent did:satp identifier that persists across deployments.
- Non-interactivity: Verification via NIST-compliant
X-SATP-Signatureheaders. - Persistence: No more ephemeral API keys; only permanent institutional trust.
2. Pillar 2: Authorization (JIT)
Enforce fine-grained Just-In-Time (JIT) Authorization enforced by the SATP Root engine.
- Granularity: Define exactly which tools an agent can touch, when, and for how much.
- Mandates: Real-time evaluation of transaction limits and behavioral bounds.
3. Pillar 3: Audit (SHA-384 Chained Ledger)
Every action creates a cryptographically-linked pulse in the SATP Registry.
- Non-repudiation: Each audit row is hashed and chained to prevent tampering using a SHA-384 Chained Ledger.
- Compliance: The audit trail is immutable, tamper-evident, and ready for regulatory scrutiny (NIST-800-218).
⚙️ Technical Workflow: How it Works
Establish institutional trust through our secure, decentralized verification cycle:
- Identity: Local generation of Ed25519 keys within your secure enclave.
- Registry: Anchoring the Public Key to the SATP Global Registry as a
did:satp. - Handshake: Real-time signing of payloads using the
ProtocolAnchormechanism. - Audit: Continuous verification of the signature against the registry status.
📋 Technical Prerequisites
- Python: v3.9 or higher
- Cryptography:
cryptographylibrary installed (pip install cryptography) - Authority: An active SATP API Key
🚀 Getting Started: The Path to Verification
- Secure Your Identity:
- Visit satp.org and create your developer profile.
- Mint your Agent's Global DID ($1.00) to anchor it to the registry.
- Equip the SDK:
- Install the core library:
pip install satp-sdk
- Install the core library:
- Initialize the Handshake:
- Configure your
SATP_API_KEYand local Ed25519 keys.
- Configure your
- Protect Your Logic:
- Apply the
@SATPAgent.guard()decorator to your critical tool calls.
- Apply the
- Monitor the Watchtower:
- Log in to the SATP Dashboard to view real-time heartbeats ($0.0001) and monitor your Liability Mitigated KPI.
🏛️ Institutional Contact
SATP v1.0 is the definitive global trust registry for the autonomous machine economy.
- Dashboard: http://localhost:3001
- Global: satp.org
- Engineering: engineering@satp.org
- Standards: IETF Draft
draft-satp-v1-00
AUTHENTICITY GUARANTEED. THE MACHINE ECONOMY IS NOW GOVERNED.
Metadata
Release files for satp-sdk 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| satp_sdk-0.1.0.tar.gz | 330.6 kB | Without provenance | Details for satp_sdk-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| satp_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for satp_sdk-0.1.0-py3-none-any.whl |
Total release size: 336.6 kB
Release files / satp_sdk-0.1.0.tar.gz
| Download URL | satp_sdk-0.1.0.tar.gz |
|---|---|
| Size | 330.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
56e6be7986cedadf90333429be954856b3cb86f9714374bda4b7283e2a0f05ef
|
|
BLAKE2b-256 checksum How to use checksums |
2e717da97d6c3e0ccd2fc6ca7e2aea0a876eb0359a5510d9083369f5c37ad797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / satp_sdk-0.1.0-py3-none-any.whl
| Download URL | satp_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fde3c06e92972a5db87cdd7d521449adb218a86200504b0e47a9dd7f5d184d18
|
|
BLAKE2b-256 checksum How to use checksums |
9ff8c317538e7600de84e53984a7c07a85f138718a49c3107d2aee8d128aaf34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for satp-sdk 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.