MetaMarket

MetaMarket is cross-game software infrastructure that helps studios build lasting player relationships across their titles.

One backend runs your quests, progression, rewards, inventory, currencies, energy, and quotas as configuration rather than services you build. It carries one player identity into every title you ship.

Build the first game. Reuse the foundation for every one after it.

Onboarding runs through the MetaMarket team. We register your app, prepare its configuration with you, and deliver the SDK. There is no self-service signup today. Get in touch to start.

Get started

1. Understand the model. Read One Player, Many Games to see what belongs to one game, what spans your portfolio, and who can change what. Evaluate MetaMarket covers what to check before committing.

2. Check what is available. Product Availability lists the status of every capability.

3. Get access. Getting Access covers registration and what you receive.

4. Make your first call. The Integration Walkthrough signs a player in, sends an action, and reads state back.

5. Declare your mechanics. App Configuration covers the configuration document your game runs on.

6. Go live. Production Operations covers retries, idempotency, and error handling.

Build

Area	What you get
Engagement and Loyalty	Quests, achievements, daily challenges, reward campaigns
Game Economy Infrastructure	Soft currencies, sinks and faucets, energy gating, shops
Marketplace Workflows	Player listings and studio catalogues
Local and Shared Economies	What a game owns, what the platform owns, and why no game can mint or read shared value

Integrate

Page	Covers
SDK Guide	The typed .NET client
HTTP API	Routes, headers, errors, the response envelope
Authentication	Device keys, sessions, and handoff
Sending Actions	Reporting player activity and handling the response
Worked Examples	Complete request and response pairs

Understand

Page	Covers
Why MetaMarket	The problem the platform solves, and what you trade
Who It's For	The studio profiles the platform suits
When MetaMarket Is a Good Fit	Where it fits, and where another tool is better
Architecture Overview	The services and where data lives
Security and Tenant Isolation	How the boundaries are enforced
Studio and Platform Responsibilities	Who owns what, including the real-money boundary
Product in Practice	One flow from sign-in to a state change, against real interfaces

Questions about a specific integration? Get in touch.