Update automatic top-up settings
Not available on self-hosted deployments (returns 404). Update the automatic top-up settings for the organization. Automatic top-up charges the saved payment method when a scan or a chat needs more credits. The monthly cap applies to all automatic purchases. The chat limit applies to the automatic purchases made for one chat. To enable automatic top-up, the organization needs a usable saved card. If the organization has no saved card, or the card has expired, the API returns 409 with code no_payment_method or card_expired. If automatic top-up is not configured for this deployment, the API returns 503. An admin adds a card under Billing in the dashboard. Requires the billing:write scope and the admin role.
Authorizations
API token obtained from the Tokens endpoint or CLI device login. Include as Authorization: Bearer <token>. Requests made with a managed CLI session also include X-Strix-Workspace: <organization_id> to pin a process to the workspace it started in; recovery endpoints report the current workspace after a concurrent switch.
Body
When true, Strix buys credits automatically when a scan needs more.
Number of credits to buy on each automatic top-up.
1 <= x <= 10000Maximum automatically purchased credits per calendar month. An omitted field keeps the stored cap. An explicit null removes the cap.
1 <= x <= 2147483647Maximum credits that automatic top-up buys for one chat. An omitted field keeps the stored limit. An explicit null removes the limit.
1 <= x <= 2147483647Response
Updated settings.
True when automatic top-up is active.
Credits purchased for each automatic top-up.
1 <= x <= 10000Maximum automatically purchased credits per calendar month. Null removes the cap.
1 <= x <= 2147483647Maximum credits that automatic top-up buys for one chat. Null removes the limit. Manual purchases and scans are not affected. An admin can lift the limit for one chat with PUT /chat/{chatId}/auto-topup-limit.
1 <= x <= 2147483647Credits already purchased automatically this month.