Skip to main content
Add cross-border payments to any AI-built app — customer onboarding, on-ramp deposits, off-ramps, transfers, and webhooks — by pasting a prompt into your builder of choice. Lumx ships three surfaces that fit any AI workflow: copy-paste prompts tailored per builder, a docs MCP server for inline schema lookup, and the REST API itself.

​
Pick your builder

  • Lovable — add Lumx to a Lovable app with Supabase-backed secrets.
  • v0 — generate a Next.js Lumx flow with Vercel env vars and server actions.
  • Bolt.new — wire Lumx into a Bolt.new StackBlitz project.
  • Replit — ship with Replit Agent and Replit Secrets.
  • Cursor — pair Lumx’s docs MCP server with Cursor’s composer.
  • Claude Code — drop Lumx into any codebase from the terminal.
  • Codex — use OpenAI’s CLI or cloud agent with the Lumx docs MCP.

​
The three integration surfaces

1

Copy-paste prompts

Each builder page ships a prompt that scaffolds the integration end-to-end: server routes for customer onboarding, on-ramp deposits, and transaction lookup, plus a starter UI. Paste it once and the agent does the rest.
Prompt fragment
Build a stablecoin payments backend that uses the Lumx API.
Server routes to build:
  POST /api/customers, POST /api/on-ramp, GET /api/transactions/:id.
Read LUMX_API_KEY from environment variables. Never expose it
in client-side code.
2

Docs MCP server

The Lumx documentation runs as a Model Context Protocol server. Connect it to Claude Code, Cursor, VS Code, or Claude Web, and your agent pulls endpoint shapes, field definitions, and examples on demand — no copying schemas into the prompt.
Claude Code
claude mcp add --transport http lumx-docs https://docs.lumx.io/mcp
See MCP server for setup in every supported host.
3

REST API

For everything else — CI scripts, edge functions, server jobs, backends an AI tool doesn’t touch — call the Lumx REST API directly. Every builder integration above eventually compiles down to these calls.
cURL
curl https://api-sandbox.lumx.io/customers \
  -H "Authorization: Bearer YOUR_API_KEY"
See Authentication for credentials and the API reference for endpoint shapes.
Get your API key from the Lumx Dashboard. Start in Sandbox — every transaction is simulated and no real money moves. Production access requires a call with our team — see Environments.

​
Next steps

  • Create a customer — the first call in every Lumx integration
  • Use cases — global accounts, payroll, treasury, marketplaces, remittances
  • Webhooks — subscribe to transaction status changes instead of polling