Works with the wallets and credential providers merchants already use.
Verify First. Execute Second. Aiyo evaluates whether a consequential action should execute — combining identity, policy, authority, budget, approval, and (where relevant) verified on-rail payment settlement into a single Runtime Decision Point, issuing a portable authorization artifact any downstream execution surface can verify locally. Quadruple-agnostic across rail, wallet, identity, and agent by architectural design.
Aiyo's Runtime Decision Point governs execution, not payment. Payment is one possible condition for allowing an action to run — and where money is the consequence, the strongest one. The primitive is authorization at the moment before execution — for any consequential action, on any rail, by any actor.
AI agents transacting on behalf of users. Autonomous workflows orchestrating multi-step actions. Autonomous DevOps agents deploying code, procurement agents negotiating with suppliers, machine-to-machine commerce where no human approves every step. Consequential execution — monetary or otherwise — that needs to be gated by policy, budget, approval, and (where relevant) settlement evidence, not just by an identity check that passed.
Aiyo is the Economic Execution Authorization plane for these systems. We don't replace identity infrastructure, payment rails, or mandate-issuance providers — we compose above them, evaluate all the runtime conditions surrounding a specific action at the moment it's about to execute, and issue a portable authorization artifact any downstream surface can verify locally. Payment settlement is one possible evidence signal, and the strongest one where money is the consequence. Equally valid signals include an approved PO, an on-call human's approval, a budget check against an ERP, a code-review sign-off, or a webhook from an upstream system. The primitive is authorization at the moment before execution — not payment authorization narrowed to one shape.
Authorization inputs can originate from a human principal, another agent, a workflow policy, a budget authority, a machine capability, a payment settlement, a delegated authority, a risk engine, or an organizational policy. Aiyo does not assume a human is in the loop for every transaction — designed for machine-to-machine and agent-scale automation from day one.
Live across Open Payments (over Interledger), x402 with USDC on Base, plus Coinbase, Crossmint, Turnkey, and Privy adapters. The execution-authorization decision is the same primitive whether settlement is on a stablecoin rail, a traditional rail, or one that hasn't launched yet.
Aiyo never holds, accepts, or transmits funds. Wallets custody; Aiyo composes above whichever wallet the customer or agent already has — GateHub, Coinbase, Crossmint, MetaMask, Phantom, Turnkey, Privy, OWS-compliant agent wallets. Your integrators choose the wallet. Aiyo verifies authorization.
The consequential action Aiyo authorizes doesn't have to move money. A procurement agent negotiating with a supplier, a DevOps agent deploying code, a workflow agent invoking a paid tool, a compliance-sensitive database write — all fit the same primitive. Payment is one possible evidence signal, not the only one. Equally valid: an approved PO, a human approval, a budget check, a code-review sign-off, an SSO group membership, a webhook from an upstream system. The RDP evaluates whichever evidence the merchant's policy names.
Works with the wallets and credential providers merchants already use.
An agent, customer, or workflow submits an intent. Aiyo's Runtime Decision Point gathers whatever runtime state is available — identity, policy, budget, capability lifetime, prior approvals, payment settlement, risk signals, execution context, prior lineage — and evaluates a single ALLOW/DENY. On ALLOW, Aiyo issues a portable cryptographically-signed execution receipt any downstream execution surface can verify locally without round-tripping through Aiyo.
One Economic Execution Authorization plane across identity providers, mandate-issuance infrastructure, wallets, and settlement rails. No silent failures. No execution without a verifiable authorization artifact. No decision without a reconstructable lineage record.
Each layer answers a different question. Identity providers verify who the actor is. Authorization infrastructure verifies what the actor is allowed to do in principle. Aiyo — the Economic Execution Authorization plane — evaluates should this specific action execute right now, under these runtime conditions? Settlement rails move the value.
Aiyo composes with every layer above and below it. Aiyo does not compete with any of them. That's what makes actor-agnostic, rail-agnostic, wallet-agnostic architecturally honest rather than marketing copy.
We're shipping the Economic Execution Authorization plane for autonomous systems — Verify First. Execute Second. Join the early developer list to integrate against the SDK, get a walkthrough of the Runtime Decision Point, and see how portable authorization artifacts compose with the wallets, rails, and identity providers you already use.