Workspaces & shared credits

A workspace lets you share one credit balance with other people — teammates, friends, or a class — and cap how much each member can spend. You fund a shared wallet once; members make API calls that draw from it, and you see exactly who spent what.

• Shared wallet — the workspace holds its own credit balance, separate from your personal balance.
• Members — people you invite by email. Each can have an optional spend cap.
• Per-member usage — every request is attributed to the member who made it, so you can see spend per person.

In the dashboard, open Workspace and create one with a name. Workspaces are free — there is no per-seat charge; you only pay for the model usage that draws from the shared wallet.

As the owner, deposit funds from your personal Routing balance into the workspace wallet. You can withdraw unused funds back to your personal balance at any time.

Invite people by email from the Workspace page. They receive an invite link (you can also copy it directly) and join after signing in. Owners and admins can invite; members cannot.

Set an optional lifetime spend cap (in dollars) for each member. Once a member's spend reaches their cap, their requests are rejected with a 402 SPEND_LIMIT_EXCEEDED error until you raise it. Leave the cap empty for unlimited (bounded only by the shared wallet balance).

To charge a workspace wallet, create the API key while that workspace is selected in the dashboard. The key is permanently bound to that billing account, so send it like any other routing.run key:

curl https://api.routing.run/v1/chat/completions \
  -H "Authorization: Bearer rk_live_workspace_key" \
  -H "Content-Type: application/json" \
  -d '{"model": "deepseek-v4-pro", "messages": [{"role": "user", "content": "Hi"}]}'

Requests made with that key debit the shared wallet and count against the member's spend cap. A personal key continues to debit the personal Routing balance. Do not try to switch a key's billing owner with request headers.