orchagent uses a credit-based billing system for platform usage. Add credits to your account and they’re consumed when you run agents.
How It Works
Sign up → Add credits → Run agents → Credits consumed per call
Adding Credits
Add prepaid credits to your account.
# Add $10 in credits (minimum $5)
orch billing add 10
# Check your balance
orch billing balance
# View transaction history
orch billing history
You can also add credits from the dashboard at Settings > Billing > Add Credits.
Credits are added via Stripe Checkout. They don’t expire and are refundable on request.
Plans & Execution Limits
Each plan includes daily execution allowances. Limits reset at midnight UTC.
| Free | Pro ($29/mo) | Team ($99/mo) | Enterprise |
|---|
| Tool executions/day | 50 | 500 | 2,000 | Custom |
| Agent executions/day | 5 | 50 | 200 | Custom |
| Tool timeout | 30s | 2 min | 5 min | 15 min |
| Agent timeout | 2 min | 5 min | 5 min | 15 min |
| Cron schedules | 2 | 20 | 100 | Unlimited |
| Private agents | 0 | 50 | Unlimited | Unlimited |
| Workspace members | 1 | 5 | 25 | Unlimited |
| Always-on services | 0 | 2 included | 5 included | Unlimited |
Tool vs Agent executions: “Tool” refers to code runtime agents (your code in a sandbox). “Agent” refers to managed loop agents (LLM tool-use loop). Direct LLM agents (prompt + schema only) count as tool executions.
Always-On Services
Pro and Team plans include always-on service slots. Additional services are $5/mo each. Services run on shared-CPU infrastructure with 512 MB RAM. See Services for details.
Running Agents
When you run an agent, the platform usage cost is deducted from your credit balance automatically. If your balance is insufficient, you’ll get a 402 Payment Required error.
Access Control
| Download Enabled | orch run (cloud, default) | orch run --local / install |
|---|
| OFF (default) | Anyone | Blocked — cloud only |
| ON | Anyone | Anyone |
New agents default to local-download enabled (allow_local_download=true). Authors can disable via --no-local-download flag or the web UI toggle to make agents server-only.
# Non-owner trying to run a server-only agent locally:
$ orch run --local acme/server-agent
Error: This agent is server-only and cannot be downloaded.
Use: orch run acme/server-agent@latest --data '{...}'
# Owner downloading their own agent (always works):
$ orch run --local acme/my-agent
✔ Downloaded acme/my-agent@latest
Service Usage
Always-on services consume compute time continuously while running. Service compute is metered separately from on-demand agent runs.
- Service instances are billed by runtime minutes
- Compute time counts toward your workspace usage
- Instance counts and concurrent service limits depend on your plan tier
- Paused or deleted services stop accruing compute time
Check service compute usage in the dashboard under your workspace usage page.
CLI Commands
| Command | Description |
|---|
orch billing balance | Check credit balance |
orch billing add <amount> | Add credits ($5 minimum) |
orch billing history | View transaction history |