Authentication

Every client request carries an API key as a bearer token:

curl -sS "https://llms.party/v1/models" \
  -H "Authorization: Bearer $LLMS_PARTY_KEY"

const response = await fetch('https://llms.party/v1/models', {
  headers: { authorization: `Bearer ${process.env.LLMS_PARTY_KEY}` },
});
const { data } = await response.json();
console.log(data);

import os
import requests
 
response = requests.get(
    "https://llms.party/v1/models",
    headers={"Authorization": f"Bearer {os.environ['LLMS_PARTY_KEY']}"},
    timeout=30,
)
print(response.json()["data"])

Keys are issued by your administrator. Each key is bounded in three ways:

Grants are frozen when a key is issued

A key's model access is recorded at creation time. Adding a model group does not extend existing keys; ask for a new key. GET /v1/models is the authoritative list for a key.

Read your balance

GET /v1/usage returns the calling key's budget, spend and model access. Use it to show a remaining balance or explain a budget error; the fields are documented under Usage and balance.

Try a key from this page

The playgrounds keep the key in this tab's sessionStorage and send it only to the gateway. This panel is shared by every playground on the page.

Status codes

Rotation and revocation

Ask your administrator for a new key when one may have leaked. Revocation takes effect on the next request; there is no cache to wait out.