Decantr Content API

This page keeps the historical registry API URL for link compatibility. The current API is a Fly-hosted content/reference helper backed by @decantr/content, not a public registry portal, account system, upload service, or billing surface.

Base URL

https://api.decantr.ai/v1

Prefer DECANTR_API_URL for custom deployments. REGISTRY_URL remains a legacy alias in Decantr 3.x clients.

Retained Routes

GET /health
GET /v1/search
GET /v1/{patterns|themes|blueprints|archetypes|shells}
GET /v1/{type}/@official/:slug
GET /v1/schema/:name

GET /v1/intelligence/summary
GET /v1/showcase/manifest
GET /v1/showcase/shortlist
GET /v1/showcase/shortlist-verification
POST /v1/packs/compile
POST /v1/packs/select

The API no longer serves hosted auth, publish, source upload, scan, critique, billing, organization, user, usage-metering, Supabase, Stripe, or PostHog routes.

Content Search And Lists

GET /search?q=portfolio&type=blueprint&sort=recommended
GET /blueprints?blueprint_set=featured
GET /patterns?limit=50&offset=0
GET /patterns/@official/hero

Response schemas: search-response.v1.json, public-content-list.v1.json, and public-content-record.v1.json.

Execution Packs

POST /packs/compile?namespace=@official
POST /packs/select?namespace=@official

Request bodies must include valid Decantr Essence v4 documents. Response schemas: execution-pack-bundle.v1.json and selected-execution-pack.v1.json.

CLI And MCP

decantr content summary --namespace @official --json
decantr content compile-packs decantr.essence.json --write-context
decantr content get-pack manifest --namespace @official --json

Legacy decantr registry ... aliases remain callable for scripts. MCP keeps decantr_registry as the compatibility content-corpus tool name; Decantr 3.x does not add a ninth MCP content tool.

Schemas

Canonical schemas are published at /schemas/.