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

# Custom toolset (API)

> Turn any REST API into agent tools by pointing Clarion at its documentation.

When a system has no Clarion integration and no MCP server, a **custom toolset** closes the gap. Give Clarion the API's base URL and its documentation, and it infers the tools — which you then review before any agent sees them.

<Note>
  This is different from a [custom MCP server](/integrations/custom-mcp). Use custom MCP when the vendor already ships an MCP server. Use a custom toolset when they don't.
</Note>

## Create one

1. In Clarion, open **Integrations → Custom toolsets** and click **Add**.
2. Give it a **name** — this becomes the tool namespace agents see.
3. Enter the API's **base URL**.
4. Configure **authentication**:

| Auth       | Sends                           |
| ---------- | ------------------------------- |
| **None**   | Nothing — for public APIs       |
| **Bearer** | `Authorization: Bearer <token>` |
| **Header** | A custom header name and value  |
| **Basic**  | Username and password           |
| **Query**  | A key as a query parameter      |

5. Provide **documentation** — paste text, link a URL, or upload a file.
6. Click **Scan**. Clarion reads the docs and proposes a list of tools.

Credentials are encrypted at rest and attached to the request outside the sandbox, so an agent never sees the key it is authenticating with.

## Review before enabling

The inferred tool list is a **proposal**, not a live surface. Every tool is disabled until you enable it, and only enabled tools are exposed to agents. Review each one's name, description, and parameters before turning it on — the description is what an agent reasons about when deciding to call it.

<Warning>
  Enable the narrowest set that does the job, and be deliberate about anything that writes. A tool an agent can call is a tool an agent can be talked into calling.
</Warning>

Responses pass through secret redaction before they reach a transcript or the UI.

## Rescans

Clarion hashes the normalized documentation. Rescanning after an unchanged doc is a no-op; when the docs change, you get a fresh proposal to review rather than silent drift in what your agents can do.

## Use in skills

Once enabled, a custom toolset's tools appear in the skill editor's tool picker like any other integration's, and can be embedded in skill content.

## Delete

Delete the toolset from **Integrations → Custom toolsets**. Stored credentials are removed, and skills referencing its tools surface them as missing.