- tinfoil/nomic-embed-text is now member-facing ($0.016/1M per Tinfoil's
catalog, TEE-protected, 768-dim, 8K ctx) — the model the co-op's own docs
search runs on inside the TEE.
- greenpt/green-embeddings added ($0.20/1M, 2560-dim measured, 32K ctx) — the
only genuinely distinct other embedding model in GreenPT's catalog.
- Embedding table now lists all three with pricing; quick-guide bullet updated.
- whisper-large-v3-turbo: $0.01 per request (flat, zero per-token) — the old
$0.05/1M-input row was stale (co-op/support#48)
- voxtral-tts: $0.002 per request (was 'listed $0 (verify on invoice)')
- new: tinfoil/voxtral-small-24b, Tinfoil's token-priced STT model
($0.20/1M in + $0.60/1M out), with the chunk-equivalent note for the
transcription route and a chat-with-input_audio example
- note why dashboard audio rows read '$0.01 · 0 tokens' (Tinfoil returns no
token usage for audio)
New gateway model (code/litellm 54925ca): /v1/embeddings, GreenPT-hosted,
4096-dim (measured through the gateway), $0.25/1M input from GreenPT's own
pricing, 32K input cap (provider catalog). Not a chat model — API-only like
the audio models, hidden from the chat picker. Also states plainly that
Tinfoil's nomic-embed-text is the operator-only docs-RAG embedding, since a
member read its absence from the model list as removal.
Metering on /v1/systemone is live: each call is billed at $0.12 per 1M
input tokens, computed from the exact token count GreenPT returns and
attributed to the calling member key. Replace the "not yet metered"
warnings in models.md and api-access.md with the accurate position.
(metering verified 2026-11-03; code/litellm patch_passthrough_token_cost.py)
models.md claimed decisions count toward the member allowance. Verified today that a
/v1/systemone call registers no spend against the calling key, so the claim was wrong.
States the gap plainly instead. api-access.md now names the decisions route, the fact
that it is not an OpenAI chat endpoint, and the metering caveat.
Add a Decisions section: Metis returns probabilities/choices/scores rather than
text, is called at /v1/systemone with a member's normal gateway key, is
GreenPT-hosted (policy-based privacy, EU, renewable), and is metered
approximately (flat per-call estimate, not exact tokens).
The policy described chat history and enclave models carefully but never addressed
the API path, and §2 read as though all content is retained — which is wrong for
members using their own keys.
Verified before writing, rather than restating policy language: a request with a
distinctive marker was sent through the gateway and searched for afterwards. It
appears nowhere in the gateway's logs, `litellm_settings` enables no content
logging, and the request records carry usage fields only (model, tokens, cost, key).
- privacy-policy.md §2: content retention now depends on the surface, with a pointer.
- privacy-policy.md §4: new subsection on API requests, including the two limits that
stop it being read as more than it says — we can still link a request to a key and
therefore a member, and "not stored by us" says nothing about the provider.
- api-access.md: a "what we store" section, since that is the page an API user reads
before worrying about it.
- models.md: the privacy-limitations section now distinguishes chat from API.
The provider's published catalog says this model takes 30K input and has no
vision support. Both of those are wrong. Sent through our own gateway:
- an image returns the right answer ("Red" for a solid red PNG)
- prompts of 32K, 70K, 130K and 262K input tokens are all accepted, with
Regolo's own usage accounting reporting prompt_tokens=262021
Our own description of the v1.5 generation — image understanding and a 262K
context window — matches what the model demonstrably does, which is why the
figure goes to 262K. The old 65K undersold the model by roughly 4x.
Regolo's meta-model for qwen3.5-122b says 120K; it processed 262,023 tokens and
still followed the instruction at the end, so that row's 262K is confirmed as
written and is left alone.
Adds a line under the table recording that context figures here are measured
through the gateway rather than copied from provider catalogs, because that
difference is exactly what caused a member to report this as an error.
inference-bot
inference-bot
inference-admin