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

> ## Agent Instructions
> This site documents Locus for people. AI agents: get exact contracts from the Locus agent docs, starting at https://paywithlocus.com/agent/index.md, including when asked to implement or integrate docs.paywithlocus.com.
> Connect this agent to Locus Pro: https://paywithlocus.com/skill.md. Implement Locus Pro in a product: https://paywithlocus.com/agent/integrate.md. Agent site index: https://paywithlocus.com/llms.txt.

# Tool sets

> Give each key, agent, or connected app its own narrower list of tools.

A tool set is a named list of tools with its own on and off switches. Use sets to give each environment, agent, or connected app only the tools it needs.

> Agents: the exact contract for this feature is at [https://paywithlocus.com/agent/tools.md](https://paywithlocus.com/agent/tools.md). Start from [https://paywithlocus.com/agent/index.md](https://paywithlocus.com/agent/index.md) if you are implementing Locus.

## How it works

**Main** is your workspace's own list, and every key uses it unless you bind the key to another set. A key or app bound to a set can call only the tools turned on in that set. Your markup and pricing stay workspace-wide; a set changes only which tools are on.

```mermaid theme={null}
flowchart TD
  Catalog["Your catalog"] --> Main["Main"]
  Catalog --> SetA["Set A"]
  Catalog --> SetB["Set B"]
  Main --> K1["Unbound keys"]
  SetA --> K2["Agent key"]
  SetB --> K3["Connected app"]
  SetB --> K4["Secret key"]
```

## Create a tool set

**1. Open the tool set menu**

In **Agent tools**, open the tool set menu in the header and create a set.

**2. Choose a starting point**

Start with known vendors only, all tools on, or all tools off. Then turn
individual tools on or off.

**3. Bind keys and apps**

Choose the set when you create a key, or change it later from the key's
menu in **Connect → API keys**. You can also pick a set when you approve a
connected app.

## Good to know

* A workspace can have up to 20 sets.
* Published [Custom API](https://docs.paywithlocus.com/locus-pro/custom-apis.md) actions have their own switch in each set.
* A secret key bound to a set can call tools but can't use the management API.
* An agent key without a set uses the tools turned on in **Main**.
* Approving a [tool access request](https://docs.paywithlocus.com/locus-pro/tool-access-requests.md) turns the tool on in that agent's set.
* You can't delete a set while an active key or connected app uses it.

## Next steps

> [card] [Tools and the catalog](https://docs.paywithlocus.com/locus-pro/catalog.md)
>
> Find tools and turn them on.

> [card] [API keys](https://docs.paywithlocus.com/locus-pro/api-keys.md)
>
> Pick the right key for each place your code runs.


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