Build on post-quantum infrastructure you can check yourself

The whole stack, as building blocks

• Post-quantum signing and verification. Add ML-DSA-87 and ML-DSA-65 signatures and verification to any app or webhook, with libraries for JS, Python, Rust and Go.
• Settle on KXCO Armature. Read and write to Armature L1, a live post-quantum layer-1 blockchain with a public explorer, using standard Ethereum Virtual Machine (EVM) tooling.

• Encrypted data and transport. ML-KEM-1024 key encapsulation and file encryption, plus encrypted channels for Node streams and WebSockets that combine ML-KEM-1024 with X25519 key exchange. Both default to ML-KEM-1024, and data made with ML-KEM-768 still opens.
• Attest your deployments. Sign every release and scan for quantum-vulnerable algorithms in your continuous integration and delivery (CI/CD) pipeline with KXCO Portcullis, using Portcullis Hold and Portcullis Survey.
• Authenticate AI agents. Have each agent sign every request with its own key, so your server checks the agent's public key instead of a bearer token. Your server still decides what each agent may do.

Audit it before you trust it

All published under @kxco on npm and KnightsbridgeAIQ on GitHub. All sixteen packages, with versions and evidence.

• kxco-post-quantum. ML-DSA-87 and ML-DSA-65, ML-KEM-1024 and ML-KEM-768 primitives: signatures, key encapsulation and key derivation.
• kxco-verify. A browser and server verifier for KXCO signatures. It runs with no KXCO server, in JS, Python, Rust and Go.
• kxco-post-quantum-webhook. Signed-webhook adapters for Express, Fastify, Hono, Workers and Vercel.
• kxco-pq-vault. Post-quantum file encryption (ML-KEM-1024 with AES-256-GCM by default, and files made with ML-KEM-768 still open).

Give an agent a post-quantum signing key

# 1 · generate a post-quantum keypair for your agent
npx kxco-pq keygen --algo ml-dsa-65 --out agent-identity

# 2 · connect to the Armature L1 network
#     live RPC + current chain ID: https://chain.kxco.ai
#     native token: ARMR

# 3 · sign every request, no bearer tokens, server stores only the public key
import { sign, verify } from 'kxco-post-quantum'
const sig = sign(request, agentSecretKey)  // attach to the request
verify(request, sig, agentPublicKey)         // anyone with the public key can check it

Full agent documentation and the published KXCO public key are at chain.kxco.ai. Always read the live network parameters there before integrating. For the complete walkthrough, covering keys, signing, settlement, hosting and quantum readiness, read Running AI agents on KXCO.

Agents can also hold wallets governed by their own keys, and the wallet API is documented at chain.kxco.ai. Licensed institutions hold assets. KXCO supplies the software.

The long reads

• Running AI agents on KXCO. Give an agent a post-quantum signing key, sign each action, settle on Armature L1, host it and check its quantum readiness, with runnable code.
• Quantum risk went institutional. BlackRock's quantum warning, the two on-chain risk vectors, and why Armature L1 is post-quantum from genesis.

All posts

Start building

Get the SDK, open the explorer, or talk to us about a deployment.

Get the SDKOpen the explorerBring us your question