A managed wallet can pay any x402 endpoint, not just Laso’s. See Pay an
endpoint.
When to use one
Good fit
Your agent runs somewhere you would rather not put a private key. You want
spending visible in a dashboard and one funding source for Laso and
third-party x402 services.
Poor fit
You need self-custody or a spending-policy engine richer than a per-payment
cap. Use Locus, Sponge, or Ampersend instead.
The calls
All four are Firebase callables athttps://laso.finance/<name>, authorized with Authorization: Bearer <id_token>. Arguments go in a data object; responses come back in a result object.
Setup
1
Sign in
Call
GET /auth as in the authentication guide
and save the id_token, refresh_token, and user_id. The examples
reference the token as $LASO_ID_TOKEN.2
Announce the connection
Call this right after sign-in, before anything else.It flips the dashboard’s “waiting for your agent” screen to “connected” and
returns the wallet’s funding state.
3
Read the wallet and fund it
wallet_address. If needs_funding is true,
ask your human for a deposit. If has_wallet is false, setup finishes at
laso.finance/agent/dashboard.Next steps
Pay an endpoint
Use
agentX402Pay for Laso routes and external x402 services.Guardrails
Pin the price, asset, network, and receiver before paying a third party.
Spend limit and activity
The human’s per-payment cap, and where every payment is recorded.
Bank accounts
Fund this wallet by bank transfer instead of on-chain.