Capabilities
Two planes, two credentials
LTG exposes a management plane for provisioning and reporting, and an inference plane that applications call. They use different hostnames and different credentials.
Token keys start with
ltg_sk_. The inference plane rejects Telnyx account API keys and provider secrets; the management plane rejects token keys. Keep every credential in a trusted backend or secret store, never in browser code, source control or logs.
How it works
- Create a token group with an explicit
allowed_modelslist and optional budget and rate limits. To use your own OpenAI or Anthropic account, attach a provider key to the group. - Issue a token key in that group, optionally bound to a token user. The secret is returned once, on the create response.
- Call models from the application with an OpenAI SDK (or, for Anthropic BYOK models, an Anthropic SDK) pointed at the inference base URL and authenticated with the token key.
- Inspect usage with the spend events and spend summary endpoints, filtered by group, user, key or end user.
- Revoke the key when the application no longer needs it. New admissions stop immediately; spend history is retained.
cost values use a flat reference rate for enforcement and attribution; see Budgets.
Next steps
Quickstart
Create a group, issue a token key, make a request and revoke the key.
Inference API
Telnyx-hosted and BYOK models, OpenAI and Anthropic SDK configuration, streaming, request limits and supported fields.
Management API
Groups, users, keys, end users and provider keys, with idempotency and ETag rules.
Budgets and rate limits
How each control is enforced and what happens at the limit.
Bring your own key
Use your own OpenAI or Anthropic key; your provider bills those requests.
Usage reporting
Spend events, dimensional summaries and snapshot pagination.
Errors
Status codes, structured error codes and how to handle them.