Documentation
Owari Robo
Owari Robo lets teams teach an assistant, test private answers, publish a public chat, capture Contacts, and relay finished conversations through Owari Forms without exposing Memory or Router as separate customer products.
Use the Robo console for onboarding, teaching, publishing, Contacts, team, history, and billing.
Published assistants receive a slug-scoped public chat page with consent, limits, retention policy, and contact capture.
Each Robo tenant owns internal Memory and Router resources while Robo enforces product limits, audit, public chat, and Contacts.
Quickstart
Use the public chat and OpenAI-compatible runtime surfaces from customer-facing clients and server integrations.
1. Read public chat configuration
Fetch the published assistant configuration before showing a public chat experience.
curl "https://api.owarilabs.com/robo/v1/public/robots/cartorio/config" 2. Start a public session
Public chat clients create a session before sending messages or contact requests.
curl -X POST "https://api.owarilabs.com/robo/v1/public/robots/cartorio/sessions" \
-H "Content-Type: application/json" \
-d '{
"visitor_label": "website visitor",
"consent_accepted": true
}'
# Use the returned session_id to send a message.
curl -X POST "https://api.owarilabs.com/robo/v1/public/sessions/$SESSION_ID/messages" \
-H "Content-Type: application/json" \
-d '{
"message": "What services do you offer?",
"consent_accepted": true
}' 3. Call the Responses API
Server-side integrations can use tenant-scoped Robo API keys for OpenAI-compatible runtime calls.
curl -X POST "https://api.owarilabs.com/robo/v1/responses" \
-H "Authorization: Bearer $ROBO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"conversation_channel": "public_chat",
"model": "owari-default",
"input": "Summarize your support options."
}' Endpoints
Robo exposes public chat, widget, and OpenAI-compatible runtime surfaces for customer-facing integrations.
/health/live Check whether the Robo API process is live.
/health/ready Check whether the Robo API can serve traffic.
/v1/public/robots/{slug}/config Return public chat configuration for a Robo slug.
/v1/public/robots/{slug}/sessions Create a public chat session.
/v1/public/widgets/{slug}/config Return widget-safe configuration for an allowed website origin.
/v1/public/widgets/{slug}/sessions Create a widget public chat session.
/v1/public/sessions/{sessionId}/messages Send a public chat message and receive an answer.
/v1/public/sessions/{sessionId}/feedback Submit thumbs up or down feedback.
/v1/public/sessions/{sessionId}/finish Finish an idempotent widget or public chat session.
/v1/public/sessions/{sessionId}/expand-tokens Create a one-time token to expand a widget conversation into public chat.
/v1/public/expand-tokens/{token}/redeem Redeem a one-time widget expand token and hydrate the public chat transcript.
/v1/public/sessions/{sessionId}/contact-handoffs Create a Contact from public chat handoff.
/v1/responses Use Robo through an OpenAI-compatible Responses API.
/v1/chat/completions Use Robo through an OpenAI-compatible Chat Completions API.
Swagger / OpenAPI
Use the embedded reference to inspect current Robo request and response schemas.
The public OpenAPI contract below intentionally omits dashboard console and internal control-plane routes.