How to pay with crypto using AI: what it can do alone and where you still sign

If you ask an AI to pay in crypto, how much of the payment really happens on its own? The answer depends on one thing: who holds the key that signs the transfer.

This article is for people who already hold crypto and want to use an AI such as ChatGPT or Claude, or an AI agent, to make payments or to help with them.

It describes things as of 2 October 2026. Every statement about how the mechanisms work is limited to what we confirmed by reading official documentation and public responses between 20:19 and 21:10 Japan time that day.

The numbered steps were added on 3 October 2026. The steps for Setup 2 come from official documentation we read that day. We have not tried them ourselves.

By the end you will know three things:

what an AI can do automatically, and what still needs your own hands
where x402, a way for AI agents to pay per request, stands today
what you should never do when an AI is involved in a payment

We have not made a payment through this mechanism ourselves. We read the documentation and looked at the responses without paying, and nothing more.

You ask an AI to pay, and the payment does not go through

Suppose you tell a chat AI to pay an invoice in USDC. If the AI does not hold your wallet’s key, it cannot send anything. It can describe the steps, but the transfer itself stays with you.

The opposite case is worse. If you hand the key over, the AI is in a position to send the entire balance. A transfer sent to the wrong address on a blockchain cannot be taken back.

The difficulty is that the ground between “it can pay nothing” and “it can pay everything” is hard to see. Most of the practical answers sit in that middle ground.

A transfer needs a signature from a key

A crypto transfer is valid only when it is signed with the wallet’s private key. Whoever can produce that signature can move the assets, and nobody else can.

An AI model has no key of its own. So the ways of using AI for payments split in two, according to how the key is held.

Figure 1: the two ways to pay with AI. The difference is who holds the key that signs the transfer

Setup 1: only you hold the key. The AI helps organise the steps and check the details, and you send the payment yourself
Setup 2: an AI agent is given a small wallet of its own and pays only from what is inside it

In both setups, the key to the wallet you use every day is never given to the AI. That one rule decides how much can go wrong.

Setup 1: let the AI handle steps and checks, and send it yourself

This is the form you can use today. The money leaves your own wallet, under your own signature, and the AI works only with information that is already public.

What you need first

your own wallet, one that can send USDC. Only you hold its key
the USDC you will pay with, plus the network’s own currency for the transfer fee (gas). These steps are for people who already hold USDC
the payee’s instruction page: the page that states how to pay, the price and the supported networks

Eight steps: have the AI read, check the screens, sign it yourself

The example is paying in USDC for usage time on our Hype Trade, a service where you log in and view the records of your own Hyperliquid account.

The supported wallets and networks and the prices are on the page on how to pay with USDC (as of 3 October 2026). In this example you also need to sign up for an account.

open the payee’s instruction page. In the example, that is the page above
give the AI the page’s URL or its text, and have it lay the key points out in a table (prompt 1 below)
compare the AI’s table with the page itself. Where they differ, the page is what counts
log in as the page describes and connect your own wallet. The private key and the recovery phrase are not given to the AI
on the payment screen, choose a period and press “Buy”. In the example, the service sets the recipient
on the confirmation dialog and on your wallet’s screen, check the recipient, the network and the amount with your own eyes (prompt 2)
if they match, approve (sign) the transfer yourself. If they do not, stop without approving
confirm that it arrived, and keep a record (prompt 3). In the example, usage time is added once the transfer is confirmed on the blockchain

If the payment is not reflected, reopen the payment screen. If it still is not, contact the payee with the transaction hash (the signature on Solana) from your wallet history.

Where the service sets the recipient, as in the example, check in the browser’s address bar that the screen you are on belongs to the same site as the instruction page.

For a payment where you paste the recipient yourself, copy the address from the requester’s screen and compare its first and last few characters by eye.

What to keep in the record is under “Frequently asked questions”. Why a transfer cannot be taken back is under “Three things you should never do”.

Example prompts for the AI (usable as they are)

Prompt 1: have it read the instruction page

