Skip to main content

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

​
The setup path

  1. Add one or more base URLs and 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 where your auth token lives and the exact storage key name.

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 authorization session header.
  • 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 session headers.
  • What the agent may do: your tools and features.
  • What the agent may answer from: your knowledge base.