Next, you write or paste your content into the editor. That can be a short text or a longer document with multiple sections. In most cases you start in the default language. Then you can use the built-in AI assistant and give concrete instructions, for example: “Write it factual and informal”, “make it shorter and clearer”, or “make it technical but easy to understand”. If needed, you let the AI correct or rephrase the text, review the result, and adjust until it fits your purpose.

If you often work on similar texts, templates are especially useful. You can create templates for recurring tasks, such as “shorter and clearer”, “more friendly”, “technical but understandable”, or different styles like “App Store” and “Website”. That makes your work more consistent and faster, and you do not have to rethink instructions every time.

Once your texts are complete, you can generate translations directly in BetterLocale Doc. The app uses an AI service of your choice. Currently supported are OpenAI, Google Gemini, Anthropic Claude, Perplexity AI, xAI Grok, and DeepL.

To use a provider, you need your own account there. You will receive an API token that enables access to the API and handles billing. You enter that token in BetterLocale Doc under Settings. It is stored only locally on your Mac and is not sent to us. Before your first translation run, you should use the connection test so you can verify token, endpoint, and network access without running a full translation.

Costs depend heavily on provider, model, and text volume. Many providers bill by “units” (for example tokens or characters). With ChatGPT / OpenAI the logic is typically:

A text is split into tokens (a single word can be multiple tokens depending on length and special characters).

Input (your text + context) and output (the generated translation) are billed separately.

So you pay both for what you send and for what you receive. To control costs, it usually helps to translate only fields that are missing or changed, and to keep context short and precise.

Create an AI API key and enter it in the app

To use automatic translations and the AI chat in the app, you need an API key from an AI provider.
Think of it as a personal access code: the provider can tell the request comes from you and bills usage to your account.

The app currently supports: OpenAI, Google Gemini, Anthropic Claude, Perplexity AI, xAI Grok, and DeepL.

Setup is very similar for all providers.

What you should know first
• API key = access code: You enter it in the app so it can send requests to the provider on your behalf.
• Costs are billed to you: The app sends the requests, but billing happens directly in your provider account.
• Billing is often required: Many providers only allow API requests after a payment method is added. Without billing you may get errors or very small limits.

Quick start: set up in 5 steps
1. Create an account or sign in

Go to your provider’s website and sign in.
2. Create an API key

Look for a section like API, Developer, Dashboard, or API Keys and create a new key there.
3. Copy the key and store it safely

Copy the key immediately and store it securely, ideally in a password manager.
Important: Many providers show the full key only once.
4. Enable billing/payment

Add a payment method or enable billing. Otherwise API requests often won’t work, or will be limited.
5. Enter the key in the app

Open the app → Settings → AI Providers → select a provider → paste the API key → Save

After that you can start translations and use the AI chat.

Provider guides (with direct links)

OpenAI (ChatGPT / OpenAI API)
1. Open the OpenAI dashboard:
https://platform.openai.com/
2. Create an API key:
https://platform.openai.com/settings/organization/api-keys
3. Set up billing/payment method:
https://platform.openai.com/settings/organization/billing/payment-methods

Tip: You often see the full key only once, later only partially.

Claude (Anthropic)
1. Open the Claude console:
https://platform.claude.com/
2. In the console, go to Account Settings and create an API key there.
3. Enable billing in the console so you can use the API.

Note: It previously used console.anthropic.com in some places; it is now moving to platform.claude.com and may redirect.

Gemini (Google)
1. Open Google AI Studio (API keys):
https://aistudio.google.com/app/apikey
2. If you don’t have a project yet, AI Studio often creates a default project automatically. Otherwise select/import a Google Cloud project.
3. Create and copy the API key.

Gemini API key documentation:
https://ai.google.dev/gemini-api/docs/api-key

PerplexityAI
1. Open account/settings:
https://www.perplexity.ai/account
2. In Settings, open the </> API tab and generate a key (“Generate API Key”).
3. Alternatively (depending on the UI), use the API portal:
https://www.perplexity.ai/account/api

Optional: API groups can be useful if you want separate keys (e.g. “Dev” and “Prod”).

xAI Grok
1. Open the xAI account/developer area:
https://x.ai/
2. In the developer/API area, create a new API key and copy it.
3. Enable billing/payment if required so API requests are not blocked.

Note: The exact location of the API key page may change depending on the xAI UI. Search for “API”, “Developers”, or “API Keys”.

DeepL
1. Open DeepL and sign in:
https://www.deepl.com/
2. Go to Account → API Keys & Limits.
3. Click Create key, enter a name, confirm, and copy the key.
DeepL help article:
https://support.deepl.com/hc/en-us/articles/360020695820-API-key-for-DeepL-API

Notes on costs and privacy
• Using AI APIs is usually paid and billed directly to your provider account, typically based on text volume (tokens).
• The app sends only the content you select (e.g. the texts to translate) plus your instruction to the provider.
• Your API key is stored only locally on your Mac in the Keychain and is not shared with third parties.

Security

Treat your API key like a password:
• Do not share it and do not copy it into public repos.
• If you think the key is compromised, disable it in the provider dashboard and create a new one.
• If you use multiple devices or projects, it’s best to use a separate key per device/project so you can revoke access without breaking everything.

Once your base text is ready, you start translating into the selected languages. You can choose which provider to use. You can also decide whether to test one language first or translate all languages at once. You can add notes for tone, audience, or purpose. You can regenerate translations at any time, for example after changing the source text or when you want to try a different provider.

The AI chat is designed to give you quick support without leaving your workflow. Use it to clarify questions, get wording alternatives, or generate multiple variants for different audiences or tones. It is also useful for structure, for example if you want help organizing a section or checking which points are still missing. The chat is great for brainstorming, and you can copy the best version straight into your document.

In BetterLocale you can define templates so you do not have to type recurring AI instructions over and over again. You set once how a text should sound, for example shorter, more factual, more friendly, more marketing-focused, or technical but easy to read. You can pick a template based on the task and apply it directly to text or translations. That saves time and keeps results more consistent. It is also helpful for teams because everyone can work with the same rules. You can create multiple templates, name them, and switch quickly depending on whether you are working on App Store text, documentation, or support. This turns “copy & paste” into a clean, repeatable workflow.