LoreOS | LoreOS

A prompt can imitate a character for one turn. LoreOS runs one over time.

LoreOS is a managed Character OS for teams building companion apps, fictional characters, social agents, and character-driven products. Instead of wrapping a model in one growing prompt, LoreOS runs the stateful backend behind the character: memory, character facts, relationship state, world continuity, life simulation, visual identity, delivery, metering, and observability.

You bring the product, audience, and character concept. LoreOS runs the character runtime.

Base URL — every endpoint lives under https://api.loreos.app (for example, POST https://api.loreos.app/v1/characters).

What LoreOS gives you

Stateful character runtime — memory, character facts, relationship state, and safe runtime context.
Story Room — weekly arcs and daily-life packages so characters can live between messages.
Visual identity — identity images, assets, inventory, readiness checks, and image probes.
Delivery — async replies, session events, SSE, and managed Telegram channels.
Operations — metering, caps, readiness, run traces, and observability.

The core idea

Models can imagine. LoreOS validates. Runtime only sees safe context.

Generated candidates do not automatically become facts.
Accepted state does not automatically become visible.
Private plans and future forecasts do not enter the chat actor’s context.

Prompt wrapper vs. LoreOS

Prompt wrapper	LoreOS
One large prompt tries to hold everything	Typed ledgers compile into current character state
Memory is usually retrieval text	Memory, character facts, relationship, and user-specific state are separate
The model may turn ideas into “facts”	Code controls lifecycle, visibility, and commit boundaries
Images are one-off generations	Visual identity, assets, readiness, and probes support consistency
Operators guess why a reply failed	Runs, events, delivery logs, usage, and traces are inspectable

The API model

Three objects are all you need to understand:

App — your tenant. You’re given one when you’re provisioned; everything you create is scoped to it by your API key.
Character — the persona you create and configure: name, personality, voice, and (optionally) a face so it can send selfies.
Session — a 1:1 conversation between one of your characters and one of your end-users. You send messages and read the character’s replies.

What you can build

LoreOS is strongest for companion and fictional-character apps, social products with persistent AI characters, games and interactive story apps, and managed Telegram character bots. Persona-heavy tutors, guides, and assistants can use the same runtime when continuity and relationship state matter.

Learn the platform

Why LoreOS — what the platform manages beyond a model prompt.
Architecture — how API calls become stateful character behavior.
Character state — memory, character facts, relationship, and runtime context.
Story Room and life simulation — how characters live between messages.
Visual system — identity images, assets, inventory, and probes.

Get started

Get an API key — LoreOS is invite-only today.
Build with a coding agent — the resource order and pitfalls for agents.
Quickstart — your first reply in four calls.
Deploy a minimal chat app — server-side key, browser UI, async event polling.
Core concepts — async replies, end-users, usage.
API Reference — every endpoint, grouped by resource.

Building with a coding agent? Start with Build with a coding agent, then point it at https://api.loreos.app/v1/llms.txt.