3 SETTLED
payments settled at 0.10 USDT0
Flare Summer Signal · Flare Confidential Compute Track
Your AI agent gets a budget, not a private key.
AgentVault is the spending-authority layer for standard x402 on Flare. Agents pay autonomously from your Vault, without the private key ever entering the agent runtime.
- Private
- Verifiable
- Non-custodial
Three 0.10 payments settled; the 4th was declined when cumulative spend reached 0.40, above the 0.35 budget window.
The layer x402 doesn't define
A funded private key in an LLM runtime turns prompt injection, tool misuse, loops, and replay into financial risk. Public on-chain allowances work, but the budget is readable by the agent and anyone watching the chain.
Agentic wallets isolate keys and set session caps. Scoped control planes grant revocable access to wallets you already use. They still leave spending authority close to the agent runtime, and policy enforcement in infrastructure you cannot independently verify on-chain.
x402 standardizes how an API requests and settles a payment. It does not decide where the Agent's spending authority lives, who enforces the rules, or whether those rules stay private.
AgentVault gives agents bounded spending authority over standard x402 APIs: private policy, Owner-controlled USDT0, and on-chain verification through an EIP-1271 Vault. No agent wallet custody. No public budget on-chain. No trust in an opaque backend policy engine. Without putting the Vault's payment-signing key inside the agent runtime, every payment passes a registered Flare FCC check and a Vault signature check before it settles.
How AgentVault works
-
Owner funds the Vault
Deposit mock USDT0 into a non-custodial Vault that pays via EIP-1271 contract signature verification.
-
Owner sets four private rules
Max per payment, max spend per hour, vendor allowlist, and max payments per hour. Policy is encrypted to the registered machine key.
-
Agent requests, never signs
The Agent holds a revocable credential, not the private key, and never signs the payment itself.
-
FCC evaluates privately
A registered Flare Confidential Compute machine checks every request and signs an exact EIP-3009 authorization only when every rule passes.
-
Vault verifies, then x402 settles
The Vault independently checks the pinned signer, exact recipient, and amount before standard x402 settlement.
What is proven on Coston2
4th DECLINED
0.40 spent exceeded 0.35 budget window
0.70 WITHDRAWN
withdrawn after Owner pause
The Agent ran the full x402 HTTP arc:
402 → X-PAYMENT → 200 + data.
Three payments settled. The fourth was blocked by private policy before settlement.
The Owner paused and withdrew the remainder.
Built during Flare Summer Signal
- EIP-1271 AgentVault contract as non-custodial x402 payer
- Four-rule private policy evaluator in the Flare FCC enclave
- Standard x402 + EIP-3009 settlement through Flare reference stack
Next: MCP integration for your agent.