Skip to content
OctaFuse OctaFuse

Providers

In Admin, open Inference → Providers. A Provider represents one upstream service account. Each record contains OpenAI-compatible, Anthropic, and Gemini endpoints, one upstream API key, and an active / disabled status. Create multiple Providers when you have multiple accounts at the same vendor.

OctaFuse Admin New Provider form with name, API key, status, and OpenAI, Anthropic, and Gemini endpoint settings.
Each Provider represents one upstream account and API key. Configure only the protocol base URLs or capability endpoints that account supports.

What to do in Admin

Section titled “What to do in Admin”
  1. In the sidebar under Inference, open Providers.
  2. Create or edit: set the display name, per-protocol endpoints (base or full capability URLs — follow upstream docs for /v1 paths), one API Key, status, and optional notes.
  3. Multiple accounts: create one Provider per vendor account, then add multiple Upstream Targets to the same Route Pool. Configure priority, weight, and distribution strategy under Routing.
  4. Import from catalog: use the built-in catalog to pre-fill endpoints; you still need a valid API Key. For Images, confirm generations (and edits when needed); see Images.
  5. After saving, go to Routing to bind models to this vendor and protocol; use Playground or Simulator to validate connectivity.

Gemini Generate Content

Section titled “Gemini Generate Content”

For standard Gemini services, set the Base URL to the path immediately before {model}, for example https://generativelanguage.googleapis.com/v1beta/models. For a non-standard upstream, use one Advanced models.generate template such as https://example.com/v1beta/models/{model}:{action}; {action} resolves to generateContent or streamGenerateContent at runtime. Legacy per-action templates remain readable, but new configuration should use the unified template.

Notes

Section titled “Notes”
  • Wrong base URLs / endpoints often show up as 404/401 — double-check upstream docs.
  • This screen does not include a one-click connectivity test; validate via routes + Playground / Simulator.
  • When the upstream rotates a key, replace it here. Use multiple Providers and Route Targets for gradual cutover or backup accounts.

Automation

Section titled “Automation”

For bulk changes from your backend, use the admin HTTP API — see the GitHub technical reference.

Next

Section titled “Next”