$ORUN launching soon Burn 30,000 ORUN for 50 runs once it launches. Until then every wallet gets 3 prelim runs. How the pass works
Docs

How orbio.run works.

What it does, what it stores, what it costs, and the limits. orbio.run runs on the Orbio protocol on Robinhood Chain.

Overview

You write what you want done. orbio.run turns that into an agent with its own wallet on Robinhood Chain (chain 4663), a model, a set of tools and a schedule. When it runs, the model works through the job with its tools and finishes with a short report. Every run leaves a receipt: each step, what it cost, and the report.

orbio.run deploys no contracts of its own. It uses orbio's live protocol (CREDIT, the Exchange and gateway wallet keys) and the $ORUN token's own burn.

The two payments

1. Runs: the pass

Burn 30,000 ORUN in one transaction with the token's burn(uint256) and your wallet gets 50 runs. A run is one agent run, by hand or on schedule, for any agent you own. The burn destroys the tokens; nobody receives them. See Burn for live totals.

2. Compute: the agent's CREDIT

orbio.run never pays for compute. Each agent spends CREDIT activated to its own wallet, at orbio's gateway prices. You fund it from your wallet in one transaction, either way:

  • CREDIT you hold: CREDIT.activate(amount, bytes32(agent wallet)).
  • USDG: Exchange.buyAndActivate(usdgIn, minCreditOut, bytes32(agent wallet), maxFills) buys CREDIT on orbio's book and activates it to the agent in the same call.

Activated CREDIT cannot come back. It can only be spent on AI and tools by that agent's wallet. It cannot be moved, sent back or cashed out, and deleting the agent wipes its key, so anything left on it is lost. Fund small amounts and top up.

Agent wallets

Each agent gets a fresh wallet made on the server. Its private key is encrypted (AES-256-GCM) before it is stored and is used for one thing: signing that agent's orbio gateway key, the same wallet-signed key anyone gets on orbio.so. The key and the gateway key never leave the server, are never logged and are never returned by any page or API.

None of the agent's tools sign transactions. An agent cannot send tokens, trade or move funds. Its balance is AI balance on orbio's gateway, not tokens in the wallet.

A run, step by step

  1. One run is taken from your pass (or a prelim run). If the run never reaches the model, it is given back.
  2. The agent's CREDIT balance is read. Below 0.01 CREDIT the run stops with "Fund this agent with CREDIT first" and the run is given back.
  3. The model gets the job, today's date in UTC, the agent's own wallet address, the price of each tool, and the rule that tool results are untrusted data.
  4. It calls tools for up to 8 rounds. Each result is trimmed to 8 KB before it goes back to the model.
  5. The run stops before a step would pass the agent's cost cap, and always within 240 seconds.
  6. Steps are saved as they happen, then the report and the total cost.

Scheduled agents run hourly, every 6 hours or daily, checked every minute. If the owner has no runs left or the agent has no balance, the schedule skips that turn quietly and the agent shows why.

Models and tools

Models: Claude Sonnet 5.5, Claude Haiku 5.5, Claude Opus 5.5 and DeepSeek V4.1 Flash, through orbio's gateway. Tools, each priced by orbio:

Web search
0.0011 CREDIT a result, up to 5
Web read
0.0011 CREDIT a page
X reads
0.0055 CREDIT a post
Chain reads
about 0.000013 a balance read
Decisions
about 0.000018 a short one
Code sandbox
about 0.022 for 5 minutes, unused part released

The code sandbox is one E2B workspace per run, made on first use through orbio's infrastructure tools and always deleted when the run ends. Prices can change; receipts show what was charged.

What is stored

  • Each agent: its name, the job text, model, tools, schedule, cost cap, the public setting, its wallet address and its encrypted wallet key.
  • Each run: the trigger, times, every step (tool arguments trimmed, a short summary, the cost), the report, the total and any error. The last 50 runs per agent are listed.
  • Your pass: runs granted, used and left, and the burn transactions counted.
  • Sign-in: a session token in this browser's storage, valid 7 days. No email, no password.

Who sees receipts

Your agents and runs are visible only to the wallet that owns them. Turn on public receipts for an agent and its runs can be opened by anyone with the link at /run?id=..., with the agent's name, the steps, costs and report. The job text and the wallet key are never on a public page.

Limits

Agents per wallet
10
Name
60 characters
Job text
4,000 characters
Cost cap per run
0.01 to 5 CREDIT
Rounds per run
8
Time per run
240 seconds
Scheduled runs
2 started per minute across the site

Prelim runs

Until $ORUN launches, every wallet gets 3 prelim runs instead of a pass. They work like pass runs; compute is still paid by the agent's CREDIT. When $ORUN launches its contract address appears in the bar at the top of every page and the burn opens.

Deleting an agent

Deleting stops the schedule, removes the agent from your list and wipes its encrypted wallet key for good. Any CREDIT left on the agent's wallet can then never be used again: it was never movable, and with the key gone nothing can spend it. Its past receipts stay readable to you. Pause instead if you may want it back.