Decks

Enterprise

Three changed lines.One new contract.

Your code keeps the OpenAI shape; the base URL, key and model string move to Decks. Everything else about the enterprise agreement is scoped credentials, capacity and billing — set up while you integrate.

Contact Us Read the API docs

Credentials

One key per application, scoped end to end.

  1. 01

    Issue

    One credential per application and environment. Live and test keys are separate from day one.

    dk_live_… · dk_test_…

  2. 02

    Scope

    Each key is restricted to the models that application actually uses — nothing else is reachable with it.

    allow: ["anthropic/claude-opus-5", "deepseek/deepseek-v4-pro"]

  3. 03

    Limit

    A rate limit and a monthly budget are attached to the key, so a runaway workload stops at its own ceiling.

    600 req/min · $2,000 / month

  4. 04

    Rotate

    Keys rotate or revoke without downtime — the old key keeps serving until the new one is live.

    old key expires T+24h after rotation

Migration

The entire migration, in one file.

This is a working call against the Decks endpoint. If your integration already speaks OpenAI, the diff is the constructor — the request body does not change.

chat/completions
from openai import OpenAI

client = OpenAI(
    base_url="https://api.decksdigital.ai/v1",
    api_key="YOUR_DECKS_API_KEY"
)

response = client.chat.completions.create(
    model="deepseek/deepseek-v4-pro",
    messages=[
        {
            "role": "user",
            "content": "Summarise this customer report."
        }
    ]
)

print(response.choices[0].message.content)

Selecting a different model is a different string in the same request — browse the catalogue for the full list.

Next step

Start your integration.

Engineering integrates against the docs while we set up credentials, capacity and billing for your account — in parallel, not in sequence.

Read the API docsContact Us