Mojang
Mojang Studios is the developer of Minecraft. The Mojang / Minecraft Services API surface covers Minecraft player identity (UUID and profile lookup), skins and capes, name history and name change, server session verification, blocked server lists, player attributes (privacy, chat, friends settings), friends graph, presence, public keys for profile signature verification, and account entitlements. Endpoints span three hosts: the legacy api.mojang.com, the session-server sessionserver.mojang.com (Yggdrasil), and the modern Microsoft-side api.minecraftservices.com. Most read endpoints are public and unauthenticated; player-account endpoints require a Bearer Minecraft access token obtained via the Xbox Live / XSTS authentication chain.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Mojang the way a machine reads it — 129 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mojang scores 46.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Mojang
Each block below is one kind of artifact we hold for Mojang. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mojang Attributes API
Profanity filter, friends, chat preferences
Mojang Authentication API
Exchange Xbox Live tokens for Minecraft access tokens
Mojang Blocklist API
Player privacy blocklist
Mojang Capes API
Cape selection and visibility
Mojang Entitlements API
Account ownership and entitlement checks
Mojang Friends API
Friends graph (list, add, remove)
Mojang Identity API
Player UUID and username lookup
Mojang Keys API
Signature keypairs and Mojang public keys
Mojang Presence API
Online / playing presence reporting
Mojang Profile API
Authenticated profile and name management
Mojang Server API
Server-policy artifacts (blocked servers)
Mojang Session API
Login-handshake session verification
Mojang Skins API
Skin selection, upload, and reset
Mojang Textures API
Player skin and cape texture lookup
Scroll within the panel for all 14 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Minecraft Services API
OPEN COLLECTIONMojang Public API
OPEN COLLECTIONMojang Session Server
OPEN COLLECTIONRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mojang Rate Limits
RATE LIMITSSemantic Vocabularies 4
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mojang Api Context
JSON-LDMojang Public Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Mojang API Rules
SPECTRALMojang API Rules
SPECTRALJSON Schema 34
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AuthenticatedProfile
JSON SCHEMABanStatus
JSON SCHEMABlocklist
JSON SCHEMACape
JSON SCHEMACapeSelection
JSON SCHEMAChangeSkinRequest
JSON SCHEMAEntitlementItem
JSON SCHEMAEntitlements
JSON SCHEMAFriend
JSON SCHEMAFriendUpdateRequest
JSON SCHEMAFriendsList
JSON SCHEMAFriendsPreferences
JSON SCHEMAMinecraftAccessToken
JSON SCHEMANameAvailability
JSON SCHEMANameChangeInfo
JSON SCHEMAPlayerAttributes
JSON SCHEMAPlayerAttributesUpdate
JSON SCHEMAPlayerCertificates
JSON SCHEMAPresenceEntry
JSON SCHEMAPresenceReport
JSON SCHEMAPrivilegeMap
JSON SCHEMAProfanityFilterPreferences
JSON SCHEMAProfile
JSON SCHEMAPublicKeyEntry
JSON SCHEMAPublicKeys
JSON SCHEMASkin
JSON SCHEMAXboxLoginRequest
JSON SCHEMANameChange
JSON SCHEMAProfile
JSON SCHEMASaleStatisticsRequest
JSON SCHEMASaleStatistics
JSON SCHEMAJoinRequest
JSON SCHEMASessionProfile
JSON SCHEMASessionProperty
JSON SCHEMAScroll within the panel for all 34 ·
JSON Structure 34
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Minecraft Services Authenticated Profile Structure
JSON STRUCTUREMinecraft Services Ban Status Structure
JSON STRUCTUREMinecraft Services Blocklist Structure
JSON STRUCTUREMinecraft Services Cape Selection Structure
JSON STRUCTUREMinecraft Services Cape Structure
JSON STRUCTUREMinecraft Services Change Skin Request Structure
JSON STRUCTUREMinecraft Services Entitlement Item Structure
JSON STRUCTUREMinecraft Services Entitlements Structure
JSON STRUCTUREMinecraft Services Friend Structure
JSON STRUCTUREMinecraft Services Friend Update Request Structure
JSON STRUCTUREMinecraft Services Friends List Structure
JSON STRUCTUREMinecraft Services Friends Preferences Structure
JSON STRUCTUREMinecraft Services Minecraft Access Token Structure
JSON STRUCTUREMinecraft Services Name Availability Structure
JSON STRUCTUREMinecraft Services Name Change Info Structure
JSON STRUCTUREMinecraft Services Player Attributes Structure
JSON STRUCTUREMinecraft Services Player Attributes Update Structure
JSON STRUCTUREMinecraft Services Player Certificates Structure
JSON STRUCTUREMinecraft Services Presence Entry Structure
JSON STRUCTUREMinecraft Services Presence Report Structure
JSON STRUCTUREMinecraft Services Privilege Map Structure
JSON STRUCTUREMinecraft Services Profile Structure
JSON STRUCTUREMinecraft Services Public Key Entry Structure
JSON STRUCTUREMinecraft Services Public Keys Structure
JSON STRUCTUREMinecraft Services Skin Structure
JSON STRUCTUREMinecraft Services Xbox Login Request Structure
JSON STRUCTUREPublic Api Name Change Structure
JSON STRUCTUREPublic Api Profile Structure
JSON STRUCTUREPublic Api Sale Statistics Request Structure
JSON STRUCTUREPublic Api Sale Statistics Structure
JSON STRUCTURESession Server Join Request Structure
JSON STRUCTURESession Server Session Profile Structure
JSON STRUCTURESession Server Session Property Structure
JSON STRUCTUREScroll within the panel for all 34 ·
Examples 34
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Public Api Profile Example
EXAMPLEScroll within the panel for all 34 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mojang — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mojang · machine-readable index on apis.io