MineSkin API

Name: MineSkin API
Brand: MineSkin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingbearer9 EndpointsREST

For Agents

Generate signed Minecraft skin textures from a URL, an uploaded image, or a player UUID, and look up previously generated skins by id. Used by Minecraft plugins and avatar tools.

Install Jentic One Beta

Connect the MineSkin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MineSkin 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.

Step 1: 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

Step 2: 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 MineSkin API.

Generate a signed Minecraft skin from an image URL with POST /generate/url

Upload an image file directly and receive a signed skin payload via POST /generate/upload

Reuse an existing Mojang account skin with POST /generate/user given a player UUID

GET STARTED

Start building with MineSkin API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MineSkin API for, with concrete tasks.

★ Minecraft Plugin Avatar Generation

Server plugins call /generate/url or /generate/upload to mint signed skin payloads on demand for cosmetic items, NPCs, or trail effects. MineSkin returns the value and signature pair Mojang expects on the player profile properties, so plugins do not need to handle Mojang authentication themselves.

Submit a skin URL via POST /generate/url and pass the returned value+signature to a Minecraft plugin's NPC creation call

Player Skin Lookup

Resolve any Minecraft player's current skin from a UUID through GET /get/uuid/{uuid}. Useful for leaderboards, profile pages, and avatar caches that render player heads alongside scores or stats. The signed payload can be re-used wherever a Mojang skin is expected.

Call GET /get/uuid/{uuid} and surface the skin texture URL on a leaderboard avatar

Skin History Pagination

Browse historical generations with GET /get/list/{page} for moderation queues, gallery features, or analytics over generated skins. Each page returns a fixed-size set of records that the agent can iterate through to enumerate all skins on the account.

Iterate GET /get/list/{page} from page 1 onwards until the response returns no records, collecting all skin ids

Agent-Driven Skin Generation

An AI agent receives a player avatar request and uses Jentic to find and call the MineSkin generator without learning the API by hand. Jentic isolates the bearer token, so the agent calls /generate/url through a scoped execution request and returns the signed skin payload to the calling app.

Search Jentic for 'generate a Minecraft skin from a URL', load the MineSkin schema, and execute against a 64x64 PNG hosted on Imgur

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for mineskin api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/generate/url

Generate a skin from an image URL

POST

/generate/upload

Generate a skin from an uploaded file

POST

/generate/user

Generate from an existing user UUID

GET

/get/id/{id}

Get a skin by id

GET

/get/uuid/{uuid}

Get a skin record by player UUID

GET

/get/list/{page}

Page through generated skins

GET

/get/delay

Get current generation delay

POST

/generate/url

Generate a skin from an image URL

POST

/generate/upload

Generate a skin from an uploaded file

POST

/generate/user

Generate from an existing user UUID

GET

/get/id/{id}

Get a skin by id

GET

/get/uuid/{uuid}

Get a skin record by player UUID

Why Jentic?

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

Credential isolation

The MineSkin bearer token is stored in the Jentic vault. Agents call generation endpoints through scoped Jentic execution requests, so the token never appears in agent context, prompts, or logs.

Intent-based discovery

Agents search Jentic for intents like 'generate a Minecraft skin' and Jentic returns the right /generate variant — URL, upload, or user — with its input schema so the agent picks the correct flow.

Time to first call

Direct MineSkin integration: a few hours to wire bearer auth and respect the delay endpoint. Through Jentic: minutes — search, load schema, execute.

FAQs

Specific to using MineSkin API through Jentic.

Why is there no official OpenAPI spec for MineSkin API?

MineSkin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MineSkin API 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 MineSkin API use?

MineSkin uses HTTP bearer token authentication. The token goes in the Authorization header as `Bearer <token>`. Through Jentic the token is stored in the vault and injected per call so the agent does not handle the raw secret.

Can I generate a skin from a hosted image URL?

Yes. POST /generate/url accepts an image URL and returns the signed Minecraft skin texture payload (value and signature) that Mojang expects on a player's profile properties.

What is /get/delay used for?

GET /get/delay returns the current per-account delay in seconds before the next generation request is allowed. Agents should call it before bursts of /generate calls and back off if the delay is non-zero.

How do I generate a Minecraft skin through Jentic?

Run `pip install jentic`, search Jentic for 'generate a Minecraft skin from a URL', and Jentic returns the MineSkin /generate/url operation. Pass the image URL and execute; the signed payload comes back as JSON.

MineSkin API

Connect the MineSkin API to your agent

Capabilities

Start building with MineSkin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs