Sverse Build
Publish a game
No business entity. No KYB. No platform review queue. Target: under 30 minutes
from finished build to live storefront.
✓ Studio & game
✓ Integration
3 Catalog
4 Live
1 · Studio
2 · Integration
3 · MCP run
4 · Live
🪪
Your S-Passport is the studio account — creating it deploys a Studio Vault
that receives 90% of every sale instantly. No entity, no KYB at this tier.
Create studio & continue →
How do you want to wire up payments?
Let my AI do it RECOMMENDED
Point Claude or ChatGPT at the project. The Sverse MCP server
scans your code, proposes a catalog, maps it onto interop schemas, installs the
SDK and runs a testnet purchase. You review and approve before anything mints.
Do it manually
Install the SDK yourself and define the catalog by hand or
from a CSV. Same three lines of code — just without the agent writing them.
Tokenization level
L0
Payments only
No NFTs, zero wallet friction for your players L2
Tokenized items DEFAULT
ERC-1155 minted to the player's passport L3
Living Items
Mutable traits + deed ledger L4
Tokenized economy
Needs an economy review before publishing
A dial, not a door. Moving up later is a
config change — but it is one-way, because player ownership must not be revocable.
← Back
Run integration →
claude · sverse mcp server
› add sverse payments to my game
✓ sverse.scan_project godot 4.3 · 41 scenes · 3 monetizable surfaces
✓ sverse.propose_items 12 candidates → 3 packs · priced vs comparables
✓ sverse.map_to_schema sts/cosmetic/wearable/v1 · sts/content/chapter/v1 → T1
◐ sverse.create_item_pack blocked — awaiting catalog approval
· sverse.install_sdk
· sverse.test_purchase
· sverse.publish
✋
The agent is paused. create_item_pack writes real
item definitions, so it requires your approval first. Nothing has minted yet.
Proposed catalog · edit anything
Ashen Cloak
sts/cosmetic/wearable/v1 · T1 · slot torso
SRV
✕
Chapter 2 · Cinderfall
sts/content/chapter/v1 · T0
SRV
✕
Starter Bundle
3 relics, 2 revives, 400 embers
SRV
✕
＋ Add an item the agent missed
🌐
map_to_schema ran automatically, so these items are
interop-ready by default — the cloak can render in other Sverse titles on day
one. That is how a standard actually gets adopted: for free, on every AI-assisted
integration, instead of as an opt-in chore.
← Back
Approve catalog
Publish to the Store →
Publish is disabled until the catalog is
approved — the reason is always stated, never just greyed out.
State: a step failed
claude · sverse mcp server
✓ sverse.install_sdk sverse-godot 1.4.2 · 11 lines changed
✗ sverse.test_purchase
402 insufficient_funds — test passport has 0 SRV
· retry clears steps after this one
Retry step
Fund test passport
Emberloop is live
Automated review passed — malware scan, IP
fingerprint, content policy.
4m 12s
elapsed from "create studio" to live storefront
Studio Vault deployed · receives 90%
Protocol fee 10% → 5% with staking
Items minted 3 · interop T1
Club opened automatically
Listing bond staked 250 SRV
The bond is slashable for fraud or IP
infringement — it is what makes an open, review-light storefront survivable at
thousands of studios.
State: blocked on bond
🔒
Emberloop stays in review. Publishing requires a staked listing bond of
250 SRV; your vault has 88 SRV available.
Top up the vault →