Summary

OmniClaw provides a policy-controlled payment network designed for autonomous agents, enabling secure, gasless, and real-money transactions at machine speed. It addresses the critical security and operational challenges of using software agents for economic activities, offering a robust solution for programmatic payments where traditional wallets fall short due to key exposure risks and speed limitations.

How It Works

The system employs a two-part architecture: a Financial Policy Engine run by the owner, which securely holds private keys and enforces spending policies defined in policy.json, and a thin CLI client used by the agent. This separation ensures agents never access private keys, mitigating risks of wallet drainage. Payments are facilitated via Circle's Gateway using the EIP-3009 protocol, enabling gasless nanopayments with instant settlement, making high-frequency agent-to-agent commerce economically viable.

Quick Start & Requirements

Installation is straightforward via pip install omniclaw. Key requirements include setting several environment variables: OMNICLAW_PRIVATE_KEY (agent's signing key), OMNICLAW_AGENT_TOKEN (from policy.json), OMNICLAW_AGENT_POLICY_PATH (path to policy file), and CIRCLE_API_KEY. Network configuration (OMNICLAW_NETWORK, OMNICLAW_RPC_URL) is also necessary. The Financial Policy Engine is started with uvicorn omniclaw.agent.server:app --port 8080, and the CLI is configured using omniclaw-cli configure. Official documentation is available for agent setup, skills, features, and policy reference.

Highlighted Details

• Gasless Nanopayments: Utilizes Circle Gateway and EIP-3009 for sub-cent, instant, gas-free transactions, crucial for high-frequency agent commerce.
• Policy-Driven Security: Enforces granular spending limits and recipient controls via policy.json, safeguarding assets.
• Agentic Execution Layer: Separates sensitive key management from agent operations, preventing direct key exposure.
• Bidirectional Commerce: Supports agents acting as both payers and receivers, with the ability to expose services via the x402 protocol.

Maintenance & Community

The project is licensed under MIT by Omnuron AI. Specific details regarding community channels (e.g., Discord, Slack), active contributors, sponsorships, or a public roadmap are not detailed in the provided README.

Licensing & Compatibility

The project is released under the MIT license, which is permissive and generally allows for commercial use, modification, and distribution, including integration into closed-source applications.

Limitations & Caveats

The README indicates that the nanopayment functionality, specifically CAIP-2 derivation, is EVM-only. No other explicit limitations, alpha/beta status, or known bugs are mentioned.