Salambo separates configuration access from runtime execution access. You can configure agents, deployments, API keys, integrations, and workspace settings before every runtime prerequisite is complete. Actual hosted execution is gated by billing/runtime readiness.

​
Billing-owner workspaces

Standard and agency workspaces own billing. Their sidebar can include:
  • Usage
  • Billing
  • API Keys
The billing page shows runtime readiness, payment method, invoices, plan controls, billing details, and usage for users with billing management permission.

​
Client workspaces

Client workspaces inherit billing from their parent agency. In the deployed app, client workspace navigation includes:
  • Dashboard
  • Agents
  • Runs
  • General
  • Members
  • API Keys
Client workspace navigation intentionally hides:
  • Billing
  • Usage
Direct client billing and usage URLs return a not-found page.

​
Runtime-ready billing states

Runtime execution is allowed when the billing owner is in a runtime-ready state, including:
  • active
  • pending
  • ending soon
If billing fails or payment setup is incomplete, runtime-capable operations can be blocked until billing is recovered.

​
Runtime-capable scopes

Creating or rotating an API key with any of these scopes checks billing readiness:
  • responses:write
  • files:read
  • runs:write
Configuration-only scopes can still be used for setup work that does not start or access runtime execution.

​
Usage attribution

Usage is charged to the billing owner. When execution comes from a client workspace, Salambo preserves the client identity for attribution where supported.