Transfers are encrypted before they leave your account, then settle in 400ms slots. Each agent gets an account of its own, pays over x402 natively, and can never go a cent past the limits you set.
Decrypted in your browser. Nobody else sees these figures. Main account @mara.sable.
Live feed of accounts, balances and activity.
Right now, AI agents are earning, spending and settling with one another at every hour of the day. Sable gives them a private place to do it. It is a non-custodial neobank where people and agents move money confidentially, with each settlement checked on Solana.
People and their agents share a single protocol. The program itself enforces each feature listed here, rather than a promise written in a policy.
Each amount is hidden and a range proof shows it is valid. The program checks every transfer without ever learning the figure.
Each agent gets a separate account and separate limits it cannot break. The policy is checked before any transaction is signed.
Spend your private balance wherever cards are accepted. Freeze or rotate a card, and reveal its details only when it matters.
Agents settle API calls one request at a time, without waiting on a person, and each payment is recorded.
Show an auditor precisely what they need and not a byte beyond it. Scoped, read-only, and revocable whenever you choose.
Final within a couple of slots for a fraction of a cent, on a chain that already carries agent traffic.
Accounts for people and accounts for AI agents sit next to each other on the same protocol. They are non-custodial, shielded, and governed by spending policies on-chain rather than rules on a server. Your funds take orders from you, not from a database.
Every amount is encrypted and a range proof shows it is correct. No observer can read it, yet anyone can verify it. Whenever you decide to share, a view key exposes only what you pick.
An agent account handles x402 payment requests by itself, without anyone stepping in. Because spending policies live on-chain, no agent can exceed its mandate, and split routing breaks each payment apart to keep it private.
Split-path payments break a transfer into pieces sent along parallel routes, so nobody watching can see all of it. Settlement is still atomic. Stealth addresses keep receipts from being linked together.
The chain proves that each transaction happened while the amounts remain encrypted. A view key gives an auditor read-only access, the public sees nothing, and custody stays with you the whole time.
All it takes is an email and a passkey. Your keys are made on your device, and your balances never leave it unencrypted.
Move in USDC on Solana, or top up straight from a wallet. A small SOL reserve pays fees on its own, so they never need your attention.
Send an encrypted amount to any @handle, or create an agent account with a spend policy and let it cover its own costs over x402.
One lightweight, typed SDK wraps the REST API. A single client covers accounts, encrypted transfers, agent accounts with spend policies, and webhooks.
import { Sable } from "@sable/sdk"; const bank = new Sable({ apiKey: process.env.SABLE_API_KEY }); // On-chain, the amount stays encrypted. You get confirmation // that it settled, never the figure itself in plaintext. const transfer = await bank.transfers.create({ to: "@vendor", amount: "125.00", asset: "USDC", memo: "Invoice #4471", }); // Spin up an agent with its own account and a strict budget. const agent = await bank.agents.create({ handle: "datafetch", policy: { dailyLimit: "50.00", maxPerRequest: "5.00" }, }); console.log(transfer.status, agent.address);
No. It keeps amounts and balances private. Handles and the fact that a transfer happened can still be seen, and your identity is verified once at sign-up.
No. You sign in with a passkey and send to an @handle. Keys, fees and proofs are handled for you.
A separate account with its own balance and its own spend policy, owned by you and operated by software. It can pay x402 requests on its own.
No. The limits are checked by the program before a transaction is signed, and any overspend reverts.
Create a scoped view key for the transfers you choose. It is read-only and you can revoke it at any time.
Transfers are free during the beta. Fee design is a launch target and will be posted before it applies.
Get set up in a few minutes. It costs nothing in beta, and your very first transfer is already private.