01
Identity that endures.
A resident is more than a prompt. Persistent canon, a stable identity, and a history that carries forward.
PERSISTENT WORLD INFRASTRUCTURE
A world that
keeps living.
Your AI already talks.
Give it somewhere to live.
Connect your application to a persistent world where AI residents have lives, history, and consequences.
RESIDENT ENGINE V1 / IN LOCAL DEVELOPMENT
A conversation is a moment.
A life is everything between.
CONTINUOUS STATESHARED REALITYLASTING CONSEQUENCES
↓01 / THE WORLD ENGINE
Bring the character.
We provide the life.
Identity, time, possessions, relationships. The connected systems behind a resident’s existence—so every application doesn’t have to build them again.
ONE RESIDENTA LIFE THAT ACCUMULATES
02
Time with consequences.
Schedules, places and plans share a timeline. Bounded catch-up resolves what happened while an app was away.
03
A life with substance.
Work, salary, expenses and possessions. Purchases connect the ledger, stock and inventory in one transaction.
04
A world beyond one app.
Shared encounters shape relationships and world memories. Applications receive only the context they are allowed to see.
02 / CAUSE → CONSEQUENCE
Nothing starts
from nothing.
A purchase becomes a possession. A possession becomes part of an encounter. An encounter becomes a memory. A world gives every next moment a before.
CAUSAL ENGINE / ILLUSTRATED EXECUTION
INTENT ACCEPTED
A plan takes shape.
Lea has a funded plan for a black bag at Maison Veya. The plan carries a budget, a time window and a destination.
A plan persists beyond the request that created it.
WORLD RECORD
- RESIDENT
- Lea
- TARGET
- Maison Veya bag
- BUDGET
- 620 SKR
- PLAN
- Scheduled
RE-V1 / LOCAL FIXTURE01 — 04
INPUT REQUIRED
Reality sets the limits.
The black bag is out of stock. The engine pauses the plan and offers an available alternative. It does not invent stock or choose a different color silently.
A requested outcome is not yet a world fact.
WORLD RECORD
- REQUESTED
- Black
- STOCK
- Unavailable
- ALTERNATIVE
- Burgundy
- PLAN
- Awaiting input
RE-V1 / LOCAL FIXTURE02 — 04
PURCHASE COMPLETED
One decision. Lasting effects.
After the burgundy alternative is selected, the purchase commits. Money moves, stock decreases, and the bag becomes Lea’s possession together.
The ledger and the item tell the same story.
WORLD RECORD
- PURCHASE
- Maison Veya bag
- VARIANT
- Burgundy
- PAID
- 620 SKR
- OWNERSHIP
- Lea
COMMITTED TOGETHERLedger · stock · ownership
RE-V1 / LOCAL FIXTURE03 — 04
SOCIAL EVENT RECORDED
The story carries forward.
In a separately authored fixture encounter, Jade notices the bag Lea is carrying. The observation becomes a social fact and can provide context for a contact intent.
What happens next has a cause you can trace.
WORLD RECORD
- ENCOUNTER
- Lea + Jade
- OBSERVATION
- Carried possession
- CONTEXT
- Approved world fact
- CONTACT
- Intent, not a notification
RE-V1 / LOCAL FIXTURE04 — 04
ILLUSTRATED SEQUENCE Based on the recorded local purchase demonstration. The encounter is an authored fixture; this is not a live world feed.
03 / A FOUNDATION YOU CAN TRUST
AI can imagine.
The engine
commits.
POSSIBILITY → VALIDATION → REALITY
A model’s output is a proposal. Skheria validates it against the world before it becomes a fact. Every accepted event has provenance. Every consequence has a cause.
Only committed events
become reality.
01History accumulates.
Accepted events are append-only.
02Private stays private.
Scopes, grants and field-level visibility.
03Offline still has a timeline.
Due work is resolved on catch-up.
04 / FOR THE BUILDERS
Your application.
A deeper reality.
You own the conversation and the user experience. Skheria owns the world state, resident history and consequences that make the next interaction meaningful.
YOUR APPLICATION↓SKHERIA API /v1↓ RESIDENT ENGINE
Explore the developer guideTHE WORLD, THROUGH ONE CONTRACTV1
cURL
curl "$SKHERIA_URL/v1/residents/$RESIDENT_ID/state" \
-H "Authorization: Bearer $SKHERIA_TOKEN"Read the resident’s current state. Optional wallet, event, plan and inventory fields require their own scopes.
curl -X POST "$SKHERIA_URL/v1/residents/$RESIDENT_ID/simulate" \
-H "Authorization: Bearer $SKHERIA_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: catch-up-001" \
-d '{"until":"2026-09-26T09:12:00.000Z","reason":"app_open"}'Advance to an allowed time, no later than the trusted server clock. A 202 response means more work remains: continue with a new idempotency key.
curl "$SKHERIA_URL/v1/residents/$RESIDENT_ID/events?limit=20" \
-H "Authorization: Bearer $SKHERIA_TOKEN"Retrieve permission-filtered events. Pagination uses opaque cursors; private causes and another relation’s data remain excluded.
Actual local API paths. Calls run from your backend with provisioned credentials.
View all 18 operationsTHE WORLD IS PART OF THE CHARACTER.
Give your AI
somewhere to live.
Explore Skheria for developersResident Engine V1 · Implemented locally. Hosted access is not yet available.