Skip to main content

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 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 third-party provider signup 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, or USDC on Base to its Base address. Both land in the same balance. 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.

2. Fund the wallet

A wallet with no USDC in it cannot pay for anything, so this is the step that actually turns the API on. Ask your agent for its wallet address, then send it USDC.
  • Laso-managed wallet: the agent reads its addresses from getAgentWallet and shows them to you. Send USDC on Solana or USDC on Base to the matching address.
  • Self-custody wallet (Locus, Sponge, Ampersend): send USDC on Base or Solana to the address on the provider’s dashboard.
At least $5 covers a first card order, plus a little headroom for the paid endpoints your agent calls along the way. Funds are yours the whole time: anything left over can be pulled back out with POST /withdraw.

3. Authenticate with Laso Finance

How your agent gets API credentials depends on which wallet it uses. Both calls are free. Laso-managed wallet. Your agent holds a Laso agent API key (it starts with lasoak_), not a private key, so it cannot sign in with a wallet signature. It presents the key to agentAuth instead. The setup helper in SKILL.md does this for it. Tell your agent:
Self-custody wallet (Locus, Sponge, Ampersend). Your agent proves wallet ownership by calling GET /auth with a SIGN-IN-WITH-X signature header. Tell your agent:
Either response includes:
  • id_token: Bearer token for authenticated endpoints (like /get-card-data). Expires after ~1 hour.
  • refresh_token: Use with POST /auth (grant_type: "refresh_token") to get a new id_token when it expires.
  • user_id: Your agent’s opaque account id. It is not a deposit address.
The managed wallet guide and the authentication guide cover each path in full.
Your agent should store these credentials and reuse them across requests. /auth and /get-card return fresh tokens — always save them. When the id_token expires, call POST /auth with grant_type: "refresh_token" and the refresh_token — no payment needed.

4. Order the first card

With a funded wallet and credentials in hand, your agent can order a prepaid card. GET /get-card is paywalled, so the x402 client (or agentX402Pay on a Laso-managed wallet) settles the USDC payment and the request goes through. Tell your agent:
The order comes back immediately with a card_id and status: "pending". The number, CVV, and expiry take ~7-10 seconds to be issued, which is what the poll is for. The USA card is issued in USD and works at U.S. merchants.
The USA card is non-reloadable, so order for the exact checkout total when you know it. Nothing is stranded if you do not: leftover balance stays spendable at another merchant. For recurring spend, use a reloadable card instead.
Your agent can discover the rest of the API on its own from the files listed under agent discovery, starting with https://laso.finance/SKILL.md.

Next

Making a purchase

Buy something online with the card your agent just ordered.
Managing multiple agents or need spending guardrails? 1Claw’s Payment Card Vault wraps the Laso API with per-agent spending limits, automatic PAN redaction, and audit-logged reveals — so your agents can order cards without ever seeing the full card number.