Bring Your Own Key

Garth supports Bring Your Own Key (BYOK), which lets you supply your own API key from an AI provider instead of relying on Garth’s shared capacity. All keys are encrypted and stored in Garth’s secure vault — they are never logged or exposed in plain text.

Why use BYOK?

Your own rate limits

Reviews and scans draw from your provider account’s quota, so high-volume teams are never throttled by shared limits.

Data residency control

Requests go directly from Garth to your provider under your account, giving you full control over which region processes your code.

Cost visibility

All token usage is billed to your provider account so you can track AI spend alongside your other developer tooling.

Supported providers

Claude

Recommended. Best-in-class reasoning for code review and security analysis.

OpenAI

GPT-4o and GPT-4 Turbo models supported.

Gemini

Gemini 1.5 Pro and Gemini 2.0 Flash supported.

Sarvam AI

Sarvam-105B and Sarvam-M models optimized for Indian languages.

Claude is the default and recommended provider. It consistently produces the most accurate inline review comments and security findings across the codebases Garth has been tested on.

Adding your API key

All keys are stored in the Garth Secure Vault — encrypted at rest, never written to logs, and scoped to your organisation only.

Open the Integrations settings

Navigate to Settings → Integrations → LLM in the Garth dashboard.

Select a provider

Choose Claude, OpenAI, Gemini, or Sarvam AI from the provider list.

Paste your API key

Enter your API key in the input field. The key is immediately encrypted before it leaves your browser.

Save to vault

Click Save. Garth validates the key against the provider’s API, then stores it in the secure vault. A masked preview (e.g. sk-ant-••••••••XXXX) confirms the key is saved.

Set as active provider

If you have keys for more than one provider, select which provider Garth should use for new requests under Active Provider.

You can only have one active provider at a time. Switching providers does not delete existing keys — stored keys remain in the vault until you explicitly remove them.

Provider reference

Claude (Anthropic)

Get your API key from the Anthropic Console.

Setting	Value
Key format	`sk-ant-api03-…`
Recommended model	`claude-sonnet-4-6` or `claude-haiku-4-5` (faster, lower cost)
Rate limits	Depend on your usage tier — see Claude tier limits

OpenAI

Get your API key from the OpenAI Platform.

Setting	Value
Key format	`sk-proj-…` or `sk-…`
Recommended model	`gpt-4o`
Rate limits	Depend on your OpenAI usage tier — see OpenAI models and tiers

Gemini (Google AI)

Get your API key from Google AI Studio.

Setting	Value
Key format	`AIza…`
Recommended model	`gemini-1.5-pro` or `gemini-2.0-flash`
Rate limits	Depend on your Google Cloud project quota — see Gemini models and rate limits

Sarvam AI

Get your API key from the Sarvam AI Dashboard.

Setting	Value
Key format	Alphanumeric string passed as `api-subscription-key`
Recommended model	`sarvam-105b` (complex reasoning) or `sarvam-m` (faster, lower cost)
Rate limits	Depend on your Sarvam AI subscription tier — see Sarvam AI rate limits

Removing a key

To remove a stored key, go to Settings → Integrations → LLM, find the provider, and click Disconnect. The key is permanently deleted from the vault and cannot be recovered.

Removing an active key will pause all AI-powered reviews and scans until a new key is added or the provider is switched.

Next steps

Claude tier limits

Understand Claude API usage tiers and choose the right tier for your team’s volume.

OpenAI models and tiers

Understand OpenAI’s usage tiers and choose the right GPT model for your team’s volume.

Gemini models and rate limits

Understand Gemini’s free and pay-as-you-go tiers and model options.

Sarvam AI rate limits

Understand Sarvam AI subscription tiers and models optimized for Indian-language codebases.

Customize review

Write custom instructions to align Garth’s reviews with your team’s standards.

Overview

Setup your repository