Skip to main content
SupaCortex
Sign in Book a Demo
Solution

Help inside the product, for the person using it

Your users should not have to leave the app to find an answer - or open a ticket to learn their order status. Put an assistant in the product that knows who they are, answers from your docs and works with their own account.

Book a demo See pricing
  • Signed-in users
  • Web and mobile
  • Actions confirmed first

What is SupaCortex's in-product assistant?

It is SupaCortex's chat widget in identified mode, embedded in your web app or opened in a mobile WebView. Your backend signs a short-lived token for the signed-in user, so the assistant answers how-to questions from your docs with citations, scoped to that customer, and - through a custom HTTP connector - looks up or changes things in their account using your own API, asking them to confirm before any change.

  • One script tag for the web; a WebView URL for Android and iOS.
  • Identity from a signed token, valid at most 15 minutes.
  • Any HTTPS API: describe endpoints or import OpenAPI 3 / Swagger 2.
  • API key, bearer, basic, HMAC or OAuth 2 client-credentials auth.
  • Your title, colour, greeting and quick actions per project.
Getting started

What you set up

  1. 01

    1. A product project

    Your docs and help centre, crawled and kept in step. Customer-specific documents tagged with that customer's id.

  2. 02

    2. Sign a token

    A few lines in your backend sign the user's id, name and company with the project's widget secret.

  3. 03

    3. Describe your API

    Import your OpenAPI file, keep the endpoints you want, add example phrases, and test each with Try.

  4. 04

    4. Embed it

    The script tag in your web app, the WebView URL in your mobile app. Style it to match.

In detail

Answers, lookups and actions

Lookups: "what's the status of order 1042?"

Example phrases route a question to an endpoint. The assistant extracts what it needs, asks for what is missing, and reads the answer from the fields you mapped.

  • Parameters come from the user's words, or from the verified identity - never both for the same value.
  • Only the fields you map are used; raw responses never reach the model.
  • Optional templates render a reply with no model involved.
  • In public mode, only lookups you mark public-safe can run.

Actions: "cancel my add-on"

Anything that changes data is an action, and every action waits for a yes.

  • The user sees the action's name and the values before confirming.
  • Confirmed calls carry an idempotency key.
  • Every call is audited: endpoint, status and timing, never the body.
  • Per-user and per-project rate limits; secrets encrypted and never shown again.

Prefer to make calls from your own backend? The chat API's orchestrator mode hands the call to your product and takes the result back.

Read next

Website & In-App Chat Widget

One script tag for your site, a WebView URL for your mobile app - public or signed-in users.

Actions & API Connectors

Let the assistant look up an order or raise a request in your own systems - with confirmation first.

Search & Answer API

The same brain behind your own tools: scoped API keys, /v1/search and /v1/answer.

SaaS & Software

Docs that change every release, answered correctly the day they change.

E-Commerce & Retail

Shipping, returns and "where is my order?" - the last one from your own order system.

Security

Separate databases per workspace, encrypted secrets, and answers scoped to who is asking.
Frequently asked

Questions people ask before they start

Your backend signs a short-lived token - valid for at most 15 minutes - with the project's widget secret, naming the user and their company. SupaCortex checks the signature on every request. The secret stays on your server; the browser only ever holds the token.

No. Values that identify the user or their company are filled only from the verified token, never from the conversation. Content tagged for one customer is only searchable for that customer, and every call to your API is audited.

Yes. Each project has a mobile URL to open in an Android or iOS WebView, in public mode or with the signed token passed in.

Only through endpoints you describe as actions, and only after the user confirms what will be sent. Each confirmed action carries an idempotency key, so a retry does not do it twice.

No. App users are counted as widget sessions, never as seats. An answer uses one AI credit; a turn that calls your API uses two. Custom connectors are included from the Growth plan.

Put the answers where your users already are.

Book a 30-minute demo on your own documents. We set up a 14-day trial workspace for you - no credit card, no setup fee.

Book a demo See pricing

Questions first? Email info@greatdevelopers.com or call +91 8585953085.

Still curious? Ask your favorite AI about SupaCortex.

ChatGPT Claude Perplexity Grok