Request a demo
Developer Documentation

Build a real-time human interface into your product.

Understand the integration model for Core Avatar, website embeds, real-time sessions, events, and downstream actions.

Sign in to start buildingContact developer support

Choose Core Avatar or Receptionist Mode

Core Avatar

You supply intelligence, knowledge, and workflow. Athira supplies the real-time face and voice.

Right when you are building your own experience.

Receptionist Mode

A complete visitor experience built on Core Avatar, configured rather than coded.

Right when the job is greeting, qualifying, and booking.

Core Concepts

Your application and your intelligence stay on your side of the boundary. Athira renders the conversation and returns approved events.

Your application & intelligence

Models, retrieval, and business logic.

Athira real-time avatar

Rendering, speech, expression, session.

Browser experience

What the person sees and hears.

Your application & intelligence

Models, retrieval, and business logic.

Athira real-time avatar

Rendering, speech, expression, session.

Browser experience

What the person sees and hears.

Approved events and actions return to your systems.

Embeds

An embed places a configured avatar on a page or inside a view. Delivery is plugin-free in the browser over WebRTC.

Placement and size are yours to choose
Page context is available to the conversation
Nothing speaks or asks for a microphone before the person acts
Final API reference content required before publication.

Real-Time Sessions

Conceptually, every session follows the same five steps.

01Initialize - the surface is prepared with the configuration it should use.
02Connect - a real-time channel opens once the person has acted.
03Converse - audio and text stream both ways while the avatar renders live.
04Receive events - turns, outcomes, and requested actions arrive as they happen.
05End gracefully - a soft close, with a final chance to capture the next step.
Illustrative integration shapefinal SDK syntax may differ
session = initialize(configuration)
session.on("turn" -> update your UI
session.on("action" -> your handler decides
session.on("outcome" -> write to your systems
session.connect() when the person acts
session.end() soft close

Pseudocode. Names, packages, and endpoints are not final.

Events & Actions

Events describe what happened in the conversation. Actions are the things your application is asked to do - and it decides whether to do them.

Conversation events

Turns taken, topics raised, session state changes.

Outcome events

Booked, captured, answered, or ended.

Requested actions

Only from the set you have permitted.

Final API reference content required before publication.

Guardrails

Some behavior is fixed on every deployment, and some is yours to define.

Always on
·No legal, medical, or financial advice
·No binding prices, no negotiation
·Never claims to be human
·Never invents an answer
Yours to define
·Prohibited topics and never-say rules
·Handoff triggers
·Price and competitor handling
·Which actions are permitted

Integration Patterns

Embed on a marketing site

Configuration lives with Athira; the page only places the surface.

Avatar inside your product

Your app owns the session and passes the context the conversation needs.

Conversation to workflow

Outcome events drive whatever runs next on your side.

Plugin-free browser delivery over WebRTC.
Designed for natural, real-time conversation.
English today; more languages planned.

Support

Developer support

Questions about sessions, embeds, events, or behavior.

[email protected]
Contact Sales

Deployment scope, integration design, and pricing.

Talk to Sales
Final API reference content required before publication.

Start building with Athira.

View pricingContact Sales