Agent-ready OpenAPI document · curated by JenticMediaContent Deliverybearer24 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Resolve Minecraft usernames to UUIDs and read public profiles without a credential, and, with a bearer token, read the signed-in profile, change the name, and manage skins and capes.
Use for: Get the UUID for a Minecraft username, Look up a player's profile by UUID, Resolve a list of usernames to UUIDs, Read my current Minecraft profile
Not supported: Covers Minecraft player identity, profile, skins, capes, and the join session handshake. Does not manage game servers, purchases, or world data.
The Mojang API resolves Minecraft player identities and manages the signed-in player's profile. Public endpoints turn a username into a UUID, look a profile up by UUID, and resolve names in bulk, so no credential is needed to read basic player data. Authenticated endpoints, which take a bearer token, read the current profile, change the player name, upload or clear skins and capes, and read attributes and entitlements. Session endpoints back the join handshake used by game servers.
Install Jentic One Beta
Connect the Mojang API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mojang API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmojang.com%2Fmojang" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmojang.com%2Fmojang" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Mojang API.
Resolve a Minecraft username to a UUID and look a profile up by UUID
Resolve many usernames to UUIDs in one bulk call
Read the signed-in player's profile with a bearer token
Check name availability and change the player name
Upload, activate, or clear the player's skins and capes
Read player attributes, entitlements, and the join session state
Use Cases
Patterns agents use Mojang API for, with concrete tasks.
★ Agent Player Lookup
A community bot can turn a Minecraft username into a stable UUID and read the public profile without any credential. The agent calls the username-to-UUID endpoint, reads back the UUID, and fetches the profile, so a request like 'find this player's UUID' is answered from the public endpoints alone.
Resolve a username to a UUID and return the public profile for it
Bulk Roster Resolution
A server-management agent can resolve a whole roster of usernames to UUIDs in one call before it applies whitelist or ban changes. It posts the name list to the bulk lookup endpoint and reads back the UUIDs, so a large roster is normalized in a single request rather than one call per name.
Resolve a list of usernames to UUIDs in one bulk call for a whitelist update
Profile Self-Service
With the player's bearer token, an assistant can manage the signed-in profile on request. It reads the current profile, checks name availability, and uploads a new skin when asked, so a change like 'set this skin' runs through the authenticated endpoints while the token stays on the player's own infrastructure.
Read the signed-in profile and upload a requested skin using the player's bearer token
Key Endpoints
24 endpoints — the mojang api resolves minecraft player identities and manages the signed-in player's profile.
METHOD
PATH
DESCRIPTION
GET
/users/profiles/minecraft/{playerName}
Resolve a username to a UUID
GET
/session/minecraft/profile/{uuid}
Look up a profile by UUID
POST
/minecraft/profile/lookup/bulk/byname
Resolve many usernames in bulk
GET
/minecraft/profile
Read the signed-in profile
PUT
/minecraft/profile/name/{newName}
Change the player name
POST
/minecraft/profile/skins
Upload a skin
GET
/users/profiles/minecraft/{playerName}
Resolve a username to a UUID
GET
/session/minecraft/profile/{uuid}
Look up a profile by UUID
POST
/minecraft/profile/lookup/bulk/byname
Resolve many usernames in bulk
GET
/minecraft/profile
Read the signed-in profile
PUT
/minecraft/profile/name/{newName}
Change the player name
POST
/minecraft/profile/skins
Upload a skin
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Mojang API
- AI-Aware (B)66/100
93
Foundational Compliance62
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability60
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
47%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mojang API by hand means tracking which endpoints are open and which take a bearer token, and spreading calls across its profile and session hosts. Through Jentic you install once, import it from the API Directory, store the token for the authenticated calls, and your agent uses the profile operations.
Permission scoping
A rule can allow only the operations your agent needs, such as the public username-to-UUID lookups, and leave the account-changing operations like name changes and skin uploads out of scope until you add them. You decide which operations are in scope, and every call the agent makes is logged.
Credential isolation
Your Mojang bearer token is stored once, encrypted, by your own Jentic One instance and added only to the authenticated calls at execution time. It never enters the agent's prompt, logs, or context, and the public lookups run without it.
Intent-based discovery
Agents search Jentic by intent such as 'resolve a Minecraft username' or 'read my profile', and Jentic returns the matching Mojang operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mojang API through Jentic.
What authentication does the Mojang API use?
The Mojang API mixes open and authenticated endpoints, per its OpenAPI spec: the profile lookups that resolve usernames and UUIDs need no credential, while reading the signed-in profile and managing skins, capes, and the name take a bearer token in the Authorization header. Through Jentic that token is held by your own self-hosted instance and added only to the calls that need it.
Can I resolve a Minecraft username to a UUID with the Mojang API?
Yes, and it needs no credential. Call the username-to-UUID lookup with a player name to get the UUID, then look the profile up by UUID. To resolve many names at once, post the list to the bulk lookup endpoint.
What are the rate limits for the Mojang API?
The OpenAPI spec for the Mojang API does not define rate limits. Mojang applies per-endpoint throttling on the profile lookups, so check its current documentation before running high-volume resolution.
Is there a Mojang API MCP server?
You don't need an MCP server to give your agent the Mojang API. Jentic connects it directly from the API Directory: import it, store the bearer token for the authenticated calls, and your agent uses the profile and session operations without another server's tool definitions loaded into its context.
Can I limit what my agent is allowed to do with the Mojang API?
Yes. Write a rule that allows only the public profile-lookup operations, so the agent can resolve players but cannot change the name or clear skins unless you add those operations. The scoped set is yours to choose, and each request is recorded.
How do I resolve a Minecraft username through Jentic?
Search Jentic with an intent like 'get the UUID for a Minecraft username', and it returns the lookup operation with its input schema so the agent submits the name and reads back the UUID. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED