> For the complete documentation index, see [llms.txt](https://sdk.metamarket.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.metamarket.tech/overview/current-scope.md). # Product Availability The single reference for what MetaMarket provides right now. Other pages link here rather than repeat status details, so this is where to confirm the exact state of a capability. ## Status meanings | Status | What it means | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Proven in MetaMarket's own games and modules** | Running today in MetaMarket's own reference games and platform modules. | | **Available through assisted integration** | A partner can build on it now; registration, configuration, and onboarding are done with the MetaMarket team rather than self-serve. | | **Planned** | Committed work, not yet built. See the [Roadmap](/releases-and-reference/roadmap.md). | | **Under evaluation** | A direction being considered, with no commitment. See the [Roadmap](/releases-and-reference/roadmap.md). | | **Internal only** | A privileged platform mechanism operated by MetaMarket, not offered for partner integration (the `system` app, `Platform.Sdk`, and admin/provisioning surfaces). | ## What a studio can build on today The configuration-driven engine covers quests, progression, rewards, resources, and refillable quotas. All of it is proven in MetaMarket's own games and available to a partner through assisted integration. Because mechanics are read from configuration on each request, changing one takes effect within the platform's refresh window and without a redeploy. Player identity is durable and works across devices. A device proves possession of a key it generated, and a one-time handoff links a second install to the same player. Sign-in uses guest identity today, so passkey, social login, and durable account recovery without a signed-in device are planned rather than available. The shared economy is a platform currency, GG, together with a loyalty tier and badge ladder that stay consistent across connected games. All of it is platform-owned: a connected game reports milestones that the platform turns into GG and loyalty grants, and cannot read or configure the result. A platform-operated daily login reward also credits loyalty. What a partner integrates is the milestone report itself, through assisted onboarding; cross-game content and redemption remain planned. Within a single game, players can list items they own for others to buy. Quest renewal is recorded as structured events. Other activity, including actions, rewards, inventory changes, and economy movements, is captured in operational logs. Between them they support monitoring and investigation today, while a durable queryable store and reporting built on top of it are planned. [Operational Data](/use-cases/engagement-data-and-operational-insights.md) sets out what a partner can obtain now and how. Integration is a .NET SDK or the HTTP API, both using the same response envelope on mutating domain calls (authentication and read-only calls return their own shapes), so any stack integrates over HTTP once it implements the device-key authentication the SDK otherwise handles. Registration and configuration are set up with the team; self-serve onboarding is planned. ## Capability status | Capability | Status | | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | Configuration-driven engine (quests, rewards, resources, quotas) | Proven in MetaMarket's own games and modules · Available through assisted integration | | Player identity, device auth, cross-install handoff | Proven in MetaMarket's own games and modules · Available through assisted integration (guest sign-in) | | Platform currency (GG), loyalty tiers and badges (platform-operated, not a partner-integrated interface) | Proven in MetaMarket's own games and modules | | Reporting a milestone that the bridge turns into a GG or loyalty grant | Available through assisted integration | | Within-game item listings and studio shops | Proven in MetaMarket's own games and modules · Available through assisted integration | | Operational records (logs; quest renewal events) | Proven in MetaMarket's own games; partner access is team-operated today, with no partner-facing stream | | .NET SDK and HTTP API | Available through assisted integration | | Passkey and social sign-in; durable account recovery | Planned | | Cross-game progression; shared marketplace catalogue and cross-game redemption | Planned | | Reporting, dashboards, durable event store | Planned | | Designer-facing configuration tooling | Planned | | Self-serve onboarding and sandbox | Planned | | Segmentation, experimentation, cross-game player-to-player trading, real-money exchange | Under evaluation | | First-party surfaces: the `system` app, `Platform.Sdk`, admin and seeding endpoints | Internal only | MetaMarket works on game-native value; the real-money boundary is covered in [Studio and platform responsibilities](/architecture-and-trust/responsibilities-and-boundaries.md). The [Roadmap](/releases-and-reference/roadmap.md) has the direction and ordering behind everything marked planned or under evaluation. *** Last reviewed 2026-07. Documentation release `docs-release-2026-07`; runtime `net10.0`. The SDK, HTTP API, and configuration schema are separately unversioned ([Compatibility](/releases-and-reference/compatibility.md)).