Pick your path
App builders
Tools that generate and host a full app from a prompt. Each guide shows where the builder keeps your API key and ships one prompt that scaffolds onboarding, deposits, and transaction lookup.- 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.
Coding assistants
Agents that work inside a codebase you already have. Each guide connects the docs MCP server and ships a prompt that adds Lumx to your existing project.- 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.
Prompt library
Prompts for one task each, which work with any coding agent. Use them once the basics run, or when you need a single capability rather than a starter app.- Sandbox quickstart — prove a deposit-to-stablecoin round trip before you write product code.
- Integrate off-ramps — pay out from a stablecoin balance to a local bank account.
- Integrate webhooks — receive signed events that survive retries and secret rotation.
- Migrate SWIFT wires — move international wires onto local payout rails.
The three integration surfaces
1
Copy-paste prompts
Builder and assistant guides ship a prompt that scaffolds the integration end-to-end: server routes for customer onboarding, on-ramp deposits, and transaction lookup, plus a starter UI. The prompt library adds one prompt per task, from payouts to migrations. Paste a prompt once and the agent does the rest.
Prompt fragment
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.See MCP server for setup in every supported host.
Claude Code
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 prompt above eventually compiles down to these calls.See Authentication for credentials and the API reference for endpoint shapes.
cURL
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