
Image: Kilo Code
Why it mattersA team stops pasting and rotating API keys to use Claude inside Kilo. The security pain and the second bill both go away.
Kilo Code released linked billing with Claude Platform in beta on 18 November 2026. The post was written by Ari Messer on Kilo's blog. An admin links the team's Claude Platform organisation to Kilo once. After that, Anthropic bills every Claude API call to that account.
What it fixes
Before this, a team that wanted to use Claude in Kilo had one path. Someone made an API key in the Claude console. They pasted it into Kilo. The key then had to be rotated when a person left the team. If the key leaked, it had to be cancelled and a new one made.
Linked billing takes the API key out of the loop. The link is between two accounts, not between a tool and a secret. Kilo asks the admin to approve the link once. Anthropic sends the bill to the organisation's existing account. A team can set a monthly spend limit on the Claude console too. And the link can be removed at any time.
How it works
Kilo tells an admin to "Switch to your organization, open the Bring Your Own Key (BYOK) page". From there, choose Link your Claude organization on the Claude card. After that, Claude is on every Kilo surface. The post names four: VS Code, JetBrains, the terminal, and Kilo's Desktop app. A reader of the post can set it up without an engineer in the loop.
Kilo is a multi-model IDE. It works with Claude, GPT, Gemini and 500 other models. So this is not Kilo moving to Claude. It is Kilo making one of those models easier to pay for.
What it does not say
The post gives no pricing. A team that links its account still pays the usual Claude API rate for every token it uses. The post does not say whether a Claude Pro or Max seat carries over to the linked account. It does not say what happens if the Anthropic bill goes unpaid.
An admin reading this today can audit their own team. If somebody has pasted an API key into a tool, that key is probably still there a year later. Linked billing is the one way to retire the key without cutting off the person who uses it. The audit question is the same for every tool a team has pasted keys into. Kilo covers one tool. The rest is still a person's job.
Source
Kilo now supports linked billing with Claude Platform, Kilo Code.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.


