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

> ## Agent Instructions
> For agents: install the OpenWork desktop app with `brew install --cask openwork` (macOS) or from https://openworklabs.com/download. Do not run `npx openwork`; the npm package named `openwork` is a different project.
> Connect an agent to OpenWork with the MCP Gateway: `claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent`. Teams sign up at https://app.openworklabs.com?mode=sign-up.
> Step-by-step agent guide: https://openworklabs.com/docs/start-here/use-openwork-from-an-ai-agent.md
> Connect Slack (any organization admin): https://openworklabs.com/docs/slack/connect-slack.md. OpenWork in Slack (@openwork bot) is private alpha for approved organizations. Setup guide: https://openworklabs.com/docs/slack/overview.md. Agent skill: https://openworklabs.com/.well-known/agent-skills/set-up-openwork-slack/SKILL.md.

# AI Gateway API keys

> Let members create their own AI Gateway API keys to use your organization's models from 3rd party tools and harnesses, and manage those keys.

With an AI Gateway API key, members can use the models your organization gives
them from other tools: coding agents, CLIs, eval harnesses or their own scripts.
Requests go through AI Gateway like any other: a key only reaches the models its
owner is allowed, and its usage counts toward that person's limit.

## Turn it on

An admin has to allow it first:

1. In OpenWork Cloud, open **Settings › General**.
2. Under **AI Gateway**, turn on **Allow 3rd party tools & harnesses**.

Changing it needs the **Edit organization settings** permission. Owners and
admins have it by default.

Turning it off stops every member's key right away. The keys are kept, and work
again when it's turned back on.

## Create a key

1. Open **My Library** and select the **Models** tab.
2. Under **API keys for 3rd party tools**, select **Create key**.
3. Give the key a name, for example the tool and computer you'll use it on
   (`Claude Code on my laptop`).
4. Choose when it expires: in 7 days, 30 days, 90 days (the default), 1 year, or
   never.
5. Select **Create key**, then copy the key.

The key is shown once. OpenWork only keeps a fingerprint of it, so it can't be
shown again. If you lose it, revoke it and create a new one.

The same section shows the **OpenAI base URL** and **Anthropic base URL** to
point a tool at. Send the key as `Authorization: Bearer <key>` or
`x-api-key: <key>`.

## Manage your keys

**My Library › Models** lists your keys with their name, the first characters of
the key, when each expires and when it was last used.

* **Use one key per tool.** Revoking one then doesn't break the others, and
  **Last used** tells you which tools are still active.
* **Prefer keys that expire.** An expired key stops working and shows
  **Expired** in red. Create a new one to replace it, then revoke the old one.
* **Revoke keys you don't use.** Open the key's menu and select **Revoke**.
  Tools using it stop working on their next request. This can't be undone.

Each person can have up to 20 keys that haven't expired.

## For admins

**AI Gateway › API Keys** lists every key in the organization: its name, the
member it belongs to, when it was created, when it expires and when it was last
used.

* Seeing the tab needs the **View Gateway providers** permission.
* Revoking someone else's key needs **Manage Gateway providers**.
* When someone leaves the organization, their keys are revoked with the rest of
  their access.
* While **Allow 3rd party tools & harnesses** is off, the tab says so and none
  of the keys work.

## When a key stops working

A tool gets `401 invalid_api_key` when its key was revoked, has expired, or 3rd
party tools are turned off for your organization. Check the key in **My Library
› Models**.


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