Olbos Documentation

Olbos is an autonomous treasury engine for Solana. AI agents pay for it over x402 and it deploys their idle USDC into real on-chain yield venues — within risk policy, under custody the agent's owner controls, fully auditable: every action lands in an append-only, replayable log.

The name is ὄλβος (olbos), the ancient Greek word for wealth that works for you. The mark is a torc — a worn ring of value. The venues are named after Greek treasuries.

Start here

Introduction — what Olbos is, the problem it solves, and the one mental model that makes everything else click.
How it works — the full lifecycle of a treasury, from an agent's first request to capital earning yield.

For agent builders

Agents quickstart — give your agent a treasury in five lines (SDK) or one command (MCP). The full tool/API surface.
Strategies & policy — the three risk templates, the allocation engine, and every dial that governs how your capital moves.
Payments (x402) — how agents pay, why the payment is the deposit, and what each call costs.

For owners

Dashboard — sign in with your wallet, read your treasury, and the one red button.
Custody & control — how your wallet holds root authority, why the engine can't move your funds, and how to fire it on-chain.

For operators & auditors

Architecture — the event-sourced engine, the venue adapter contract, the payment rail seam, and how the pieces fit.
Security model — the threat model, what can and cannot happen, written for a reviewer.
Venues — what a venue is, the adapter interface, and the Kamino and Marginfi integrations in detail.
Operations — deploy, configure, fund, back up, and monitor a hosted instance.

Reference

HTTP API — every endpoint.
Event vocabulary — the append-only log that is simultaneously the audit trail, the replay source, and the dashboard feed.
Glossary — every term in one place.

The shape of the thing, in one paragraph

An agent holds a wallet and an intent — "earn safe yield on my idle USDC." It calls Olbos over x402; the payment settles and becomes the deposit. Olbos creates a per-strategy Swig smart account where the agent's owner holds root authority and the Olbos engine holds a narrow, revocable role — it can move funds into approved venues only, never out to anyone. An event-sourced engine scores venues by risk-adjusted yield, plans moves that clear a break-even gate, simulates every transaction before sending it, and records every decision to an append-only log. The owner watches through a read-only dashboard and holds one break-glass: a wallet signature, or an on-chain revoke that fires the engine even if Olbos is offline. Agents pay, owners sign, owners withdraw, owners can always walk away with their keys.