> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumx.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ship with AI

> Ship stablecoin payments in apps built with AI coding tools and agents. Lumx drops into any builder through copy-paste prompts, a docs MCP server, and a REST API.

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**](/guides/build-with-ai/lovable) — add Lumx to a Lovable app with Supabase-backed secrets.
* [**v0**](/guides/build-with-ai/v0) — generate a Next.js Lumx flow with Vercel env vars and server actions.
* [**Bolt.new**](/guides/build-with-ai/bolt) — wire Lumx into a Bolt.new StackBlitz project.
* [**Replit**](/guides/build-with-ai/replit) — ship with Replit Agent and Replit Secrets.
* [**Cursor**](/guides/build-with-ai/cursor) — pair Lumx's docs MCP server with Cursor's composer.
* [**Claude Code**](/guides/build-with-ai/claude-code) — drop Lumx into any codebase from the terminal.
* [**Codex**](/guides/build-with-ai/codex) — use OpenAI's CLI or cloud agent with the Lumx docs MCP.

## The three integration surfaces

<Steps>
  <Step title="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.

    ```text Prompt fragment theme={null}
    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.
    ```
  </Step>

  <Step title="Docs MCP server">
    The Lumx documentation runs as a [Model Context Protocol](https://modelcontextprotocol.io/) 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.

    ```bash Claude Code theme={null}
    claude mcp add --transport http lumx-docs https://docs.lumx.io/mcp
    ```

    See [MCP server](/developer/mcp-server) for setup in every supported host.
  </Step>

  <Step title="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.

    ```bash cURL theme={null}
    curl https://api-sandbox.lumx.io/customers \
      -H "Authorization: Bearer YOUR_API_KEY"
    ```

    See [Authentication](/get-started/authentication) for credentials and the API reference for endpoint shapes.
  </Step>
</Steps>

<Info>
  Get your API key from the [Lumx Dashboard](https://dashboard.lumx.io). Start in Sandbox — every transaction is simulated and no real money moves. Production access requires a call with our team — see [Environments](/get-started/environments).
</Info>

## Next steps

* [Create a customer](/guides/create-a-customer) — the first call in every Lumx integration
* [Use cases](/guides/use-cases/global-accounts) — global accounts, payroll, treasury, marketplaces, remittances
* [Webhooks](/developer/webhooks) — subscribe to transaction status changes instead of polling