Zambo guide

@x402/mcp Client

The @x402/mcp client lets an agent answer a 402 challenge from an MCP server and keep working.

How the client handles 402

The client needs to understand the payment challenge, use a wallet and network it supports, and resume the same request after payment. A service can still refuse or fail the underlying call, so inspect its response separately.

Check the current client and server documentation before enabling unattended payment.

Connecting to zambo.dev/mcp

Open the app picker, choose the client you use and follow the current connection steps there. The server URL is https://zambo.dev/mcp. Copying it does not connect the account by itself; confirm that your AI app shows the server as connected.

Ask the AI to use Zambo for one small task. If the app does not support remote MCP connections, use another supported client or try Zambo Chat.

What the receipt shows

The payment challenge describes the request and the amount due. A separate work receipt records the tool call and its returned status; it should not be treated as a wallet settlement confirmation.

Open the saved call at the receipt checker to inspect its recorded fields.

Try this prompt

Start with a small request. Change the details to match your task.

Use Zambo to explain the payment step before it happens, then show the receipt for the completed request.

FAQ

What is @x402/mcp client?

The @x402/mcp client lets an agent answer a 402 challenge from an MCP server and keep working.

What does a Zambo receipt show?

It shows the saved record and its available status. It does not prove that the output is correct or complete.

How do I try this with Zambo?

Check the payment request in your wallet, approve only a request you intend to pay, then review the resulting receipt.

Try it with your AI

Connect Zambo once, then ask your AI to use it for a real task.

Add Zambo to your AI Try Zambo Chat