SAULT is the control layer for agents that spend money. Builders open a vault, set per-agent policies, and connect agents — SAULT does the rest. When an agent calls a paid service that responds withDocumentation Index
Fetch the complete documentation index at: https://docs.sault.ai/llms.txt
Use this file to discover all available pages before exploring further.
402 Payment Required, SAULT picks the rail, signs the credential inside a secure enclave, and retries the request.
Every rail. Your rules.
Rail-agnostic
Agents call URLs. SAULT picks the rail (x402, MPP, more later). Your code does not change when the rail does.
Multi-chain vault
One vault holds funds across Tempo, Base, and Solana. Spend on whichever chain a service accepts.
Funds you control
Private keys live in a secure enclave. SAULT signs on your authorisation; you revoke at any time.
Per-agent limits
Daily spend and per-request maximum. Checked before anything is signed. Edits take effect on the next request.
How agents connect
Every surface is a thin wrapper over the same SAULT agent API. Pick what matches your agent.| Agent platform | Integration | Discovery |
|---|---|---|
| Claude Code, Cursor, Codex, Cline, local scripts | CLI | Bundled SKILL.md teaches commands |
| Claude Desktop, any MCP-capable client | Hosted MCP | Tool descriptions + SKILL.md served by the server |
Quick setup
Open the console
Sign in at app.sault.ai. Onboarding creates your vault and a first agent.
Pair your agent
Run
sault login (CLI) or call the sault_login MCP tool. Approve the request in the console.Fund the vault
Send USDC to the vault address, or add funds with a card from the console. See Top Up. The agent can pay as soon as funds settle.