OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Infrastructure

Omniclaw

Omniclaw is open-source payment infrastructure for agent buyers that combines a Python SDK, CLI, financial policy engine, wallet and payment routing, Circle Gateway buyer-readiness helpers, and x402 payment execution. It lets applications submit controlled payments to external paid endpoints while applying budgets, approvals, trust checks, simulation, ledger, payment-intent and idempotency controls.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Omniclaw — OpenViST project profile in Agent Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Omniclaw when an agent needs to pay external services and the payment flow must include policy controls, inspection, routing and transaction safeguards rather than unrestricted wallet authority.

Who it is for

  • Developers building autonomous agents that purchase paid APIs or external services.
  • Teams requiring budgets, approvals and trust checks around agent wallet activity.
  • Builders creating payment orchestration services with ledger and idempotency handling.

Documented uses

  • Configure policy-controlled payment execution for autonomous agents.
  • Inspect and pay compatible x402 endpoints through the buyer CLI.
  • Route buyer payments through Circle Gateway or standard x402 paths according to the configured flow.
  • Add repeatable transaction handling with payment intents and idempotency controls.
Before you choose

Requirements & limits

The project is public, open-source and MIT-licensed. The documented setup targets Linux, Docker, CLI and server environments. Payment configuration requires the relevant credentials, tokens, network and RPC settings described in the repository quickstart.

  • Buyer-side scope: core covers SDK, policy, routing and x402 execution, not recipient-side endpoint hosting or settlement.
  • Integration surface: builders can use the Python SDK via OmniClaw().pay(...) or the CLI commands pay, inspect-x402 and can-pay.
  • Control model: budgets, approvals, trust checks, simulation, ledger, payment intents and idempotency are included in the stated core capabilities.
  • Payment path: the buyer supports Circle transfer and x402 rails, with Gateway or standard x402 selection based on seller accepts, buyer configuration and Gateway balance.
  • Deployment: the quickstart uses Docker Compose, environment variables, a runtime policy file and a local server URL.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up the Omniclaw buyer service and inspect an x402 endpoint

Configure the documented buyer environment and inspect an external x402 endpoint before making a payment.

Before you start

  • Linux, Docker and Docker Compose
  • Python and pip for installing the package
  • A copied .env file with the required buyer mode, keys, tokens, network and RPC settings
  • A buyer policy file whose token matches OMNICLAW_AGENT_TOKEN
  • An external x402 endpoint

Steps

  1. Install the package with pip install omniclaw.

  2. Copy .env.example to .env and fill the variables required for the selected buyer mode.

  3. Copy the example buyer policy to examples/agent/buyer/runtime/policy.json and edit its token to match OMNICLAW_AGENT_TOKEN.

  4. Start the buyer service with Docker Compose, then set OMNICLAW_SERVER_URL and OMNICLAW_TOKEN for the CLI.

  5. Run omniclaw-cli inspect-x402 with the endpoint recipient before using the documented pay command.

Expected outcome

A configured buyer service can inspect the selected x402 endpoint through the documented CLI flow.

Guide limitations

  • The documented setup does not establish that a payment will succeed for a particular endpoint.
  • Payment routing depends on seller accepts, buyer configuration and Gateway balance.
  • The core repository does not include recipient-side paid endpoint hosting or settlement code.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
4 October 2026
Original website title
omnuron/omniclaw · Official homepage title · retained in its source language
How we review sourcesSuggest a correction