Overview
Use Terminal to run OSS models through a fully serverless, OpenAI-compatible API built to scale to trillions of tokens every day.Why Terminal for agents
Agent workloads are not one-size-fits-all. An interactive coding step may need fast tokens now, while a background review, eval, or research job can wait if that makes it cheaper. Terminal lets you choose that tradeoff per request. Use the Standard window for interactive work, use Flex when a job can be patient, and use request-level SLA headers as they become available for finer latency and cost control. You only pay per token. Terminal is serverless by default, with no deployments to manage and no rate limits to size around.Base URL
Endpoint
Authentication
Terminal is currently invite-based. To request an API key, email shubham@terminal.fyi. All examples in these docs use the placeholderTERMINAL_API_KEY.
First request
Current models
| Model | ID | Good for |
|---|---|---|
| Gemma 4 31B | gemma-4-31b | Cheap multimodal/general chat workloads |
| MiniMax M3 | minimax-m3 | Long-context, agentic, and multimodal workloads |
Service windows
| Window | Use when | Behavior |
|---|---|---|
| Standard | You need interactive latency | Fast responses, 100+ tokens/sec on average |
| Flex | You can wait to reduce cost | Same endpoint waits for completion, usually 5-20 minutes |
Next steps
- Quickstart: make your first Chat Completions request.
- Service tiers: choose Standard or Flex windows.
- Models & pricing: compare current model pricing.
- Model requests: request models that are not listed yet.