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

​
Read settings

GET /billing/v1/ai-models-included/settings returns the current settings.
extraUsageEnabled turns extra usage on or off for the workspace. When it is off, every member’s effective extra usage limit is zero, with source workspace. Configured member and group limits stay in place for when you turn extra usage on again. workspaceExtraUsageLimit caps extra usage in extraUsagePeriod. Chat, agent, and personal API key usage count toward that cap, and so do Agent API calls with a workspace key when the agent budget is always with a limited amount. Other workspace API usage, workflow runs, and custom model usage do not. See Extra usage. An unlimited member or group limit does not remove it. extraUsagePeriodSpend is the usage counted toward the cap. It is null when the workspace hides per user spend. defaultExtraUsageLimitPerPlan is the default extra usage limit for Business (business) and Business Max (business_max). A member who inherits uses these defaults together with group limits. See Get Included User. usageRequestsEnabled lets members ask an admin for more usage.
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.