Read the following page and make a table of: the wallet needed, the supported networks, the price, the fees, and what happens if I make a mistake or the payment is not reflected.

Where the page does not say, write “not stated”. URL: (the instruction page’s URL)

Prompt 2: compare before sending

Compare the key points of the instruction page with what my wallet’s confirmation screen shows (currency USDC, network ____, amount ____), and list every mismatch.

Prompt 3: write up the record

Summarise this payment in one line, in this order: date and time, currency, amount, network, counterparty, transaction hash.

If the AI cannot open URLs, paste the page’s text. Read the confirmation screen yourself and type in what it shows.

What the AI is not given, and what you check with your own eyes

Not given: the private key, the recovery phrase (seed phrase), the wallet password
Checked with your own eyes: the recipient, the network and the amount, on the instruction page and on your wallet’s screen

Give the AI only information that is already public: addresses, amounts and network names. Nothing that can sign a transfer should enter the conversation.

An AI’s answer can be wrong. Do not approve a transfer on the strength of the AI’s summary alone.

Setup 2: give an AI agent a small wallet of its own

One mechanism that lets an AI agent pay by itself is x402. It uses the HTTP status 402, which means payment required, and settles each request in stablecoins.

The official site describes it as needing no account and no personal information. Coinbase’s documentation lays the flow out in nine steps, condensed here.

Figure 2: the x402 payment flow. The nine steps in Coinbase’s documentation, condensed to five (checked at 21:10 JST on 2 October 2026)

We also confirmed that it exists in practice. Calling CoinStats’s x402 endpoint without paying returned HTTP 402 with these terms: 0.001 USDC in USDC on Base, valid for 300 seconds (20:21 on 2 October).

Zerion publishes a price of 0.01 dollars per request. CoinGecko also offers x402 endpoints, with a notice that they are experimental and may change without warning.

So what we could confirm is very small payments per request, for things like fetching data. We did not confirm any case of it being used for shopping or for paying an invoice.

Three more things remain unconfirmed:

the usage figures shown on the official site. We could not match them against on-chain records, so we do not repeat them here
refunds and recurring payments. The documentation we read does not mention either
the exact signing method on the buyer’s side, and the network fee for each payment

If you use it, create a wallet only for the agent and fund it with a small amount you could afford to lose. The balance you put in becomes the ceiling on any loss.

Top it up by hand when it runs low. An agent that can refill itself from your main wallet no longer has a ceiling.

What you need first

a newly created wallet used only by the agent, kept apart from your everyday wallet
a small amount of USDC to move into it. These steps are for people who already hold USDC
the instruction page of a payee that accepts x402: its price and its supported networks

Eight steps: create a dedicated wallet, set a cap, move the remainder back

We have not tried these steps ourselves. They are the steps in the official documentation. We read it at 21:25 Japan time on 3 October 2026; the documents are named at the end of this article.

There are two example tools. The official x402 documentation shows a form in which the wallet’s private key is loaded from an environment variable and used to sign.

Coinbase’s Agentic Wallet CLI is used after authenticating by email. Its documentation says the private keys stay inside Coinbase’s infrastructure.

We are not suggesting one over the other. The commands below are the ones in the Agentic Wallet CLI documentation.

create the dedicated wallet: authenticate with npx awal auth login your-email and auth verify, then confirm with npx awal status
show its address with npx awal address and send a small amount of USDC to it yourself. The documentation says deposits are USDC on Base
confirm that the amount arrived with npx awal balance
set a cap per payment: add --max-amount to the payment command (1000000 is one dollar)
set the cap per day by how much you put in. The documentation we read does not describe a setting that limits the total for a day
give the agent only the ability to pay from this wallet. The key to your everyday wallet is not handed over
let it pay: npx awal x402 pay payee-URL --max-amount 100000 (an example with a cap of 0.10 dollars)
check how much was spent with npx awal balance, and when you are done, move the remainder back with npx awal send amount recipient

