Skip to main content
The Search Playground lets you test semantic search across your organization’s content library in your browser. Try queries, see how results rank, and preview what the Search API will return before you build it into your application.
The Search Playground is available to organizations with Data Engine access. Data Engine is currently at capacity. See Billing & Plans to request access.You also need content uploaded to your content library. See Manage Content to add content.

Getting Started

1

Open Gloo AI Studio

Log in to Gloo AI Studio.
2

Open the Search Playground

Click Playground in the main navigation, then select the Search tab.
3

Choose a publisher (optional)

Optionally, narrow the search with the publisher filter (the default is All publishers).
4

Search

Enter a search query in the text input, then press Enter or click the arrow button to see results.
Only Publishers where you have access appear in the filter. If your organization has no Publishers, the Playground shows “This organization has no publishers” and search is disabled. Create a Publisher and upload content first.
After you search, a second All publishers filter lets you narrow the results you already have to a single publisher without searching again.
Publisher dropdown showing available content libraries

Understanding Search Results

Each result card shows: Results are ranked by semantic relevance, not keyword matching, so the most relevant content appears first even without your exact search terms.
A search for “dealing with anxiety” might return content about “managing stress” or “finding peace” because they’re semantically related.
Search results showing cards with titles, sources, and snippets

Exploring Key Insights

Some search results include a Key Insights section:
1

Open a result

Select a result to open its details panel.
2

Find Key Insights

Look for the Key Insights section in the panel, below the title, publisher, and snippet.
3

Review the analysis

Review the AI-generated analysis, which includes why the snippet matters, the questions it answers, flourishing and thriving analysis, and ratings such as sentiment and readability.
Key Insights are generated automatically when available; whether a result has them depends on result quality and content type.
Expanded Key Insights panel showing AI-generated summaries
Semantic search finds content by meaning rather than by exact words. Your query and your content are each turned into an embedding, a list of numbers that captures meaning, and results are ranked by how close in meaning they are to your query. See Embeddings: How AI Understands Meaning for more. Compared with keyword search: Example Comparisons:
Think about what users mean, not just what they say: semantic search finds content that answers the underlying question.

Transitioning to API

To call search from code, follow the Search API Guide to implement semantic search in your application, and Generate API Keys for API access. Upload Content covers content ingestion and management.

Frequently Asked Questions

It requires Data Engine access; Inference on its own does not include search. Request Data Engine access to use this feature.
Publishers appear once your organization has created them. Create a Publisher, then upload content via Manage Content or the Content API, then return to the Search Playground.
The Playground returns up to 10 results by default. The Search API sets the count with the limit parameter; 10 to 100 is recommended.
Try these steps:
  • Make your query more specific with additional context
  • Verify your content library contains relevant material
  • Test different query phrasings
  • Ensure content has been fully processed after upload
Semantic search finds conceptually related content even without exact word matches; keyword search only matches specific words. Semantic search works better for natural-language queries.
The Playground shows all results from the selected Publisher. Use the Search API to implement custom filtering by content type, date, author, or other metadata in your application.
Search results include text snippets suited to RAG. The snippets preview the content you’ll receive via the API, which you can pass to the Completions API as context for generating answers.

Next steps

Search results depend on how content was prepared: see Preparing Content for Ingestion. To answer questions from these results with sources people can check, see Building Trustworthy Grounded Applications.

Search guide

How the Search API works.

Step-by-step tutorial

Build custom search in code.

Manage Publishers

Choose and manage the publishers you search.

Manage Content

Upload and organize content in Studio