Bring your own keys

Add an Anthropic, OpenAI, Google, xAI, or Ollama Cloud API key in app Settings and Jobably’s AI operations run against your key instead of platform quotas.

Keys are checked before they’re saved

When you add a key, Jobably first asks the provider to confirm it works. A key the provider rejects is never stored — you’ll see a clear message so you can fix a typo or generate a fresh key. If the provider can’t be reached at that moment, the key is saved anyway and simply used on your next operation.

How keys are stored

Each key is sealed with bank-grade encryption the moment it arrives, and keys are write-only: Jobably can use a key to run your work, show you its last four characters so you know which one it is, or delete it — but nothing, including our own screens and logs, can ever display a key back. Automated tests verify this on every release.

Scope of use

Your keys are used solely to run your workloads — scoring your postings, tailoring your resumes, building your prep packets. Costs accrue on your provider account under your agreement with them.

Removing a key

Instant, from Settings. In-flight work falls back to platform models within your plan quotas.

Pick your tailoring model

With a key stored, Settings → Preferences → Resume tailoring model lets you run tailoring (and its cover letter) on a stronger model of your choice:

• Anthropic — Claude Opus 5, Claude Sonnet 5
• OpenAI — GPT-5
• Google — Gemini 2.5 Pro
• xAI — Grok 4.5, Grok 4.3
• Ollama Cloud — DeepSeek V4 Flash, Qwen 3.5, Kimi K3, GPT-OSS 120B

Stronger models produce noticeably stronger resumes; the AI usage runs on your key (Ollama Cloud bills through your Ollama subscription rather than per token). If the key is removed, tailoring falls back to the platform default automatically.