Agentonomy

CONTROL PLANE / CONTROLLED PILOT

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.

Explore Marketplace Download OPC
ONE NODEONE MCPCORE CONTROL

ILLUSTRATIVE TRANSACTION · NOT LIVE ACTIVITY

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 / CATALOG PREVIEW

Capabilities ready
for an Agent to find.

Loading current services…
A live selection, not the full directory. 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 generic

CODEX 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.

01 / CUSTODY

Keys remain in your wallet.

No seed phrases, private keys or MPC shares enter the Agent or Core.

02 / CONTROL

Core owns the decision.

Identity, mandate, policy, risk, funding and audit share one control plane.

03 / BUDGET

One request, one reservation.

Exact budgets are checked and reserved idempotently before execution.

04 / TRUTH

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.

C WALLET APP

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 ↗
OPC / MACOS + LINUX

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 ↗
USER CONTROL

Connecting is not paying.

Review wallet, network, limits and expiry yourself. Linking an Agent does not bind a wallet, sign, approve or enable payments.

MILESTONES & ROADMAP

From authorized payments
to agent commerce.

A connected service ecosystem. Working payment rails. Now bringing them together into everyday agent experiences.

Already built.

FOUNDATION / VALIDATION / INTEGRATION

Connected ecosystem

14,000+

Connected service entries

A connected catalog that gives agents a world of services to discover.

End-to-end validated

Marketplace

Discovery → payment → delivery

The full journey brought together: discover a service, pay within bounds, verify the result and receive delivery.

Explore the catalog ↗

Demo validated

Polymarket

Prediction market integration

A working prediction-market demo, bringing market discovery and trading workflows into the agent experience.

  1. One payment foundation.

    Identity, spending authority, budgets and execution connected through one Node and MCP.

    Unified architecture

  2. Real value, settled.

    Our first agent payment settled on Base mainnet, with independent verification and reconciliation.

    Mainnet settlement

  3. Wallet-native access.

    Native authorization connects wallet identity, signed spending limits and payment readiness in one flow.

    Native authorization

SERVICES. PAYMENTS. PREDICTION MARKETS. ONE SHARED FOUNDATION FOR AGENTS THAT ACT.

Where we go next.

BUILDING TOWARD AUTONOMY
  1. 01Now

    Make it everyday.

    Bring autonomous spending into everyday workflows, from wallet-native agents to your own agent environment.

    • Seamless wallet payment journeys
    • Purchases and address transfers
    • Clear controls. Reliable execution.
  2. 02Next

    Grow the network.

    Make the connected ecosystem easier to use and build on, from developer integration to repeatable service delivery.

    • Simpler developer and merchant onboarding
    • Better discovery and service quality
    • Broader production access
  3. 03Exploring

    Put more rules onchain.

    Extend verifiable spending boundaries with smart accounts and composable onchain permissions.

    • Onchain spending controls
    • Smart-account execution paths
    • EIP-7702 and delegated permissions

More autonomy. The same principle: authority stays with the user.

PERMISSIONED BY DESIGN

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 / x86_64

Linux

Validated on Ubuntu 24.04 (64-bit Intel / AMD). Requires Python 3.12.

Download for Linux

.tar.gz · r6 guided pilot

MACOS / APPLE SILICON

macOS

For Apple Silicon (M-series / arm64), not Intel Mac. Requires Python 3.12.

Download for Mac

.tar.gz · r6 guided pilot

CHECK / INSTALL / CONNECT

Before 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 guide

Download SHA256SUMS

Version 0.1.0-pilot.20260918-r6 · Agent-guided wallet setup · Wallet private keys stay in your wallet.

THE SERVICE LAYER IS OPENING

Let your Agent
act within the line.

Explore the Marketplace