OrchestKit developer resources
Every developer-facing surface of OrchestKit by Yonyon in one place: documentation, OpenAPI spec, MCP servers, SDK packages, and the auth and API policies. All public, all free, no account required.
Resources
- Documentation — Install guides, concepts, and reference for all 111 skills, 37 agents, and 210 hooks.
- OpenAPI specification — OpenAPI 3.1 description of the public, read-only docs API — search, Markdown fetch, batch, async jobs.
- MCP server (hosted, Streamable HTTP) — Connect AI agents to the docs natively. No auth. Server card at /.well-known/mcp/server-card.json.
- MCP server (stdio, Docker image) — Run locally: docker run -i --rm ghcr.io/yonatangross/orchestkit-docs-mcp — multi-arch (amd64 + arm64).
- NLWeb natural-language endpoint — POST or GET /ask with a question; JSON or SSE streaming responses (NLWeb protocol).
- Python package (PyPI) — orchestkit-hook-contract — typed hook I/O contract for building OrchestKit-compatible tooling in Python.
- Authentication policy — The API is public and anonymous-only — auth.md states it in the WorkOS auth.md shape, with RFC 9728 PRM.
- API versioning & deprecation policy — Versioning scheme, RFC 8594 Deprecation/Sunset headers, and the 6-month sunset guarantee.
- llms.txt — Machine-readable site index for AI agents — canonical description, use cases, and resource map.
- API catalog (RFC 9727) — Linkset of every discoverable API surface at /.well-known/api-catalog.
- Source code (GitHub) — MIT-licensed monorepo: plugin source, hooks, MCP server, docs site, and CI.
- MCP registry entry — io.github.yonatangross/orchestkit on the official Model Context Protocol registry — republished every release.
For AI agents
Agents should start at the RFC 9727 API catalog or llms.txt above. The docs API needs no credentials; errors use RFC 9457 Problem Details; rate limits are communicated via standard RateLimit headers. The same docs are reachable as Markdown by appending .md to any page URL.