Developer Tools

SAW

Simple Agent Wallet: the official AxLabs wallet for x402 payments

Client

AxLabs (Self-funded)

Year

2026

Category

Agentic Infrastructure

Duration

Ongoing

SAW homepage: a focused CLI wallet for agents that pay over HTTP 402 / x402
SAW homepage: a focused CLI wallet for agents that pay over HTTP 402 / x402

Technology Stack

Go

x402 / HTTP 402

EVM (incl. Neo X)

Solana

Hedera

Permit2

Universal Commerce Protocol (UCP)

Go

EVM (incl. Neo X)

Hedera

Universal Commerce Protocol (UCP)

x402 / HTTP 402

Solana

Permit2

Overview

SAW (Simple Agent Wallet) is a focused CLI wallet built for agents that pay over HTTP 402 / x402. It supports EVM chains, Solana and Hedera in a single wallet file, keeps keys local, never takes secrets on the CLI, and speaks x402 exact and batch-settlement without scraping truncated payment headers.

SAW is the official AxLabs agent wallet for x402 payments. It is purpose-built for autonomous agent payment flows: inspect a paid endpoint, confirm the details, and pay, with headers staying inside the tool instead of being passed through shell history or truncated by curl output.

Agents can read the docs too: agents.md and llms.txt

SAW binaries for Linux, macOS and Windows, and the agent skill install command
SAW documentation: install and init commands

The Problem

Generic wallets and raw curl-based payment flows break down for agents:

  • curl truncates long base64 payment headers: agents scrape PAYMENT-REQUIRED headers from tool output and lose data, producing failed or incorrect payments.

  • Secrets in CLI flags leak into shell history: passing private keys or mnemonics as arguments is a credential exposure risk agents cannot afford.

  • No standard way to inspect before paying: agents need to see amount, asset, network, payTo, scheme and feePayer before committing, but generic tools do not separate inspection from execution.

  • Multi-chain means multi-tool: supporting EVM, Solana and Hedera usually means juggling different wallets, key formats and RPC setups instead of one consistent interface.

  • Token approvals are a separate headache: ERC-20 flows with Permit2 require a pre-approval step that most wallet CLIs do not model cleanly for agent workflows.

  • Batch settlement needs session state: x402 batch settlement requires channel management and refund flows that generic wallets do not expose.

For an autonomous agent, these are not edge cases. They are the normal operating conditions.

How It Works

Inspect → Confirm → Pay

SAW keeps the payment flow explicit and auditable: inspect, confirm, pay.

  1. Init: saw init runs an interactive TTY wizard, or saw init create / saw init import set up a wallet for a specific family (EVM, Solana, Hedera). Secrets come from stdin or prompts only, never CLI flags. The wallet lives at ~/.config/saw/wallet.json (mode 0600), overridable via SAW_CONFIG_DIR, with optional encryption via --encrypt / SAW_PASSWORD.

  2. Inspect: saw inspect <url> fetches and decodes the 402 accepts[] from a paid endpoint. The agent sees amount, asset, network, payTo, scheme and feePayer without paying yet. This is the step that avoids header scraping and truncation.

  3. Approve (when needed): for EVM permit2 flows where allowance may be missing, saw approve-permit2 --chain-id <N> --token 0x... --confirm handles the ERC-20 approval in one command.

  4. Pay: saw pay <url> --confirm signs and retries with the same method and body used in inspect. --confirm is required: there are no loops without user confirmation. Flags such as --scheme, --network, --asset and --asset-transfer-method give full control over the payment.

  5. Batch settlement and refunds: saw channels lists sessions and saw refund <url> --confirm issues a refund, optionally for a specific --amount. Sessions persist under ~/.config/saw/channels/.

Commands

  • saw init / create / import / status: multi-family wallet lifecycle

  • saw address: print configured addresses

  • saw balance: native and token balances

  • saw inspect <url>: decode 402 accepts[]

  • saw pay <url> --confirm: sign and retry

  • saw channels / saw refund: batch-settlement sessions

  • saw approve-permit2 --confirm: ERC-20 approve for Permit2

  • saw transfer --confirm: EVM, Solana and Hedera transfers

  • saw call / saw abi encode: EVM only

Security Rules

  • Never print private keys or mnemonics after init.

  • Never invent header names: use saw inspect / saw pay output.

  • Never pass PAYMENT-REQUIRED / PAYMENT-SIGNATURE tokens as CLI args.

  • Discovery of merchant URLs comes from the user or the 402 body.

  • If the selected accept family has no credentials, run saw init for that family first.

Agent Integration

Agent skill: npx skills add AxLabs/simple-agent-wallet --skill saw -g -y installs the skill for Cursor and compatible skill hosts.

Plain text docs: agents.md and llms.txt at the site root give agents the same content in a machine-friendly format.

UCP integration: SAW integrates with the Universal Commerce Protocol for full agentic commerce flows: discovery, cart, checkout and payment. The flow is saw inspect to verify the request, then saw pay --confirm to execute.

Supported Chains

  • EVM: eip155:* chains including Ethereum, Base, Polygon, Optimism, Neo X and all other EVM chains.

  • Solana: mainnet and testnet via SAW_SOLANA_RPC.

  • Hedera: via SAW_HEDERA_NETWORK (testnet, mainnet, previewnet).

RPC endpoints are configured in ~/.config/saw/config.env.

Distribution

SAW is distributed as cross-platform binaries (Linux amd64/arm64, macOS Apple Silicon/Intel, Windows amd64/arm64) from GitHub Releases, and can be built from source with make build && make install.

What Makes It Different

  • Built for agents, not adapted from a human wallet: the inspect → confirm → pay flow, stdin-only secrets and header handling are designed around how agents actually operate.

  • Headers stay inside the tool: saw inspect and saw pay fetch and sign 402 payment headers directly, eliminating the truncation and scraping problems of curl-based workflows.

  • One wallet, three families: EVM, Solana and Hedera in a single wallet.json, with a consistent CLI across all of them.

  • x402 native: first-class support for exact and batch-settlement schemes, plus approve-permit2 for token flows.

  • Agent-ready distribution: skill, agents.md and llms.txt mean agents can discover and use SAW without human setup beyond installing the binary.

  • UCP-native agentic commerce: integrates with the Universal Commerce Protocol for end-to-end flows from discovery through payment.

Impact

With SAW, agent builders and operators get:

  • Real autonomy: agents can inspect, confirm and pay for resources without a human clicking through a browser wallet.

  • No credential leaks: secrets via stdin or prompts only, never CLI flags, never shell history.

  • One tool for multi-chain payments: EVM, Solana and Hedera from the same binary and wallet file.

  • Correct payments by construction: inspect before pay, headers inside the tool, confirmation required, no automated retry loops.

  • Agent discovery built in: skill and plain-text docs mean agents find and use SAW without custom glue code.

  • Full agentic commerce with UCP: discovery, cart, checkout and payment in one flow, with SAW handling the payment leg.

Conclusion

SAW is what a wallet looks like when the primary user is an agent. It keeps secrets out of CLI arguments, avoids the header truncation that breaks curl-based payment scraping, and gives agents a clean inspect → confirm → pay flow across EVM, Solana and Hedera. It is the official AxLabs wallet for x402 and integrates with the Universal Commerce Protocol for full agentic commerce.

As more workloads shift from human-driven to agent-driven, the tools those agents use to pay need to be as purpose-built as the agents themselves. SAW is that tool for x402 payments.

© Made with

♥️

in 🇨🇭 Switzerland

© Made with

♥️

in 🇨🇭 Switzerland

© Made with

♥️

in 🇨🇭 Switzerland