x402-compatible policy-bound payments for AI finance agents
Policy-bound payments for AI finance agents.
AI finance agents need paid APIs, market data, MCP tools, and tokenized-asset services, without holding unrestricted wallets.
Osmium is an on-chain SpendOps layer for AI finance agents on Robinhood Chain. Agents can request paid resources through x402-compatible flows, but funds only move when Osmium verifies the mandate, policy, receipt, context, budget, and replay rules.
Autonomous finance agents should not hold blank-check wallets.
A normal agent wallet creates a dangerous path:
LLM → private key → direct transfer → audit later
Osmium replaces that with a controlled settlement path:
Agent intent → SettlementRouter → Stylus PolicyEngine → allow / deny → settlement + receipt
Osmium proves whether an AI finance agent was allowed to pay before settlement:
approved merchant
allowed token
max transaction amount
rolling budget
mandate and context match
receipt hash present
replay protection
settlement result
If any check fails, no funds move.
The demo shows a TSLA market-data agent on Robinhood Chain Testnet.
The agent receives a narrow mandate: buy verified TSLA market data from an approved merchant, within a fixed amount and context.
The valid payment clears and settles on-chain. Unsafe attempts are denied before settlement:
replayed payment
unknown merchant
missing receipt
wrong context
over-limit payment
The Proofs tab exposes the latest judge matrix with a real on-chain settlement transaction, honest pre-settlement denials, raw JSON proofs, and explorer links.
Osmium is not only a demo app.
The submission includes both sides of the integration path:
external merchant integration
external agent integration
The Merchant Kit shows how a paid API, dataset, or MCP server can protect an endpoint with Osmium clearance:
no clearance → 402 Payment Required
valid Osmium receipt → data unlocks
missing receipt or wrong context → no unlock
The external agent example shows how builders can connect their own agent to a protected API. Osmium blocks fake proofs, wrong context, and missing receipts before any unlock.
Robinhood Chain Testnet:
PolicyEngine: 0x5e30622c7639aa5edc43313830c9a01341585728
SettlementRouter: 0x1CD04cbD3348D5fa28B30776902464752e878ac7
TSLA token used in live proof: 0xC9f9c86933092BbbfFF3CCb4b105A4A94bf3Bd4E
Robinhood Chain Testnet
Arbitrum Stylus
x402-compatible payment flow
Solidity SettlementRouter
Merchant Kit for external paid APIs
External agent example
policy authorization
settlement routing
ERC20 vault balance movement
replay protection
receipt and intent/context checks
allow/deny settlement decisions
AI agent runner
merchant API
x402-compatible HTTP challenge flow
frontend UI
proof artifact generation
Osmium is a production-oriented testnet deployment on Robinhood Chain Testnet.
The current system includes deployed core contracts, a live agent runner, a public Proofs matrix, a real on-chain TSLA settlement transaction, pre-settlement denial proofs, a standalone Merchant Kit integration test, an external agent example, security docs, and a deployment manifest.
The system is designed around explicit trust boundaries:
the LLM can request and explain actions, but cannot bypass policy checks
the PolicyEngine decides allow / deny
the SettlementRouter only moves funds after policy approval
unsafe attempts are denied before settlement
external merchants unlock data only after a valid Osmium receipt
external agents cannot bypass Osmium with fake proofs or wrong context
independent smart contract audit
expanded invariant and fuzz testing
multisig-controlled operational roles
published SDK package
self-serve merchant onboarding
production monitoring and incident response
expanded policy templates for tokenized-asset services
