1. Set up your agent’s wallet
Your agent needs USDC to pay for Laso Finance API calls. If your agent does not already have a wallet, use a Laso-managed wallet. It is the whole setup: no provider signup, no private key to look after, no endpoint registration. The other tabs are for agents that already have a wallet with Locus, Sponge, or Ampersend. Those all work with every Laso endpoint, so there is nothing to migrate. If you are not already using one of them, you do not need one.- Laso-managed (start here)
- Locus
- Sponge
- Ampersend
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:From there the agent calls
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.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.
2. Authenticate with Laso Finance
Once your agent has a funded wallet, tell it to call the/auth endpoint to get API credentials. This endpoint is free: your agent proves wallet ownership with a SIGN-IN-WITH-X signature header. Tokens are returned for use in subsequent requests.
Tell your agent:
/auth response includes:
id_token— Bearer token for authenticated endpoints (like/get-card-data). Expires after ~1 hour.refresh_token— Use withPOST /auth(grant_type: "refresh_token") to get a newid_tokenwhen it expires.user_id— Your agent’s user ID (derived from wallet address).
3. Discover available endpoints
Your agent can discover everything it needs from these standard files:4. What your agent can do
Once authenticated, point your agent at any of these flows. Each guide covers the full happy path, parameters, response shape, and example agent prompts.Order a USA prepaid card
Best for U.S. online merchants. Two-step flow: provision the card, then poll
/get-card-data for the number, CVV, and expiry.Order an international prepaid card
Works with non-U.S. merchants and addresses. Stays
queued until an admin
fulfills the order (typically within 24 hours).Send money to a debit card
Push USDC out to any USD, EUR, or GBP debit card. The recipient completes a
short form at the returned
redemption_url.Order a gift card
Pick a brand from the multi-brand catalog with
/search-gift-cards, then
order by laso_server_id. Redemption details returned instantly.Open a bank account
Real US bank details for dollars in, and a payout address for dollars out.
Your agent runs the whole setup except identity verification.
Pay any x402 endpoint
With a Laso-managed wallet, your agent can settle 402 challenges on
external services too, with a price ceiling you pin per call.
Check merchant compatibility
Search the merchant database before ordering to confirm a retailer accepts
Laso prepaid cards.
Authenticate and refresh tokens
SIGN-IN-WITH-X, ID tokens, and OAuth2 refresh — the plumbing that backs
every paywalled call.
The USA prepaid card is U.S. only — issued in USD, usable at U.S. merchants
only, and physical goods must ship to a U.S. address. For international
purchases, use the international prepaid card instead.
Next steps
Making a purchase
Walk through ordering a card and buying something with your agent.