Extract model catalog into a single models.md; point chat + API docs at it

This commit is contained in:
inference-bot committed 2026-09-23 20:47:38 -06:00
1 parent 5724b0ca2f
commit c6b659aeef
5 files changed
+52 -66

No files matched your search

+1
View File
@@ -11,6 +11,7 @@ funded through our [Open Collective](https://opencollective.com/inference-cooper
## Start here
- **New here?** → [Getting started](getting-started.md) — join, use the chat, and get involved in governance.
- **Which models can I use?** → [Models](models.md) — the full catalog of providers and models.
- **Want API access?** → [API access](api-access.md) — use our models programmatically.
- **Curious how it works?** → [Infrastructure](infrastructure.md) — a map of the stack and the codebase.
+2 -34
View File
@@ -9,43 +9,11 @@ client works.
- **Base URL:** `https://gateway.inference.coop/v1`
- **Auth:** a bearer API key (create one in the [Member Dashboard](https://dashboard.inference.coop))
- **Format:** OpenAI chat completions — `POST https://gateway.inference.coop/v1/chat/completions`
- **Models:** see the table below.
- **Models:** see the [model list](models.md).
API usage draws from the **same monthly allowance as chat** — there's no separate
quota.
## Models
Models are named `provider/model-name`, so you can choose not just *which* model
but *where* it runs. Providers carry a value you can route by:
| Model | Provider | Value |
|---|---|---|
| `deepseek-v4-1-flash` | Tinfoil | **private** (TEE) |
| `gpt-oss-120b` | Tinfoil | **private** (TEE) |
| `glm-5-3-flash` | Tinfoil | **private** (TEE) |
| `greenpt/green-r` | GreenPT | **green** (renewable) |
| `greenpt/green-l` | GreenPT | **green** (renewable) |
- **Tinfoil** — *private*. Models run inside hardware enclaves (TEEs) with
end-to-end encryption, so neither we nor the provider can read your prompts
or responses. Best privacy.
- **GreenPT** — *green*. Models served on 100% renewable energy in the EU.
Cleaner energy, standard (non-enclave) hosting.
> **Note:** the three Tinfoil models currently use their bare names (no
> `tinfoil/` prefix). They'll be renamed to `tinfoil/deepseek-v4-1-flash` and so
> on in an upcoming change — we'll email members before that happens. GreenPT
> models already use the `greenpt/` prefix.
**Which to pick:**
- `deepseek-v4-1-flash` — default; best for agentic tasks (1M context, tool calling).
- `gpt-oss-120b` — lightweight fallback.
- `glm-5-3-flash` — fast, efficient MoE model.
- `greenpt/green-r` — reasoning, renewable energy.
- `greenpt/green-l` — lightweight, renewable energy.
## Get a key
Log in to the [Member Dashboard](https://dashboard.inference.coop) and create an
@@ -89,7 +57,7 @@ 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:** one from the table above, e.g. `deepseek-v4-1-flash` or `greenpt/green-r`
- **Model:** one from the [model list](models.md), e.g. `deepseek-v4-1-flash` or `greenpt/green-r`
A typical provider entry looks like:
+1 -1
View File
@@ -39,7 +39,7 @@ with the account you created in step 1.
- **Choose your model.** You can pick not just *which* model but *where* it runs:
**private** (Tinfoil, runs in encrypted enclaves) or **green** (GreenPT, 100%
renewable energy). See [API access](api-access.md#models) for the full list.
renewable energy). See the [model list](models.md) for the full list.
- **Web search** is enabled by default (self-hosted, no external dependency).
- **File uploads** work out of the box — ask the chat about a document you attach.
- Your usage draws from your monthly allowance; you can see it on the
+7 -31
View File
@@ -100,38 +100,14 @@ Questions about the Git itself? Write to info@inference.coop.
## Models and providers
The co-op serves models from multiple providers, named `provider/model-name` so
members can choose both *which* model and *where* it runs. Each provider carries
a value you can route by:
The co-op serves models from multiple providers (Tinfoil for privacy, GreenPT
for renewable energy, PublicAI coming soon). See the [model list](models.md) for
the current catalog — that's the single source of truth for which models are
available and how they're named.
| Provider | Value | How it works |
|---|---|---|
| **Tinfoil** | *private* | Models run inside hardware enclaves (TEEs); request/response bodies are encrypted end-to-end (EHBP), so even Tinfoil's infrastructure can't read them. Verifiable via remote attestation. |
| **GreenPT** | *green* | Models served on 100% renewable energy in the EU. Standard (non-enclave) hosting — cleaner energy, but privacy is a policy commitment, not architectural. |
| **PublicAI** | *public* | (coming soon — publicly developed models.) |
Five models are currently exposed:
- **DeepSeek V4.1 Flash** (`deepseek-v4-1-flash`) — default, agentic tasks. *(Tinfoil)*
- **GPT-OSS 120B** (`gpt-oss-120b`) — lightweight fallback. *(Tinfoil)*
- **GLM-5.3 Flash** (`glm-5-3-flash`) — fast, efficient. *(Tinfoil)*
- **Green-R** (`greenpt/green-r`) — reasoning, renewable energy. *(GreenPT)*
- **Green-L** (`greenpt/green-l`) — lightweight, renewable energy. *(GreenPT)*
The three Tinfoil models currently use their bare names (no `tinfoil/` prefix);
they'll be renamed to `tinfoil/…` in an upcoming, announced change.
A local Tinfoil proxy sidecar handles the enclave encryption on our side of the
gateway.
The honest caveat: only **Tinfoil** offers architectural privacy. The other
providers are chosen for their value (renewable energy, public models) but do
not run in enclaves — prompts and responses pass through them in the ordinary
way. Your **chat history** is also stored on our server so you can revisit it,
and that stored history is not encrypted in a way that prevents us from
technically reading it — we commit not to. The full distinction — what's
architecturally private versus what's a policy commitment — is in the
[Privacy Policy](privacy-policy.md).
One infra detail worth knowing: a local Tinfoil proxy sidecar handles the
enclave encryption on our side of the gateway — only Tinfoil traffic goes
through it; the other providers are called directly.
## Security posture (plain language)
+41
View File
@@ -0,0 +1,41 @@
# Models
The co-op serves models from multiple providers. This is the single list — both
the chat and the API draw from it, so it's the one place to look (and the one
place to update).
## Naming
Models are named `provider/model-name`, so you can choose not just *which* model
but *where* it runs. The provider part tells you the value it stands for:
| Provider | Value | What it means |
|---|---|---|
| **Tinfoil** | *private* | Models run inside hardware enclaves (TEEs), and requests/responses are encrypted end-to-end (EHBP), so neither we nor the provider can read your prompts or responses. Verifiable via remote attestation. |
| **GreenPT** | *green* | Models served on 100% renewable energy in the EU. Cleaner energy, but standard (non-enclave) hosting — privacy here is a policy commitment, not architectural. |
| **PublicAI** | *public* | (coming soon — publicly developed models.) |
## Current models
| Model | Provider | Value | Notes |
|---|---|---|---|
| `deepseek-v4-1-flash` | Tinfoil | **private** | Default; best for agentic tasks (1M context, tool calling). |
| `gpt-oss-120b` | Tinfoil | **private** | Lightweight fallback. |
| `glm-5-3-flash` | Tinfoil | **private** | Fast, efficient MoE model. |
| `greenpt/green-r` | GreenPT | **green** | Reasoning, renewable energy. |
| `greenpt/green-l` | GreenPT | **green** | Lightweight, renewable energy. |
> **Note:** the three Tinfoil models currently use their bare names (no
> `tinfoil/` prefix). They'll be renamed to `tinfoil/deepseek-v4-1-flash` and so
> on in an upcoming change — we'll email members before that happens. GreenPT
> models already use the `greenpt/` prefix.
## The honest caveat
Only **Tinfoil** offers architectural privacy. The other providers are chosen
for their value (renewable energy, public models) but do not run in enclaves —
prompts and responses pass through them in the ordinary way. Your **chat
history** is also stored on our server so you can revisit it, and that stored
history is not encrypted in a way that prevents us from technically reading it —
we commit not to. The full distinction — what's architecturally private versus
what's a policy commitment — is in the [Privacy Policy](privacy-policy.md).