Connect
Sign in, approve Orbio OAuth, and encrypt the gateway key inside your isolated tenant.
The control plane for Orbio-powered agents
Connect Orbio.
Control every
agent.
Every user connects an isolated Orbio account. Every agent gets its own identity, budget, model rules, and kill switch. Gateway keys stay encrypted; prompts and responses stay out of the ledger.
Your Orbio
1
encrypted tenant
A1research
A2coding
A3ops
Guard
active
active
LiveOrbio model catalogue and policy checks
Codexproduction shell and file tool lifecycle
Atomicagent and shared project budget reservations
Privatemetadata-only request records
The missing layer
Orbio powers the agent.
Guard makes it operable.
Each user gets a recoverable Guard tenant. OAuth connects their own Orbio account. A private Durable Object isolates their keys, agents, budgets, and metadata-only activity.
Issue
Create separate agent tokens with daily budgets, request ceilings, and model policies.
Run
Use production-verified Codex or a supported inference API while Guard reserves and reconciles Orbio spend. Other client tool lifecycles remain unverified.
Built and verified on Orbio
Not another agent wrapper.
Control for text and tool agents.
live verification · secrets removed
$ codex exec "Use pwd, then report the directory"
model: gpt-5.6-sol
provider: orbio_guard
exec /bin/zsh -lc pwd
✓ /Users/developer/project
Codex: /Users/developer/projectReal Codex. GPT-5.6 Sol text and shell-tool turns completed through Guard.
Real accounting. Final usage confirms spend; incomplete requests keep a clearly labeled conservative bound.
Real isolation. Each tenant has an isolated encrypted Orbio connection, agents, budgets, and audit records.
Real enforcement. Model, request, budget, pause, and disable decisions happen before gateway forwarding.
Built on Orbio MCP