Skip to main content

Experiences

An experience is the user-facing thing you've built — a search page, a chat window — and the access token that lets a website talk to it. Everything else in Interakt (indexes, tools, prompts, providers) is plumbing. The experience is what your users actually open in a browser.

There are two kinds:

  • Search experience — a search box with filters and result cards, backed by one or more search indexes.
  • AI experience (chat) — a chatbot, backed by an AI provider, that can use tools to answer.

You build them in the same place — sidebar → Experiences. The list shows both.

Where to find this screen

Sidebar → Experiences.

The list screen

A unified list of all your experiences with type filters at the top.

  • Title: "Experiences."
  • New Experience button — opens the create flow.

Stats cards (four numbers)

  • Total — count of experiences.
  • Active — count with active toggle on, plus the percentage.
  • AI Experiences — count of chat experiences.
  • Search Experiences — count of search experiences.

Filter and view controls

  • Type tabs — All / AI / Search.
  • View toggle — List (table) or Grid (cards). Grid is the default; list is denser.
  • Search input — search by name or slug.
  • Status dropdown — All / Active / Inactive.
  • Clear filters button.
  • Refresh button.

Each row shows

WhatWhat it tells you
Icon + name + slugThe experience and how it's addressed in the API / URL.
Type badgeAI (amber) or Search (teal).
Status badgeActive (green) or Inactive (grey).
DetailsFor AI: pipeline mode + assigned-tools count. For Search: attached-indexes count.
CreatedDate.
⋮ menuView Details / Edit / Delete.

Pagination at the bottom: "Showing 1–20 of 35" style.

Creating an experience

Click New Experience. The first step asks which kind:

  • Search Experience — search interfaces with filters, AI summaries, configurable result display.
  • AI Experience — chatbots, with tools, guardrails, configurable personality.

Pick one and a wizard runs. See:

What every experience has

Regardless of type:

  • A name and a slug. The slug is the URL path your users hit.
  • An access token — the credential the embed widget or your custom frontend uses to call the API. Issued automatically on creation. Can be regenerated from the detail page.
  • An active/inactive toggle. Inactive experiences exist but reject incoming traffic.
  • An allowed origins list (CORS) — which domains are allowed to make browser requests to this experience. Empty means all origins are allowed.
  • An embed widget configuration — theme, colours, layout, behaviour. The detail page has a card with a live preview and a Copy button for the snippet.
  • A delete in the danger zone, requiring you to type the experience name to confirm.

Most pages and concepts described in Search experiences and Chat experiences apply to both.

Where to go next