cd /news/ai-agents/railway-now-supports-linked-billing-… · home › topics › ai-agents › article
[ARTICLE · art-171596] src=blog.railway.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Railway now supports linked billing with Claude Platform

Railway added linked billing with Claude Platform, letting a Railway workspace connect its Claude organization so Anthropic bills Claude API usage in Railway Agent, Cloud Agents, and the Slack and Discord bots directly on existing terms, with no API key to share. A Railway workspace admin starts the link and an owner, admin, or billing admin of the Claude organization approves it, after which admins can set a monthly spend limit in the Claude Console's Linked platforms page and unlink at any time. API keys remain supported as an additional option, and Railway checks each request before it leaves to confirm it targets the correct organization for billing.

key takeaway

Railway workspaces can link a Claude Platform organization to bill Claude API usage directly, with no API key stored and a monthly spend cap set in the Claude Console; whichever of Railway's or the organization's limit is reached first stops requests.

by read4 min views8 publishedNov 17, 2026
Railway now supports linked billing with Claude Platform
Image: Blog (auto-discovered)

You can now link your Claude Platform organization to your Railway workspace. 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. An admin approves the link, can set a monthly spend limit, and can unlink at any time.

Use the Claude organization you already have #

A lot of you already have a Claude organization. When you run agents on Railway, you should be able to use it instead of starting a second bill for the same access.

Until now, the way to do this was to create a Claude API key and paste it into the Agent Settings page. API keys are still supported, and can be added within the agents configuration screen. Linked billing is an additional option.

We added linked billing so you can use Claude in Railway with no API key to share, store or rotate. Link your organization, set your model - and just go build.

Linking requires a Railway workspace admin to start the flow, and an owner, admin, or billing admin of the Claude organization you're linking to, to approve it (often that's the same person). The flow looks like this:

  1. Open Account Settings , then Agents with the workspace you want to link selected.
  2. Find the Claude Platform Organization card in theProviders section and clickLink .
  3. Claude opens in a popup. Choose the organization if you belong to more than one, set a monthly spend limit for Railway if you want one, and approve.

Claude models show up under the Claude Platform header in the Default Model list and in the chat's model picker, and with a (Claude Platform) label inside cloud agents.

If someone on the team has already added their own Claude API key and selected the API key configurations as their Default Model, Railway will keep using it for their requests. Their usage goes to their key, and everyone else's goes to the linked organization.

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.

Spend controls in Claude #

Since Anthropic is the one billing your Claude API usage, the controls live where your Claude administrators already work. On the Linked platforms page in the Claude Console they can see what Railway has cost this month, set or change Railway's monthly spend limit (the Console calls it a spend cap), or unlink it. Workspace admins can jump there from Manage on the card.

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

When a limit is reached, the card says so (Spend limit reached), agents try again on the next request, and members can switch to a Railway model in the meantime.

Clicking Unlink in Railway stops Claude API usage in Railway from being billed to your organization, removes Railway from your Linked platforms page, and resets any default model.

There isn't much to line up before you click Link:

  • You need to be an admin of the Railway workspace.
  • You (or a teammate) are an owner, admin, or billing admin of the Claude organization.
  • Anthropic bills that organization directly

Start here #

We want to build a platform that unburdens users so they can focus on what matters - shipping great software. That applies to the models behind your agents as much as it does to the service running your app. With linked billing, you can use Claude where you ship, with no API key to share.

The Claude Platform docs cover linking, spend, and every card state in detail. Link your organization from Agents settings, pick a model, and tell us how it goes on Central Station.

Happy shipping.

── more in #ai-agents 4 stories · sorted by recency
── more on @railway 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/railway-now-supports…] indexed:0 read:4min 2026-11-17 · —