OmniClaw CLI
A Python CLI and SDK for agent payments in USDC: transfers from Circle wallets and paid API calls over the x402 protocol
- 570 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The wallet private key and Circle keys open real accounts, and an agent with the `pay` command moves money on its own
- A mistake in the policy file or an oversized budget lets the agent spend more than you planned
- The agent and owner tokens live in the `.env` file and the policy file: a leak of either opens payment control
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/omniclawDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The wallet private key and Circle keys open real accounts, and an agent with the `pay` command moves money on its own
- A mistake in the policy file or an oversized budget lets the agent spend more than you planned
- The agent and owner tokens live in the `.env` file and the policy file: a leak of either opens payment control
This is third-party code. Review the repository files before installing.
What it does
OmniClaw helps agents and applications pay through checked channels without giving software unrestricted wallet authority. The core is called the Financial Policy Engine. It sets budgets, approval rules and recipient trust checks. An agent gets the `omniclaw-cli` command. The `can-pay` command checks whether paying a recipient is allowed, `inspect-x402` parses the terms of a paid endpoint, and `pay` makes the payment. For programs there is a Python SDK with the `OmniClaw().pay(...)` call. Payments go over two routes that the policy defines: `circle_transfer` for direct transfers from Circle Developer Wallet wallets, and x402 for paying paid APIs. For x402 the system itself picks a Circle Gateway nanopayment or the standard path, based on the seller's terms, the buyer's settings and the balance.
Who it is for. For developers of agent payment flows who need spending limits, an operations ledger and a check before paying for a paid API.
Good fit when
- An agent must pay for calls to a paid API over x402 within a budget set by the policy
- You need to check whether a recipient may be paid before money leaves
- You need to retry a payment request without a double charge: `pay` takes an idempotency key
- You want to simulate a payment and read the operations ledger without sending money
Not a fit when
- You need the recipient side: hosting paid endpoints and settlement with sellers are not part of the project core
- You need payments in rubles or through banks: the system works with the USDC stablecoin and Circle wallets
- You need a ready production service: the package is marked as alpha
- You are not ready to keep a wallet private key on your machine: the policy engine cannot start without it in any mode
Example request
Check whether paying the paid endpoint's address is allowed, inspect the x402 terms and pay 0.10 USDC with the idempotency key `job-123`.Limitations
You need Python 3.10 or newer and Docker: the policy engine runs as a separate server, and the CLI reaches it at the address from `OMNICLAW_SERVER_URL`, http://127.0.0.1:9091 in the example. The default hybrid mode needs Circle keys, a wallet private key, agent and owner tokens, plus a network and an RPC address. The `OMNICLAW_BUYER_MODE=x402` mode works without Circle keys, yet it still needs the wallet private key. The engine writes wallet state to `examples/agent/buyer/runtime/wallet-state.json`, next to the policy file. The last commit was made in May 2026.
How to disable. Stop the containers with `docker compose down` and remove the package with `pip uninstall omniclaw`. Delete the `.env` file with the keys and the `examples/agent/buyer/runtime` directory with wallet state by hand, and rotate the agent and owner tokens if they were saved anywhere.
FAQ
How do I install OmniClaw and start the policy engine?
Install the package with `pip install omniclaw`, copy `.env.example` to `.env` and fill in the keys. Copy `examples/agent/buyer/policy.example.json` to `examples/agent/buyer/runtime/policy.json` and edit the token in it to match `OMNICLAW_AGENT_TOKEN`. Then run docker compose with the `examples/agent/buyer/docker-compose.yml` file.
What does the `inspect-x402` command do?
It parses a paid API endpoint under the x402 standard and shows the payment terms before any money leaves. The payment itself is made by the `pay` command.
Why are there two tokens, for the agent and for the owner?
The agent token goes to the agent: with it the agent talks to the server through `OMNICLAW_TOKEN`, and it must match the token in the policy file. The owner token `OMNICLAW_OWNER_TOKEN` is set separately and plays no part in the agent examples. Do not hand it to the agent.
Does OmniClaw have an MCP server?
Yes, it sits in the `mcp_server` directory and exposes wallets, payments and ledger lookup as MCP tools. The author treats the CLI and SDK as the main way to work.
Can I try it first without real money?
Yes. The core can simulate payments, and the sample MCP server settings use the ARC-TESTNET test network. For first runs use such a network and small budgets in the policy.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI with an MCP server and a skill: the agent calls paid APIs while the user approves each HTTP 402 stablecoin payment with Touch ID
A skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
PayPal's official agent toolkit: an MCP server and SDK for invoices, orders, subscriptions, refunds and disputes
Skills for crypto agents: wallets, token swaps, onchain data and protocols such as Uniswap, Base, Alchemy and Zerion, each installed on its own
OKX's official toolkit for agents: an MCP server with 167 tools, a CLI and skills for market data, orders, bots and earn products on the OKX exchange
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| OmniClaw (this entry) | no | 570 | |
| Pay | yes | 1,799 | a CLI with an MCP server and a skill from the Solana Foundation: the user confirms each HTTP 402 stablecoin payment with Touch ID |
| Bankr Skills | no | 1,208 | a collection of skills for crypto agents: wallets, token swaps and onchain data |
README in short
The project page separates the core from the other parts: the core handles the buyer, the policy engine and payment routing, and the recipient side is not part of it. The quickstart goes from installing the package to a Docker Compose launch and a first payment.