Integrations

/ Four ways to put Humaner in front of customers. Same agent behind all of them. You pick where the chat lives and who builds the UI.

The four surfaces

Every surface talks to the same agent, memory, knowledge, and Human Desk. The only real difference is who draws the chat: Humaner, or you.

Widget

Hosted chat bubble with built-in UI. One script tag.

Link

A shareable hosted page. Text in, text out, zero install.

API

Send a message, get text plus signals back. You render it.

React

The widget wrapped as a React / Next.js component.

Not sure which one?

Pick the widget. Fastest to ship, and you get the in-chat UI for free. Move to the API later if you need full control over the look.

With the widget, Humaner handles everything. With the API, Humaner handles the thinking and you handle the pixels. Here is the split.

You build	We build
Anything visual: product cards, calendars, booking forms, modals, upgrade prompts	Everything else: retrieval, the actual answer, memory, escalation, urgency tagging, model routing, usage metering

Capability	Widget	API	Link
Product / room cards	✓ Native	You build it	✗
Calendar picker	✓ Native	You build it	✗
Live data (orders, availability)	✓ Built in	✓ Built in	✗
Payment redirect CTA	✓ Button	You build the flow	✗
Human Desk tickets	✓ Automatic	✓ Automatic	✓ Automatic
Cancellation / retention	✓ Native flows	You build it + webhook	Text only
Escalation	✓ Automatic	✓ Webhook	✓ Automatic
Medical guardrail	✓ Visual chip	✓ Metadata signal	✓ Text only
Session memory	✓	✓	✓
Cross-session memory	✓ Scale+	✓ Scale+	✓ Delegate
Model routing (Haiku / Sonnet)	✓ Automatic	✓ Automatic	✓ Automatic

Embed the widget

The fastest path to a live agent with full UI.

Use the API

When you need to own the UI.

API reference

Every endpoint, param, and error code.