Docs menu
⌘K

Ship

Workspaces & billing

A workspace is the account new requests bill to. It can be personal or shared with an organization.

Choose a billing workspace

Signing in gives you at least a personal workspace. If you belong to an organization, you can send new work to its shared wallet instead. List what this login can bill:

midas workspace list

The list shows each workspace by name, slug, and your role. Switch with the slug:

midas workspace use acme

Inside a session, run /workspace or its alias /billing. The choice applies to new requests, not requests already in flight. Every request records which workspace paid for it, so usage and billing stay separate.

Organizations and teams

An organization has one shared wallet, a roster, and roles. Owners and admins manage settings; members use the wallet within their limits. In the dashboard you can:

  • Add credits to the shared wallet and set a budget for the organization.
  • Set a per-person budget and watch usage against it.
  • Group people into teams as budget containers.
  • Invite people and change their role.
  • Use OIDC SSO for sign-in and SCIM to provision and deprovision accounts.
  • Review spend in the organization overview, people, and teams pages.

The organization and personal paths are separate URLs in the dashboard. A personal page lives under /me and an organization page under /org/<slug>, with the same pages in each: usage, billing, sessions, reviews, and sandboxes.

What bills where

  • Model requests bill to the workspace selected for the session.
  • Pull request reviews bill to the workspace that owns the GitHub installation.
  • Cloud sandbox compute bills to the workspace that started the sandbox, separately from its model use.
  • Review spend and sandbox compute both appear with the rest of your usage.
The compute rate for cloud sandboxes is set for the workspace by an administrator. The session limit is also a workspace setting. See Cloud sandboxes.

Related