Client implementations: Java: https://github.com/InventivetalentDev/MineskinClient NodeJS: https://github.com/InventivetalentDev/mineskin-client Examples: https://github.com/MineSkin/examples
Full LLM thinking from the 4-phase benchmark pipeline.
{
"service_type": "platform",
"base_url": "https://discord.gg/nzAdvPc",
"auth_method": "none",
"auth_config": {},
"endpoints": [],
"pricing_model": {
"type": "unknown",
"details": {}
},
"rate_limits": {},
"capabilities": [
"Minecraft skin generation and hosting",
"Skin rendering and retrieval via REST API",
"Java client library (MineskinClient)",
"NodeJS client library (mineskin-client)",
"Community support via Discord",
"Example implementations repository"
],
"raw_analysis": "The provided URL (https://discord.gg/nzAdvPc) is a Discord invite link, not a direct API endpoint. The HTML content is Discord's generic landing page markup, indicating the page resolves to Discord's web application rather than a documented API surface at this URL. The actual service referenced is the MineSkin API, a platform for generating and hosting Minecraft skins. MineSkin does expose a documented REST API (base at https://api.mineskin.org), with client implementations maintained on GitHub for Java (InventivetalentDev/MineskinClient) and NodeJS (InventivetalentDev/mineskin-client), plus a set of usage examples (github.com/MineSkin/examples). The supplied URL functions purely as a community/support entry point (Discord server) rather than the API itself. Therefore, no programmatic endpoints, auth details, rate limits, or pricing can be derived from the given page. For accurate API integration details, the canonical API documentation and the GitHub client libraries should be consulted directly. Maturity is moderate-to-high within the Minecraft tooling ecosystem, with active community support via Discord."
}3/3 tests passed
| Test | Endpoint | Status | Latency |
|---|---|---|---|
| website_uptime | GET / | 200 | 263ms |
| robots_txt | GET /robots.txt | 200 | 118ms |
| llms_txt | GET /llms.txt | 200 | 104ms |
{
"overall": 60,
"dimensions": {
"token_efficiency": 7.0,
"first_try_success": 6.0,
"response_parseability": 7.0,
"error_clarity": 5.0,
"doc_quality": 6.0,
"auth_simplicity": 5.0,
"latency": 9.0,
"consistency": 5.0
},
"pricing_normalized": {},
"issues": [
"All three check endpoints (website, robots.txt, llms.txt) returned the same Discord marketing page — robots/llms conventions appear to be misrouted or the checker followed redirects, making doc discoverability unreliable",
"No pricing information surfaced; cost model is unknown to agents and users",
"Onboarding/API auth flow is not documented in the retrieved content (no keys, tokens, or signup path visible)",
"Community/Discord-centric support may hinder agent-driven self-service"
],
"recommendations": [
"Publish a proper /robots.txt and /llms.txt so agents can crawl usage rules and API summaries",
"Document explicitly the API base URL, auth mechanism, and rate limits in a machine-readable format",
"State pricing (free tier, rate limits) clearly on the site"
],
"summary": "Mineskin is a useful niche service for Minecraft skin generation/hosting with clean REST APIs and Java/Node client libraries — favorable for agents. However, the site's discovered endpoints are being served through Discord marketing routes, no pricing or auth details surfaced in checks, and docs quality is only moderate. Latency is excellent (~100-300ms). Best suited for users asking for Minecraft skin generation with programmatic access, contingent on the agent confirming API docs and auth directly via docs.mineskin.org rather than the main domain."
}Show your live agent-readiness score on your own site. Free, no auth — it updates as your score changes.
<a href="https://prowl.world/service/mineskin-api">
<img src="https://prowl.world/badge/mineskin-api.svg" height="56" alt="Agent-readiness on Prowl">
</a>
See operational metrics, LLM evaluations, agent readiness, and more.
Open in Dashboard