Example link
Example mug
Product
$12.50
pay.example.com/l/yourshop-mug- USDClive
- Cardtest mode
Example only. Yours opens for real.
Payments for agents, and the people who run them
Give your agents financial superpowers.
They sell for you on every channel your customers use, by card or crypto. The money goes straight to you.
To be paid, you need a key.
Your private keyYours
- Sui
- Ethereum
- Base
- Solana
- Bitcoin
- ASI
Free.
Free.
To be paid, you need a key.
Your private keyYours
- Sui
- Ethereum
- Base
- Solana
- Bitcoin
- ASI
Free.
Free.
Payments for agents, and the people who run them
Give your agents financial superpowers.
They sell for you on every channel your customers use, by card or crypto. The money goes straight to you.
To be paid, you need a key.
Your private keyYours
- Sui
- Ethereum
- Base
- Solana
- Bitcoin
- ASI
Free.
Free.
The sale
One link. Paid by card or USDC.
Product
Sold, the book
The playbook, every chapter
$20Example price.
Buy · $20Card checkout by ONEPaid into the seller's Stripe.
Example sale. Nothing here is a real payment.See the whole sale, screen by screen
The call
Your website in, a payment link for each product.
Cards
Take cards.
You pay Stripe’s cost. We add nothing.
Cards go to your own Stripe account. Make a product, then open its checkout.
Cards · Make
A name and a price. That is a product.
Type what you sell and what it costs. Signed in, I can write the description for you. Nothing saves until you press Save.
“A 30-minute strategy call, $10”
activeService
30-minute strategy call
An example product, made from one sentence in the chat.
- Price
- $10.00
- Status
- Active
Do it as a person
Type a name and a price in your shop, then press Save.
Do it as an agent
One call makes it. Set status to active, or it stays a draft.
$ one ask products:create --data '{
"slug": "<your workspace>",
"name": "30-minute strategy call",
"status": "active",
"prices": [{ "unit_amount": 1000 }] }'It answers with a pid and a ppid. Next, checkout:link turns the ppid into a pay link.
Proof. Press Save and the product shows in your shop with the name and price you typed. An agent checks with products:list on its slug.
Cards · Sell
Every product gets a checkout page. Open a real one.
This one is ONE’s own shop, selling Sold, its course, so it is real. Sales in your own shop run in test mode today: a Stripe test card pays and no real money moves. Crypto pays on Sui.
Test mode · test card
30-minute strategy callExample$10.00
Stripe test mode · nothing is charged
How would you like to pay?
Pay by card
Pay with USDC
Do it as a person
Open the real checkout. You’ll see the course’s price and the ways to pay.
Do it as an agent
checkout:link turns a product into a pay link. For USDC, each order gets its own quote and its own deposit address.
Proof. Open the checkout in a private window, signed out. If you still see the price and the ways to pay, so does a stranger.
Crypto
Take USDC. We take 0%.
By default it goes straight to you. ONE holds it only if you switch escrow on.
Stablecoins on Sui, wallet to wallet.
Crypto
Send USDC. A receipt comes back.
Your key signs on your device and the chain settles it. The network charges its own small fee, paid in SUI.
Send 5.00 USDCto
0x9c21…4bd0 · SuiExample amounts.
Open on SuiscanA real transfer on Sui, 11 Nov 2026: ONE’s owner sent 20 USDC to ONE’s agent. ONE took no fee. Not yours.
Do it as a person
Open Wallets and press Send. Read the confirm screen before you approve.
Do it as an agent
The key signs and broadcasts the transfer on the agent’s own machine. The digest is the receipt: any Sui explorer reads it back. Once you own the shop, this records it on your books:
$ one wallet send <to> --chain SUI --amount 5 \
--currency USDC --payment-tx <hash>The command never signs, and it takes the owner’s key: an agent key is refused, by name.
Proof. Paste the transaction hash into any Sui explorer and see the amount arrive.
The key
One key. Yours alone.
Your machine makes it.
The key
Make your own key. Nothing is sent while it’s drawn.
Your device draws twenty-four words. Those words are the key itself, not a hint at it. From the press to the words, nothing asks the network for anything. ONE never sees them, so ONE can’t recover them.
Do it as an agent
One command writes the key to a file and prints your five addresses.
$ npx oneie key new --out key.json \
--yes-i-accept-plaintext-file --jsonThe words go to key.json at mode 0600, never to your output. npx fetches the package first; the key command itself opens no connection.
Proof. DevTools, Network: clear it, press Generate; no new row appears before the words land. Agents: install oneie, run it under macOS sandbox-exec with network denied; key.json still appears.
Your agents
Agents with a key of their own.
Your agents
Your agent builds it. One link, and you own it.
Your agent builds the business first, then sends you one link. You make and keep your own key and press Own, and you take the owner seat. No key changes hands.
Your agentlimit you set
5.00 / 50.00 USDC this week
$ npx oneie Do it as a person
Open the link, make and keep your key, press Own. Press again if asked. You see: You own it.
Do it as an agent
npx oneie prints the owner link once the first sale is counted: open it, press Accept, and you hold the owner seat.
Proof. After you press Own, open your dashboard. You hold the owner seat.
Do it now
A first sale, from your own link.
Do it now
Watch a sale land.
This is an example: a link is paid, the checkout reads it back, and your shop counts it. Your own first sale works the same way.
Example sale
ONE receipts · example
$10.00 paid
Example receipt
- Item
- 30-minute strategy call
- Paid
- $10.00
- Method
- Card · Stripe test card
- Network
- Stripe · test mode
Example receipt. Nothing here was paid.
Do it as a person
Watch the example. Your own sale reads back the same way.
Do it as an agent
The agent’s own practice, a payment made and read back from the chain, is a drill in the course: /sold/limit.
Proof. Your own sale is counted only when your shop reads it back from the checkout, never because a page says so.
The gift
Send your agent.
Needs Claude Code on this computer. Run it once and the link works. Get Claude Code
OpenThe app opens with the prompt in it
PasteOne line for the terminal you already use
ConnectOnce, and every later prompt can reach ONE
Pass it onTo the machine that will run it
All yours. Make your key.
$ npx oneie - Sui
- Ethereum
- Base
- Solana
- Bitcoin
- ASI
HoldsThe prompt carries no key. Your agent makes its own on its own machine, and the words are never printed.
Gives upOpen it in a web agent and the prompt goes to that provider. It holds nothing secret. The agent’s key stays on the machine that ran it. Whoever holds that machine holds it.
ONE charges nothing for the key, the wallets or a stablecoin send. The network’s small fee is paid in SUI. Made on your device, and only you hold it.
Sold
One thing costs money.
Sold is a course where people and agents learn to sell together. A hundred dollars, once.
It is the one thing ONE sells.
How it is builtWhat it defends, and four ways an agent holds money
The threat model
What it defends, and what it accepts.
A table, not a promise. Each row names both sides.
Key made on your device
Defendsthe server never sees it
Acceptsyou must keep it
Words on paper
Defendsyou can rebuild anywhere
Acceptspaper can be found
An agent’s credit limit
Defendspaid ONE services stop at the limit
Acceptsthe limit is credits, not a cap on its own wallet
Real money
Defendsonly your key can move it
Acceptsa lost key and lost words cannot be undone
Agents and money
Four ways an agent holds money. You pick.
An agent’s monthly credit limit for ONE’s paid services is a number only a person can raise. What sits in its own wallet it can spend.
- 1
Co-sign
the person approves each spend
- 2
Scoped
a budget, a ceiling, a clock
- 3
Capability
one task, one key, then gone
- 4
Peer
the agent’s own wallet, in its own name