Glossary
This page lists the technical words of Tollgate and the meaning of each word.
All Tollgate documents use these words with these meanings only. If a document needs a new technical word, add it to this page in the same pull request.
Technical names
| Word | Meaning |
|---|---|
| access log | The JSON line that Tollgate writes for each request. It has metadata only, never bodies or keys. |
| adapter | The code that sends requests to one kind of provider, for example Anthropic or Vertex AI. |
| admin port | The second listener of Tollgate. It serves metrics, the admin API, and the dashboard. By default, it listens on 127.0.0.1:9090. |
| admin token | The bearer token that the admin port needs when it is not on a loopback address. |
| ADR | Architecture decision record. One file in docs/adr/ that records one design decision. |
| budget | The maximum spend for a tenant in a window, in USD. |
| cache read tokens | Input tokens that the provider reads from its prompt cache. They cost less than other input tokens. |
| cache write tokens | Input tokens that the provider writes to its prompt cache. |
| circuit breaker | A switch for each provider, model, and region. When too many requests fail, the breaker opens, and Tollgate sends no requests to that target for a period. |
| connect timeout | The longest time that Tollgate waits for a connection to a provider. |
| data plane | The listener that receives client requests. By default, it listens on :8080. |
| drain | The shutdown steps: Tollgate refuses new requests and lets open streams finish. |
| error event | An event that Tollgate adds to a stream when the provider fails after the first byte. Then Tollgate closes the stream. |
| exact cache | A cache that returns a stored response only for a request with the same bytes and the same tenant. |
| fail closed | To refuse a request when Tollgate cannot check a limit. Hard budgets fail closed. |
| fail open | To send a request when Tollgate cannot check a limit. Rate limits fail open. |
| fake provider | The test server in cmd/fakeprovider. It speaks the Anthropic and OpenAI wire formats. |
| fallback | To send a request to the next target after a failure. |
| first byte | The first byte of the response that Tollgate sends to the client. After the first byte, Tollgate does not fall back. |
| first-token timeout | The longest time that Tollgate waits for the first part of a response from a provider. |
| gateway overhead | The time in Tollgate before the first upstream request, without the time to read the request body. |
| golden file | A file in testdata/ that holds the expected bytes of a response. Tests compare the output of Tollgate with it. |
| hard budget | A budget that stops requests when the spend reaches the limit. |
| inter-token latency | The mean time between two output tokens of one stream. |
| idle timeout | The longest time between two parts of a response body. It is also the longest time to write one part to the client. |
| limit store | The store of the rate limit and budget counters: memory for one copy, Redis for two or more copies. |
| local limit | The rate limit that each copy keeps in memory and uses when Redis is not available. |
| micro-USD | One millionth of a US dollar. Tollgate stores all amounts in micro-USD. |
| overspend | The spend over the limit of a hard budget. Its largest value is in docs/limits.md. |
| OTLP | OpenTelemetry Protocol. The protocol that Tollgate uses to send spans to a trace receiver. |
| preflight | The step that reads the model and the stream setting of a request and estimates its tokens and cost. |
| price table | The list of prices for each provider and model, by date. The default is pricing.yaml. |
| provider | A service that runs LLMs, for example Anthropic, OpenAI, Vertex AI, or Ollama. |
| rate limit | The maximum number of requests or tokens for a tenant in one minute. |
| relay | The step that sends the provider response to the client and reads a copy of it. |
| request ID | The ID that Tollgate gives to each request. It is in the x-request-id header and in the access log. |
| reservation | An estimated cost that Tollgate adds to a budget before it sends a request. |
| retry budget | The maximum ratio of retries to requests. |
| route | The configuration for one model name that clients send. It gives the API format and the list of targets. |
| session | A group of requests from one agent task. |
| settle | To replace a reservation with the real cost after the response. |
| span | One timed step of a request in a trace, for example one upstream attempt. |
| sliding-window counter | The method that Tollgate uses to count requests and tokens for the last 60 seconds from two one-minute counters. |
| soft budget | A budget that only gives a warning when the spend reaches the limit. |
| SSE | Server-sent events. The stream format that Anthropic and OpenAI use. |
| STE | ASD-STE100 Simplified Technical English. The writing rules for Tollgate documents. |
| sticky routing | To send all requests of one session to the same target. |
| Application Default Credentials | Google credentials that a library finds from the environment, a local login, or the host identity. |
| cooldown | The time after a 429 during which a target gets no requests. |
| half-open | The breaker state that permits one test attempt. |
| Ollama | A local model server with an OpenAI-compatible API. |
| Vertex AI | The Google Cloud service that hosts Claude models. |
| target | One provider and one model in the list of a route. |
| time to first token | The time from the start of a request to the first byte of the response body. |
| trace | The spans of one request. Each request is one trace. |
| tenant | A user or a team that has its own keys, limits, and budgets. |
| total timeout | The longest time for one full upstream request. |
| usage event | The record of one request: tokens, cost, timing, and status. |
| usage file | The JSONL file with one usage event for each request. |
| virtual key | A key that Tollgate gives to a client. It starts with tg_. It is not a provider key. |
| window | The period of a budget, for example a month or a session. |
Word choices
Use the word in the first column. Do not use the words in the second column.
| Use | Do not use |
|---|---|
| make | create, generate (except in names of API endpoints and commands) |
| start | launch, spin up, kick off, boot |
| stop | kill, shut off |
| send | fire, dispatch, push |
| show | display, print out |
| find | look up, locate |
| use | utilize, leverage |
| fail | break, blow up |
| request | call (as a noun) |