OwlPay
icon_en
🚀 Cut fees by 93%?

💸 Here’s a real-world example that actually did it with OwlPay Harbor 👀 👉

Unlock the case
Wallet Pro

OwlPay Agent Wallet Now Supports x402 Payments

July 17, 2026
cover image

TL;DR OwlPay Agent Wallet now settles x402-protected resources directly from the terminal. Run owlp pay <url>, and your agent pays the exact amount in USDC — network fee included — for any API, dataset, or OwlPay checkout link that returns an HTTP 402 challenge. Spending stays bounded with --max-amount, and every payment can be previewed before it goes out. This release also ships a handful of smaller reliability improvements, covered briefly at the end.

 

If you've been following along, you already know the gap: AI agents can write the code, book the meeting, draft the contract — but the moment a task requires payment, most of them still stop and hand it back to you. We covered why in AI Agent Wallets Explained.

That gap just got smaller.

OwlPay Agent Wallet is the CLI that gives AI agents a self-custody USDC wallet — the ability to hold funds, check balances, and send payments directly from the terminal, with your private keys never leaving your machine.

 

Pay the Web with One Command

As of v0.7.0, it ships a new command: owlp pay <url>. Point it at any x402-gated resource or OwlPay checkout link, and your agent settles it in USDC on the spot. You don't pre-load a card, register an account, or top up a balance with the recipient ahead of time. The agent hits the endpoint, receives the payment terms, signs, and retries — all in one call. The network fee is covered as part of the flow, so there's no separate step to fund gas before a payment can go through.

This is the same "pay-as-it-goes" pattern that's starting to show up across the AI agent ecosystem: an agent hits a paywalled endpoint, gets a 402 response, pays the exact amount up to a ceiling you set, and moves on. No keys bought up front. It pays for what it actually uses.

 

What Is x402?

x402 is an open protocol that repurposes the long-dormant HTTP 402 "Payment Required" status code. When a client — in this case, an AI agent — requests a resource that requires payment, the server responds with a 402 status and machine-readable payment terms: the amount, the accepted token, and the destination address. The client signs a payment for that exact amount and retries the request. No account creation, no stored card, no login flow — just a request, a price, and a signed payment.

For agents specifically, this matters because it removes the one step that used to require a human: authorizing payment. An agent that can read a 402 challenge and respond to it can complete a task end-to-end instead of pausing to ask you to log in somewhere and pay manually.

 

What This Means for You

A few concrete scenarios this unlocks:

  • Pay-per-call APIs. Your agent needs data from a paywalled endpoint — market data, a specialized query, a compute service. It pays the exact amount per call instead of requiring you to set up a subscription or pre-funded account.
  • Micropayments that were never worth the overhead. Say an endpoint charges $0.002 per request — a price too small to justify a credit card transaction or a subscription plan. With x402, the agent just pays it, request by request, without you setting up a billing relationship for a few tenths of a cent.
  • Bounded spending on autonomous runs. For any task where the agent might hit several paid endpoints in sequence, --max-amount keeps the total spend inside a ceiling you set in advance, so you're not reviewing every single micro-payment.

 

How to Use It

If you haven't installed Agent Wallet yet:

npm install -g @owlpay/owlp-cli

Full setup — creating a wallet, funding it, and connecting it to your agent — is covered in the Setup Guide. Once your wallet is set up, paying an x402-gated resource is one command:

 

owlp pay https://api.example.com/premium-data

By default, this previews the payment — amount, recipient, and network — before anything is sent. To review without committing at all, add --inspect for a read-only look. To execute immediately without a manual confirmation step, add --confirm. To cap what the agent is allowed to spend on a given run, set a ceiling with --max-amount.

Supported chains today: Ethereum, Stellar, and Solana. USDC is the supported settlement asset.

 

Also in This Release

A few smaller improvements shipped alongside x402 support, in v0.8.0:

  • Transfers and payments can now be made retry-safe with --idempotency-key — an accidental re-run returns the original result instead of moving funds twice.
  • Identity verification no longer waits indefinitely: after 30 minutes, the CLI hands back control and tells you how to check status later.
  • Error messages now point at the fix — most failures include the exact next command to run.

 

💡 Ready to let your agent pay for what it needs, on its own?

Install Button.png

 

FAQ

Does paying via x402 cost anything extra? 

The network fee is covered as part of the payment flow. You pay the amount the resource requests, in USDC.

Can I stop my agent from overspending? 

Yes. Use --max-amount to set a spending ceiling, or run without --confirm to preview every payment before it's sent. --inspect gives you a read-only look with no execution at all.

Do I need to set anything up in advance to use this? 

No new onboarding step — if your wallet is already set up per the Setup Guide, owlp pay works immediately.

 

 

 

 

©2026 OBOOK Holdings Inc. or its affiliates