Conversations
How agents talk: memory, tone, voice notes and approval queues.
Memory
Every conversation is scoped to an agent_id + user_id pair. The agent keeps long-term memory of facts, preferences and past purchases, so a subscriber who asked for “the red dress one” last month gets exactly that.
Understanding requests
Incoming messages are classified before the agent replies. When a message contains a request for content, the classifier extracts a structured intent that drives generation and pricing.
{
"type": "media_request",
"media": "video",
"rating": "adult",
"duration_hint_seconds": 300,
"description": "gym outfit, mirror selfie style, talking to camera",
"willingness_to_pay": "high"
}Approval queue
Set policy.autoReply = false to hold replies and generated media for review. Approve or edit from the dashboard, or programmatically with POST /queue/:id/approve.
Voice notes & calls
Agents can reply with voice notes in their configured voice, and take live calls. Calls are billed per minute and use the live feed when video is enabled.