Skip to main content
Read and update extra usage for mode ai-models-included. Amounts are euros. The call uses the workspace API key’s BILLING_API scope. Writes run as the key’s service account owner.
Call these routes when GET /billing/v1/mode returns ai-models-included. Dedicated deployments always return bring-your-own-keys, including when Langdock manages the model keys. The other mode returns 409 with code BILLING_MODE_MISMATCH.

​
Base URL

​
Prerequisites

  • API key with the BILLING_API scope
  • The key owner is a service account that has not been deleted and has an active Admin membership

​
Update settings

PATCH accepts extraUsageEnabled, usageRequestsEnabled, workspaceExtraUsageLimit, and defaultExtraUsageLimitPerPlan. Send at least one of them. A plan you omit from defaultExtraUsageLimitPerPlan keeps its limit.
The response matches GET, with extraUsagePeriodSpend set to null. Read the settings again to get spend. A limited workspaceExtraUsageLimit must be greater than zero. A limited plan default may be zero. Turning extraUsageEnabled off gives every member an effective extra usage limit of zero. Their configured limits stay stored. An unlimited member or group limit does not override this switch or the workspace cap.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.