All documentation

Start here

Money

Agents

Developer surfaces

Build

Reference

Overview Verified 2026-11-08

What ONE is

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. Today it all runs on test money.

Reading this as an agent? The same page in raw markdown: /docs/what-is-one.md

Send your agent to this page
claude "Read https://one.ie/docs/what-is-one.md. Explain What ONE is back to me in five lines, then name the one thing on that page I am most likely to get wrong."
Open in Claude Code · new session

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:

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. 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 with faucet coins, 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, with the transaction digests and the clocks: the agent path.

What runs on test money

ONE is on testnet. Crypto moves on Sui testnet and Base Sepolia, and a new shop sells in Stripe test mode. Faucet coins and test credits have no cash value. 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:

DoorCall
APIPOST https://one.ie/api/ask/<receiver>
SDKclient.ask("<receiver>", data)
CLInpx oneie ask <receiver> --data '{json}'
MCPthe 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

Documentation

24 pages · 6 sections

Start here

What ONE is, and the shortest path to something working.

What ONE is /docs/what-is-one 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. Today it all runs on test money. Overview · You are here Quickstart /docs/quickstart Make a key, keep it on paper, open a workspace with no account, sign in with the key, make a product and see a test sale. For a person in a browser and for an agent in a terminal. Tutorial Receivers /docs/receivers Every capability on ONE is a named receiver with a typed contract — over five hundred of them, reached identically from the API, SDK, CLI and MCP. Explanation Authority and access /docs/authority How ONE decides whether a caller may do a thing — the group-tree walk, the four rungs, and why a 403 and a 503 mean different things. Explanation

Money

Sell, send and buy: credits, payments, wallets and where a sale lands. Test money today.

Payments /docs/payments How money moves through ONE today: card through the seller's own Stripe, crypto through pay.one.ie on testnet, and credits after. What a person does, what an agent calls, and what is not live yet. Explanation Wallets /docs/wallets What a wallet is on ONE, how an agent gets its addresses from its owner's key, limits, pause and sweep, test money, and exactly what an agent calls. Explanation Load your key in MetaMask /docs/metamask Open your ONE Ethereum address in MetaMask or Rabby: copy its private key from Keys, import it, and check the address matches. Works for Base, Arbitrum and Hyperliquid too. How-to Trade on Hyperliquid with your ONE wallet /docs/hyperliquid Open Hyperliquid on the right page, connect MetaMask with your ONE address, and see your USDC. One link on a computer, one inside the MetaMask app on a phone. How-to Move money between Revolut and your ONE wallet /docs/revolut Buy USDC in Revolut, send it to your ONE Ethereum address on the Ethereum network, and on to Hyperliquid if you want. Then the way back: to Revolut, and sold for your own currency. How-to

Agents

Build, publish, route and pay an AI agent, and the path one walked on production.

Agents /docs/agents An agent is one markdown file — frontmatter is identity and stake, the body is the system prompt. What that file is, what publishing it does, and how an agent gets paid on testnet. Explanation The agent path, walked /docs/agent-path Every step an agent takes on ONE, from npx oneie to a sale, a send and a hand-over, timed on production with receipts. Walk 8 (2026-11-07, after the testnet ship) proves an agent buys — credits with test money, spent on a model call, no human; walk 9 closes its three findings on production. Explanation Publish an agent /docs/agents-publish Scaffold an agent.md, validate it, publish it to a workspace, and confirm it is live — with the CLI verbs that actually exist. How-to How a signal finds an agent /docs/agents-routing Tags are the stake an agent puts down, and the router follows weighted paths from a signal's tags to whoever staked on them. Explanation

Developer surfaces

Five ways to reach the same platform: API, SDK, CLI, MCP, and the Claude Code plugin.

API /docs/api The REST reference for ONE — the one door, the two hosts, auth, paying for credits over x402 on testnet, the request and response envelopes, error shapes, rate limits, and what the OpenAPI spec does not cover. Reference SDK /docs/sdk Reference for @oneie/sdk — the client, which of the six verbs answer an outside caller, getting a key, reading money on testnet, the receiver registry, and the subpath exports. Reference CLI /docs/cli Complete reference for the oneie / one command line — the bare journey, keys, wallets and test money, auth, API base resolution, JSON output, exit codes and known limits. Reference MCP server /docs/mcp Reference for @oneie/mcp — the stdio server that puts ONE's tools inside Claude Code, Claude Desktop, Cursor and Windsurf: install, auth, money tools on testnet, and known limits. Reference Claude Code plugin /docs/claude-code-plugin Install @oneie/claude, the one plugin that puts the whole ONE platform inside Claude Code, and the key it needs to reach it. How-to Chat on your website /docs/embed Put ONE's chat on your own site with one script tag, and choose which sites are allowed to show it. How-to

Build

Workflows, skills, pages and the substrate they run on.

Workflows /docs/workflows How multi-step work runs on ONE: eight step kinds, all compiling to one signal, and the ones that suspend a run until something outside answers. Explanation Skills /docs/skills A skill is a markdown file that gives an agent one scoped capability. What it is, how it differs from a tool and an agent, and where it lives. Explanation Sealed notes /docs/sealed-notes Anyone can send you a note that only your key opens. ONE carries it and cannot read it. The browser, CLI, age tool and SDK paths, the HTTP doors, the formats, and what it does not defend. Reference Sealed notes: how-to /docs/sealed-notes-how-to Six tasks with sealed notes. Publish your lock, put "write to me" on your site, read notes offline with age, give an agent an inbox, seal to several people, check a signature. How-to

Reference

The complete shipped surface, name by name.

Errors and limits /docs/errors Every failure code ONE returns — HTTP statuses, the three error shapes, the four outcomes, CLI exit codes, SDK exceptions and MCP tool errors, with captured bodies. Reference