Policy-checked payments for OpenClaw agents
Connect an OpenClaw agent to Conto so payment requests can be evaluated before execution. Conto checks budgets, recipient rules, and approval thresholds before funds move, then records the result.
Connect OpenClaw to Conto
1. Install the skill
npx clawhub install conto
bash skills/conto/conto-check.sh setup "my-openclaw-agent" "0xYourWalletAddress" EVM 42431CONTO_SDK_KEY to your OpenClaw config. Setup guide3. Try a payment. Ask your agent to make a sandbox payment. Conto returns the policy decision before funds can move.
How OpenClaw payment requests move through Conto
The Conto skill sends each payment request to Conto and returns an approve, deny, or review-needed decision.
Agent requests a payment
Your OpenClaw agent calls a payment tool. The Conto skill sends the request to Conto first.
Works with x402 micropayments and direct transfers.
Conto evaluates context
Amount limits, categories, recipient trust, time windows, and velocity rules are checked together.
A decision and its reasons, typically within a second.
The payment clears or pauses
Approved payments continue. Denied payments return the violation. High-value requests route to a reviewer with context attached.
A complete payment record stays in Conto.
Payment controls your wallet cannot provide alone
Rules that evaluate recipient, amount, category, timing, and approval state.
Spend limits
Set per-payment, daily, weekly, and monthly caps scoped by agent or project.
Category policy
Keep agent spend inside approved categories such as API providers, cloud services, or vendors.
Counterparty rules
Allow approved recipients, block risky addresses, or route unknown vendors to review.
Time windows
Keep payments inside business hours, weekdays, or custom schedules when a workflow needs boundaries.
x402/MPP controls
Cap per-request cost, daily service spend, and approved endpoints for paid API or inference calls.
Approval routing
Send high-value requests to reviewers with the agent, recipient, and policy context attached.
Manage Conto policies from OpenClaw
With an admin SDK key, your agent can create, inspect, and update policy through natural language.
/conto create a policy that limits each transaction to 200 pathUSD/conto only allow API_PROVIDER and CLOUD categories/conto block address <address> from receiving payments/conto require approval for payments over 500 pathUSD/conto list my policiesPayment activity for OpenClaw agents
Review requests, policy results, denied payments, and alerts for OpenClaw agents from the Conto workspace.
- Agent
- procurement-agent
- Category
- compute
- Policy
- compute-spend-v3
- Tx
- 0x9f2c…a8e1
Reconciliation
- Requested09:14:02
- Policy approved09:14:02
- Executed onchain09:14:05
- Settled09:14:11
- Reconciled09:15:00
Documentation and references
ClawHub
Install via ClawHub. View source and version history.
Agent skill docs
Install the skill, configure keys, create policies, and test payments.
Policy reference
Amount limits, category rules, recipient policy, approval routing, and evaluation examples.
SDK authentication
Standard vs admin keys, scopes, and API reference.
Bring Conto payment policy into OpenClaw
Install the skill, connect an SDK key, and test on Tempo Testnet.