api-access: -green/-tee aliases, and a table of where they point today
Names now say which route rather than how fresh a version is, and the page answers the question the names raise: what each alias serves right now.
This commit is contained in:
1 parent
7f8480f13d
commit
481a9f40cd
1 file changed
+20
-6
+20
-6
@@ -98,8 +98,8 @@ endpoint configuration:
|
||||
- **API type / protocol:** "OpenAI compatible" (or `openai-completions` where a
|
||||
protocol string must be named) — not "Ollama", "Anthropic", or "Responses"
|
||||
- **API key:** your member key (the `sk-…` string)
|
||||
- **Model:** a **stable alias** — `deepseek-flash-latest`, `glm-flash-latest`, `deepseek-flash-tee`, or
|
||||
`glm-tee` — or any id from the [model list](models.md), e.g. `tinfoil/deepseek-v4-1-flash`
|
||||
- **Model:** a **stable alias** — `deepseek-flash-green`, `glm-green`, `deepseek-flash-tee`, or `glm-tee`
|
||||
— or any id from the [model list](models.md), e.g. `tinfoil/deepseek-v4-1-flash`
|
||||
|
||||
A typical provider entry looks like:
|
||||
|
||||
@@ -111,8 +111,8 @@ A typical provider entry looks like:
|
||||
"api": "openai-completions",
|
||||
"apiKey": "sk-your-key",
|
||||
"models": [
|
||||
{ "id": "deepseek-flash-latest" },
|
||||
{ "id": "glm-flash-latest" },
|
||||
{ "id": "deepseek-flash-green" },
|
||||
{ "id": "glm-green" },
|
||||
{ "id": "deepseek-flash-tee" },
|
||||
{ "id": "glm-tee" }
|
||||
]
|
||||
@@ -123,12 +123,26 @@ A typical provider entry looks like:
|
||||
|
||||
The four names in `models` are **stable aliases**: we re-point them when a
|
||||
provider retires or replaces a model, so a config that pins one keeps working
|
||||
across transitions. `-latest` is the default route for a family (renewable energy,
|
||||
policy-based privacy); `-tee` serves the same family inside attested hardware.
|
||||
across transitions. The suffix says which route: `-green` is the default
|
||||
(renewable energy, policy-based privacy), `-tee` serves the same family inside
|
||||
attested hardware. Each alias is paired, so the two routes sit side by side in the
|
||||
model list.
|
||||
Pricing is set at the alias, so a transition that changes price appears in the
|
||||
model list rather than arriving as a surprise. If you need one particular version,
|
||||
use the provider-prefixed id from the [model list](models.md) instead.
|
||||
|
||||
Where the aliases point today:
|
||||
|
||||
| Alias | Serves today | Route |
|
||||
| --- | --- | --- |
|
||||
| `deepseek-flash-green` | `greenpt/deepseek-v4.1-flash` | Renewable energy; policy-based privacy |
|
||||
| `glm-green` | `greenpt/glm-5.3-flash` | Renewable energy; policy-based privacy |
|
||||
| `deepseek-flash-tee` | `tinfoil/deepseek-v4-1-flash` | Confidential computing (TEE) |
|
||||
| `glm-tee` | `tinfoil/glm-5.3` | Confidential computing (TEE) |
|
||||
|
||||
*Points as of 2026-11-14. We re-point these when a provider retires or replaces a
|
||||
model; the alias names stay as they are, and this table changes with them.*
|
||||
|
||||
If a tool's own docs show a local-server example (e.g.
|
||||
`baseUrl: http://localhost:11434/v1` with `api: "openai-completions"`),
|
||||
substitute our base URL and your member key for `apiKey` — the protocol value
|
||||
|
||||
Reference in new issue
Block a user