Bend the Interface.

Interfaces, no longer static.

Make dashboards responsive to intent, embed an AI agent to turn user requests into actions.

Executes only approved endpointsSame-origin by defaultSession-aware via header mapping

Turn user intent into UI actions

Configure what Warpy is allowed to do. The agent reads the user’s session context, calls only approved APIs, and performs UI actions that map to your product’s real workflows.

Drop-in widget

Embed a lightweight JS widget into any dashboard. It stays unobtrusive until the user signals intent.

Scoped execution

Define endpoint schemas and feature groups. Warpy executes only what you enable.

Session-aware headers

Map session headers (like Authorization) so the agent can call your APIs in the user’s context.

Executes user actions

The widget can execute UI actions on behalf of the user, using only the endpoints and features you enable.

Example flow

A real request, mapped to real actions.

Warpy reads session context, calls only approved endpoints, then applies UI actions in the host dashboard. What used to take your users minutes can now be done in seconds.

User request
User
Show enterprise accounts from the last 90 days. Group them by plan and hide trials. Add a "Renewal risk" column.
Uses existing sessionCalls your APIs
Agent actions
Scoped execution
  1. Step 1API
    POST /api/accounts/query
    Fetch candidate accounts and apply filters.
    {
      "sinceDays": 90,
      "segment": "enterprise",
      "exclude": ["trial"],
      "groupBy": "plan"
    }
  2. Step 2API
    POST /filter/post/filter
    Build a filter state that matches the request.
    {
      "table": "accounts",
      "filters": {
        "createdWithinDays": 90,
        "segment": "enterprise",
        "exclude": ["trial"]
      }
    }
  3. Step 3UI
    UI.Action.apply
    Apply filters, group enterprise accounts, and add the renewal_risk column.
    Grouping appliedColumn added

Install once. Configure continuously.

Teams set base URLs per environment, map session headers, and define endpoint schemas the agent is allowed to call. Endpoints are grouped into features you can enable or disable at any time.

  • Keep execution bounded: schemas + feature flags define what exists.
  • Keep auth simple: read headers from the user’s session (and optionally add signed tokens).
  • Keep UX crisp: no spinners; expand to predicted size and shimmer a skeleton while results arrive.
Framework
Package
pnpm add @warpy-ai/widget

import { Widget } from "@warpy-ai/widget/react"

<Widget
  agentId="agent_demo_7f3a"
  baseUrl="https://api.your-product.com"
  scriptSrc="https://cdn.warpy.ai/widget.js"
/>

Your product stays in control.

Warpy is not a generic chat layer. It’s an execution layer you scope and audit for B2B environments with real permissions, real data, and real workflows.

Approved endpoints only
The agent can call only the schemas you define, grouped into features you can turn on/off.
Same-origin by default
Use your existing APIs (often on the same origin) and keep requests inside your normal session context.

Ready to bend the interface?

We’ll scope your first set of endpoints, map session headers, and ship an embed that feels native to your UI.