Endpoint Types

Gloo AI Responses and Completions endpoints belong to one of three families. All three share the same model catalog, authentication, metering and rate limits. What differs is what runs around your request.

​

Pricing at a glance

Published rates are listed on Supported Models and returned by GET /platform/v2/models. See Billing & Plans for how credits are drawn down. Each family comes in both request shapes — the OpenAI-compatible Responses format and the Chat Completions format — so the family and the shape are independent choices for generation requests.

​

Guarded endpoints

Choose these when you want Gloo to handle safety for you. A guarded request runs Gloo’s full safety and values pipeline: input guardrails, output moderation, values-aligned (tradition) responses, model_family selection and opt-in auto-routing.

• Responses (POST /ai/v2/guarded/responses) — the Responses format with Gloo’s guardrails.
• Completions (POST /ai/v2/guarded/chat/completions) — fully supported, and the home of routing and model_family.

​

Direct endpoints

Direct endpoints send your request straight to the model you name. Gloo adds nothing between your prompt and the provider: no guardrails, no output moderation, no values-alignment, no routing. What you send is what the model sees; what the model returns is what you get. You can spot a direct endpoint by the /direct/ segment in its path. Use them when your application owns its own safety and prompting end to end — an agent framework with its own moderation, a backend that composes prompts itself, tooling that needs byte-faithful model behavior.

• Direct Responses (POST /ai/v2/direct/responses) — the default for new work that owns its own safety; multimodal.
• Direct Completions (POST /ai/v2/direct/chat/completions) — for existing Chat Completions tooling.
• Anthropic Messages (POST /ai/v2/direct/anthropic/v1/messages) — Anthropic’s Messages API for Claude models, for code built on the Anthropic SDKs. It serves Claude only, has no provider failover, and returns an error for a retired model instead of serving its replacement.

​

What runs, and what does not

Direct means direct about content, not a bypass of the platform: Still applies on direct Responses and Completions requests:

• Authentication (Bearer API key) and organization entitlement
• Usage metering and billing
• The Gloo model catalog — you address models by their gloo-* Model ID
• Provider resiliency. Gloo serves the model you asked for, but not always from the same place: when the provider currently serving it is failing or unhealthy, your request fails over to another provider that serves the same model, and a stream cut mid-answer can be continued on a fallback provider. The model you receive is the model you asked for — resiliency changes who serves it, never what you get. See Provider Failover.
• Platform rate limits

Deliberately not applied:

• Input guardrails and output moderation
• Values-alignment (tradition)
• model_family selection and auto-routing — nothing picks a different model than the one you named (distinct from provider resiliency above, which only changes which provider serves that same model). The one exception is a deprecated model ID: once the catalog names a replacement_model, requests for it are served by that replacement. See Model Lifecycle.
• Gloo prompt augmentation — your messages go to the model verbatim

​

Grounded endpoints

Grounded endpoints retrieve relevant passages from content you have uploaded, inject them as context before generation, and tell you whether the answer was grounded in your sources.

• Grounded Responses (POST /ai/v1/grounded/responses) — grounding in the Responses shape.
• Grounded Completions (POST /ai/v2/grounded/chat/completions) — grounding on Completions V2, with citation metadata and tradition.

​

Which endpoint should I use?

When in doubt, start with Direct Responses, and move to the guarded Responses API when you want Gloo’s guardrails and moderation. The guarded and direct Responses endpoints take the same request body, so moving between them later is a URL change.

​

Choosing a model

Every endpoint takes a model ID, for example gloo-openai-gpt-5-mini or gloo-anthropic-claude-sonnet-4.6.

• Pin a model for production. A pinned model ID gives predictable behavior. Auto-routing and model_family selection (Completions endpoints) can change the model between calls.
• See the live catalog. Supported Models lists current model IDs, capabilities, and rates, rendered from GET /platform/v2/models.
• Pick by capability and cost. Check the catalog for each model’s capabilities (such as vision or tool calling) and rates, and test candidates with your own prompts.
• Plan for deprecation. Models can be deprecated and retired. See Model lifecycle for how notice works and how to migrate.

​

Legacy endpoint aliases

The previous v2 paths remain available as aliases for existing integrations. New integrations should use the canonical paths above: The /ai/v1/grounded/responses endpoint is unchanged.

​

Next Steps