Providers reference

This page is the authoritative provider contract for Diffgazer. It lists every add-now, experimental, deferred, and rejected candidate exactly once and documents the nine selectable products. For the conceptual overview, see providers and models.

Diffgazer exposes nine selectable products in Web, Ink, and CLI setup. Each product is a distinct hosted API transport contract with its own credential kind, endpoint profile, exact-model policy, admission checks, billing/privacy notice, and enablement gate. Nothing outside this list is selectable.

The selectable roster is: Google Gemini, Z.AI, OpenRouter, DeepSeek, Qwen International, Moonshot Open Platform, MiniMax International, Ollama Cloud, and OpenCode Zen.

Each product's billing and privacy notice (the Privacy/billing column below) is shown for information wherever you configure it — the setup wizard, Configure Provider, and the provider details pane. You accept the sending of repository content once, globally, in the setup wizard or in the Provider data notice that opens before the first action that would send it; after that a configuration's notice is acknowledged for you when it is saved, and you are only asked again for a product whose notice materially changed. See configuration.

The matrix below is frozen documentation. A compatible endpoint, free credit, or local binary cannot override the frozen verdict at runtime. Experimental, deferred, and rejected rows remain non-runnable until a separately acknowledged scope satisfies the listed falsifier. Skipped live probes are evidence only; they never enable a product.

Add-now products

Experimental candidates

Deferred candidates

Rejected candidates

Each saved provider setup is a versioned configuration identified by configurationId, revision, and an immutable execution fingerprint. The local API exposes six generic actions on POST /api/config/actions:

Client-safe responses never include literal secrets, environment values, auth paths, or raw diagnostics. See Configuration and Local API reference.

A record this build cannot decode — one whose product has since been retired, or one a newer build wrote — is kept on disk byte for byte and listed separately as an unrecognized configuration. Both the web app and the TUI show it in the provider list under its configurationId and offer delete and nothing else, so retiring a product never leaves a configuration you can only remove by hand-editing config.json.

Hosted add-now products accept either a stored literal credential or an environment reference.

When you choose an environment reference, Diffgazer stores only the variable name and reads the live value at runtime. See Environment variables for the hosted reference names.

• Providers and models — how Diffgazer chooses and validates models.
• Configuration — where configurations are stored.
• Environment variables — hosted credential reference names.
• Troubleshooting — readiness and review failure remediation.