The treasury layer of agentic finance

Income earned over x402, put to work: allocated to yield, guarded by policy, audited in real time.

Agents earn around the clock.Their treasury should work the same hours.

Three acts, on repeat

Agents earn

Revenue from x402 services settles straight into the treasury. USDC in, no human in the deposit path.

Olbos deploys

Policy decides where capital goes: staking, lending, liquidity. Within its mandate, never outside it.

Capital compounds, safely

Circuit breakers watch every position. Yield accrues. Every move lands in the audit log.

stakinglendingliquidity
$4,500.00
+0.04%

What the engine does

An olive branch growing from a cracked marble urn

Autonomous yield

Strategies run without a human in the loop, inside hard policy bounds.

A bronze shield resting in a stone niche

Risk guardrails

Per-venue caps, drawdown limits, and breach behavior defined up front.

Water flowing through channels cut in stone

Multi-venue routing

Capital moves between staking, lending, and LP venues as conditions shift.

A gold coin on a stone step before a barred gate, light pouring through

x402-native

Funding, metering, settlement: the agent payment rail is the front door.

A written scroll resting on a marble sill in low sun

Real-time audit

Every allocation, every rebalance, every receipt. Replayable from genesis.

A brass key beside a black wax seal stamped with an omega

Non-custodial

Swig smart-wallet custody with scoped session keys. Your keys stay yours.

Two ways in

One treasury. Pick your door.

MCP for agents, SDK for builders. Same engine behind both doors.

Hand your agent the keys, scoped.

One config block and your agent holds treasury tools it can call on its own: deposit, check positions, adjust within policy. Never outside it.

MCP guide
.mcp.json
{  "mcpServers": {    "olbos": {      "command": "npx",      "args": ["-y", "@olbos/mcp"],      "env": { "OLBOS_SESSION_KEY": "<scoped-session-key>" }    }  }}
olbos tools available to your agent

Agents act. Humans govern.

Mission control for the treasury: positions, venue health, receipts, and the controls that matter, all in one room.

OlbosTREASURY
AUM
$4,500.00
APY
4.56%
Strategy
demo-treasury
KILL SWITCHhold · the ring closes
Decision feed
  • 17:59:33x402 payment 0.01 USDC from demo-agent-001 · strategies/strat_mq18b3kcg/withdrawals
  • 17:59:33Rebalanced 1,000 USDC · idle → olympiaview tx
  • 17:59:33Confirmed on-chain · slot 13572view tx
  • 17:59:33Simulation passed · intent 1d946760eff876aa
  • 17:59:33Risk gate passed · rebalance idle → olympia
  • 17:59:33Proposed: move 1,000 USDC idle → olympia (+3.00%)
  • 17:59:33Rebalanced 3,500 USDC · idle → delphiview tx
  • 17:59:33Confirmed on-chain · slot 13571view tx
  • 17:59:32Simulation passed · intent 724df21780281648
  • 17:59:32Risk gate passed · rebalance idle → delphi
  • 17:59:325,000 USDC credited via x402
  • 17:59:32x402 payment 5,000 USDC from demo-agent-001 · strategies/strat_mq18b3kcg/fund
Show more · 143 earlier
4
strategies running
1,283
x402 settlements
312
rebalances executed
6
venues integrated

Engineered for distrust

An autonomous treasury earns trust by making every action inspectable and every failure survivable.

Scoped custody

Swig smart wallets with session keys that can act only inside their mandate. Olbos never holds your root key.

Circuit breakers

Volatility, depeg, and drawdown triggers halt deployment before damage spreads.

Break-glass

One action drains every venue back to the vault. Owner-only, always available, no questions asked.

Audit log

An append-only record of every decision the engine makes, signed and replayable.

A dark reflecting pool in a marble courtyard, gold light held in still water

Common questions

Does Olbos hold my capital?
No. Custody lives in Swig smart wallets you own. Olbos operates through scoped session keys that can act only inside the policy you set, and break-glass drains every venue back to your vault in one action.
What is x402?
An open payment standard built on the HTTP 402 status code. Agents pay per request in USDC on Solana: the server answers 402 Payment Required, the agent settles, the call goes through. For Olbos it is also the deposit rail, since the payment itself is the funding.
How does my agent connect?
Three ways: the MCP server (one config block and your agent holds treasury tools), the TypeScript SDK, or the x402-metered REST API. All three drive the same engine.
What happens when a venue fails or an asset depegs?
Circuit breakers watch volatility, depeg, and drawdown signals on every position. A trigger halts deployment and unwinds per policy before damage spreads, and the whole episode lands in the audit log.
What does it cost?
Usage is metered per call over x402. No subscriptions, no invoices, no API keys to provision: your agent pays for exactly what it uses.
Which venues does Olbos deploy to?
Staking, lending, and liquidity venues on Solana, each allowlisted by your policy with its own exposure cap. Capital never touches a venue your mandate does not name.
A colonnade terrace at sunrise, full light across the stone

Put your agents’ earnings to work

Launch app