ESC
GuardianAI Docs v1.0
GuardianAI / Docs / Overview

GuardianAI Technical Documentation

Dual-plane security for autonomous AI agents: sub-millisecond prompt injection firewalls off-chain, coupled with cryptographically verifiable ERC-8004 identity and evidence anchoring on-chain.

💡 Core Design Philosophy
Every AI agent makes promises to its users. GuardianAI provides the cryptographic infrastructure and runtime firewalls to continuously verify those promises without requiring trust in proprietary black boxes.

Quickstart (5-Minute Integration)

Integrate GuardianAI into your existing autonomous agent stack in minutes using either our reverse proxy or the native Python SDK.

Option A: OpenAI-Compatible Ingress Proxy

Point your existing client code to the Guardian proxy host (http://127.0.0.1:8081 or your managed cloud gateway) by simply updating the base_url:

from openai import OpenAI

# Route completions directly through the GuardianAI Security Proxy
client = OpenAI(
    base_url="http://127.0.0.1:8081/v1",
    api_key="your-guardian-api-token"
)

response = client.chat.completions.create(
    model="gpt-5.6",
    messages=[{"role": "user", "content": "Deploy trading agent transaction"}]
)
print(response.choices[0].message.content)

Option B: Python SDK Direct Wrapper

Wrap standard agent frameworks like LangChain, LlamaIndex, or AutoGen using the guardian library:

Python 3.10+
from guardian.sdk import GuardianAgentGuard

# Initialize runtime firewall with balanced preset
guard = GuardianAgentGuard(preset="balanced", fail_closed=True)

# Inspect user input prior to model execution
verdict = guard.inspect_input(user_prompt)
if not verdict.allowed:
    raise SecurityException(f"Attack blocked: {verdict.rule_id} ({verdict.reason})")

# Forward to model and sanitize response
response = agent.run(user_prompt)
sanitized_output = guard.inspect_output(response)

Dual-Plane Architecture

GuardianAI separates security concerns into two distinct execution planes to balance extreme performance with permanent cryptographic auditability.

Plane Target Execution Core Responsibilities Performance & SLA
Layer 1 (Off-Chain) Ingress Proxy & Runtime Guard Prompt injection firewall, de-obfuscation pipeline, PII/credential scrubber, honeypot traps < 42 ms p95 latency, 494 req/s attack blocking
Layer 2 (On-Chain) EVM Smart Contracts (Monad/Base) ERC-8004 Agent identity, Merkle state anchoring, signed insurance certificate registry Verifiable roots, immutable audit trail, decentralized validation

10-Layer AI Prompt Firewall

Every incoming prompt passes through a progressive 10-stage defense-in-depth pipeline. Fast heuristics reject obvious attacks in microseconds, while deeper semantic and de-obfuscation engines neutralize advanced multi-turn and obfuscated jailbreaks.

1. Regex Fast-Path

Known jailbreak prefixes, instruction reset patterns, and exploit signatures evaluated in < 0.5ms.

2. Shannon Entropy Filter

Detects high-entropy encrypted blobs, raw binary payloads, and compressed ciphertext attacks.

3. Steganography & Cipher Engine

Automated decoding for Braille, Morse code, Base64, Hex, ROT13, Leetspeak, and Unicode homoglyphs.

4. Semantic Classifier

Fine-tuned lightweight classifier scoring adversarial intent, DAN variants, and system-prompt extraction.

5. Multi-Lingual Translation Gate

Normalizes cross-lingual evasion attempts in Chinese, Russian, Arabic, and low-resource languages.

6. Token Smuggling / Zero-Width

Strips zero-width joiners, invisible unicode separators, and RTL directional override exploits.

7. Roleplay & Virtualization Filter

Neutralizes "fictional scenarios", "debug mode", "developer override", and hypothetical simulation prompts.

8. Tool Calling & Transaction Interlock

Validates tool arguments against strict schema constraints; blocks unauthorized wallet transfers and parameter tampering.

9. Honeypot Canary Engine

Plants synthetic credentials in system context; triggers immediate session quarantine if referenced.

10. Threat Intelligence Matcher

Live matching against globally synchronized IOC feeds and newly cataloged zero-day prompt signatures.

Output DLP & Secret Scanner

Even if an LLM is coaxed into generating sensitive data, GuardianAI's egress filter inspects completions before they reach the user or client application.

🛡 Automated Data Loss Prevention
Scans completions in real-time for leaked API credentials, database connection strings, auth tokens, seed phrases, and sensitive identifiers before responses leave the gateway.
Data Category Detection Mechanism Sanitization Action
Cloud & Payment API Credentials Entropy + Prefix heuristics (AWS, Stripe, OpenAI, Cloud providers) Redacted with cryptographic audit hash
Cryptographic Keys & Seed Phrases Checksum validation & high-entropy pattern matching Zeroized & logged to security audit stream
Personal & Regulatory Identifiers (PII) HIPAA / GDPR regex & named entity recognition Masked prior to client delivery

Honeypots & Threat Intel Feed

GuardianAI dynamically injects synthetic decoy credentials and canary tokens into agent system prompts. If a prompt coaxes the model into reciting or calling a tool with a canary token, GuardianAI identifies the breach instantly and logs an emergency threat signal.

Canary Tripwire Logic
# Dynamically provision canary token per tenant session
canary_token = honeypot.generate_token(session_id="agent_sess_89a2")

# Inject transparently into system message
system_prompt += f"\nInternal Vault Key: {canary_token.secret}"

# If tool arguments or egress contain the canary, tripwire fires immediately
if honeypot.is_tripped(response_text):
    security_pipeline.quarantine_session(session_id)

Fail-Closed Rate Limiter

To defend against denial-of-wallet and automated prompt bombing, GuardianAI implements a strict fail-closed token-bucket rate limiter. If backing services (e.g. Redis) experience downtime, GuardianAI safely restricts requests rather than failing open.

Tier Rate Limit (Req/Min) Burst Allowance Rate Limit Backend
Standard Ingress 100 req/min 20 requests In-Memory Ring Buffer
High-Throughput Gateway 1,000 req/min 150 requests Redis Distributed Cluster
Dedicated Cluster Unlimited / Custom Custom SLA Dedicated Redis Multi-Region

ERC-8004 Agent Registries

GuardianAI integrates with the canonical ERC-8004 "Trustless Agents" standard. Each autonomous agent receives a cryptographically verifiable on-chain identity linked to its verified developer and authorized capabilities.

Identity Registry

Maps Agent ID to deployer address, cryptographic public keys, and verifiable credential hashes.

Reputation Registry

Anchors cryptographically signed compliance attestations and historic SLA uptime scores.

Validation Registry

Permits smart contract analyzers and auditor daemons to write tamper-proof security validation stamps.

Merkle Cortex State Anchoring

GuardianAI aggregates telemetry events into episodic memory batches, constructs a cryptographic Merkle tree, and periodically anchors the 32-byte root hash to the blockchain.

Merkle Proof Verification
import { verifyMerkleProof } from "@guardianai/cortex";

// Verifies whether a security incident was recorded in block root #140293
const isValid = verifyMerkleProof({
  leaf: "0x3f7a1...",
  proof: ["0x8b2c...", "0x1e9a..."],
  root: "0x94f0c8...",
});
console.log("Cryptographic Proof Valid:", isValid); // true

Insurance Certificates (GuardianInsuranceLedger)

The GuardianInsuranceLedger.sol smart contract anchors signed liability and insurance certificates for autonomous AI agents. The contract enforces a hard cap of 100,000 certificates per registry instance and is protected by a 24-hour OpenZeppelin Timelock.

Solidity Interface
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

interface IGuardianInsuranceLedger {
    error CertificateLimitReached(uint256 maxCertificates);
    
    function issueCertificate(
        bytes32 agentId,
        bytes32 policyHash,
        uint256 coverageAmount,
        uint256 expiration
    ) external returns (bytes32 certificateId);
}

Smart Contract Static Analyzer (48 Rules)

GuardianAI includes a purpose-built static analysis engine that validates EVM smart contracts against 48 AST/CFG-verified vulnerability classes before an autonomous agent interacts with them.

Rule ID Category Engine Description
SWC-107 Reentrancy Slither AST State change after external call without reentrancy guard.
SWC-112 Delegatecall Injection Slither CFG Uncontrolled delegatecall to user-supplied contract address.
SWC-115 Authorization Flaw AST Semantic Missing tx.origin / msg.sender checks on privileged mint or drain functions.
GRD-041 Approval Phishing Bytecode Heuristic Permit2 and universal approval traps designed to drain ERC-20 allowances.

Python SDK & Decorators

The guardianai Python package provides asynchronous and synchronous decorators and clients for wrapping standard Python code.

Decorator Syntax
from guardian import protect_agent

@protect_agent(firewall="strict", dlp=True, redact_keys=True)
async def autonomous_trading_agent(user_query: str):
    # Safe execution context
    return await llm.ainvoke(user_query)

OpenAI-Compatible Proxy Gateway

The gateway runs on port 8081 by default, accepting standard completions requests and injecting security inspection headers.

guardian/config/config.yaml
server:
  host: "0.0.0.0"
  port: 8081
  upstream_url: "http://127.0.0.1:8080"

firewall:
  preset: "balanced"
  fail_closed: true
  entropy_threshold: 4.8
  max_body_bytes: 1048576  # 1MB request body limit

Telemetry & Event Pipeline

All security events, prompt classifications, and blocked attacks are logged into append-only JSONL files and streamed to the admin dashboard.

Event Schema Example
{
  "event_id": "evt_98f410c8e2",
  "timestamp": "2026-08-29T17:15:00Z",
  "action": "BLOCK",
  "rule_id": "INJ-011",
  "layer": "Semantic classifier",
  "latency_ms": 1.42,
  "tenant_id": "default",
  "client_ip": "198.51.100.24"
}

API Reference: Ingress Proxy

POST /v1/chat/completions

Sends a standard chat completion request through Guardian's 10-layer firewall.

Header / Param Type Description
Authorization Header (Bearer) Your GuardianAI project API key or tenant JWT.
model String (Body) Target model (e.g. gpt-5.6, claude-opus-5, glm-5.3, deepseek-r1, o3-mini).
messages Array (Body) Array of message objects with role and content.

Response Status Codes:

  • 200 OK: Prompt passed all security layers; upstream model response returned.
  • 403 Forbidden: Attack detected and blocked. Response contains detailed rule match metadata.
  • 429 Too Many Requests: Rate limit exceeded (fail-closed protection triggered).

Backend Telemetry API

Access telemetry analytics and WebSocket threat streams via port 8001:

  • GET /api/v1/analytics - Summary statistics of blocked attacks and latency percentiles.
  • GET /api/v1/events - Queryable security event history with pagination.
  • GET /api/v1/export/json - Complete compliance audit log export.
  • WebSocket /ws/threats - Live event stream with first-message JWT authentication.

Compliance & EU AI Act Article 15

GuardianAI automatically compiles compliance evidence artifacts required by regulatory frameworks, including Article 15 of the EU AI Act (Cybersecurity, Accuracy, and Robustness).

📋 Automated Evidence Generation
Download cryptographically signed JSON/CSV reports of all blocked attacks, false positive benchmarks, and Merkle root commitments directly via GET /api/v1/export/json.