DEVELOPER DOCUMENTATION
Commerce & monetization
Subscriptions, metered voice, paid content and companion commerce.
The business layer connects character experiences to products, entitlements and payments. We scope commerce around your audience and operating model.
Revenue models
| Model | Typical implementation |
|---|---|
| Subscriptions | Membership access and recurring entitlements |
| Voice calls | Metered usage or allocated conversation minutes |
| Paid content | Photos, generated clips and voice messages |
| Creator cloning | Creator-based characters with agreed commercial terms |
| Companion commerce | Product discovery and explicit purchase journeys inside conversations |
Entitlements before delivery
Authenticate the user and verify the relevant subscription, balance or purchase before delivering a paid experience. Keep billing decisions on the server. A visible interface state alone must not grant access.
Payments and reconciliation
Agree the payment gateway, supported regions, webhook verification, order states and reconciliation process before launch. Retried payment events must not grant the same credit or content more than once.
Companion-led commerce
A character can suggest relevant products and open a product or checkout flow. The purchase itself remains an explicit user action handled by your commerce system. Product catalog access and available actions are configured for the deployment.
Marketplace scope
Catalog structure, creator onboarding, content storage, payment processing and operational responsibilities are agreed in the white-label or integration project. This documentation describes the architecture; it does not expose a public generic orders or billing API.
Talk to our team about your architecture, character and launch.
Discuss your integration ↗