Skip to documentation
Let’s build
PUBLIC TECHNICAL PREVIEW Production access and integration details are agreed during onboarding.
Amora Docs/Character configuration

DEVELOPER DOCUMENTATION

Character configuration

Persona, behavior, voice and visual identity.

A character combines a recognizable identity with a clear role in your product. Configure the persona, voice, visual references and memory behavior as one system.

Character brief

Prepare the intended name, presentation, language, tone, conversation goals, boundaries and audience. Include example dialogue and visual references that communicate the experience you want.

Runtime configuration

Define identity instructions, personality, response style, roleplay behavior, knowledge access and tools. Keep product actions, such as opening a purchase flow, explicit and controlled by your application.

Voice and visual identity

Pair the character with an approved voice configuration. Add Custom Character LoRA when a consistent face and body are required across scenes and content assets.

See One character, any scene for Amora's visual examples.

Localization and channels

Plan localization around the intended language and market rather than translating only the interface labels. Validate voice, dialogue style and commercial flows on the website, mobile web experience and Telegram Mini App.

Acceptance review

Review sample conversations, knowledge accuracy, memory continuity, voice quality and visual consistency before publishing a character. Version approved configurations so later changes can be evaluated and rolled back.

Building something personal?

Talk to our team about your architecture, character and launch.

Discuss your integration ↗