> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.alephant.io/docs/overview/core-concepts/provider-virtual-keys/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.alephant.io/_mcp/server.

# Provider & Virtual Keys

> Understand the difference between Master Keys and Virtual Keys

Alephant operates on a dual-key architecture, ensuring security and granular cost tracking.

## Provider Keys (Master Keys)

**Provider Keys** are your raw, Bring-Your-Own-Key (BYO-KEY) credentials from providers like OpenAI, Anthropic, or Azure.

* They are securely encrypted at rest (AES-256).
* End users never see these keys.
* You can map multiple Virtual Keys to a single Provider Key.

## Virtual Keys (VKs)

**Virtual Keys** are proxy credentials generated by Alephant.

* **The Sole Billing Axis:** All usage metering, billing, and budget limits in Alephant are tied to Virtual Keys.
* **Bound to Entities:** A VK is either bound to an **Agent** or a **Member**.
* **Independent Controls:** Each VK can have its own budget. If a VK exceeds its limit, it can be configured to alert administrators or automatically block further requests.

### Virtual Key Expansion

Each subscription tier includes a base number of VKs. If you need more, you can purchase **VK Expansions** via the billing dashboard (available on Pro and higher).

> Understand the difference between Master Keys and Virtual Keys