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

# Resell a Private Model

> Give each customer an isolated Planck key for a private or fine-tuned model while keeping the upstream provider credential secret.

Use the Enterprise Customer Portal when your consultancy operates a model for
multiple customers and wants customer-level authentication, limits, and usage
without exposing the upstream provider credential.

The request path is:

<Steps>
  <Step title="Customer application">
    The customer calls Planck's OpenAI-compatible endpoint with its own
    `sk-cp-...` Planck key.
  </Step>

  <Step title="Planck gateway">
    Planck identifies the customer workspace, applies its limits and access
    policy, and records its usage separately.
  </Step>

  <Step title="Private upstream model">
    Planck routes the request through the consultancy-owned provider credential.
    The customer never receives that credential.
  </Step>
</Steps>

## Fireworks private or fine-tuned models

Fireworks is supported as a normal BYOK provider. The model does not need to be
in Planck's public registry: an unknown model with an explicit provider route
stays BYOK-only and is forwarded with the exact upstream model ID.

In **Enterprise → Customer Portal**:

1. Create or open a customer.
2. Open **Upstream model** and connect a Fireworks API key owned by the
   consultancy.
3. Pin the exact model route. For example:

```text theme={null}
fireworks/accounts/your-account/models/customer-support-v2
```

4. Open **Planck keys**, create a customer key, and copy it once.
5. Give the Planck key and model route to the customer. Do not give them the
   Fireworks key.

The customer can then use the standard OpenAI client:

```python theme={null}
from openai import OpenAI

client = OpenAI(
    api_key="sk-cp-...",
    base_url="https://api.inquantum.ai/v1",
)

response = client.chat.completions.create(
    model="fireworks/accounts/your-account/models/customer-support-v2",
    messages=[{"role": "user", "content": "Hello"}],
)
```

<Note>
  Customer Portal keys do not fall back to Planck-through-billing. They use the
  upstream credential assigned by the consultancy, which keeps costs and
  provider ownership under the consultancy's control.
</Note>

## What is isolated per customer

* Planck API keys and revocation
* Request and cost usage
* Monthly request and cost limits
* Members and workspace access
* Model-access policies when configured

The upstream provider credential remains in the parent consultancy workspace
and can be assigned without exposing its raw value.

<Warning>
  The portal workflow covers supported providers such as Fireworks using their
  exact private model IDs. An arbitrary self-hosted base URL uses Planck's
  separate custom-target allowlist and is not configured through this portal.
</Warning>