← Blog · Guides

Railway Now Bills Claude to Your Own Organization With No API Key to Share. What That Changes About Custody

November 17, 2026

Last week we asked a question at the end of Railway Will Pay for the Stolen AI Tokens. Which of Your Platforms Holds a Key?: how many platforms are holding one of your AI provider keys right now? On 17 November 2026 Railway published a feature that changes the answer for one platform and one provider. In "Railway now supports linked billing with Claude Platform", by Cody De Arkland, it puts it this way:

"We added linked billing so you can use Claude in Railway with no API key to share, store or rotate."

The headline is the missing key. The more useful change is quieter: the control that stops the spending now lives in Anthropic's console, not Railway's, and a team can have more than one of them without noticing.

One thing to be clear about first. Railway's post does not mention the October incident, the compensation bulletin or security at all. It presents linked billing as a convenience: use the Claude organization you already have instead of starting a second bill. The connection to the breach is ours, not Railway's, and we draw it because the question is the same: where does the credential live?

What linked billing is

Until now, the way to use your own Claude account in Railway's agents was to create an API key and paste it into the Agent Settings page. Linked billing replaces the pasted key with an approval:

"Once linked, Anthropic bills that organization directly for Claude API usage in Railway Agent, Cloud Agents, and the Slack and Discord bots, on your existing terms. There is no API key to share."

The flow takes two people, or one person with both roles. A Railway workspace admin starts it from Account Settings, then Agents. An owner, admin or billing admin of the Claude organization approves it in a Claude popup, where they can also set a monthly spend limit for Railway. Railway adds: "often that's the same person".

The scope is specific. It covers Claude API usage in Railway's own agent features (Railway Agent, Cloud Agents, and the Slack and Discord bots). The post does not describe any change to how other secrets, such as your apps' environment variables, are stored.

What changes about custody, and what does not

The section of Railway's post worth reading twice is titled "What access Railway holds":

"An admin approves the link on Claude's own page. There's no API key from your organization sitting in Railway's database."

"Every request to a Claude Platform model goes through a check before it leaves Railway, to make sure it's targeting the correct organization for billing. If that check fails, Railway doesn't send it."

"Only billing is linked, and requests still run in Railway's organization."

Read together, those three paragraphs describe a different shape of trust. On the linked path there is no reusable secret of yours in Railway's database, which is exactly the kind of row the October attacker searched for by variable name. Requests are sent from Railway's own organization, and the link decides only who is billed. That last sentence matters: linking does not mean your requests run inside your Anthropic organization, and Railway says so directly.

Two things the linked path does not do:

  • It does not remove keys that are already there. API keys are still supported, and the post calls linked billing "an additional option". If a teammate has pasted their own key and picked it as their default model, it keeps working for them: "Their usage goes to their key, and everyone else's goes to the linked organization." So the absence of your key from Railway's database is true of the linked path, not automatically of your whole team. If you link, check whether anyone still has a personal key configured.
  • It does not remove the ability to spend. A link is not a secret anyone can copy, but it is still a standing permission to bill your organization for usage through Railway. That is our reading, not Railway's wording, and it is why the next part matters.

Two spend limits, and the first one wins

The spend controls live in the Claude Console, not in Railway. On the Linked platforms page an administrator can see what Railway has cost this month, set or change Railway's monthly limit (Railway notes "the Console calls it a spend cap"), or unlink it. The organization's own limit still applies alongside it:

"Your organization's own monthly spend limit still applies, and whichever of the two is reached first is the one that stops requests."

So there are two ceilings, not one: the per-platform limit for Railway and the organization-wide monthly limit. When either is reached, the card in Railway shows "Spend limit reached", agents try again on the next request, and members can switch to a Railway model in the meantime. A member who pasted their own key is, on our reading, outside both. Railway says "Their usage goes to their key", so the linked organization's limits would not count that usage, and whatever stops it is set wherever that key was issued. A team that thinks it has one ceiling can have one per pasted key. Clicking Unlink stops Railway usage being billed to your organization, removes Railway from the Linked platforms page and resets any default model.

Our earlier post's advice was to cap the spend at the provider. This is that advice turned into a limit for one platform, held by the provider.

The question to ask every platform that has one of your keys

Railway's change covers one platform and one provider. The inventory you made after the October incident probably lists more. For each entry, four questions are worth asking:

  • Is there a path that is not a pasted key? A link approved on the provider's own page, with no reusable secret stored on the platform, is now an option in at least one place.
  • If it is a key, where is it stored? A central database of every customer's variables is a different target from a file on the server your app runs on.
  • Can you cap spend for that platform alone, at the provider? One limit per platform tells you which one is burning money and stops only that one.
  • How do you revoke it, and how long does that take? Unlinking is one click. Rotating a pasted key means issuing a new one and getting it into every place that used the old one.

Where keys live on DeployBase, and what that does and does not protect against, is in the earlier post.

If you are still owed a claim

The date Railway's compensation bulletin gave is 18 November 2026. Quoted whole, as before, because the second half matters: "Please submit claims by Weds 11/18/2026, though we will do our best to honor claims submitted after that." If you had unauthorized AI spend on a key stored in Railway between 13:50 UTC on 20 October and 09:25 UTC on 21 October, the bulletin has the process.

Sources, read 18 November 2026: Railway, "Railway now supports linked billing with Claude Platform" (17 November 2026). Our earlier post quotes Railway's "Bulletin: Compensation for unauthorized AI usage" (12 November 2026).