Menu

Explorer & Settings

Tempo Explorer Submit Project
Back to all projects

omniclaw

by omnuron · Updated 7 days ago

The first agentic payment network: policy-controlled, gasless, and real money-ready. OmniClaw CLI + Financial Policy Engine let autonomous agents pay and earn safely at machine speed.

Open source alternative to:

In the AI payments ecosystem

omniclaw is a widely-adopted Python project in the AI payments / x402 ecosystem, focused on agent-economy, ai-agents, ai-payments, autonomous-agents. It currently has 575 GitHub stars and 43 forks, and sits alongside related tools like awesome-agent-economy, awesome-agent-economy, crewai-x402, awesome-molt-ecosystem, dna-x402, sample-agentic-serverless-payments.

Our take

OmniClaw calls itself the first agentic payment network: a CLI plus a Financial Policy Engine that lets autonomous agents pay and earn "safely at machine speed" — policy-controlled, gasless, and USDC-denominated.

The policy-engine framing is the right one. The hard question in agent payments is not "can the agent pay" (x402 solved that) but "what is the agent allowed to pay for, how much, and under whose authority". OmniClaw makes that policy layer the product, with MCP server support so agents can call it as a tool. Python-based, which suits AI-native teams.

Best for: operators who need enforceable spending rules around fleets of agents, not just a wallet.

README.md View on GitHub →

OmniClaw

Policy-controlled payment infrastructure for agent buyers.

OmniClaw core is focused on one job: letting agents and applications pay through controlled, auditable rails without giving software unrestricted wallet authority.

Product Boundary

Product Directory Owns
OmniClaw core src/omniclaw buyer SDK, policy engine, wallet/payment routing, x402 buyer execution, Gateway buyer readiness

Core should not include recipient-side paid endpoint hosting or settlement service code.

Core Capabilities

  • Financial Policy Engine for budgets, approvals, trust checks, and execution control
  • Python buyer SDK via OmniClaw().pay(...)
  • Agent buyer CLI via omniclaw-cli pay, inspect-x402, and can-pay
  • Circle Gateway buyer funding/readiness helpers
  • Standard x402 buyer flow for paying external paid endpoints
  • Ledger, idempotency, simulation, and payment-intent controls

Core Quickstart

Install:

pip install omniclaw

Start the policy engine:

cp .env.example .env
# Hybrid mode (default): leave OMNICLAW_BUYER_MODE=hybrid and fill CIRCLE_API_KEY,
# ENTITY_SECRET, OMNICLAW_PRIVATE_KEY, OMNICLAW_AGENT_TOKEN, OMNICLAW_OWNER_TOKEN,
# OMNICLAW_NETWORK, and OMNICLAW_RPC_URL.
# x402-only Gateway mode: set OMNICLAW_BUYER_MODE=x402, leave CIRCLE_API_KEY and
# ENTITY_SECRET empty unless you need optional Circle Gateway API helpers, and fill
# OMNICLAW_PRIVATE_KEY, OMNICLAW_AGENT_TOKEN, OMNICLAW_OWNER_TOKEN,
# OMNICLAW_NETWORK, and OMNICLAW_RPC_URL.

mkdir -p examples/agent/buyer/runtime
cp examples/agent/buyer/policy.example.json examples/agent/buyer/runtime/policy.json
# Edit examples/agent/buyer/runtime/policy.json so the token matches OMNICLAW_AGENT_TOKEN.

docker compose -f examples/agent/buyer/docker-compose.yml --env-file .env up --build

The policy file is stable configuration. Generated wallet state is written separately to examples/agent/buyer/runtime/wallet-state.json.

Buyer-facing policy rails are:

  • circle_transfer for direct Circle Developer Wallet transfers.
  • x402 for paid API payments. OmniClaw chooses Gateway nanopayment or the standard x402 payment path internally based on seller accepts, buyer config, and Gateway balance.

Configure the buyer CLI:

set -a; source .env; set +a
export OMNICLAW_SERVER_URL="http://127.0.0.1:9091"
export OMNICLAW_TOKEN="$OMNICLAW_AGENT_TOKEN"

Inspect and pay an x402 endpoint:

omniclaw-cli inspect-x402 --recipient "http://127.0.0.1:4023/compute?size=20"
omniclaw-cli pay --recipient "http://127.0.0.1:4023/compute?size=20" --amount 0.10 --idempotency-key job-123

Development

Run core tests:

uv run pytest
All Autonomous Agents projects →