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

# Personal API keys

> Control who can create personal API keys, monitor their usage, and revoke keys across your workspace.

<Frame>
  <img src="https://mintcdn.com/langdock-34/9Y2RQ5qliRYBiJPG/images/personal-api-keys-settings.png?fit=max&auto=format&n=9Y2RQ5qliRYBiJPG&q=85&s=043e367580be6ae387106e5355a77acd" alt="API settings showing the Workspace API keys and Personal API keys tabs, with the Personal API keys tab selected" style={{borderRadius: '6px'}} width="2006" height="898" data-path="images/personal-api-keys-settings.png" />
</Frame>

Personal API keys let members use your workspace's models from coding tools and their own projects, without you handing out a shared workspace key. Each key belongs to the member who created it, reaches the completion endpoints only, and spends that member's usage budget, so you decide who gets access and how much they can spend.

<Info>
  The **Personal API keys** tab only appears once the feature is enabled for your workspace. Members only see **API keys** in [their account settings](/en/using-langdock/account/personal-api-keys) after you give them access.
</Info>

## Give members access

<Steps>
  <Step title="Open the personal API key settings">
    Go to [Settings > Workspace > Products > API](https://app.langdock.com/settings/workspace/products/api), then open **Personal API keys**.
  </Step>

  <Step title="Choose who gets access">
    Open access to the whole workspace, or keep it to the people who need it:

    <Tabs>
      <Tab title="Everyone">
        Turn on **General access** so everyone in the workspace can create a personal API key.

        <Frame>
          <img src="https://mintcdn.com/langdock-34/9Y2RQ5qliRYBiJPG/images/personal-api-keys-general-access.png?fit=max&auto=format&n=9Y2RQ5qliRYBiJPG&q=85&s=a07cf2ee1bdd6d917050f23e9833ab89" alt="General access toggle turned on, so everyone in the workspace can create a personal API key" style={{borderRadius: '6px'}} width="2004" height="372" data-path="images/personal-api-keys-general-access.png" />
        </Frame>
      </Tab>

      <Tab title="Specific members and groups">
        Leave **General access** off and turn on **Allow specific members or groups to create personal API keys**, then add the members and groups that need it.

        <Frame>
          <img src="https://mintcdn.com/langdock-34/9Y2RQ5qliRYBiJPG/images/personal-api-keys-specific-members.png?fit=max&auto=format&n=9Y2RQ5qliRYBiJPG&q=85&s=72d632a3d718008a3a0b80e7be759656" alt="Toggle for allowing specific members or groups to create personal API keys, turned on" style={{borderRadius: '6px'}} width="1998" height="354" data-path="images/personal-api-keys-specific-members.png" />
        </Frame>
      </Tab>
    </Tabs>
  </Step>

  <Step title="Give them budget to spend">
    <Frame>
      <img src="https://mintcdn.com/langdock-34/9Y2RQ5qliRYBiJPG/images/personal-api-keys-spend-limits.png?fit=max&auto=format&n=9Y2RQ5qliRYBiJPG&q=85&s=017803166f638ea1264e3ee98b13d0d7" alt="Spend limits for users, groups, and agents with the Users tab open, showing a member's plan, usage, and extra usage limit" style={{borderRadius: '6px'}} width="2002" height="668" data-path="images/personal-api-keys-spend-limits.png" />
    </Frame>

    Personal API usage draws on the same budget as the member's chat and agent usage. Under [Settings > Workspace > Usage](https://app.langdock.com/settings/workspace/usage), enable [extra usage](/en/admin/manage-usage/extra-usage) and set an effective limit above zero for each member you granted access.
  </Step>
</Steps>

A member with access but no available budget can still open the personal API key page, but cannot create a key. If [usage requests](/en/admin/manage-usage/extra-usage#usage-requests) are enabled, they can ask for a higher limit right there.

<Note>
  On BYOK and dedicated deployments, set an individual extra usage limit above zero for each member instead. Plan and group limits do not apply to personal keys there, and extra usage does not have to be enabled. See [BYOK usage limits](/en/admin/manage-usage/byok/usage-limits) for how the limits fit together.
</Note>

## Monitor usage and revoke keys

**Usage insights** shows API spend for the current month, how many keys are active, how many members hold one, and daily spend per member over the last 14 days.

<Frame>
  <img src="https://mintcdn.com/langdock-34/9Y2RQ5qliRYBiJPG/images/personal-api-keys-usage-insights.png?fit=max&auto=format&n=9Y2RQ5qliRYBiJPG&q=85&s=d78f3279949f28283e45465305d17f19" alt="Usage insights cards showing API spend this month, the number of active keys, and how many members hold a key" style={{borderRadius: '6px'}} width="2002" height="594" data-path="images/personal-api-keys-usage-insights.png" />
</Frame>

**All personal keys** is where you review individual keys. Search by member, filter by spend or activity, check each key's owner, last use, monthly spend, and status, and revoke a key when you need to.

Revoking takes effect immediately and cannot be undone. A personal key also stops working when you take away a member's access to personal API keys or deactivate their workspace membership.

## When should I use a personal key?

Reach for a personal API key when one member needs API access under their own identity and usage budget. Use a workspace API key for shared applications and automations that should not depend on one person's account.