> ## Documentation Index
> Fetch the complete documentation index at: https://docs.langdock.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Included Workspace Settings

> Change extra usage, usage requests, the workspace extra usage cap, and the default limit on each plan

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.

> [!NOTE]
>
> 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

```
https://api.langdock.com/billing/v1/ai-models-included/settings
```

## 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.

```bash theme={null}
curl -X PATCH https://api.langdock.com/billing/v1/ai-models-included/settings \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"defaultExtraUsageLimitPerPlan":{"business_max":{"type":"limited","amount":150}}}'
```

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.

> [!NOTE]
>
> 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](https://docs.langdock.com/en/admin/ai-adoption-and-rollout/best-practices/api-key-best-practices.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.