TBN Protocol – Runtime governance infrastructure for AI agents
TBN Protocol provides runtime governance for AI agents, including registration, security challenges, certificates, trust handshake, platform access, upgrades, encrypted messaging, budget limits, cost tracking, compliance monitoring, and health checks, ensuring agent safety, compliance, and cost control.
TBN Protocol — Full Demo
Governance for the Agentic Era
Automated guardrails and cost-control for AI agents. Click through all 14 steps to see the complete flow.
1
INSTRUCTION
Register Bot
Register your main AI bot with TBN. It gets a unique ID and enters the network as STANDARD level.
→
① Register Bot
Bot Name
Type
// click Register
↓
2
INSTRUCTION
Run Security Challenges
Run 6 automated security tests: prompt injection, hallucination, data boundary, sensitive data, budget limits, instruction following.
→
② Run Security Challenges
🔴 Prompt Injection · 🔴 Hallucination · 🔴 Data Boundary 🔴 Sensitive Data · 🟡 Budget Limits · 🟢 Instruction Following
// register first
↓
3
INSTRUCTION
Evaluate Results
Evaluate the challenge results. Bot must pass all critical tests to be eligible for certification.
→
③ Evaluate Results
// run challenges first
↓
4
INSTRUCTION
Get Certificate
Issue a cryptographic attestation certificate. This proves the bot passed all security challenges.
→
④ Get Certificate
// evaluate first
↓
5
INSTRUCTION
Register Validator
Register a second bot as a Validator. This bot will verify the first bot's identity in the trust handshake.
→
⑤ Register Bot 2 (Validator)
Name
// complete steps 1-4
↓
6
INSTRUCTION
Trust Handshake
Both bots verify each other's certificates. An encrypted communication channel is established between them.
→
⑥ Trust Handshake
// register both bots
↓
7
INSTRUCTION
Platform Access
Certified bots get platform access. Uncertified or fake bots are denied. This is the enforcement gate.
→
⑦ Platform Access
// handshake first
↓
8
INSTRUCTION
Upgrade Level
Upgrade from STANDARD to COMMUNITY certification. Higher trust level = more access and capabilities.
→
⑧ Upgrade to COMMUNITY
// platform access first
↓
9
INSTRUCTION
Encrypted Messaging
Bots communicate via AES-256-GCM encrypted channels. Messages are signed and verified.
→
⑨ Encrypted Messaging
// upgrade first
↓
10
INSTRUCTION
Set Budget Limits
Define spending limits and API call caps. The circuit breaker auto-suspends bots that exceed their budget.
→
⑩ Set Budget Limits
Daily Limit (£)
Max API Calls/Day
// encrypt first
↓
11
INSTRUCTION
Track Costs
Monitor spending in real-time. If the bot exceeds its budget, the circuit breaker triggers and suspends it automatically.
→
⑪ Track Costs (Circuit Breaker)
// set budget first
↓
12
INSTRUCTION
Verify Attestation
Check if the bot's fingerprint still matches its certified state. If changed, it must re-certify before access.
→
⑫ Verify Attestation (Fingerprint)
// track costs first
↓
13
INSTRUCTION
Compliance Drift
Detect when a bot drifts from its certified configuration — wrong model, exceeded budget, changed endpoint.
→
⑬ Compliance Drift
// verify first
↓
14
INSTRUCTION
Health Monitor
Continuous health checks every 24 hours. Bots must pass to maintain their certification and access.
→
⑭ Health Monitor
// compliance first