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

# Account & keys

> Get an Unpod account, find your org handle and API key, and know which credential each path needs.

Every developer path needs the same two things: an Unpod org, and the right
credential for the surface you call. This page gets you both in a few
minutes.

**1. Request access**

Open [unpod.ai](https://unpod.ai/), click **Request a Call Back**, fill in the
form and submit it. Your login credentials arrive by email.

![Request a Call Back form on unpod.ai](https://mintcdn.com/unpodai/oJhXffLbYN4-as7f/images/Introduction2.png?fit=max\&auto=format\&n=oJhXffLbYN4-as7f\&q=85\&s=75e61c22dcefa97566f0f558e982ab9d)

**2. Sign in and create your hub**

Click **Sign In** on [unpod.ai](https://unpod.ai/). On first login you create
a hub for your organization:

| Field | What to enter |
| - | - |
| **Hub name** | Your organization's name |
| **Domain name** | Your org's domain, e.g. `acme.com` |
| **Privacy type** | **Private** (only people on your domain see it) or **Public** |
| **Type of account** | The option closest to how you use Unpod |

![Create hub form shown on first login](https://mintcdn.com/unpodai/oJhXffLbYN4-as7f/images/Introduction5.png?fit=max\&auto=format\&n=oJhXffLbYN4-as7f\&q=85\&s=8512d1e4953a00ec025ec49f133e91fb)

**3. Generate an API key**

1. Click **Settings** at the bottom of the left sidebar.
2. Under **Access**, click **API keys**.
3. Click **Generate New**, then copy the key.

Only the workspace owner sees **Access**. You can hold one key at a time:
delete the old key to generate a new one.

**4. Put both in your environment**

```bash .env theme={null}
UNPOD_BASE_URL="https://unpod.ai"
UNPOD_SERVICE_BASE_URL="https://unpod.ai"   # bare host - no path
UNPOD_PLATFORM_TOKEN="..."                  # the API key from step 3
UNPOD_ORG_HANDLE="your-org"                 # your organization's domain handle
```

`import unpod` loads `.env` from the working directory. The SDK sends them as
`Authorization: Token <key>` and `Org-Handle: <handle>`; call the REST API
directly with the same two headers.

## Which credential is which

Unpod's credentials are not interchangeable:

| You are calling | Host | Auth | Where it comes from |
| - | - | - | - |
| **Python SDK** (agents, numbers, calls) | `unpod.ai` | `UNPOD_PLATFORM_TOKEN` + `UNPOD_ORG_HANDLE` | API key + org handle, above |
| **AgentRunner** (your own brain) | the orchestrator | `UNPOD_PLATFORM_TOKEN` + `UNPOD_ORG_HANDLE` | API key + org handle, above |
| **Platform REST API** | `unpod.ai` | `Authorization: Token` + `Org-Handle` headers | API key + org handle, above |
| **Chat API** (your agent as a model) | `inference.unpod.ai` | `Authorization: Bearer` endpoint key | Playground → **Deploy as Endpoint** |

Token auth (`UNPOD_PLATFORM_TOKEN` + `UNPOD_ORG_HANDLE`) wins over
`UNPOD_API_KEY` when both are set. Analytics and telephony calls need token
auth, so use the token.

## Next

> [card] [Quickstart](https://docs.unpod.ai/home/quickstart.md)
>
> Six SDK calls: your phone rings and an agent speaks.

> [card] [Core concepts](https://docs.unpod.ai/get-started/core-concepts.md)
>
> How Unpod fits together, and every term defined once.


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