Channels
Web widget, Telegram, WhatsApp, and live realtime voice from one agent runtime.
Platform · API
Agent infrastructure, exposed as an API
Build with assistants, knowledge, pipelines, tools, conversations, and signed webhooks through a versioned interface. Documentation and access are currently in gated beta.
Looking for white-label agency packaging instead? See Partners.
Capabilities
What you get under the hood
Product-builder surface — not an agency pitch. White-label resale lives on the partners pages.
Ingestion & RAG
Files, URLs, and facts into searchable knowledge with tenant isolation.
Tools & webhooks
HTTP webhooks and native actions in production; MCP/SQL on the roadmap.
Voice pipelines
Realtime phone conversations with the same grounded core as chat.
Cost-tier routing
Route model spend by workload so unit economics stay intentional.
Ledger billing
Resolution-oriented metering and published plan economics.
Multi-tenant
Org isolation for knowledge, secrets, conversations, and configuration.
Ops & handoff
Logs, guardrails, and human escalation paths built for production.
Architecture
Designed as a distributed platform
Microservices, event-driven streams, and clear tenancy boundaries — so you embed agent capability instead of growing a second platform team.
01Ingress
Web widget
Telegram
bot · userbot
Cloud · userbot
Voice
realtime · live
02Routing
Cost-tier router
classify → simple → complex
Provider fallback
multi-provider chain
03Agent core
RAG / pgvector
jina-embeddings-v5-text-small
Persona + prompt layers
Tools & webhooks
Scheduling
cron · delayed
04Metering
Ledger billing
append-only credit ledger
Payments
Stripe · MercadoPago
multi-tenant · event-driven (NATS JetStream) · per-tenant isolation for knowledge, secrets & conversations
Ingress channels feed a shared agent runtime grounded in per-tenant knowledge. Tools execute under policy. Billing meters resolutions. Voice and chat share the same brain.
Access
Request developer access
Tell us what you are building. Early access is barter-friendly when the fit is strong.
Developer FAQ
Infrastructure questions
Straight answers for teams who would otherwise build this themselves.