Skip to main content

What these pages cover

The pricing and billing, resource limits and managed wallet pages, and the billing API reference, were checked against the server source at 689feb5b8d2b2efcb0ae7b49704db42299de8ab8 and the CLI’s main branch on 31 October 2026:
  • Plan prices and allowances come from the server’s plan definitions, and add-on and credit-pack prices from its billing catalog.
  • The existing-account transition ends at the time recorded for each account at rollout, 30 days later: 25 November 2026 at 08:01 UTC.
  • Billing writes are console-only at the API gateway. Checkout, the billing portal, plan and add-on changes, cancelling a scheduled change and credit-pack checkout answer 404 to an API key. Subscription status, the catalog, operation status and wallet history stay readable with one.
  • rig limits and rig whoami show a Billing block, and payment refusals link to Billing, from a CLI newer than 0.13.2.

API source

Both references are exported from that server revision with its pinned Rust toolchain. Neither export starts a service, connects to a database, or calls the live API. The gateway export (rig-gateway --print-openapi) supplies the wallet and limits components, which are copied into the gateway spec without touching unrelated paths or schemas. auth-api.json is the complete auth-service export, so it lists all nine billing operations, including the console-only writes that the gateway leaves out of its public spec. Several billing responses are generic JSON objects, because the handlers return untyped JSON. Rely on the fields a response actually carries rather than assuming more. The provenance record lists the revision, toolchain, export hashes and the checked claims.