Oak Agent Kit

How it works

How Oak works

One install, one wallet, 25 projects. Here is who does what, and where your key stays.

Inside a carved oak root hollow, a hooded olive-felt wooden agent tends a dovetailed oak lockbox on a miniature workbench. Soft lime light glows from the keyhole beside a wooden key.

What Oak is, and why

Every project on Robinhood Chain has its own contracts, its own API, its own decimal and approval rules and its own ways to fail. Installing and maintaining 25 separate tool servers, or giving 25 tools access to one wallet, is more than anyone wants to do.

At launch, Oak will be one MCP server for the whole chain. MCP (AI tool connector) is short for Model Context Protocol, the standard way an AI agent plugs in tools. It will connect an agent to 25 projects behind one local wallet, one naming pattern for tools, one amount format, a simulated preview before every signature, and error messages written as plain sentences.

  • Your keys stay on your computer. The wallet is created and kept on your computer.
  • One format across 25 projects. Multi-step approvals, auction-style quotes and claim proofs are handled inside each module, so the agent sees the same kind of tool everywhere.
  • Open kit, closed server. The add-on, the shared core and the module definitions are open source under the MIT licence at launch. The hosted server is a closed service.

Who does what

Part 1

Your computer

Your private key is created here and stays here.

Oak cannot recover a lost key.

oak init runs in your own terminal, never through the agent.

Part 2

The Oak server

It reads chain and project data, and builds unsigned transactions and previews.

It never sees your key and never signs or sends a transaction.

Part 3

Robinhood Chain

Chain ID 4663, the number that names this network.

25 projects, reached through one local wallet. Oak itself never trades.

The full custody story is on the security page.

From a request to a result

  1. At launch, install Oak with one command on the computer where your agent runs.
  2. Create the wallet and set up identity. Run oak init in your own terminal, write down the 24 recovery words, and confirm a three-word backup check. Then run oak setup to link an existing ERC-8004 agent ID with an owner signature (no ETH needed) or register a new agent ID on-chain.
  3. Fund the address. Send what you want the agent to use, plus a little ETH to pay for gas (the network fee).
  4. Connect your agent to oak mcp, which runs on your computer, and ask for what you want. Read tools work any time; run oak identity unlink any time to unlink without gas.

To buy a coin, the agent will look up the verified asset, ask for a quote that compares routes across KyberSwap, Velora and Pons launch curves, preview the result, and then swap with an exact approval. A quote will be good for 60 seconds, and signing will happen on your computer.

You

Put 100 dollars of stablecoin into a yield vault.

Agent

Here is the plan. Nothing has been signed yet.

Preview

ApproveApprove exactly 100 for the vault
DepositDeposit 100 and receive vault shares
GasPaid in ETH from the agent's wallet
SigningSigned on your computer

Agent

Say go and I will send it.

An illustration of the flow, not a live result.

Every move is previewed

At launch, before signing any transaction, the add-on will simulate it and show how each balance in the wallet would change. Read that preview every time.

Oak will add no safety checks, spending caps or allowlists of its own. You and your agent decide what to sign, so send the wallet only what you are willing to let the agent use.

Oak never promises returns, pools anyone's money or gives financial advice.

Where to next

Docs

What each group of projects can do.

Security

Who holds which key, and what Oak cannot protect you from.

About

Why Oak exists, and what is open source.

Follow on X