Spending controls for OpenClaw
Set budgets, recipient rules, and approval thresholds for payments routed through the OpenClaw skill.
Connect OpenClaw to Conto
npx clawhub install contobash skills/CONTO_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 the skill checks a payment
Your payment tools must require Conto authorization before signing. An unrestricted signer can bypass the check.
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 checks your rules
Amount limits, categories, recipient trust, time windows, and velocity rules are checked together.
The result identifies the rule that applied.
The agent handles the decision
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.
Choose the rules for your agent
Rules that evaluate recipient, amount, category, timing, and approval state before execution.
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.
Recipient 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
An authorized owner or administrator can use an admin SDK key to manage policies. Keep that key separate from the spending agent.
/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.
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.