> Lettrove docs 1.x · https://docs.lettrove.com/docs/app/ai

# AI and your allowance

## Where AI works

- **In the editor**, the assistant designs an email from a brief, or changes the one open from an
  instruction ("shorten the headline", "make the button say Reserve my seat"). Every change it makes
  is an ordinary edit in the email's history, with the assistant as its author, and can be undone.
- **Pictures** can be generated from a description, in the editor's Images panel, and land in your
  library like an upload.
- **Reading a PDF** of contacts: the model is asked only to read the table; every row then goes
  through the same checks as a CSV ([Bringing contacts in](/docs/app/audiences/import)).
- **Through the MCP server**, an assistant of your own (Claude, Cursor…) does the same things with
  its own model; see [MCP server](/docs/app/mcp).

## What the models see

What you give them: the brief, the email being edited, the picture description, the PDF. Never your
contact lists as a whole, your sending domains, your members or your keys. An assistant connected
through the MCP server sees what the tools return to it, which is what you could see yourself.

## The allowance

AI use on lettrove.com, and in the editor embedded inside your products, draws from **one allowance
per account** each period: the account that created the workspace holds it, and every workspace of
that account draws from the same one. **Settings → Usage** shows how much of the period's allowance
is used and how it divides between workspaces. When it is used up, AI features pause until it
resets; everything else keeps working.

For the embedded editor, picture generation can be switched off per project under
**Settings → Embed → AI**, so your users cannot draw from the allowance there.