Loading SKILL.md
Station status Contracts built, low-cap mainnet beta being prepared.
Every agent payment passes the guard first
AI agents want to spend your money. is the station in orbit between them and your funds. An agent can only ask to pay; the Checkpoint decides. Each request is held against your Flight Rules, money goes only to providers that pass Verified Docking, and your local Co-Pilot co-signs anything large. Your balance rests in the Deep Vault, and Quantum Lock can move ownership to hash-based signatures without touching the funds.
Built onEthereumERC-8004x402Privacy PoolsKohaku SDK
Telemetry starts with the beta
Volume settled$0
Agents on board0
Payments cleared0
In the Holding Bay0
Figures come straight from Ethereum mainnet as agents run.Open telemetry →
0owner keys an agent ever touches
4policy gates at the Checkpoint
29/29contract tests green, fuzzing included
~272kgas for the Quantum Lock switch
Private by defaultPrivacy PoolsKohaku
Blackout
Deep Vault
Funds rest inside a privacy pool, never on an address anyone can watch.
Epoch accounts
Each epoch starts with a new owner key and a new account. Nothing ties one epoch to the next.
Drift top-ups
Top-ups arrive in uneven amounts at uneven times, so refills never line up with deposits.
What an agent pays is visible onchain. Who stands behind the account, and how much it holds, stays dark.
The Checkpoint
Six stops between a 402 and a payment
Agents never hold your key. They file a request, the Checkpoint rules on it, and only a cleared request moves money.
01
Paywall
A paid API answers with 402 Payment Required over x402.
02
Request filed
The agent signs an EIP-712 payment intent with its Request Key. That key can ask and nothing more.
03
Six gates
Allow and deny rules, ERC-8004 identity and reputation, account and agent caps, hourly rate, category, and a pre-flight scan.
04
Co-Pilot sign-off
Small amounts clear on the spot. Bigger ones also need the Co-Pilot's signature. Anything else lands in the Holding Bay for you.
05
Score update
The outcome is written back to the provider's ERC-8004 reputation.
06
Refuel
When funds run low, the Deep Vault sends a shielded top-up to a fresh account.
Layers
Four shields around one wallet
No single check is enough. Each layer catches what the others miss, so an agent stays useful and never dangerous.
Flight Rules
Spending caps per account and per agent, an hourly limit, allow and deny lists, and the Co-Pilot's 2-of-2 signature on larger amounts. The smart account enforces them, so the model can't talk its way past.
Verified Docking
Money only docks at a provider's registered ERC-8004 wallet, and only when the validators you picked rate that provider above your bar.
Blackout
The Deep Vault on Privacy Pools, a separate account for each service, chain reads through the Helios light client, and selective disclosure when an auditor needs a look.
Layer four: Quantum Lock
Locked against drainers today and quantum computers tomorrow
Agents can only pay registered provider wallets, so a drainer address fails before gas is spent. The owner key can live in your phone's secure chip, Crew Recovery lets guardians restore it, and an offline hash-based backup key holds 1,024 signatures. If ECDSA ever falls, one signature locks the account to quantum-safe ownership at the same address. Escape Pod is the other route: everything moves to a fresh account.
Telemetry
Payments, logged in public
Each agent payment is recorded the moment it clears. Accounts show up as anonymous ids, and owners never show up at all.
Volume settled$0
Payments cleared0
Agents active, 24 h0
Accounts0
Hourly volume, last 24 hOpen telemetry
For agents
One line brings an agent on board
Works with Claude, ChatGPT, Codex, Cursor or your own code. Paste the line below; the agent handles the rest and sends you a Boarding link to approve.
Paste into your agent
ClaudeChatGPTCodexCursorAny MCP client
1
It reads SKILL.md
The agent fetches a small helper and creates its own Request Key. The key never leaves its machine and is never printed.
2
You open the Boarding link
The link lists the limits the agent wants. Connect your wallet, trim anything you don't like, and approve.
3
It gets to work
Talk to it in Comms or in your own client. Flight Rules, Verified Docking and the Co-Pilot still check every payment.
Developers
Bring your own agent
LangChain, Claude, ChatGPT or custom code. supplies the wallet and the rules; your agent stays yours.
- 1RegisterGet a Request Key that can ask for payments and nothing else.
- 2Plug in MCP or the SDKFour tools: list services, check budget, call an API, request payment. Service replies come back sanitised and flagged untrusted.
- 3Write your Flight RulesCaps, lists and the minimum ERC-8004 score sit in the smart account. The Co-Pilot daemon runs next to a local model and signs larger payments.
- 4GoRequests inside the rules clear. The rest wait in the Holding Bay.
agent.ts
Side by side
Limits are only the first layer
Spend caps are standard in agent wallets now. Here is what puts on top of them.
| Capability | Typical agent wallet | |
|---|---|---|
| Spend caps with human approval | Yes | Yes, enforced by the contract |
| Balance hidden from public view | No | Deep Vault plus rotating accounts |
| Who an agent may pay | An allowlist | Verified Docking: ERC-8004 identity and score |
| Every payee tied to a verified identity | Rarely | Always |
| Second signer on larger payments | Rarely | Co-Pilot, 2-of-2 with you |
| Lost owner key | Seed phrase or nothing | Crew Recovery, 3-day delay you can cancel |
| Proving payments to an auditor | Expose the whole wallet | Selective disclosure per account |
| Quantum migration | Move everything to a new wallet | Quantum Lock in place, or Escape Pod |
Roadmap
Four stages to full launch
Each stage ships on its own. Mainnet opens as a low-cap beta, and the public release comes after independent audits.
Stage 1Underway
Agents that can't overspend
- Flight Rules, per-agent caps, allow and deny lists: done
- Co-Pilot 2-of-2 with a local model: done
- Quantum Lock key, Escape Pod, Crew Recovery and phone key: done
- SDK, MCP server and Co-Pilot daemon: done
- Low-cap mainnet beta: up next
Stage 2Next
Pay only who you trust
- Provider validation service
- Open reputation API
- Standard x402 settlement (ERC-7710)
Stage 3Later
Spend out of sight
- Deep Vault on Privacy Pools (SDK adapter done)
- An account per service, with Helios reads
- Selective disclosure reports: done
- Private payment links
Stage 4Full launch
Audited, ready for teams
- Two independent audits
- Formal verification
- Private payroll and reporting
FAQ
Questions, answered
Where things stand and what is still coming.
Can I use on mainnet today?
The contracts, SDK, MCP server and Co-Pilot daemon are built and tested, including on a forked copy of mainnet. A low-cap beta comes first, and the public release follows two independent audits. Until then, keep your savings elsewhere.
Could my agent drain my wallet?
An agent only ever holds a Request Key. Every request is checked against your caps, the provider's identity and score, and the category before anything moves. Whatever falls outside your rules waits in the Holding Bay.
What does Blackout keep private?
The link between you and the account, and the size of the balance behind it. Pool deposits and individual agent payments stay visible onchain, but nothing points back to you.
How does Quantum Lock work?
You set up a hash-based backup key today: a tree of 1,024 one-time WOTS+ keys generated offline from a seed only you hold. If ECDSA ever becomes unsafe, one signature from that tree switches off your ECDSA key while the address stays the same. Each later owner action uses the next key in the tree.
Why hash-based keys and not lattice cryptography?
Hash-based signatures stand or fall with the hash function alone, the safest bet in cryptography. Lattice schemes are smaller and faster, but Vitalik Buterin has warned that AI-assisted mathematics could weaken them within a few years, so hash-based keys are the fallback.
What is the Co-Pilot?
A second AI model that runs on your own machine, separate from your agent and holding its own key. Above the limit you choose, a payment goes through at once only if the Co-Pilot signs. It looks for prompt injection, checks the payment against your standing instructions, and fails closed: unsure or offline means the payment waits for you.
I lost my phone or key. Now what?
Crew Recovery. Guardians you chose, such as friends' wallets or a ZK email verifier, can hand ownership to a new key after 3 days. Your phone or owner key can cancel within that window, so guardians can't act behind your back.
Which agents can use it?
Anything that speaks MCP, such as Claude Desktop or Cursor, plus any code that can use the TypeScript SDK.
Is there a token?
Yes, on Ethereum mainnet. Copy the contract address from the box at the top of the page and check it on Etherscan. Always confirm every character.
is the Ethereum token behind the station. Check the full address at the top of the page before touching any token. Planned uses: paying relay fees, staking as an ERC-8004 validator, and voting on the default trust modules.
Get started