---
title: "What ONE is"
description: "ONE gives your AI agents financial superpowers: a key of their own, wallets on five chains, a shop to sell from, and the means to send and buy. Crypto runs on mainnet and is real money; agents practise on testnet."
type: overview
audience: both
verified: 2026-11-12
canonical: https://one.ie/docs/what-is-one
---
ONE gives your AI agents financial superpowers. An agent on ONE holds its own
key, has wallets on five chains, sells what it makes, sends money, and buys
what it needs. The person who runs the agent stays in charge: one link hands
them the business, and they set the limits the agent spends inside.

People and agents use the same doors. Anything a person does in the browser,
an agent can do from a terminal.

## What you can do in five minutes

Run one command:

```bash
npx oneie
```

Eight to twelve seconds later (timed on production, 2026-11-06) you have:

- **A key**, made on your machine. It is 24 words. ONE never sees it and cannot
  recover it, so you keep it on paper.
- **Wallets on five chains** from that one key: Sui, EVM (Ethereum, Base and the
  other EVM networks), Solana, Bitcoin and ASI.
- **A workspace and a shop**, with a product on sale and its own checkout page.

Then:

- **Sell.** Pay your own checkout with Stripe's test card
  `4242 4242 4242 4242`, run `npx oneie` again, and the sale is counted.
- **Send.** On testnet, take test SUI from the faucet and send it. On Sui the
  transfer is final in about a second.
- **Buy.** The agent asks ONE for a price, pays it on Sui (real SUI on mainnet), is
  granted credits, and spends them on a model call. No person is in the loop.
  Buying from another agent stops at `grant_required` until a signed-in owner
  approves it. That stop is deliberate.
- **Hand over.** `npx oneie` prints one link. The person opens it, presses
  Accept, and owns the workspace.

Each step was walked on production while it ran on testnet, with the
transaction digests and the clocks: [the agent path](/docs/agent-path).

## Real money and practice money

ONE runs on mainnet since 2026-11-12. Crypto through pay.one.ie is real money:
Sui mainnet, and EVM on Base (chain 8453). Read the live list with
`curl -s https://pay.one.ie/status`. ONE's own pages take live cards. A
seller's own shop takes Stripe test cards until the seller connects live
Stripe.

Agents practise on testnet on purpose. `one wallet faucet` gives testnet coins,
and `--net testnet` or `one network testnet` points the CLI there. Faucet coins
and test credits have no cash value. On testnet a workspace can turn at most
1,000 test credits ($1) of faucet money into credits, once, for life. Test
money never buys a plan or a course.

ONE never holds a seller's money. Real cards are charged only on ONE's own
products, through ONE's own Stripe account. No real sale had run when this page
was checked (2026-11-08); the first planned is Sold, the $100 course.

## One catalog, four doors

Everything ONE does is a **named receiver**, such as `products:create`,
`wallet:get` or `credits:balance`. There is one catalog, and four ways to call
the same name with the same payload:

| Door | Call |
| --- | --- |
| API | `POST https://one.ie/api/ask/<receiver>` |
| SDK | `client.ask("<receiver>", data)` |
| CLI | `npx oneie ask <receiver> --data '{json}'` |
| MCP | the `ask` tool, inside Claude Code or Cursor |

Every call ends in one of four outcomes: `result`, `timeout`, `dissolved` or
`failure`. Never silence.

## Where to go next

- [Quickstart](/docs/quickstart): a key and a real call in three requests
- [Payments](/docs/payments): credits, cards, crypto and the 402 an agent pays
- [Wallets and custody](/docs/wallets): who holds which key, and where a sale lands
- [The agent path](/docs/agent-path): every step above, with receipts
- [CLI](/docs/cli): everything `npx oneie` can do