How wilds.ai works

The big picture

Five layers from input to infrastructure: user surface on top, the Wilds runtime that compiles prompts into playable worlds, the AgentOS core that powers every AI feature (memory, voice, personality, RAG), deterministic engines + game families below, and the platform stack at the foundation.

Type a sentence, get a playable world

The compiler walks 6 stations from raw prompt to a session you can click play on. Enrichment fans out 27 stages of lore, art, and audio so the world ships with depth, not just mechanics.

Companions that remember

Nine neuroscience-backed memory mechanisms shape what companions recall, forget, and reconsolidate. HEXACO personality modulates encoding salience; mood (PAD) + trust shift every turn.

The $WILD economy

Two currencies, one valve. Credits are the compute fuel — bought via Stripe credit packs, earned by creators whose worlds + companions get played, granted as a 500-credit signup bonus, dripped daily on paid tiers. Every AI action burns credits, mapped to real API cost.

$WILD is the in-world reward currency. It has no direct Stripe purchase path — instead, players bridge their credits into $WILD via a one-way bridge that pulls from the purchased + reward ledgers only. Daily-drip, monthly-plan, and signup-bonus credits stay compute-only; they never convert. $WILD never converts back into credits, so the in-world economy stays self-contained.

Marketplace purchases route 70% to the creator, 20% to the platform, and 10% to a per-blueprint reward pool that funds leaderboard payouts to players. A self-balancing governor nudges the conversion rate and pool payout multiplier within bounded envelopes on a periodic tick — pools fill faster than they drain, the multiplier scales down; pools idle, the rate opens up. The infrastructure is shipped today; user-facing checkout UI unlocks when the metaverse launches with NPC merchants, in-world purchases, and the cross-world bridge.

Creator cash-out runs on a separate rail. Every wallet has two buckets: a cashable bucket fed only by gameplay (leaderboard payouts on approved worlds) and marketplace sales, and a non-cashable bucket fed by purchased credits and signup bonuses. Only the cashable bucket reaches Stripe Connect — purchased $WILD never converts to cash by design, which keeps wilds.ai out of being a payment processor. Earnings clear a 30-day chargeback hold, then redeem above a $25 minimum through Stripe Connect Express. The full stack — buckets, FIFO eligibility ledger, payout audit table, atomic local debit with rollback on Stripe failure, webhook-driven settle/reverse, admin queue with retry + mark-resolved — is live today behind a launch flag.

VR is a fourth surface, not a fork

Every blueprint already runs on web and native mobile. The VR shell adds a third entry surface that talks to the same session API, the same companion orchestrator, the same deterministic engines. A single capability gate decides whether the headset can render a family natively, mirror it on a curved cinema screen, or fall back to flat. Creators never publish twice.

The @wilds/xr package owns the controller + hand-tracking providers, the curved-panel + cinema-screen primitives, locomotion + comfort gates (teleport, smooth move, snap turn, vignette, sitting mode), and the companion portrait/avatar bridge. Family adapters pick their track per blueprint: realtime-3d renders natively, narrative + visual novel + crawler ride the cinema screen with companion portraits floating beside, arcade + platformer + roguelike project their canvas onto a curved DOM panel. Read the full VR walkthrough on /vr.