DID
Decentralized identifiers. Who is this agent? Cryptographic binding to keys and lineage.
Signed rules. Runtime enforcement. Verifiable proof.
Middleware that forces AI agents to follow signed rules, blocks violations at runtime, and produces tamper-evident logs anyone can audit.
THE PROBLEM
AI agents are beginning to manage economic activity across payments, trading, and procurement—with zero behavioral accountability. MCP handles tool I/O. A2A handles agent messaging. AP2 handles payments. Nobody handles proof.
Until now.
SIX PRIMITIVES
Together, these turn “policy” from a promise into a proof.
Decentralized identifiers. Who is this agent? Cryptographic binding to keys and lineage.
What will it do — and won’t do? Signed, immutable constraints. Only narrowable, never loosened.
Verifiable credentials. Prove identity and compliance without revealing internals.
Every action logged. Tamper-evident. Audit trail that anyone can verify.
Same inputs, same result. Independent, deterministic verification—no trust in the verifier.
Skin in the game. Violations are costly. Stake at risk aligns behavior with commitments.
HOW IT WORKS
SEE IT FAIL CLOSED
TWO-TIER GUARANTEE
Middleware runs in a TEE. Policy bypass is prevented inside the enforcement boundary (TEE + attestation assumptions).
Assumptions & threat model: We assume the TEE is uncompromised and correctly attests its identity. The enclave intercepts all agent actions before execution; forbidden actions never reach the host. If the enclave is compromised, an attacker could bypass enforcement — attestation lets you verify which software is running. See the Spec for details.
Stake at risk. Slashing on breach. Rational agents don’t violate when the cost exceeds the gain.
WHY NOBULEX
| Guardrails / policy engines | Nobulex | |
|---|---|---|
| Enforcement | Best-effort; can be bypassed | Signed commitments; TEE or staking |
| Verification | Trust the operator | Third-party verifiable; anyone can audit |
| Consequences | Policy violation = incident | Economic enforcement; slashing on breach |
TRY IT YOURSELF
permit read;
forbid transfer where amount > 500;
require log_all;
PRICING
The accountability primitive for AI agents.
$0 — forever
Self-hosted. MIT licensed. Full protocol.
From $0.005 / verification
Like Stripe, but for AI agent compliance.
Managed compliance infrastructure. Pay per check.
Volume discounts at 1M+ verifications/month.
Join the Cloud WaitlistCustom
For regulated industries with complex requirements.
TRACTION
FOR DEVELOPERS
const { protect } = require('@nobulex/quickstart');
const agent = protect('permit read; forbid transfer where amount > 500; require log_all;');
const result = agent.check({ action: 'transfer', amount: 200 });
from langchain_nobulex import NobulexComplianceMiddleware
agent = create_agent(
model='gpt-4',
tools=tools,
middleware=[NobulexComplianceMiddleware(
rules='permit read; forbid transfer where amount > 500;'
)]
)