AI app builders
Use Ranla in Lovable, Replit, Bolt, Base44, v0, and similar AI builders.
Two kinds of install surface:
- Agent tools (MCP) — the builder’s AI can call Ranla while you develop (Replit one-click MCP; Cursor/Claude via MCP).
- App runtime (Secrets + code) — your deployed app sends mail via
RANLA_API_KEYandPOST /emails(or SMTP).
Most guides below cover (2). Replit also has a one-click path for (1).
Pick your builder
| Builder | Best for | Install surface |
|---|---|---|
| Lovable | React + Supabase apps, chat-driven features | Secrets + agent prompt (HTTP or SMTP) |
| Replit | Full-stack Replit Agent projects | MCP badge + Secrets + agent prompt |
| Bolt.new | Vite / React prototypes from chat | .env + agent prompt |
| Base44 | Base44 apps with optional custom email | When to use TX vs built-in mail |
| v0 | Next.js from Vercel v0 | Route Handler + Vercel env |
Before you paste a prompt
- Create a Ranla account and an API key (
rnl_…). - Store it as
RANLA_API_KEYin the builder’s secrets / env UI (server-side only). - For a first send before your domain verifies, use the sandbox rules in Quickstart and Agent skill notes.
Standard env var
RANLA_API_KEY=rnl_your_key_hereSome builders also accept STX_API_KEY — if their UI suggests that name, map it to the same rnl_… value. Prefer RANLA_API_KEY in generated code for consistency with our SDK and docs.
Reference
- Agent skill notes — integration defaults for AI agents
- OpenAPI — API contract
- Next.js — server-side send pattern
- Auth provider email — Clerk / Auth.js hooks
- Supabase Auth email — Send Email hook + Edge Function