Skip to main content

Overview

Palmyr wraps Laso prepaid cards with the other things a real checkout asks for: an email inbox for the order confirmation and a phone number for SMS verification. Everything is a standard x402 endpoint paid per action in USDC on Base or Solana, so your agent uses the same wallet it already uses for Laso. Palmyr maintains an isolated Laso account per agent server-side — no Laso tokens to store or refresh, no Palmyr account or API key. The paying wallet owns each resource.

1. Set up your agent’s wallet

Your agent needs USDC to pay for Laso Finance API calls. The simplest option is a Laso-managed wallet, where Laso holds the key and settles payments for you. If you would rather your agent hold its own key, use one of the self-custody providers instead.
Laso custodies a Solana wallet for your account and pays x402 endpoints on your agent’s behalf, so the agent never builds a payment header or holds a private key. There is no provider signup, no API key, and no endpoint registration.Tell your agent:
All you need to do is fund it:
1

Let your agent sign in

Your agent calls GET /auth and gets its credentials. Nothing is needed from you.
2

Fund the wallet

Your agent reads its wallet address from getAgentWallet and shows it to you. Send USDC on Solana to that address. At least $5 covers a card order.
From there the agent calls agentX402Pay instead of paying endpoints directly. See the managed agent wallet guide for the full flow, including the per-payment guardrails for external endpoints.
A managed wallet can pay any x402 endpoint, not just Laso’s. Skip to step 2 below; the Locus endpoint-registration guide does not apply.
Already set up a wallet for Laso? Reuse it — nothing else to configure. Using Locus? Add the Palmyr endpoints below to your x402 endpoint allowlist, the same way you added the Laso ones.

2. Point your agent at the Palmyr endpoints

All paths are on https://palmyr.ai. Every paid endpoint returns a 402 with the exact price before anything is charged — send the request unpaid, read the total and pay.
To learn more, see how x402 works and Palmyr’s payments & x402 docs.

Cards

Email

Phone

The disposable inbox cannot be assigned a name. POST /email/temp returns a fresh, random address such as tmp-a1b2c3d4@mail.palmyr.ai. The inbox accepts mail for 24 hours, then automatically expires. Only the paying wallet can read it, and a single extend call adds another 7 days while it’s still active (handy when a shipment confirmation arrives weeks later).
Need a permanent address on your own domain instead? POST /email/inboxes provisions a persistent encrypted inbox.
Cards follow Laso’s USA prepaid card rules (US merchants, non-reloadable), and limits mirror Laso’s: max 6 cards per agent per rolling 24 hours. Failed card purchases are refunded automatically.

3. Run the checkout

Example prompts:
Point your agent at palmyr.ai/skill.md and it can figure the rest out on its own.

Use it over MCP

Palmyr also runs a hosted MCP server — point any MCP client at https://palmyr.ai/mcp. Relevant tools: The first call to a paid tool returns x402 payment instructions as a normal result; sign and call again with the payment argument.

Palmyr

Full documentation, pricing, and the agent skill file.