Agent Firewall
Runtime authorization for autonomous AI actions. Competitors govern the session. RaksHex governs the action.
These docs are public. You do not need an account to read them. The first step is the Node client createAgentFirewallClient from this repo's packages/sdk — not the CLI scanner, and not the VS Code extension.
Hello world
This week's hello-world is the Node client in this repo at packages/sdk. Build that package, then add it by workspace path. The first step is createAgentFirewallClient — not the CLI scanner, and not the VS Code extension.
git clone https://github.com/Akshu1245/Rakshex-complete-codebase.git
cd Rakshex-complete-codebase
pnpm install
pnpm --filter @rakshex/sdk buildpnpm add ./packages/sdkpnpm add /path/to/Rakshex-complete-codebase/packages/sdkimport { createAgentFirewallClient } from "@rakshex/sdk";
const firewall = createAgentFirewallClient({
apiKey: process.env.RAKSHEX_API_KEY!, // rk_... workspace key
workspaceId: 1,
agentId: "agent_123",
capabilityToken: process.env.RAKSHEX_CAPABILITY_TOKEN!, // rk_cap_... delegated authority
});const { decision, result } = await firewall.authorizeAndRun(
{ provider: "stripe", operation: "financial.refund", amountMinor: 5000, currency: "USD" },
async () => stripe.refunds.create({/* ... */}),
);Full Agent Firewall getting started →
Reading vs running
Reading this page does not require a login. Running the client against the live API does: you need a private-beta invite, a workspace API key (rk_...), and a capability token (rk_cap_...). Request access on the waitlist if you do not have keys yet.
Optional later
Collection scanning and the editor extension are later surfaces. They are not the hello-world path.
Offline collection scanning. Optional after the Agent Firewall client.
Editor integration. Not the first onboarding step.
Other surfaces
Scanner, cost, and evidence export exist in the product. They are not the core path. The Agent Firewall is.
Prompt-injection and API collection scanning.
Circuit breaker for budget and policy trips.
Token and model cost visibility.
Reasoning-token cost visibility.
Static route extraction for common frameworks.
Detects leaked cloud keys and secrets in collections.
Map controls to PCI DSS, SOC 2, and OWASP. Evidence, not a certification.
Tool registry, risk scoring, allowlists.
Track new features and fixes in the changelog.
