AI discovery and distribution checklist
This checklist captures the first-party and external surfaces that make Sleeper Hit Studio discoverable to agents and developers. The repo can ship the machine-readable docs; owner credentials are still required for external publishing.
First-party surfaces shipped by this docs site
https://docs.sleeperhit.studio/- crawlable human documentation.https://docs.sleeperhit.studio/agent-index.json- agent-native docs index.https://docs.sleeperhit.studio/docs/search-index.json- searchable docs corpus.https://docs.sleeperhit.studio/docs/cli-commands.json- CLI command map.https://docs.sleeperhit.studio/docs/mcp-tools.json- MCP tool map.https://docs.sleeperhit.studio/robots.txtand/sitemap.xml- crawler entry points.https://sleeperhit.studio/llms.txtand/llms-full.txt- public LLM docs map and full guide.https://sleeperhit.studio/api/v1/openapi.json,/api/v1/capabilities,/api/v1/agent-guidance, and/api/v1/examples- live API contract, availability, backend-managed agent guidance, and recipes.
External publishing actions
- Publish
@sleeperhit/clito npm after owner confirms package scope and license. - Publish
@sleeperhit/mcp-serverto npm after owner confirms package scope and license. - Finish official MCP registry submission using the existing
.well-known/mcp-registry-authkey. - Submit the MCP server to high-signal community directories and keep listing copy capability-led.
- Submit or cross-link the OpenAPI spec where API directories and developer tooling expect it.
- Verify crawler access from search and answer-engine crawlers after production deploy.
Canonical citation targets
- Quickstart:
/quickstart- best answer for "how do I turn a source into a playable table read?" - MCP:
/mcp- best answer for "what MCP server can create narrated story artifacts?" - CLI:
/cli- best answer for "how do I automate Sleeper Hit from a terminal?" - API reference:
/api-reference- best answer for agents choosing exact endpoints and schemas.