- Summaries: automatically condense long text into clear takeaways.
- Chatbots and assistants: build conversational helpers into your app.
- Sentiment detection: understand user feedback at scale.
- Document Q&A: let users ask questions directly against your content.
- Creative generation: brainstorm ideas, draft copy, or expand concepts.
- Translation: serve users across languages.
- Image and document analysis: extract, summarize, and interpret key information from unstructured content.
- Workflow automation: handle repetitive or multi-step tasks inside your app.
- Semantic search and retrieval-augmented generation (RAG): search documents, knowledge bases, and content by meaning instead of exact keywords.
- Text-to-speech: turn text into spoken audio for voice narration, read-aloud, and audio-first experiences.
- Speech-to-text: transcribe voice notes, recordings, and meetings, and add voice input or dictation.
Enabling the built-in AI connector
Permission preferences
The default setting is Always allow, meaning the built-in AI connector can be used automatically in your projects. You can change your preference anytime from Connectors → App connectors → Lovable AI → Manage permissions. Choose between:- Always allow: Lovable automatically performs the action without asking for review or approval.
- Ask each time: Lovable asks for your approval whenever the action is needed. For example, if you want to add a chatbot, you can:
- Allow: enable the integration for the current project.
- Deny: decline the integration for this request. You may be asked again later.
- Adjust preferences: change the default behavior for future projects. This does not affect the current project.
- Never allow: Lovable blocks the action, informs you that AI is required, and instructs you to enable the built-in AI connector.
How it works
Lovable sets up the AI infrastructure for you:- API key: Lovable automatically generates and manages a
LOVABLE_API_KEYfor each project. You never need to create or provide it yourself. When a project is remixed, a fresh key is generated for the new project automatically. - Backend calls: AI calls run through a secure backend edge function that Lovable creates for you. Calls are never made directly from the browser, which keeps your credentials and prompts server-side.
- Streaming: the built-in AI connector supports streaming responses with server-sent events (SSE). Lovable uses streaming by default for chatbot and assistant features, so responses appear token by token rather than all at once.
Supported models for AI features in your app
Choosing a model
Not sure which to use? Describe what you want, and Lovable picks a model for you. This table shows where to start and when you might switch.Chat models
Chat models power conversational and text features: chatbots, assistants, summaries, document Q&A, translation, classification, and extraction. They range from fast, low-cost models for simple tasks to high-reasoning models for complex work. Ask Lovable to:- Build a chatbot or in-app assistant.
- Summarize long text, documents, or transcripts.
- Answer questions from your own content.
- Classify, extract, or translate text.
Faster responses with priority processing
If low latency matters, you can ask Lovable to use priority processing for a chat feature. Priority processing sends the request to OpenAI’s faster serving tier, so responses can come back more quickly during busy periods. Ask Lovable to:- Make an AI feature respond faster or with lower latency.
- Use priority processing for a chat feature.
Image models
Image models generate and edit images from text prompts, uploaded images, or both. Use them for visual assets, product mockups, marketing imagery, and in-app image editing. Ask Lovable to:- Generate images from a text description.
- Edit or restyle an uploaded image.
- Create product mockups or marketing visuals.
- Produce thumbnails or illustrations on demand.
Embedding models
Embedding models turn content into a format that can be searched by meaning instead of exact keywords. Use them for semantic search, retrieval-augmented generation (RAG), FAQ bots, document search, and knowledge bases. Ask Lovable to:- Build semantic search over uploaded documents.
- Create a FAQ bot that answers from your help content.
- Build a company knowledge base that finds relevant internal docs.
Text-to-speech models
Text-to-speech models turn text into natural-sounding spoken audio, so your app can read content aloud, narrate generated text, or talk back. Describe the voice feature you want, and Lovable wires up the backend and picks the right settings. Speech streams as it is generated by default, so playback can begin before the full clip is ready, and you can describe the tone or pacing you want in plain language (for example, “speak slowly and warmly”). Ask Lovable to:- Add a “read aloud” button that speaks an article or summary.
- Narrate AI-generated stories, lessons, or briefings.
- Turn a book or document into an audiobook.
- Build a voice assistant that responds with spoken audio.
Speech-to-text models
Speech-to-text models turn spoken audio into text, so people can talk to your app instead of typing and your app can work with what they said. Upload a voice note, call recording, or meeting audio, and the app transcribes it. Transcription streams as it is produced by default; because these features run in real time, very long recordings may time out, so transcribe long audio in segments. Ask Lovable to:- Build a meeting assistant that turns a recording into notes and action items.
- Add voice input or dictation so users can speak instead of type.
- Transcribe and search voice memos.
- Caption or subtitle uploaded audio.
Monitor AI usage and activity
Every project has an AI activity dashboard under Cloud → AI that shows what your app’s AI features cost and how they are performing. Use it to track spend, spot failed requests, and inspect individual AI calls. Lovable reads this activity too, so the agent can help you debug failures and improve your app’s AI features.- Total cost: the credits your app’s AI requests used in the selected range.
- Success rate: the percentage of requests that completed successfully.
- Avg. Duration: the average time a request took, in milliseconds.
Recent requests
The activity list shows recent AI requests, newest first. Each entry shows its status, a title taken from the request, when it ran, the model used, the input and output tokens, the credits it cost, and how long it took. When an AI action takes several steps, they appear together as a single run so you can see the cost of each step. Lovable always records this summary information for every AI request, so both the dashboard and the agent can see each call’s status, model, tokens, cost, and duration, even when the request content is not available.Let Lovable debug and improve your AI features
Give Lovable visibility into your app’s AI calls so it can help you make them better. When this is on, Lovable keeps the full request and response for each AI call, so the agent (and you) can open a request to see exactly what was sent and returned. The agent can use this to debug failures, refine your prompts and knowledge, and reduce cost and latency. Secrets are removed automatically, and details are kept for 90 days. It is on by default on Free and Pro. On Business and Enterprise it is off by default; enable it from the prompt on Cloud → AI, or from the AI activity setting in project settings. Changing it requires permission to edit the project. When it is off, the dashboard and the agent still see summary metrics (status, model, tokens, cost, and duration); they just cannot open a request to see its full content.Usage and pricing
Cancelled requests
If your app cancels an in-flight AI request, some usage may still be counted. The built-in AI connector waits briefly for the provider to finish and report final usage before closing the connection. Provider behavior on cancelled requests varies, so some usage may still be billed even if the app closes the connection before the response finishes.Workspace rate limits
To ensure reliable performance and fair access for all users, the built-in AI connector applies rate limits per workspace. These limits help maintain system stability, prevent abuse, control costs, and provide a consistent experience for everyone. Rate limits are measured in requests (model calls) per minute, not tokens per minute. If your app’s requests exceed the allowed rate, the server returns a429 Too Many Requests status code and the request will not be processed.
If your workspace runs out of credits, the server returns a 402 Payment Required status code. You can restore access by adding credits or enabling auto top-up in Settings → Plans & credit usage.
For more information, see Credits and usage.
Rate limits are more restrictive for free users, while paid plans include higher thresholds and greater flexibility.
- Free plan users: upgrade anytime to increase your limits.
- Paid plan users: contact Lovable Support if you need additional capacity.
FAQ
Is the built-in AI connector the same thing as the Lovable agent?
Is the built-in AI connector the same thing as the Lovable agent?
Do I need my own OpenAI, Google, or other provider API key?
Do I need my own OpenAI, Google, or other provider API key?
Where do AI calls run?
Where do AI calls run?
Can I choose which model my app uses?
Can I choose which model my app uses?
Can my app work with voice and audio?
Can my app work with voice and audio?
Can my app use Anthropic (Claude) models?
Can my app use Anthropic (Claude) models?
Can I use my own API key so AI usage doesn't consume my credits?
Can I use my own API key so AI usage doesn't consume my credits?
What happens if my workspace runs out of credits?
What happens if my workspace runs out of credits?
402 Payment Required status code. You can restore access by adding credits or enabling auto top-up in Settings → Plans & credit usage.For more information, see Credits and usage.