> 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/readme.md). # 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](https://metamarket.tech/#contact) to start. ## Get started 1. **Understand the model.** Read [One Player, Many Games](/core-concepts/one-player-many-games.md) to see what belongs to one game, what spans your portfolio, and who can change what. [Evaluate MetaMarket](/evaluate-and-integrate/evaluate.md) covers what to check before committing. 2. **Check what is available.** [Product Availability](/overview/current-scope.md) lists the status of every capability. 3. **Get access.** [Getting Access](/evaluate-and-integrate/getting-access.md) covers registration and what you receive. 4. **Make your first call.** The [Integration Walkthrough](/evaluate-and-integrate/quickstart.md) signs a player in, sends an action, and reads state back. 5. **Declare your mechanics.** [App Configuration](/evaluate-and-integrate/app-configuration.md) covers the configuration document your game runs on. 6. **Go live.** [Production Operations](/architecture-and-trust/production-operations.md) covers retries, idempotency, and error handling. ## Build | Area | What you get | | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- | | [Engagement and Loyalty](/use-cases/engagement-and-loyalty-use-cases.md) | Quests, achievements, daily challenges, reward campaigns | | [Game Economy Infrastructure](/use-cases/game-economy.md) | Soft currencies, sinks and faucets, energy gating, shops | | [Marketplace Workflows](/use-cases/marketplace.md) | Player listings and studio catalogues | | [Local and Shared Economies](/core-concepts/shared-economy.md) | What a game owns, what the platform owns, and why no game can mint or read shared value | ## Integrate | Page | Covers | | ------------------------------------------------------------------- | --------------------------------------------------- | | [SDK Guide](/evaluate-and-integrate/sdk-guide.md) | The typed .NET client | | [HTTP API](/evaluate-and-integrate/api-guide.md) | Routes, headers, errors, the response envelope | | [Authentication](/evaluate-and-integrate/authentication.md) | Device keys, sessions, and handoff | | [Sending Actions](/evaluate-and-integrate/events-and-directives.md) | Reporting player activity and handling the response | | [Worked Examples](/evaluate-and-integrate/examples.md) | Complete request and response pairs | ## Understand | Page | Covers | | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | [Why MetaMarket](/overview/problem-and-value.md) | The problem the platform solves, and what you trade | | [Who It's For](/overview/who-its-for.md) | The studio profiles the platform suits | | [When MetaMarket Is a Good Fit](/overview/when-good-fit.md) | Where it fits, and where another tool is better | | [Architecture Overview](/architecture-and-trust/product-overview.md) | The services and where data lives | | [Security and Tenant Isolation](/architecture-and-trust/security-and-tenant-isolation.md) | How the boundaries are enforced | | [Studio and Platform Responsibilities](/architecture-and-trust/responsibilities-and-boundaries.md) | Who owns what, including the real-money boundary | | [Product in Practice](/overview/product-in-practice.md) | One flow from sign-in to a state change, against real interfaces | Questions about a specific integration? [Get in touch](https://metamarket.tech/#contact). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://sdk.metamarket.tech/overview/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.