Stravia Docs

Core concepts

Stravia separates an upstream model service from the model name a client calls. These guides explain the main objects and show where to look when an interaction succeeds, fails, or reports incomplete usage.

Understand the request path

  1. A model service stores how Stravia connects to an upstream provider or compatible endpoint. Its credential is not the client API key.
  2. A Model ID is the name the client sends. Its configured, enabled destination selects a service and upstream model.
  3. An API key authenticates a client and can restrict which Model IDs it may use. MCP access, expiration, concurrency, and automatic capability injection are separate controls—not alternative names for model permission.
  4. Request history records the interaction and its outcome. Usage aggregates values the upstream reports; missing values are not zero and are not a precise bill.

Use Concepts for the vocabulary and Models and routing for the distinction between client IDs and upstream destinations.

Find the guide for your task

  • Model services : connection details, authentication, model inventory, and sync status.
  • Models and routing : Model IDs, enabled destinations, selection, and fallbacks.
  • API keys : model access, expiry, concurrency, MCP permission, and injection settings.
  • Request history : completed and failed interactions, attempts, tools, and sensitive-data boundaries.
  • Usage and allowances : upstream-reported usage versus provider-specific quota snapshots.

Diagnose by stage

If Stravia cannot connect to a service, inspect that service's authentication and endpoint before changing the API key. If the client receives an authorization error, check whether its key is active and permits the exact Model ID. If the Model ID is unavailable, check that both the model and at least one destination are enabled. After an invocation, use Request history for its status; use Usage for reported totals, not as a substitute for a detailed interaction record.

Continue

For the first end-to-end setup, follow Quick start . For optional platform capabilities, see Advanced features .