IntelliVerseX: One platform. A brand built to last.
How ToBa strengthened IntelliVerseX as its own platform brand: reviewing shared services, product workflows and integrations so the foundation stays consistent as the platform grows.
Client
Intelliverse
Industry
Apps, Games & Phygital Retail
Platform Architecture, SDK & Agent Skills, AI Gateway, Developer Portal
Platform
SDK, Router Portal & AI Gateway
Status
Live · MIT on GitHub
On this page
Overview
Challenge
Goals
Solution
Features
Process
Results
At a Glance
Shared infrastructure only matters if products actually connect.
Shared infrastructure only matters if products actually connect.
ToBa’s work on IntelliVerseX focused on platform integration and standardization making communication between components and shared services more consistent across the stack.
Channels
Mobile, smart kiosk, web, WhatsApp, chat & voice
SDK
Open source (MIT) across 11 engines incl. Unity, Unreal, C++, Typescript
Agent Skills
31 skills for natural-language development
Live-ops
33+ retention systems built in
Router
1 OpenAI-compatible endpoint, 9 capabilities on one key
Built on it
QuizVerse, Foundrly & partner apps
The Story
From integration friction to a strong platform foundation.
How ToBa investigated one-platform challenges across IntelliVerseX shared services, product workflows and the infrastructure that makes the brand reliable.
Before
Integration gaps
across capabilities in one platform.
Hard to connect capabilities as one platform
Inconsistent shared services & workflows
Complex app & capability integrations
Work Done
Reward system fixes
shared services and product links.
Investigated unified-platform issues
Reviewed component & service communication
Improved integrations for CX / QX / KX
After
Cohesive Platform
coordinated products and shared AI.
More consistent cross-platform workflows
Better coordination between products
Foundation for shared AI & commerce
PRODUCTS
Unstable
Connected
SHARED SERVICES
Inconsistent
Standardized
PLATFORM
Fragmented
Cohesive
Starting Point
Before.
One-platform integration challenges.
Connecting multiple capabilities in one platform was hard shared services and product workflows were inconsistent, and integrations across apps and platform features needed a stronger foundation.
01
1
Before
2
Work Done
3
After
The Challenge
A unified platform fails when products stay siloed.
Connecting multiple capabilities under IntelliVerseX was hard: shared services were inconsistent, app integrations were complex, and the platform needed clearer common infrastructure of its own.
THE OLD WAY
1 screen
is where most apps live: a phone or a kiosk, never both, with no path between them.
9 vendors
to stitch together LLMs, knowledge, media, voice, email, games and billing.
Siloed apps
Each app or game had its own users, wallet and data, with no shared platform foundation.
Rebuilt infrastructure
Auth, wallets and live-ops were rebuilt from scratch for every launch.
Retention left to chance
Teams shipped without live events, tournaments or earn mechanics.
Physical out of reach
Kiosks and vending machines needed custom hardware work to join an app.
Fragmented AI
Models, keys and costs were spread across many providers.
Slow from idea to launch
Turning an idea into a scoped build plan took weeks of meetings.
Goals
What a working unified platform had to deliver.
Success meant consistent cross-product workflows, clearer shared services, and infrastructure that actually supports IntelliVerseX as one platform brand.
01
An open toolkit
Make the core SDK free and open for anyone to read and extend.
TARGET
MIT licence
02
Build in plain English
Let AI coding agents plan, build and test from natural language.
TARGET
31 agent skills
03
Retention built in
Ship live events, tournaments and earn mechanics by default.
TARGET
33+ live-ops systems
04
Any channel
Reach people on phones, kiosks, web, WhatsApp, chat and voice.
TARGET
6 channels
Investigation, Fixes and Delivery
Work Done.
Platform integration & standardization.
We investigated unified-platform issues, reviewed communication between product components and shared services, improved integration consistency, and evaluated infrastructure so IntelliVerseX stands on a stronger foundation.
02
1
2
Before
Work Done
3
After
The Solution
One toolchain once integrations are standardized.
With platform integration issues addressed, IntelliVerseX can act as its own shared layer: SDK and services, Router and Gateway, and Brand Memory that every surface on the platform can use without reinventing connections each time.
01
Describe Your Idea
The AI Build Blueprint returns an engine, timeline and 3-phase plan.
02
Agent Skills Build
Skills guide AI coding agents from spec to live retention.
03
SDK & Services
Auth, wallet and live-ops built on Nakama and Hiro.
04
Router & Gateway
One API key for LLMs, knowledge, media, voice and comms.
05
Choose Channels
Mobile, smart kiosk, web, WhatsApp, chat or voice.
06
Grow the Platform
Add new apps and partner surfaces as the brand grows.
ONE TOOLCHAIN EVERY CHANNEL
Mobile apps
Mobile games
Smart-kiosk apps
Web apps
Web chat
Voice calls
App Quests
App Ads
Live events
Tournaments
Earn mechanics
Push & onboarding
AI Build Blueprint
Intelliverse SDK
Open source under MIT, with 31 agent skills across 11 engines and retention built in.
Intelliverse Router
A self-service AI portal with one OpenAI-compatible endpoint and 15 MCP tools for agents.
Shared Brand Memory
One brand or app ID, one wallet and one Memory across quests, content and kiosks.
Key Features
Built for builders, human and AI.
The product surfaces we designed so teams and their coding agents can go from idea to live app.
Feature 01
AI Build Blueprint
Describe an app or game in one sentence and get a recommended engine, a realistic timeline and a three-phase build plan. No email needed.
One sentence in, a build plan out
Engine recommendation across 11 engines
Hands off to the SDK or the studio
AI Build Blueprint
A trivia game with weekly tournaments
Generate
Engine
Unity
Timeline
3 phases
Retention
Tournaments
BUILD PLAN
1
Design & prototype
Mechanics, audience and goals
2
Build with Agent Skills
SDK auth, wallet and live events
3
Launch & grow
Live-ops, rewards & commerce
Illustrative output · no email required
Agent Skills
curl
Install
you › "Create an app with a knowledge base, ingest my docs, and email my users when it's live."
create_app({ name: "Docs Copilot", use_cases: ["chat","rag"] })
→ { id: "9c2e41…", recommended_tier: "pro" }
create_api_key({ name: "docs-copilot-prod", tier: "pro" })
→ { key: "sk-…" (shown once) }
kb_ingest({ documents: [{ url: "https://docs.myapp.com" }] })
→ { document_id: "d41f…", chunk_count: 42 }
send_email({ to: ["users@…"], subject: "We're live" })
→ { status: "sent", sent: 3 }
Feature 02
Router & Agent Skills
An AI agent runs the platform in plain English. It creates the app, mints keys, ingests knowledge and sends email through MCP tools.
1 OpenAI-compatible endpoint
9 capabilities on one key
15 MCP tools for AI agents
Live Events & Tournaments
Seasonal events and tournaments that bring players back.
Earn Mechanics
Wallet and rewards wired into apps and games.
Phygital Toolkit
JavaScript preview for kiosk quests and App Ads.
AI Transparency Hub
Model info, bias prevention, training data and safety.
Trust & Data Control
GDPR / CCPA ready, 2FA and passkeys, data export.
Nightly Price Audit
A public audit of prices and spend, every night.
Inside The Product
Screens from the shipped platform.
Real product surfaces from intelli-verse-x.ai and the Router portal. Swap these frames as the platform evolves.
Intelliverse Router
One API and Agent Skills: an AI agent creates apps, keys and knowledge in plain English.
Agent Skills & SDK
31 skills, 11 engines, 33+ live-ops systems, MIT.
Intelliverse Studio
Gateway vs Router vs Studio vs SDK, side by side.
How We Built It
Think. Orchestrate. Build. Accelerate.
Intelliverse followed the ToBa method. Each phase ended with something the team could review, run and measure.
T
01
Think
Weeks 1–3
Studied how teams build apps and games, and what they rebuild every time.
Builder interviews
Infrastructure audit
Channel & hardware research
DELIVERABLE
Platform thesis & scope
O
02
Orchestrate
Weeks 4–6
Designed the SDK surface, the Agent Skills format, the Router API and the shared Memory model.
SDK & engine adapters
SKILL.md skill format
Router & Gateway API
DELIVERABLE
Platform architecture
B
03
Build
Weeks 7–14
Shipped the open-source SDK, 31 agent skills, the Router portal and the AI Gateway.
31 agent skills
Nakama + Hiro live-ops
Router portal & billing
DELIVERABLE
Open SDK on GitHub (MIT)
A
04
Accelerate
Ongoing
Launched partner apps on the stack, plus QuizVerse and Foundrly.
Phygital JS toolkit
Kiosk quests & App Ads
Trust & AI transparency
DELIVERABLE
A growing app platform
Tech Stack
The engine under the platform.
Open-source foundations, one AI layer, and the trust controls teams need to ship to real users.
SDK & Engines
Build on the engine you know
Intelliverse SDK
Unity
Unreal
Godot
Roblox
Nakama
Hiro live-ops
GitHub · MIT
AI Layer
One key, many capabilities
Intelliverse Router
AI Gateway
31 Agent Skills
15 MCP tools
OpenAI-compatible API
Cursor · Claude Code · Copilot
Platform Services
Built in by default
Auth
Wallet
Live events
Tournaments
Push & onboarding
Knowledge base
Voice & email
Billing
Trust
For real users and brands
GDPR / CCPA ready
SOC 2 in progress
2FA / passkeys
AI Transparency Hub
Data export & delete
RNG audit
The Outcome
After.
A stronger platform foundation.
Cross-platform workflows are more consistent, connected products coordinate better, and there is a stronger foundation for shared AI capabilities, engagement and physical commerce.
03
1
2
3
Before
Work Done
After
Results
A stronger IntelliVerseX platform under one brand.
After the integration and standardization work, IntelliVerseX stands as a more reliable platform brand with more consistent cross-platform workflows and clearer shared AI, engagement and commerce capabilities.
11
Engines supported
Unity, Unreal, Godot, Roblox and more.
31
AI agent skills
Natural-language development for any AI coding agent.
33+
Live-ops systems
Retention built in from day one.
MIT
Open source
Free to read, try and contribute.
INTELLIVERSE VS. THE ALTERNATIVES
METRIC
INTELLIVERSE
BUILD FROM SCRATCH
SINGLE-CHANNEL PLATFORM
Channels
Mobile, kiosk, web, chat, voice
One at a time
One
Retention systems
33+ built in
Build yourself
Limited
AI tooling
31 skills + one API key
Custom integrations
Add-ons
Licence
MIT open source
N/A
Proprietary
Physical retail
Native partner surfaces
Custom hardware work
None
Before Vs After
What changed, line by line.
The same IntelliVerseX platform job, before and after ToBa’s work, across the areas that mattered most.
AREA
BEFORE
AFTER · WORK DONE
IMPACT
Shared Services
Inconsistent across workflows
Reviewed component communication
CONSISTENT
Integrations
Complex across apps & capabilities
Improved integration consistency
STABLE
Infrastructure
Unclear support for CX / QX / KX
Evaluated shared infrastructure
CLEARER
Platform
Fragmented product experience
More cohesive cross-product workflows
PHYGITAL
The Journey
One job, two journeys.
The same platform job, step by step: how products struggled to connect before, and how they run after ToBa’s integration work.
BEFORE
Fragmented
One-platform integration challenges across the brand.
1
Connect products manually
High friction
2
Shared services drift
Inconsistent workflows
3
App integrations pile up
Complex capability links
4
CX / QX / KX stay siloed
Weak shared layer
What ToBa changed
AFTER · WORK DONE
Cohesive
A more unified platform for shared AI, engagement and commerce.
1
Investigate platform issues
Root-cause clarity
2
Review service communication
Component alignment
3
Standardize integrations
Consistent workflows
4
Strengthen shared infra
CX · QX · KX
Who feels the difference
For platform teams
Clearer shared services.
Communication between product components and shared services was reviewed and made more consistent.
For product teams
Easier integrations.
Cross-application workflows are less complex and more standardized across the platform.
For the platform
One connected stack.
A stronger foundation for shared AI, engagement and physical commerce under the IntelliVerseX brand.
Learnings
What we learned building Intelliverse.
KEY INSIGHT
One channel is a complete starting point. Connection should be optional, never a requirement.
That belief let teams start mobile-only or kiosk-only and grow into phygital when it helps their users.
01
Write skills, not docs
Shipping every capability as a SKILL.md let any AI coding agent use the platform from day one.
02
Open source builds trust
An MIT SDK on GitHub made it easy for teams to read, try and adopt before talking to sales.
Start Here
Let’s build what comes next.
Two worlds, one team. One unlocks intelligence and removes systemic friction. The other builds high-fidelity digital touchpoints that capture attention.
