Reference

API reference

These paths match the product API under /api/*. For bodies, query params, and schemas, use the OpenAPI file — session cookies authenticate browser-aligned requests.

Documented routes (subset)

Authentication: session cookie when using the dashboard from a browser — send credentials: "include" on same-site requests. The OpenAPI document lists request bodies and responses.

MethodPathDescription
GET/api/meGet current authenticated user
GET/api/projectsList projects for the signed-in user
POST/api/projectsCreate a project
GET/api/workflowsList automation workflows
POST/api/workflowsCreate a workflow
GET/api/workflows/{id}Get a workflow by id
POST/api/rag/queryQuery RAG index
GET/api/rag/documentsList RAG documents
GET/api/usageList recent token usage entries
GET/api/usage/summaryDaily/monthly usage and limits summary
GET/api/billing/subscriptionGet subscription info
GET/api/ws/eventsWebSocket event stream (upgrade)

From first call to launch

What happens after you book a demo — and how fast we move.

Typical time from your first meeting to a launch-ready, usable setup: up to 5 hours.

  1. Book your discovery call using the client meeting link (Calendly).
  2. Share context for your AI agent (for example FAQs and policies you provide).
  3. Sign the proposal: $5 setup fee plus the plan you choose; an invoice is generated.
  4. We create your workflow, project, and user account.
  5. You provide the WhatsApp number that will be used as the agent channel.
  6. We test that the agent matches your context (RAG).
  7. We schedule a second meeting to demo the live agent with you.
  8. We hand off your account with sign-in credentials.
  9. 24/7 support for technical issues after go-live.