Incantory developer docs

Incantory is a registry of versioned prompts, skills, rules and agent instructions. Everything you can do on the site you can also do from code: resolve a prompt by label, render it with variables, pin it in a lockfile, install it into a coding tool, and react to changes.

Where to start

• Getting started: create a token, fetch a prompt with curl, then with an SDK or the CLI.
• Concepts: packages, versions, labels, forks, attribution and licenses. Read this once; every other page assumes it.

Guides

• TypeScript SDK (@incantory/sdk) and Python SDK (incantory): resolve owner/slug@label refs, render, pin, report evals.
• CLI: pull, push, diff, labels, forks, installs, eval reports and webhooks from the terminal and CI.
• Install into tools: put a prompt where Claude Code, Cursor, Copilot, Codex, Windsurf or Gemini will read it.
• MCP: connect Claude, Cursor or VS Code to the public read-only MCP server.
• Webhooks: get a signed HTTP request when a version is created, a label moves or an eval finishes.
• Evals and the CI gate: report eval results and block label moves on failing versions.

Reference

• REST API: every /api/v1 endpoint, generated from the live OpenAPI document.
• Rate limits and errors: headers, error codes and retry rules.
• Content licenses: what you may do with the prompts you fetch.

Ref syntax at a glance

owner/slug              the latest version
owner/slug@production   whatever version the "production" label points at
owner/slug@v3           version 3, immutable