AxLabs has released Simple Agent Wallet (SAW), a command-line wallet designed to let AI agents autonomously pay for resources across multiple blockchains using the x402 payment protocol, with Neo X among the supported settlement chains. The open-source tool, currently at version 0.3.1, enables agents to inspect and execute payments without human intervention.

Conventional crypto wallets assume a human is present: browser extensions open popups and mobile apps require a tap to confirm. For AI agents operating programmatically, those interaction models introduce friction that effectively blocks autonomous commerce. SAW addresses the problem with a wallet built entirely around command-line workflows and scriptable payment flows.

Agent-Native Design

SAW's core workflow follows an inspect-then-pay pattern: the saw inspect command decodes an HTTP 402 payment requirement so an agent can evaluate the cost and terms, after which saw pay --confirm signs and executes the transaction. HTTP 402 is the "Payment Required" status code defined by the HTTP specification and long reserved for payment use cases, which is what allows payment terms to travel inside an ordinary web response. Private keys are stored locally in a permissions-locked wallet file, and secrets are accepted only through standard input or environment variables — never as CLI flags, which could leak into process lists or shell history.

AxLabs said in a post on X: "Agents shouldn't have to wait for a human to click 'confirm' to get work done."

The wallet also includes preflight balance checks, optional encryption, and native support for EIP-3009 and Permit2 token authorization flows on EVM chains.

Multi-Chain Support in a Single Wallet

SAW manages three blockchain families from one configuration file: EVM chains — including Neo X, Ethereum and Polygon, among others — as well as Solana and Hedera. A saw init wizard walks users through wallet creation or import for each family, while commands such as saw balance and saw transfer operate across all three. For an agent that needs to move value across ecosystems, this means balances and transfers can be handled through one scriptable interface instead of separate tooling per chain. Neo X is listed among the first supported EVM chains.

This multi-chain approach distinguishes SAW within a growing category of agent-focused wallet tooling that includes offerings from Coinbase, MetaMask and AWS, among others.

Completing the Ax402 Payment Stack

SAW serves as the client-side counterpart to Ax402, the payment gateway infrastructure AxLabs launched in July and deployed as a full production stack on Sept. 15. Ax402 provides the server-side protocol handling and settlement infrastructure, while SAW gives agents the tooling to participate as paying clients.

Together, the two components form a complete autonomous payment stack: an agent requests a resource, receives an HTTP 402 response with payment terms, uses SAW to settle the payment through Ax402, and receives the resource — all without a human in the loop. Because the handshake runs over ordinary HTTP, payment becomes one more step in a standard request-response cycle rather than a separate human-facing signing ceremony. SAW supports both exact per-request payments and batch settlement through payment channels.

Neo X Settlement

On Neo X, SAW settles payments in xGAS and USDC. xGAS, a programmable wrapped GAS token with signature-based authorization, was built specifically for x402 payment flows. The integration is already live in WhisperDark, Neo Global Development's AI agent dungeon-crawler game, where autonomous agents spend real xGAS to purchase in-game items without human approval.

Availability

SAW is open source under the Apache 2.0 license, with prebuilt binaries available for Linux, macOS (Intel and Apple Silicon) and Windows. It can also be installed as an agent skill via npm. Documentation is available at and the source code is hosted on GitHub at https://github.com/AxLabs/simple-agent-wallet. At version 0.3.1, the project remains pre-1.0 software, and its public documentation and codebase give integrators a direct way to review the implementation and track how the supported chain list evolves over time.