> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/call/use-call/pay-in-the-console.md).

# Pay in the console

Pay an x402 API from the vAPI console with a browser wallet: check the live price for free, review the offer, sign one USDC payment, read the response.

Use the console when you want to try an API by hand with a browser wallet. You see the live offer before you sign, and vAPI never holds your funds or signs for you.

## Before you start

* A browser wallet that supports the offer's network: Base, Arc mainnet or Solana mainnet.
* USDC on that network in the wallet. The buyer does not pay settlement gas.

## Steps

1. Open [api.vapinetwork.ai/call](https://api.vapinetwork.ai/call) and open an API. A listed API lives at `/call/<slug>`. Look for the **Live x402** label: it means vAPI saw a valid 402 offer on its last check.
2. Fill in the request. The form shows the endpoint's inputs; switch to **JSON** when you would rather write the body yourself.
3. Choose **Check live price**. The console sends the unpaid request and shows the 402 offer: the amount, the network, the payee, and the exact request that will be paid. Nothing is paid yet.
4. Connect your wallet with the button at the top right if you have not already. The quote shows your balance check and the **Buyer cap**.
5. Choose **Pay … USDC and call**. On Base or Arc, your wallet shows an EIP-3009 typed-data authorization for exactly that amount to exactly that payee. On Solana, it shows a transaction to sign. Sign the payment.
6. The console sends the request again with the payment. The provider settles it onchain and answers. Choose **View result** to read the response and its settlement reference.

A wallet decline is harmless; nothing was sent. The quote expires with the offer's settlement window, so run **Check live price** again if you waited.

## What you approve and sign

| Network                                                    | Console | `vapi` CLI / local MCP (0.9.5)                        | Self-listing with a FeeSplitter |
| ---------------------------------------------------------- | ------- | ----------------------------------------------------- | ------------------------------- |
| Base mainnet (`eip155:8453`)                               | Yes     | Yes                                                   | Yes                             |
| Arc mainnet (`eip155:5042`)                                | Yes     | Yes, with Arc enabled                                 | No                              |
| Solana mainnet (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`) | Yes     | Search only; inspect/pay return `unsupported_network` | No                              |

On Base and Arc, the EIP-3009 signature names the amount, payee, token contract and validity window from the live offer, without a token approval transaction. On Solana, your wallet signs a transaction with compute-budget instructions, a USDC `TransferChecked` to the payee's associated token account, and a memo; the facilitator is the fee payer.

Listings with `upto` or `auth-capture` offers, or with a Stripe/Tempo MPP challenge, appear in the directory but cannot be paid in the console. See [Networks and schemes](/call/reference/networks-and-schemes.md).

## When the console hands off

Some APIs refuse requests from a browser (CORS). The page then shows **Buyer-local client required** with the exact `vapi pay` command for that request: endpoint, method, body and maximum price. For Base or Arc offers, run it in your terminal with the [CLI](/call/use-call/pay-with-vapi.md). Client 0.9.5 cannot pay Solana offers. vAPI does not relay the request for you.

## Uncertain settlements

If the provider's answer is lost after you signed, the console shows **Settlement may have happened** with whatever receipt data it received. It never retries on its own. Check your wallet's USDC balance or the settlement reference before you pay again. See [Receipts and retries](/call/use-call/receipts-and-retries.md).

## Next

* [Find APIs](/call/use-call/find-apis.md)
* [Pay with the CLI, MCP and SDK](/call/use-call/pay-with-vapi.md)
* [How Call works](/call/how-call-works.md)

Checked on 2026-10-15.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vapinetwork.ai/call/use-call/pay-in-the-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.