The orchestrator manual. Everything you need to dispatch.

Reterm is an autonomous terminal orchestrator running on Solana. It is not a chatbot and not an assistant — it is a coordinator that routes prompts to a fleet of nine specialized sub-agents, observes their output, and composes the final response.

The system is designed around one premise: most user queries are not atomic. Real work requires planning, retrieval, generation, verification, and reporting. Reterm exposes each of these as a discrete agent and lets the orchestrator decide which to dispatch.

1. 01
   Install Phantom from phantom.app.
2. 02
   Open the Console section on the landing page.
3. 03
   Click Connect Phantom and approve the connection in the popup.
4. 04
   Type a prompt and press ↵. The orchestrator dispatches and streams a response.

$ reterm.dispatch --prompt 'audit my SPL token mint authority'
[orchestrator] routing to auditor.β …

◇ mint authority detected: 5pXk…2nQ8
◇ freeze authority: null
◇ verdict: revocable, no freeze risk

✓ Done in 0.83s

Reterm runs as a single orchestrator process plus N detached agent workers. The orchestrator owns the conversation state and routing table; workers are stateless and addressable by capability.

Each sub-agent is a typed program with a manifest, a model binding, and a cost ceiling. The orchestrator selects an agent by matching the user's intent against the manifest's routes field.

The console exposes a single endpoint. Auth is wallet-based; the request body carries the prompt. The response is a streaming text/plain body.

POST /api/chat HTTP/1.1
Content-Type: application/json

{ "message": "summarize the last 24h of mempool activity" }

Response is streamed as plain text chunks:

[orchestrator] routing to analyst.β …

◇ 24h volume: 4.2M tx
◇ peak TPS: 3,108
◇ failed tx ratio: 1.7%

✓ Done in 1.04s

Reterm is a native Solana program. Agent invocations are signed by the connected wallet and recorded as off-chain attestations with on-chain commitments. The $RTM SPL token is the unit of compute.

The orchestrator never holds your private key. Wallet signatures authorize individual dispatches; revoking the session disconnects the agent fleet. Prompts are not used for training — they are scoped to the active session and discarded after settlement.

• ·No private key custody · all signing happens in your wallet
• ·Per-prompt cost ceiling · agents fail closed when budget is exceeded
• ·Sandboxed BPF execution · sub-agents cannot mutate orchestrator state
• ·Audit trail · every dispatch is hashed and committed to the log

Orchestrator

The root process that owns conversation state and routes prompts to sub-agents.

Sub-agent

A typed worker bound to a single capability and a single model. Stateless.

Dispatch

One round of routing → execution → return. Logged with an execution time.

Manifest

Declarative spec describing an agent's routes, cost ceiling, and model binding.

$RTM

The Solana SPL token used to meter compute on the network.