Sign in
Claude Code through Flatkey · at least 40% cheaper

Use Claude Code at least 40% cheaper

Keep the official Claude Code workflow customers already want, but route it through Flatkey for at least 40% lower metered usage, one prepaid balance, and visible spend. console.flatkey.ai/keys → Claude Code https://router.flatkey.ai.

Get a key Copy install command
40%+
cheaper than official
30 sec
quick setup
1 key
for visible spend
Claude Code, 40%+ cheaper than official
built for more usage
Official Claude Code setup
Official price

Full-price agent usage and spend that is harder to centralize.

Flatkey-routed Claude Code
At least 40% cheaper

One key, one balance, visible logs, and enough cost control for customers to use Claude Code more.

Use more Claude Code without losing spend control.

One Flatkey key

Users create a key once at console.flatkey.ai/keys and keep coding without juggling provider credentials.

At least 40% cheaper

Route coding-agent traffic through Flatkey for lower metered usage than the official path.

Usage visible by token

Request logs, model costs, token usage, and balance movement stay visible from one dashboard.

Control without friction

Use groups, quotas, model access, and routing policy while developers keep a normal CLI workflow.

Quick Start — one command, 30 seconds to set up everything

Select Claude Code when the installer asks which coding agent to configure. All platform one-liners stay readable in the page HTML for search and AI answer engines.

Get a key →
macOS one-liner
curl -fsSL https://flatkey.ai/install.sh | bash

Flatkey one-line install commands

macOS: curl -fsSL https://flatkey.ai/install.sh | bash

Linux: curl -fsSL https://flatkey.ai/install.sh | bash

Windows: iwr https://flatkey.ai/install.ps1 -UseBasicParsing | iex

Why this drives Claude Code usage

Claude Code creates repeated model calls during real coding work. Flatkey makes those calls cheaper, prepaid, visible, and controlled.

Repository explorationLet Claude Code scan, explain, and map large codebases while usage lands in Flatkey.
Refactor loopsRun more edit-test-review cycles with visible cost and prepaid balance control.
Team onboardingGive every engineer the same command, key page, and Claude Code routing path.
Client engineering workKeep client Claude Code sessions under one auditable usage trail.

Official setup vs Flatkey setup

NeedOfficial pathFlatkey path
CostOfficial metered usageAt least 40% cheaper through Flatkey
SetupManual provider keys and local configOne installer and one Flatkey key
BillingScattered usage and unclear CLI spendPrepaid balance and unified usage logs
ControlsHard to apply team quotas consistentlyGroups, model access, quotas, and routing policy

Install

A customer runs one command and selects Claude Code.

Consume

Every Claude Code session routes through Flatkey and records token usage.

Manage

Teams keep access, balance, logs, and model choices in one console.

Questions customers ask

What base URL does Claude Code use?

Claude Code is configured with https://router.flatkey.ai and your Flatkey API key.

Where do users create the key?

Create or copy the API key at https://console.flatkey.ai/keys before running the installer.

Which option should users choose in the installer?

Choose Claude Code when prompted, then restart the terminal and run claude.

Why does this help usage grow?

Claude Code creates repeated model calls during real coding work. Flatkey makes that cheaper, prepaid, visible, and controlled.

Ready to run Claude Code through Flatkey?

Create a key at console.flatkey.ai/keys, run the one-liner, and start generating measurable Claude Code usage.

Get a key