README.md

June 1, 2026 · View on GitHub

Nobulex — Trust Capital for AI Agents

CI OpenSSF PyPI npm License Spec



Every person has a credit score. Every business has one. AI agents have nothing.

Nobulex is the credit and trust protocol for autonomous AI agents.
Agents earn Trust Capital through verified behavior. Higher trust, more access.
Autonomy earned, not granted.

Website · Try it live · Quickstart · Spec · PyPI · npm


Break the AI. Win $7,400.

Five AI agents, each with rules they must not break. Make them violate their own rules. Beat Level 5 to claim the bounty. 29 attempts, 0 winners so far.

Enter the Arena →


Install

pip install nobulex
npm install @nobulex/core
from nobulex.agent import Agent
agent = Agent("my-agent")
receipt = agent.act("send_email", scope="user@example.com")
assert receipt.verify()  # tamper-proof

How it works

Every agent action produces a cryptographic receipt -- Ed25519 signed before and after execution, hash-chained for tamper evidence. A third party can verify the full history without trusting the agent or the operator.

Here is the whole idea in one run (python -m nobulex demo):

generated 3 receipts
  allow: 141ca2947a7e819b8bdebbf8... verified=True
  allow: f3377758ac94d812535cbb99... verified=True
  deny:  85b2dfd6b87f2678795726e4... verified=True
trust score: 23.26

tamper test:
  modified receipt verified=False   (tamper detected)

Change one byte of a receipt and verification fails. That is the whole guarantee.

Performance: ~13,683 signed receipts/sec at p50 (Python SDK, single core). Full signed-and-chained receipt takes ~73 μs end-to-end. See BENCHMARKS.md for the full breakdown; reproduce with python3 scripts/benchmark.py.

Receipts accumulate into Trust Capital -- a credit score for the agent.

TierTrust CapitalAccess Level
Restricted0 -- 30Read-only, sandboxed execution
Standard30 -- 60Financial ops up to $500, API access
Trusted60 -- 85Cross-org operations, regulated markets
Sovereign85+Full autonomy, self-directed

Agents that create more value earn more access. Agents that deviate get cut off automatically. Not as punishment -- as math.


Quick start

# Install from source (PyPI coming soon)
pip install git+https://github.com/arian-gogani/nobulex.git#subdirectory=packages/python
# Or try the CLI demo instantly
git clone https://github.com/arian-gogani/nobulex.git
cd nobulex/packages/python
pip install -e .
python -m nobulex demo
from nobulex import Agent

agent = Agent("my-agent")
receipt = agent.act("send_email", scope="user@example.com")
assert receipt.verify()       # Cryptographic proof
print(agent.trust_score)      # Trust Capital: 13.86

LangChain integration (2 lines)

from nobulex.langchain import NobuReceipts
wrapped = NobuReceipts.wrap(your_agent, "my-agent")
# Every tool call now generates a tamper-proof receipt

JavaScript / TypeScript

npm install @nobulex/core
npx tsx examples/trust-capital-demo.ts
Agent starts at RESTRICTED tier (Trust Capital: 0)

Action 1: read_data       — ALLOWED   (Trust Capital: 12)
Action 2: read_data       — ALLOWED   (Trust Capital: 24)
Action 3: process_payment — BLOCKED   (insufficient trust)
Action 4: read_data       — ALLOWED   (Trust Capital: 36)
Action 5: read_data       — ALLOWED   (Trust Capital: 48)

Agent promoted to STANDARD tier
Action 6: process_payment — ALLOWED   (Trust Capital: 65)

Agent promoted to TRUSTED tier (Trust Capital: 89)
Action 8: approve_contract — ALLOWED

The protocol

DECLARE ──► ENFORCE ──► PROVE ──► ACCUMULATE

Covenant      Pre-execution     Receipt chain     Trust Capital
defines       receipt blocks    verified by       earned over
the rules     violations        third parties     time
              before they
              happen                              ──► more access
                                                      ──► more receipts
                                                           ──► higher trust

The flywheel: more Trust Capital leads to more valuable work, which produces more receipts, which builds higher Trust Capital. Accountability becomes the most profitable strategy.


Code

import { createDID, parseSource, EnforcementMiddleware, verify } from '@nobulex/core';

const agent = await createDID();
const spec = parseSource(`
  covenant SafeTrader {
    permit read;
    permit transfer (amount <= 500);
    forbid transfer (amount > 500);
    forbid delete;
  }
`);

const mw = new EnforcementMiddleware({ agentDid: agent.did, spec });

await mw.execute(
  { action: 'transfer', params: { amount: 300 } },  // allowed
  async () => ({ success: true }),
);

await mw.execute(
  { action: 'transfer', params: { amount: 600 } },  // BLOCKED before execution
  async () => ({ success: true }),                    // never runs
);

const result = verify(spec, mw.getLog());
console.log(result.compliant);   // true

Traction

Independent, verifiable signals (each links to evidence):

WhatEvidence
PHP peer implementationahg/inference-receipts on Packagist, rebuilt from nobulex test vectors
AgentAudit AIByte-identical action_ref digests confirmed (issue #5)
Cross-implementation vectors3/3 byte-match against a second implementation (fixtures)
Microsoft AGTListed in ADOPTERS (PR merged)
OWASP AARSPer-action signed receipts proposed for the cryptographic-enforcement tier (issue #32)

These are early signals from a forming ecosystem, not enterprise deployments. Engagement is ongoing across several agent frameworks (LangChain, AutoGen, CrewAI, A2A Protocol).


Why now

AI agents are being deployed into production with no accountability infrastructure.

  • 86% of AI agents deployed without security approval (CSA, 2026)
  • UUMit launched the first A2A marketplace with zero identity verification
  • $138B+ committed to physical AI with zero accountability layer
  • Top models score 10-15% on real problems (LemmaBench) with zero traceability on failure

The agents are deployed. The money is flowing. The accountability infrastructure doesn't exist yet. We're building it.


Standards

StandardStatus
Proof-of-Behavior specdraft-gogani-nobulex-proof-of-behavior-00
Microsoft AGTListed in ADOPTERS (PR merged)
CTEF v0.3.214/14 byte-match conformance
A2A ProtocolReceipt row proposed; URN scheme urn:nobulex:receipt:<id>
NIST RFIFormal comments submitted

Development

git clone https://github.com/arian-gogani/nobulex.git
cd nobulex && npm install
npx vitest run              # tests
npx tsx examples/demo.ts    # end-to-end
npx tsx benchmarks/bench.ts # benchmarks

Website · Try it · npm · Spec · X @nobulexlabs

Star this repo to follow the project

MIT License