Understand why Singular behaves this way

Build a mental model of routing, model identity, provider fallbacks, and the boundary between public and role-gated surfaces.

ExplanationAvailability: Informational

On this page

Build the right mental model
Use explanation with reference

Choose by what you need to do

Four paths through the documentation

TutorialsLearnLearn Singular by completing a working request from key claim through streaming.How-to guidesSolveComplete a specific integration, key-management, application, or per-call payment task.ExplanationUnderstandUnderstand model identity, automatic routing, fallbacks, and role-gated platform boundaries.ReferenceReferenceFind exact request fields, compatibility, routing, streams, billing, and limitations.

Build the right mental model

Explanation pages connect implementation details into a coherent view of Singular. Read them when exact field definitions are not enough to explain model identity, automatic selection, fallbacks, or commercial control-plane boundaries.

Start with how models and routing work to understand the live catalog, explicit IDs, Auto routing, provider health, and ordered fallbacks.

Read partner and operator roles to understand why reseller, white-label, affiliate, and operator workflows remain separate from the public inference API.

Use explanation with reference

Explanation describes why the system is shaped this way. Use the reference section for exact endpoints, accepted fields, statuses, and error behavior.

In this section

Explanation

01How routing worksUnderstand the live catalog, explicit and automatic model selection, provider health, and fallback behavior.02Partner and operator rolesUnderstand the role-gated commercial and control-plane surfaces without confusing them with the public model API.