The tool in the official x402 documentation pays, by default, at most one dollar per payment, and only in assets pegged to the US dollar. The cap can be changed with maxAmountPerPayment.

If you use that form, the only key placed in the environment variable should be the dedicated wallet’s. The documentation says the result of the settlement can be read from the PAYMENT-RESPONSE header.

When moving money back, write the amount with a decimal point, such as 1.00. The documentation says a number above 100 with no decimals is treated as the smallest unit.

The overview of Agentic Wallet CLI says caps can be configured per transaction and per session. We could not confirm how to set them from the pages we read.

Three things you should never do

Paste a recovery phrase or private key into a chat: from that moment the key is no longer yours alone
Grant an approval with no limit: the other party can withdraw again and again, up to the amount you approved
Send without checking the recipient and the chain: USDC sent on the wrong chain does not arrive where you meant it to

The second point is about approve in the ERC-20 token standard. By specification, it lets the other party withdraw repeatedly up to the amount you set. Approve only what is needed.

A method that sends once per signature, EIP-3009, needs a new signature for every payment. We checked both specifications at 20:44 on 2 October.

The third point matters because the same token name exists on several chains. A request that names USDC without naming the chain is incomplete, and the AI should be asked to flag it.

What tends to work, and common pitfalls

✅ What tends to work

Make the AI the checker, not the sender. Have it compare the payment request with what your wallet’s confirmation screen shows.

A mismatch in chain, amount or address is easier to notice when something else reads both.

⚠️ Common pitfalls

Pasting a recipient or contract address that the AI gave you and sending to it.

An AI can produce an answer that looks right and is wrong. Addresses should come from the party you are paying.

Frequently asked questions

Q. If I ask ChatGPT or Claude to pay, will the money be sent?

A chat AI that holds no key cannot send it. A transfer needs a signature from whoever holds the key. We did not check the features of each AI product for this article.

Q. How much should I give an agent?

There is no single right answer. Choose an amount you would not miss if all of it were lost, and add more yourself when it runs down.

Q. How should I keep a record of a payment?

Keep the transaction hash, the date and time, the currency, the amount and the counterparty. For how to treat it in your accounts, ask a professional if you need to.

Summary

a transfer needs a key’s signature, so what an AI can do alone depends on who holds the key
the basic form: the AI organises the steps and checks before sending, and you sign
x402 exists. What we confirmed is data requests priced at 0.001 to 0.01 dollars each
never paste a recovery phrase, approve only what is needed, and check the recipient and chain

💡 To check your wallet balance and history before and after you pay

Crypto Wallet Viewer is a look-only screen: you register Ethereum and Solana addresses and it shows their balances and transfers. It never needs a private key.

It cannot make payments, and it does not display Base. Pricing starts at 2 USDC for one hour (as of 2 October 2026).

→ Check balances and transfers (wallet.microfund.co.jp)

Official documentation we referred to (checked at 21:25 JST on 3 October 2026; not linked)

x402, “Quickstart for Buyers”
https://docs.x402.org/getting-started/quickstart-for-buyers
Coinbase Developer Platform, “Agentic Wallet CLI”
https://docs.cdp.coinbase.com/agentic-wallet/cli/welcome
Coinbase Developer Platform, “Agentic Wallet CLI: Quickstart”
https://docs.cdp.coinbase.com/agentic-wallet/cli/quickstart
Coinbase Developer Platform, “Agentic Wallet CLI: Fund Wallet”
https://docs.cdp.coinbase.com/agentic-wallet/cli/skills/fund
Coinbase Developer Platform, “Agentic Wallet CLI: Pay for Service”
https://docs.cdp.coinbase.com/agentic-wallet/cli/skills/pay-for-service
Coinbase Developer Platform, “Agentic Wallet CLI: Send USDC”
https://docs.cdp.coinbase.com/agentic-wallet/cli/skills/send

This article explains how the mechanisms work. It is not a recommendation to buy or sell any asset or to use any service, and it makes no judgement about how the law applies.