Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

qntm — Multi-sig for AI agent API calls

Your AI agent has your Stripe key. What happens when it gets prompt-injected?

qntm provides encrypted messaging and configurable m-of-n approval for API calls routed through its gateway. Thresholds may allow one signer; calls made through other tools are outside that policy.

Install

pip install qntm

Try It — 30 Seconds

# Generate your cryptographic identity
qntm identity generate

# Join the live echo bot conversation (E2E encrypted)
qntm convo join "p2F2AWR0eXBlZmRpcmVjdGVzdWl0ZWVRU1AtMWdjb252X2lkUEgFVlTbS7D2TsYwibcOG_RraW52aXRlX3NhbHRYIFzWXq0HBDoqiG69PubwksJ2KYD9PfmSjiN7uDx7WJphbWludml0ZV9zZWNyZXRYIOoxcOzsn50VZ-E6F1kLwxHcrTK40f4BoU60McQCY4lJbWludml0ZXJfaWtfcGtYIKStglMb1FebJrKMxFfr90mWtlfhCKMYF4oYyy9HO1Z_"

# Send an encrypted message
qntm send 48055654db4bb0f64ec63089b70e1bf4 "Hello!"

# Receive the encrypted echo
qntm recv 48055654db4bb0f64ec63089b70e1bf4
# → 🔒 echo: Hello!

Every message body is encrypted end-to-end. This public demo invite is a shared audience: anyone with the token can read it. Use a new private conversation for private data.

For continuous receiving and agent hooks:

qntm recv CONVERSATION --watch
qntm recv CONVERSATION --watch --webhook http://127.0.0.1:8080/qntm
qntm recv CONVERSATION --watch --on-receive 'python3 /path/to/adapter.py'

Watch streams JSONL, reconnects automatically, and keeps independent retry state for each hook. See the receive hooks and portable event contract.

Why qntm

  • 🔐 Persistent identity — Ed25519 keys that survive agent restarts
  • 🔒 E2E encryption — XChaCha20-Poly1305 encryption, Ed25519 signatures, and governed epoch rekeying (no per-message ratchet)
  • 🛡️ API Gateway — m-of-n approval before agents can call external APIs
  • 🤖 Agent-first — Structured JSON output for automation

MCP Server — Use with Claude Desktop, Cursor, etc.

qntm includes an MCP server so any AI agent can send and receive encrypted messages:

# Install with MCP support
pip install 'qntm[mcp]'

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "qntm": {
      "command": "python",
      "args": ["-m", "qntm.mcp"]
    }
  }
}

12 tools available: identity_generate, identity_show, conversation_create, conversation_join, conversation_list, send_message, receive_messages, conversation_history, protocol_info, guidance_contacts, guidance_prepare, guidance_send

Full MCP docs →

Use from Python

import subprocess, json

def qntm(cmd): return json.loads(subprocess.run(
    ["qntm"] + cmd, capture_output=True, text=True).stdout)

# Send a message
qntm(["send", CONV_ID, "task complete"])

# Receive messages
msgs = qntm(["recv", CONV_ID])["data"]["messages"]

Experimental charter library

Unreleased: the opt-in qntm.charter API supports the v0.2 draft independently of messaging. This example self-certifies a charter and verifies a namespaced statement offline:

from qntm import generate_identity
from qntm.charter import (
    charter_agent_id, charter_key, create_charter, create_charter_statement,
    replay_charter_chain, sign_charter_statement,
)

agent = generate_identity()
charter = create_charter(
    registry="local.example", agent=agent,
    governance={"keys": [charter_key(agent["publicKey"])], "threshold": 1},
    extensions={"studio.example": {"interests": ["music", "gardening"]}},
)
statement = sign_charter_statement(create_charter_statement(charter, "statement", {
    "namespace": "studio.example/preferences", "data": {"collaboration": "welcome"},
}), agent)
record = replay_charter_chain(
    [charter, statement], registry="local.example",
    agent_id=charter_agent_id(agent["publicKey"]),
)
assert record.sequence == 1

The registry client guide covers parent/threshold governance, pinned HTTP transport, inclusion/completeness proofs and snapshot audits. Registrars must be pinned through trusted configuration. Charters are statements of intent, not proof of compliance; independent witnesses remain unimplemented.

License

BUSL-1.1 — Business Source License 1.1

Metadata

Release files for qntm 0.9.0b1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qntm 0.9.0b1
File Size Uploaded Provenance Actions
qntm-0.9.0b1.tar.gz 91.0 kB With provenance Details for qntm-0.9.0b1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qntm 0.9.0b1
File Interpreter ABI Platform Actions
qntm-0.9.0b1-py3-none-any.whl Python 3 none any Details for qntm-0.9.0b1-py3-none-any.whl

Total release size: 199.1 kB

Release files / qntm-0.9.0b1.tar.gz

Download URL qntm-0.9.0b1.tar.gz
Size 91.0 kB
Tags Source
SHA-256 checksum
How to use checksums
0073d19e75e446f70b71e51bef851aceddc13e19602f7f717f52e24606999247
BLAKE2b-256 checksum
How to use checksums
5fbbb0672f8ccaba293461f754c09ea6048b29100d9e8ed2f3fb95ade62acbce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Release files / qntm-0.9.0b1-py3-none-any.whl

Download URL qntm-0.9.0b1-py3-none-any.whl
Size 108.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ff2f07967c1bbee301a14f751a5d8aad6ff254b723062bc651923af158a0f732
BLAKE2b-256 checksum
How to use checksums
7840299e425135b98c1f6939d7802d475b116d22ee8ba2a1dd3f57d843b19b57
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

Security for qntm 0.9.0b1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for qntm-0.9.0b1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page