> 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/releases-and-reference/compatibility.md).

# Compatibility

What the SDK targets, how other stacks integrate, how the API changes over time, and how to identify what you are building against.

## Release identity

`docs-release-2026-07` (July 2026) identifies this documentation set. It is not a version stamp on the SDK, the API, or the configuration schema, and it does not pin them to a specific build.

Each of those surfaces is separately unversioned today:

* **The typed SDK** (`Game.Sdk` external, `Platform.Sdk` internal-only) targets `net10.0` and is delivered through onboarding rather than a public package feed. It carries no public package, build, or semantic version.
* **The HTTP API** is the current contract, with no route-level version segment.
* **The configuration document** (`AppConfigDto`) carries no version field.

So the documentation identifier describes the integration surface as it stands at this baseline, rather than mapping to a released binary or a numbered API. Changes from here are recorded in the [Release notes](/releases-and-reference/release-notes.md).

## SDK and runtime

The typed SDK is a .NET library. External games use `Game.Sdk`; it targets .NET 10 (`net10.0`) and runs on the .NET 10 runtime. It is not published to a public package feed today; it is provided as part of onboarding.

## Other stacks

The API is plain HTTP with JSON bodies, and a mutating domain call returns a single response envelope (authentication calls and read-only queries return their own shapes), so any language with an HTTP client can integrate without the .NET SDK, provided it also implements the device-key authentication the SDK handles for you: P-256 key generation and proof-of-possession signing (see [Authentication](/evaluate-and-integrate/authentication.md)). There is no MetaMarket SDK for Unity, Unreal, web, or mobile today; a game built on those integrates over the HTTP API. The .NET SDK saves you the request and directive-handling boilerplate; it is a convenience for .NET clients, not the only way in.

## API and configuration

The HTTP routes do not carry a version segment today. The compatibility posture is additive change: new fields and channels are added with safe defaults so existing clients keep working, and a change that would break an existing client is handled through the [Deprecation policy](/releases-and-reference/deprecation-policy.md) rather than shipped silently. App configuration is authored as typed configuration and updated through the assisted workflow described in [App Configuration](/evaluate-and-integrate/app-configuration.md); a configuration change reaches the running engine within its refresh window without a client release.

For the current state of each capability, see [Product availability](/overview/current-scope.md).

***

Last reviewed 2026-07. Documentation release `docs-release-2026-07`; runtime `net10.0`. The SDK, HTTP API, and configuration schema are separately unversioned. Status source of truth: [Product availability](/overview/current-scope.md).