Skip to main content
The terms you’ll meet across Gloo AI Studio and the API, grouped by topic.
This page covers Gloo AI platform and account terms. For general AI terms such as tokens, embeddings and hallucinations, see the AI 101 lessons in the AI Learning Center.

Account and access

Who belongs to an organization, what they can do, and how your code authenticates.

Organization

An Organization (often shortened to “Org”) is the root entity in Gloo AI’s multi-tenant architecture. All data, content, and users are scoped to a specific Organization. Every account belongs to at least one Org, and data is fully isolated between Organizations.

User Roles

A user’s role sets what they can access within an Organization. See Manage Users.

Author

An Author is a user who creates content for one or more Publishers. A user becomes an Author only when invited by a Publisher and after accepting the invitation. Authors are distinct from Org-level roles — a user can hold both.

API Key

An API Key is the credential you send as a bearer token in the Authorization header of Gloo AI API requests. You create API keys on the API Keys page in Studio. A key is shown only once, when you create it. See Generate API Keys.

Client Credentials

Client credentials (a Client ID and Client Secret) are the legacy way to authenticate. They are exchanged at the OAuth2 token endpoint for a short-lived access token. They are deprecated and being sunset by December 2026. Use an API key instead. See Legacy: client credentials and OAuth.

Access Token (legacy)

An Access Token is a temporary token that older integrations get by exchanging an OAuth2 Client ID and Client Secret. Client ID and Secret credentials are deprecated and being sunset by December 2026; new integrations use API keys, which are sent directly with no token exchange. See the Authentication tutorial.

Content

How your uploaded content is owned, stored and addressed in Data Engine.

Publisher

A Publisher is a sub-entity within an Organization that owns and produces content. All ingested content is associated with a Publisher. An Organization can have multiple Publishers, each representing a distinct brand, team, author, or imprint. You must create at least one Publisher before uploading content. See Manage Publishers.

publisher_id

The publisher_id is the unique identifier for a Publisher, assigned by Gloo AI when the Publisher is created. Most Content API calls require it to scope operations to the right Publisher. You can find your publisher_id in Studio under Manage Organizations: open your organization’s Actions menu, and select View Publishers. See Manage Publishers.

Tenant

A Tenant is a Publisher’s name in normalized form: spaces and whitespace are stripped, so Example Publisher name becomes ExamplePublisherName. The Search and item recommendation endpoints take it in the tenant field to scope a request to one Publisher’s content. To get the exact string, call GET /ai/v1/data/tenant/names. See Search.

Collection

A Collection is where Gloo AI keeps customer content for search. The only collection you specify in requests is GlooProd, in the collection field of Search requests. Within it, each Publisher is addressed by its tenant.

item_id

The item_id is Gloo AI’s internal UUID assigned to each content item on ingestion. It uniquely identifies an item across all API operations (edit, inspect, replace, delete).

producer_id

The producer_id is your own internal identifier for a content item, optionally provided at upload time. It lets you reference items using your existing IDs without storing Gloo’s item_id. You can later use it to look up the matching item_id with the Get Item by Producer ID endpoint. Gloo doesn’t replace items by producer_id: uploading changed content under one you’ve used creates a second item, so replace the existing item instead. To choose a stable scheme, see Preparing Content for Ingestion.

Endpoints and models

How requests are handled and how the model is chosen.

Guarded, Direct, and Grounded Endpoints

Gloo AI’s generation endpoints belong to one of three families:
  • Guarded endpoints run Gloo’s full safety and values pipeline around your request: guardrails, output moderation, and values alignment; on Guarded Completions, also model families and auto-routing.
  • Direct endpoints send your request straight to the model you name, with nothing added between your prompt and the provider.
  • Grounded endpoints retrieve passages from your own uploaded content and give them to the model as context (retrieval-augmented generation, or RAG).
See Endpoint Types for how to choose.

Grounded

A response is grounded when it is based on content retrieved from your own Publishers rather than only on the model’s training. Grounded endpoints report whether an answer was grounded. See Grounded Completions and Grounded Responses.

Model Selection

Model selection is how a request says which model runs it. Guarded Completions and Grounded Completions accept three options; send exactly one:
  • AI Select (model): you name the exact model. We recommend it for most applications, because each call uses the model you selected while it remains available (see model lifecycle).
  • AI Core Select (model_family): you name a provider family and Gloo picks a model from it.
  • AI Core (auto_routing: true): Gloo picks a model for each request.
Every other endpoint takes a model, so it always uses AI Select. See Choose how the model is selected.

Auto-routing

Auto-routing (auto_routing: true), called AI Core, lets Gloo choose the model for a request instead of you naming one. It is available on Guarded Completions and Grounded Completions. Studio’s Playground uses the same name. It can’t be combined with model or model_family.

Model Family

A Model Family is a provider group: openai, anthropic, google, or open source. Setting model_family (AI Core Select) on a Guarded Completions or Grounded Completions request lets Gloo pick a model from that group. See Completions.

Tradition

tradition is a request parameter that tailors a response to a theological perspective. Supported values are evangelical, catholic, mainline, and not_faith_specific. It is available on guarded Responses and Completions and on Grounded Completions requests. See Completions and Responses.

Billing and plans

What you buy and how it is paid for.

Product

A Product is one of the offerings you can buy in Studio, named as on the Gloo AI Studio pricing page: Inference (API access funded by prepaid credits), Data Engine (currently at capacity for new organizations), and Gloo Code (the coding agent, bought solo or per seat for a team). Products are independent, and an Organization can hold any combination on one account and one bill. See Billing & Plans.

Tier

A Tier is a level within a single Product. Gloo Code, for example, comes in Basic, Pro, and Ultra tiers, each with a Teams variant bought per seat, and every tier includes every agent and model. Tiers differ by allowance and support. A tier belongs to one product, so “Pro” in Gloo Code is a different thing from “Pro” in any other product. See Choosing a Gloo Code tier.

Plan

A Plan is how you purchase and combine Products and Tiers on one Organization: which products you hold and at which tier, billed together on one account. Older account plans (Pay-as-you-go, Pro, and Enterprise) are described as legacy plans. See Billing & Plans.

Prepaid Credits

Prepaid Credits are the balance that funds API inference, shown on the Wallet card of the Billing page. Admins add $1 to $100 at a time, optionally with auto-refill, and each API request draws it down at the model’s published rate. Credit-funded usage is capped at $4,000 per month by default. Gloo Code never spends credits. See Prepaid Credits.

Wallet

The Wallet is the card on the Billing page that shows an Organization’s prepaid credit balance. Creating an API key requires credit in the Wallet (organizations on a legacy plan need a payment method on file instead). See Prepaid Credits.

Billing

Billing is the Studio page where members who can manage billing add and remove Products, change Tiers, manage credits and the Wallet, assign Gloo Code seats, and manage payment methods and invoices. See Billing & Plans.

Gloo Code Seat

A Seat is the assignment that lets a specific user sign in to Gloo Code under an Organization’s subscription. Solo tiers include one seat; Teams tiers are bought per seat for 2–25 users with a pooled usage allowance. Admins assign and unassign seats from the Billing page. See Teams and seats.

Next steps

Developer Quickstart

Make your first API call.

Endpoint Types

Choose between guarded, direct and grounded.

Billing & Plans

Products, tiers, credits and seats.