Skip to main content

Set up the execution path before you embed the widget: config first, tools second, knowledge third, activation last.

The first sign-in now starts with a short onboarding flow that can collect your website, production API base URL, auth setup, and first agent install snippet before you reach the dashboard. If you add a website there, Warpy also turns on the knowledge base for you.

​
The setup path

If you finish the new onboarding flow, you will already have most of steps 1, 3, and 4 started for you. Use the dashboard after onboarding to refine the setup, add more tools, and expand your knowledge base.
  1. Add one or more base URLs, auth settings, and any custom session headers.
  2. Define the backend and frontend tools the agent may use.
  3. Upload a knowledge base if the agent should answer from documents.
  4. Open Activate Agent, install the widget, and configure the experience.
  5. Turn on optional signed widget tokens and rate limits if needed.
Base URLs
  -> Session headers
  -> Features and tools
  -> Knowledge base
  -> Activate Agent
  -> Widget live in your app

​
What you need before you start

Add at least local and production.

Know whether auth comes from browser storage or browser cookies.

Start with the few actions users ask for most often.

Good sources include product docs, SOPs, handbooks, and policy docs.

​
Minimum viable launch

A solid first launch is:
  • One base URL for the current environment.
  • One working auth setup.
  • One product website or scoped docs path in the knowledge base.
  • Two or three enabled backend tools.
  • One white-labeled widget name and placeholder.
  • Optional starter suggestions.

​
The mental model

Warpy works when the execution surface is explicit:
  • Where requests go: your base URL.
  • How requests authenticate: your auth settings and optional custom headers.
  • What the agent may do: your tools and features.
  • What the agent may answer from: your knowledge base.
If your app authenticates with cookies, turn on Send browser cookies with requests during setup. Warpy will send browser credentials automatically; you do not need to enter a token key for auth.