The agent SDK and the MCP server are served from this site.Read the docs

ALLOWANCEENGINE

SEC-0101

Arms

AI agents need to pay for things: APIs that charge per call over x402, data, compute, other agents. Giving an agent the private key of your wallet is how wallets get emptied. Here each agent gets its own session key, and that key can only move USDC out of its own arm, up to the budget you approved, to the addresses you listed.

Rule

An agent never holds your wallet. It holds a session key that is the SPL delegate of one USDC account your wallet owns, and the Solana token program itself refuses any transfer above the budget. Each arm also has a daily cap and an allow-list. One button closes all eight and brings the USDC and the rent back to your wallet in the same transaction.

Eight
agents
one
wallet
8
SEC-0202

How it works

The transactions

SEC-0303

Controls

08Eight agentsArms per wallet
24UTC dayCap window
%0.50%Relay fee
$USDC, 6 decimalsSettlement
eded25519 session keySignature
dSPL delegateOnchain ceiling
0None when relayedAgent SOL
1One transactionInk
r0.00204 SOL, returnedRent per arm
402x402 v1, exactProtocol
solsolanaNetwork
SEC-0404

Build

SDK

Agents plug in through a single-file SDK on top of @solana/web3.js, or through an MCP server that gives Claude and any MCP client three tools: arm_status, paid_fetch and pay. Both files are served from this site and the docs fetch them with curl.

x402

An endpoint that wants to be paid by arms calls the facilitator at /api/x402. The 402 challenge is x402 scheme exact on network solana, the payment header carries a USDC transfer signed by the session key, and settlement is one Solana transaction from the arm to your payTo address, its SOL fee paid by the facilitator.

Index

SEC-0505

Start

Open the app, connect your wallet, give your first agent an arm with one dollar of USDC and a cap of one dollar a day, and watch it pay. Allowance Engine never holds your USDC, never holds your keys and never sees the agents' keys.