Every feature is designed around one constraint: agents are non-human, autonomous, and can misbehave. Agentic Wallet enforces spending rules before the transaction — not after.
Private keys never touch your server. Keys are generated and stored inside a Trusted Execution Environment — hardware-isolated memory that even the OS cannot read.
No custodian holds your keys. No operator can export them.
Every transaction — regardless of which agent sends it — passes through the same policy gate. All five checks must pass.
Any single failure blocks the transaction, logs it, and notifies the operator. Agents cannot circumvent this.
Agents never hold the master private key. Agentic Wallet issues session keys — short-lived credentials scoped to the active policy.
When the TTL expires or you run aw freeze, the agent's signing authority is revoked instantly. No server round-trip. No revocation delay.
x402 is the standard for machine-to-machine payments over HTTP. Agents make API requests, receive HTTP 402 Payment Required, trigger the Policy Engine, sign a micropayment via TEE, and retry.
No wallet UX. No human in the loop. Just standard HTTP.
KYA is Agentic Wallet's behavioral risk scoring system. Each agent maintains a continuous score from 0.0 to 1.0. Normal, predictable agents score high.
Unusual API targets, high velocity, and failed checks drag the score down. When a score drops below your configured minimum, that agent is blocked until reviewed.
No compromises on the details.
Each agent gets an isolated wallet. One agent's budget can't affect another's.
Daily cap and per-tx cap configured once, enforced on every transaction.
Allowlist of approved destination endpoints. Unknown targets are rejected, no exceptions.
Configure spending hours (e.g. 09:00–17:00 UTC) and allowed days. Enforced onchain.
Set a minimum balance. When an agent's wallet dips below it, automatic refill from main pool.
Large transactions require 2-of-3 or 3-of-5 signatures from your team.
One command halts all agent activity immediately. aw freeze.
Publish cryptographic proof that your keys are TEE-managed. Verifiable onchain.
Every transaction, every rejection, every KYA event — logged and queryable.
Most spending controls live on a server. That means they can be misconfigured, go offline, or be deliberately bypassed.
Agentic Wallet puts rules onchain — enforced by Solana programs. An agent can't route around the policy. An operator can't override it silently.
| Agentic Wallet | Server-side controls | |
|---|---|---|
| Rules enforced by | ✔Solana smart contract | ✘Your server |
| Works if server is down | ✔Yes | ✘No |
| Operator can override silently | ✔No | ✘Yes |
| Verifiable onchain | ✔Yes | ✘No |
| Bypass by malicious agent | ✔Impossible | ✘Possible |
| TEE-backed signing | ✔Yes | ✘No |
| KYA behavioral scoring | ✔Yes | ✘No |
Private keys stay local. No account required to try.