Clients & attribution

A client is one of your end customers. If you build models for several companies — or run one product with per-customer models — clients let you see usage and cost for each of them and re-bill accurately.

Creating clients

Open Clients in the console and add a client with a name, an optional external reference (for example, the customer id in your billing system) and an optional markup percentage. Clients can be archived; archived clients keep their history.

What can be assigned

• Adapters — for organization only; doesn’t affect attribution.
• Deployments — usage through the deployment is attributed to its client unless the key says otherwise.
• API keys — a client-scoped key attributes every request to its client and limits what it can call.

Attribution rule

Each request is attributed to exactly one client, or to none:

1. If the API key is assigned to a client, that client.
2. Otherwise, if the deployment is assigned to a client, that client.
3. Otherwise, no client (shown as “Unassigned” in reports).

A client-scoped key can call only deployments assigned to the same client or to no client. Calling another client’s deployment returns 403 deployment_not_allowed_for_key. Give each client’s application its own client-scoped key.

Reports and markup

Each client has a report for any date range showing requests, input and output tokens, cost at your Basevex rates, and — if you set a markup — the amount to bill with markup applied. Reports export as CSV, and their totals match your usage dashboard for the same range.

Markup is for your own invoicing only; it doesn’t change what Basevex charges you.

Client spend caps

Owners and billing managers can give a client a monthly spend cap. Billable requests attributed to that client are refused once the month’s spend would exceed it, without affecting your other clients. See Usage & billing.