MineSkin keys and generation

MineSkin turns a skin image into a signed property that Minecraft clients can use. It is an external service with its own queues and limits.

Server URL generation

/skin url and URL-based custom skins use skin generation when needed. You can configure an optional server key:

api:
  mineskinAPIKey: "REPLACE_WITH_YOUR_API_KEY"
  mineskinSecretSkins: true

Run /sr reload. Try one valid URL and inspect the result. Keep the key private. The spelling and capitalization of mineskinAPIKey are significant.

mineskinSecretSkins: true requests an unlisted generated skin. It does not make a Minecraft texture URL private or prevent others from copying it.

Website generation

The Upload and Generator pages accept their own optional key. They do not read your server configuration.

Choose Axolotl for the free supported-cape route. Choose Official to supply your MineSkin key and check its cape grants.

The Axolotl route handles uploads with a selected cape in Axolotl mode. Plain uploads and Official-mode uploads use MineSkin's queue directly.

Generated commands can contain a MineSkin URL or an opaque skinsrestorer-axolotl:// value. SkinsRestorer resolves that opaque value through Axolotl when the command runs.

The server's generation API and the website's queue are separate request paths. Success on one does not prove the other works.

Limits and keys

Use MineSkin's API key page for current access and plan limits. Use MineSkin's documentation for current generation behavior.

Do not assume a paid key permits every cape. The website checks available cape grants and supported cape choices.

Failures

• Rate limit or queue delay: Wait before another request.
• Invalid image or URL: Use a reachable standard PNG skin template.
• Authorization error: Check the key and its grants.
• Transport error: Inspect outbound connections.

For account-name lookups, SkinsRestorer uses account services instead of image generation. Mojang batching configuration does not change MineSkin limits.