Cowrie Research

laso-finance-primary-sources-2026-05-03

3 min read

Laso Finance primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Laso Finance whitepaper or litepaper surfaced.
  • The clearest current source of truth is the agent llms.txt, the public OpenAPI spec, the published SKILL doc, the AI plugin manifest, and the help-center corpus.
  • The project is best understood as a stablecoin-to-spend control plane for prepaid cards, gift cards, and push-to-card transfers rather than as a simple consumer card site.

Primary-source snapshots

1) Agent llms.txt

  • URL: https://agents.laso.finance/llms.txt
  • Key excerpt:
    • The file describes Laso Finance as a privacy-maximizing way to spend cryptocurrency with prepaid cards, gift cards, and push-to-card transfers.
    • It says the API is payment-gated with x402 and uses USDC on Base or Solana.
    • It documents the two-step card flow where /get-card returns a pending card_id and /get-card-data must be polled until the card is ready.

2) Public OpenAPI spec

  • URL: https://laso.finance/openapi.json
  • Key excerpt:
    • The OpenAPI info.description says all paywalled routes use x402 and that the caller replays the request with a payment header after receiving a 402 Payment Required response.
    • The spec names concrete Base and Solana recipient addresses and enumerates priced endpoints for auth, U.S. prepaid cards, international prepaid cards, gift cards, and push-to-card flows.
    • The /get-card docs explicitly say card details are not immediate and must be fetched later via /get-card-data.

3) Published SKILL doc

  • URL: https://laso.finance/SKILL.md
  • Key excerpt:
    • The SKILL file walks through agent usage for prepaid cards, gift cards, and debit-card disbursements using USDC on Base or Solana.
    • It strongly emphasizes the two-step card flow and warns that /get-card does not return card numbers, CVV, or expiry.
    • It also documents Locus and Sponge as example wallet/payment clients for handling x402 negotiation.

4) AI plugin manifest

  • URL: https://laso.finance/.well-known/ai-plugin.json
  • Key excerpt:
    • The manifest summarizes Laso as a payment API that accepts x402 crypto payments and returns prepaid cards, gift cards, and push-to-card transfers.
    • It enumerates a broader set of authenticated operational endpoints including merchant search, balance checks, withdrawals, card refresh, and dashboard login-link generation.
    • The manifest reinforces that the real product surface is an operational spend workflow, not only a one-shot card checkout.

5) Help center taxonomy

  • URL: https://help.laso.finance/
  • Key excerpt:
    • The help center exposes separate collections for international users, U.S./CAD users, PayPal and Venmo, deposits, and withdrawals.
    • That support surface suggests Laso is operating a live card/spending system with region-specific workflows and post-purchase operational complexity.

Working conclusion

Laso Finance is best cataloged as x402-gated stablecoin spending infrastructure. The deciding evidence in this pass was the combination of programmable USDC payment flows, delayed card-fulfillment retrieval, gift-card and push-to-card operations, and a broader authenticated support-and-operations layer around balances, withdrawals, merchant lookup, and dashboard access.

Graph View