Skip to content

Arete documentation

For the complete documentation index optimized for AI agents, see llms.txt or llms-full.txt. A markdown version of this page is available by appending .md to the URL or sending Accept: text/markdown.

For AI agents: the documentation index is at llms.txt (full corpus: llms-full.txt). A markdown source for this page is /index.md.

An Arete sandbox is a financial virtual machine for your agent: a funded Solana wallet the agent can trade and act from, inside rules you sign. The agent asks for an action; Arete builds the transaction, checks it against your rules, signs it and sends it. The agent never sees a private key, a transaction to sign or an RPC URL.

Open your agent and paste:

Agent prompt Copy / paste

Read https://docs.arete.run/agent.md and follow it to set up Arete in your environment. Verify the setup, and simply explain what Arete is capable of.

The agent installs the a4 CLI and the Arete MCP server. Then create a sandbox and grant the agent access. The agent finds the sandboxes it has been granted itself.

No key handover

The wallet’s key never leaves Arete. The agent names actions; Arete signs them, and only when they pass your rules.

Write scope

Only the programs and instructions you enabled, within per-program spend limits. Funds can leave only to your wallet, addresses you allowed, or the sandbox’s own accounts.

Read scope

The same rules decide what the agent can see. Program reads and live views are the sandbox’s read side: a program that isn’t in the sandbox is one the agent can’t call or read through Arete.

Auditable and revocable

Every action is recorded, refusals included, with decoded instructions, events and balance changes. Revoke a grant and the agent stops at its next call.

Refusals an agent can act on

Each refusal names its code, the rule that refused, whether to retry and what to change, so the agent corrects the request instead of guessing.

Exits always allowed

The agent may always sell or exit a token the sandbox bought, so a position is never stuck behind a rule.

Program reads and live views read through a sandbox are scoped today; chain reads are not yet. See Read scope.

Your first sandbox

Create, fund, write rules, grant your agent and run its first action.

Quickstart →

Rules

Which programs, which instructions, how much, and where funds may go.

Write rules →

Arete Protocols, automations, cloud dev environments, custom live data and the SDKs are in private beta. Their docs are public; access is enabled per account.