Skip to main content

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

Metadata

Release files for omniclaw 0.0.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for omniclaw 0.0.8
File Size Uploaded Provenance
omniclaw-0.0.8.tar.gz 206.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for omniclaw 0.0.8
File Interpreter ABI Platform
omniclaw-0.0.8-py3-none-any.whl Python 3 none any Details

Total release size: 460.6 kB

Release files / omniclaw-0.0.8.tar.gz

Download URL omniclaw-0.0.8.tar.gz
Size 206.5 kB
Tags Source
SHA-256 checksum
How to use checksums
81cb332f50acfb5562d9fcd15673f14b3ffb2c7105dee9ba4d333e346e1cda18
BLAKE2b-256 checksum
How to use checksums
3f7055477bd7f4edb1f51411841b63af451e92a6761d585df10bf8a3b7def35c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / omniclaw-0.0.8-py3-none-any.whl

Download URL omniclaw-0.0.8-py3-none-any.whl
Size 254.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6d644517ebb072416b169bac3fa7750658443bd3bcf9ca4864b67fc948050242
BLAKE2b-256 checksum
How to use checksums
f8e921f7688880612886ddcaf6a72e41f5c3ad8f1749b2af47736f7fe9dc4718
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Security for omniclaw 0.0.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page