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

# Authentication

> Connect to the public API.

Use `https://api.route.fun`. Public routing and data endpoints are keyless. Builder endpoints require an API key.

```bash theme={null}
curl https://api.route.fun/api/v2/config
```

## API keys

Sign in at the [developer portal](https://build.route.fun), create a named workspace, then open **API keys**. Copy your new key when shown and keep it on your backend.

Workspace plans apply to the authenticated builder API. Public keyless endpoints retain their existing limits.

Send your key in the `x-api-key` header from your backend:

```bash theme={null}
curl https://api.route.fun/api/v2/builders/usage \
  -H "x-api-key: $ROUTE_API_KEY"
```

| Scope      | Endpoints                                          |
| ---------- | -------------------------------------------------- |
| `quote`    | Builder quotes                                     |
| `swap`     | Swap preparation, registry transaction preparation |
| `tokens`   | Token metadata, builder profile, workspace usage   |
| `receipts` | Receipt verification, builder settlement history   |

Your public builder ID attributes trades. It does not replace an API key. A key never authorizes wallet signing.

[Plans and limits](/api-reference/plans) · [Get your first quote](/cookbook/compare-quotes)

Before creating a key with `quote` or `swap` permissions, select **Activate builder ID**, choose your payout wallet and fee, then confirm the registration transaction. Activation updates automatically after confirmation. Creating a workspace alone does not register the ID onchain. Token and receipt-only keys do not require activation.