Chio.
The trust network for autonomous commerce.
A shared proof system for agents, swarms, and autonomous organizations. Every agent-to-agent action carries signed authority, recursive delegation, lineage, selective disclosure, and settlement context across trust boundaries.
Four questions go unanswered
every time an agent acts in the world.
Agents are becoming economic actors. The infrastructure still assumes they're chatbots. Tap any card to fix it with Chio.
Who is this agent?
No standard for verifiable agent identity across organizational boundaries. No portable credentials.
What can it do?
Permissions scattered across configurations, not cryptographically verifiable or safely delegatable.
What did it cost?
No spending limits, no settlement, no budget enforcement fused into the execution path itself.
What happened?
No machine-verifiable proof of what was authorized, denied, or completed. Just logs and hope.
From implicit trust
to a settled machine economy.
Four stages. The infrastructure your agents need in order to act, get paid, and be held accountable.
Actions fire
into the void.
Agents call tools without identity, budgets, or proof. Every invocation is an implicit promise the infrastructure cannot keep.
Four stages. Eighteen guards.
One fail-closed pipeline.
Every tool invocation flows through four deterministic stages: token validation, the guard pipeline, an economic check, and a signed receipt. Stage two is itself a pipeline of 18 composable guards. Switch visualizations to explore the kernel shape that fits how you think.
Stages compose declaratively in a manifest file. Each is fail-closed. If any stage fails for any reason, the invocation is denied and a signed deny-receipt is still produced.
Every decision
produces evidence.
Signed, append-only, Merkle-committed. One artifact that serves as audit trail, billing ledger, and compliance record. No separate systems to reconcile.
Audit trail
Every allow, deny, cancel, and incomplete decision is recorded with full context. Query by agent, tool, capability, or time range.
Billing ledger
Receipts carry cost data. Settlement between organizations reduces to receipt reconciliation. No separate billing system to run.
Compliance record
Non-repudiable proof that policies were enforced. Export to SIEM systems via built-in Splunk HEC and Elasticsearch adapters.
Install once.
Command the whole stack.
Chio is a Rust runtime, SDKs in four languages, and a CLI that reaches every corner of the governance lifecycle: scaffold a project, wrap an MCP server, protect an HTTP API, issue passports, run the HA trust control plane.
# Install the Chio runtime, no Rust required $ curl -fsSL https://www.chio.world/install.sh | sh # Scaffold a runnable project with deny-by-default $ chio init my-project # Wrap any MCP server, unchanged $ chio mcp serve \ --preset code-agent \ --policy policy.yaml my-mcp-server
Scaffold
chio init drops in a runnable workspace with a deny-by-default policy, a sample server, and a smoke client.
Mediate
chio mcp serve or chio api protect wraps your tools. No code changes. Deny-closed with preset guards.
Audit
Receipts stream to your SIEM. chio receipt list queries them by agent, tool, budget, or time.
Internet of agents.
Incident response across org boundaries.
Meridian Labs has a sev-1 outage caused by a bad edge rule at their CDN provider, Stratos Networks. A commander agent orchestrates triage, then delegates a bounded fix to the provider. Six hops across two organizations, every tool call mediated, every capability attenuable, every decision signed.