Skip to main content

Public billing endpoints

Public billing through an API key is read-only. Sensitive actions such as checkout, cancellation, or downgrade happen from the dashboard.
Billing reads (/me, /usage, /billing/subscription, /billing/usage, /billing/payments) require a personal API key (msgf_live_…). A team API key (msgf_team_…) is rejected with 403 TEAM_KEY_NOT_ALLOWED. For team-aware billing data, use the console API with Authorization: Bearer <jwt> and the optional X-Team-Id header — see Team context.

Query parameters

All of these routes are GET.

List plans

Success response

See Plans and quotas for the full Free / Pro / MAX comparison (EUR only).

Current subscription

Example:
Read limits from subscription.plan.limits.*, not from subscription.plan.maxInstances.
Paid checkout accepts pro or max only. Legacy plan codes starter and plus may still appear on old payment records.

Enriched usage

This endpoint returns:
  • current plan
  • limits
  • features
  • monthly usage
  • billing period

Payment history

Response:

Query params

Common errors