Mixed Reality

Name: Mixed Reality API
Brand: Azure Mixed Reality
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth210 EndpointsREST

For Agents

Provision Azure Spatial Anchors accounts, manage their access keys, and check name availability. Covers 10 endpoints across the Microsoft.MixedReality control plane.

Connect the Mixed Reality to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mixed Reality, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mixed Reality API.

Create and update Spatial Anchors accounts in a specific Azure region

List Spatial Anchors accounts across a subscription or scoped to a resource group

Retrieve the current primary and secondary keys for a Spatial Anchors account

Regenerate the primary or secondary key to rotate Spatial Anchors credentials

GET STARTED

Start building with Mixed Reality API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Mixed Reality, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Azure Mixed Reality, keeping it validated and agent-ready. The Mixed Reality Resource Provider provisions and manages Spatial Anchors accounts, the cloud resource that backs Azure Spatial Anchors apps for HoloLens, iOS, and Android. The control plane lets developers create accounts in a region, list them across a subscription or resource group, regenerate primary or secondary access keys, and check name availability before provisioning. Spatial Anchors accounts are the gating credential boundary for any client SDK call against the Spatial Anchors data plane.

Use Cases

Patterns agents use Mixed Reality API for, with concrete tasks.

★ Provisioning Spatial Anchors backends for AR apps

AR development teams building HoloLens or ARKit apps create a dedicated Spatial Anchors account per environment. The Mixed Reality API lets a CI workflow check name availability, create the account in the chosen region, retrieve the primary key, and surface that key as a secret for the mobile build pipeline. End-to-end provisioning takes under a minute for each environment.

Check availability of name spatial-prod in eastus, create the Spatial Anchors account in resource group ar-prod, and return its primary key.

Spatial Anchors key rotation

Security teams that rotate cloud credentials on a schedule need to cycle the primary or secondary keys on every Spatial Anchors account in scope. The API exposes a regenerateKey action that swaps a single key without breaking the other, allowing zero-downtime rotation: rotate secondary, deploy app updates, rotate primary. Each rotation completes in seconds.

Regenerate the secondary key on Spatial Anchors account spatial-prod in resource group ar-prod, then return the new key value for redeployment.

Cost and governance reporting on AR resources

Cloud governance dashboards need an inventory of Spatial Anchors accounts across the tenant. Listing accounts per subscription returns location, SKU, and tags, which can be joined against billing data to attribute Mixed Reality spend to product teams. Tag updates can be pushed via the same API to enforce cost-allocation policy.

List all Spatial Anchors accounts in subscription abc, group them by tag costCenter, and return a JSON summary of the count per cost center.

Agent-driven Spatial Anchors lifecycle

AI agents can use Jentic to discover Mixed Reality Resource Provider operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing the Azure REST docs. An onboarding agent for a new AR project can stand up the entire backend with a single intent search and return the credential to the developer to plug into their client SDK.

Search Jentic for create azure spatial anchors account, load the input schema, and execute it for region westeurope with the SKU S0 and tag environment dev.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for azure mixed reality, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}

Create or update a Spatial Anchors account

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MixedReality/spatialAnchorsAccounts

List Spatial Anchors accounts in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys

Get the access keys for a Spatial Anchors account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys

Regenerate a Spatial Anchors account key

POST

/subscriptions/{subscriptionId}/providers/Microsoft.MixedReality/locations/{location}/checkNameAvailability

Check Spatial Anchors account name availability

PUT

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}

Create or update a Spatial Anchors account

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MixedReality/spatialAnchorsAccounts

List Spatial Anchors accounts in a subscription

GET

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys

Get the access keys for a Spatial Anchors account

POST

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName}/keys

Regenerate a Spatial Anchors account key

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth credentials and service principals are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens for management.azure.com at execution time; client secrets and certificates never enter the agent context.

Intent-based discovery

Agents search by intent (for example create spatial anchors account or rotate spatial anchors key) and Jentic returns the matching ARM operation with its full input schema, so the agent can call the correct path without browsing Microsoft Learn docs.

Time to first call

Direct integration with the Mixed Reality REST API: 1 day for AAD auth, account provisioning flow, and key handling. Through Jentic: under 30 minutes to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Azure Cognitive Services

Provisions Cognitive Services accounts that AR apps often pair with Spatial Anchors for vision and speech.

Use this when the agent needs to provision a Computer Vision, Speech, or other Cognitive Services account alongside a Spatial Anchors account.

Complementary

Azure Maps Resource Provider

Provisions Azure Maps accounts for outdoor location services that complement indoor Spatial Anchors.

Choose this when the AR app needs outdoor mapping and routing in addition to indoor spatial anchors.

Complementary

Azure Resource Management

Manages the resource groups and tags that contain Spatial Anchors accounts.

Use this when the agent needs to create the resource group or apply tags before deploying a Spatial Anchors account.

FAQs

Specific to using Mixed Reality API through Jentic.

Why is there no official OpenAPI spec for Azure Mixed Reality?

Microsoft Azure does not publish an OpenAPI specification for the Microsoft.MixedReality Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call Azure Mixed Reality via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Azure Mixed Reality API use?

The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential.

Can I create a Spatial Anchors account through the Azure Mixed Reality API?

Yes. PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MixedReality/spatialAnchorsAccounts/{spatialAnchorsAccountName} creates or updates the account. The body must include a location and may include tags and a SKU. After creation, retrieve the access keys via the keys endpoint to wire the account into a client SDK.

What are the rate limits for the Azure Mixed Reality API?

The control plane follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. Account creation and key regeneration are infrequent control-plane operations, so practical rate limits are not a concern for typical workflows.

How do I rotate a Spatial Anchors account key through Jentic?

Search Jentic for regenerate spatial anchors key, load the schema for POST under spatialAnchorsAccounts/{name}/keys, and execute it with the keyName field set to primary or secondary. Jentic handles the AAD token exchange and returns the new key, which the agent can hand off to a deployment workflow.

Does the Mixed Reality API call the Spatial Anchors data plane?

No. This API is the control plane: it provisions accounts and manages their keys. Actual anchor creation, lookup, and deletion is done through the Spatial Anchors client SDKs (HoloLens, iOS, Android, Unity), which authenticate using the keys retrieved from this control plane.