Keys remain in your wallet.
No seed phrases, private keys or MPC shares enter the Agent or Core.
AGENTONOMY / FINANCIAL INFRASTRUCTURE
Financial infrastructure.For agents that act.
Set a signed spending boundary once. Core verifies identity, policy, budget and outcome while wallet keys stay yours.
ONE NODEONE MCPCORE CONTROL
An authorized route from an agent request to a verified service receipt
01REQUEST
Agent
Intent / route requested
02USER CONTROL
Wallet
Keys stay yours
03CHECKPOINT
Core
Policy / budget
04DELIVERY
Service
x402 endpoint
05RETURN PATH
Receipt
Audit / verified outcome
THE TRANSACTION PATH
Permission is a route,
not a blank check.
Every funded action crosses the same four checkpoints. The visual is illustrative; the control boundaries are the product.
Your Agent requests a service or an exact-address transfer through one MCP. It never receives your wallet private keys.
MARKETPLACE / EARLY CATALOG
Capabilities ready
for an Agent to find.
Loading current services…
Read-only preview. Discover first; payment remains controlled by Core.
DEVELOPER ENTRY / OPC
One command to connect
your Agent to the control plane.
OPC is a lightweight MCP Bridge for your own environment. It does not hold keys, choose a wallet or turn on payments.
TERMINAL / LOCALNO SECRET IN CONFIG
$ clink opc setup --agent codex
$ clink opc setup --agent genericCODEX Adds a secret-free clink_node MCP entry to the local Codex configuration.
GENERIC Prints a standard MCP configuration for another compatible Agent.
CORE / AUTHORITY & SECURITY
Four boundaries that
stay explicit.
Agentonomy coordinates permissioned value flow. It does not replace the wallet or pretend an external success response is proof.
Core owns the decision.
Identity, mandate, policy, risk, funding and audit share one control plane.
One request, one reservation.
Exact budgets are checked and reserved idempotently before execution.
Results are independently verified.
Payment and delivery are checked before Core records the outcome.
TWO ACCESS ROUTES / ONE CONTROL PLANE
Bring the Agent
you already use.
C wallet App and OPC connect to the same Core authority. Their user and device boundaries stay separate.
For users in the wallet App.
The App handles conversation and native confirmation. Core handles the account, spending authority and audit trail.
See the boundaries ↗For your own Agent environment.
Install the bridge, connect a compatible Agent and open the official authorization page when you choose to set a boundary.
Get the pilot client ↗Connecting is not paying.
Review wallet, network, limits and expiry yourself. Linking an Agent does not bind a wallet, sign, approve or enable payments.
PILOT STATUS / RELEASE BOUNDARIES
Deployed infrastructure
is not availability.
Mainnet contracts are deployed. Payments are not generally available; production acceptance and reconciliation remain explicit gates.
Base + Polygon contracts
Executor contracts are present on both mainnets. Deployment is a foundation, not an open payment path.
Low-value canaries
Wallet journeys, Marketplace purchase, reconciliation and rollback still move through controlled validation.
Release gates stay on
Real-money execution remains controlled until end-to-end acceptance is complete.
OPC CLIENT / CONTROLLED PILOT
Install the connection,
keep the wallet yours.
Packages include the OPC client, MCP Bridge and offline dependencies—not Python or an AI model. Verify before installing.
Linux
Validated on Ubuntu 24.04 (64-bit Intel / AMD). Requires Python 3.12.
Download for LinuxmacOS
For Apple Silicon (M-series / arm64), not Intel Mac. Requires Python 3.12.
Download for MacBefore you start
Compare the archive with the checksum, then install in a directory you own. This is a terminal client, not a signed desktop app.
Installation guideVersion 0.1.0-pilot.20260918-r6 · Agent-guided wallet setup · Wallet private keys stay in your wallet.
THE SERVICE LAYER IS OPENING