Skip to main content

Quickstart

Terminal exposes an OpenAI-compatible Chat Completions endpoint.

1. Set your API key

Contact the Terminal team to request access.

2. Choose latency and cost per request

Different agent steps have different requirements. Use Standard when a user is waiting, and use Flex when a background step can trade time for lower cost. Both windows use the same endpoint. Add service_tier: "flex" when the request can be patient. Terminal charges per token and stays fully serverless, so you do not need to manage deployments or plan around rate limits. For finer request-level control, Terminal is adding SLA headers for latency and cost preferences. See Custom SLAs.

3. Make a Standard window request

Standard is the default window. It is designed for fast responses.

4. Make a Gemma Flex window request

Flex uses the same endpoint and waits for completion. It is designed for async-style workloads where cost matters more than latency. Allow long client timeouts.

Request shape

service_tier is optional. If omitted, Terminal uses standard.