Skip to main content
Read and update monthly agent budgets in euros. Use the ai-models-included prefix for this workspace mode. The calls use 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 a budget

PATCH /agents/{agentId} accepts budget, budgetMode, or both. Send at least one.
budget is a monthly amount in euros:
  • { "type": "limited", "amount": 40 } sets a cap. The amount must be greater than zero.
  • { "type": "unlimited" } keeps a separate budget with no numeric cap. Spend can still be reported. This is different from none.
  • { "type": "none" } removes the separate agent budget. The agent then follows workspace and member limits.
budgetMode chooses when that budget is used:
  • always (Always) counts usage against the agent budget immediately, including API calls, and does not consume the member’s allowance.
  • on_limit_hit (After user limits) counts usage against the member’s limits first. After the member reaches a personal limit, usage counts against the agent budget.
The budget is enforced only while extra usage is on. While extra usage is off, the stored budget is kept but not applied, and spend stays at zero. An active agent budget still follows the workspace extra usage cap from Get Included Workspace Settings. Removing a budget does not turn that cap off. The response is the agent object with budgetPeriodSpend set to null. Read the agent again to get spend.
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.