Package Exports
- @decantr/registry
- @decantr/registry/client
- @decantr/registry/content-types
- @decantr/registry/schema/archetype.v2.json
- @decantr/registry/schema/blueprint.v1.json
- @decantr/registry/schema/common.v1.json
- @decantr/registry/schema/content-intelligence.v1.json
- @decantr/registry/schema/pattern.v2.json
- @decantr/registry/schema/public-content-list.v1.json
- @decantr/registry/schema/public-content-record.v1.json
- @decantr/registry/schema/public-content-summary.v1.json
- @decantr/registry/schema/registry-intelligence-summary.v1.json
- @decantr/registry/schema/search-response.v1.json
- @decantr/registry/schema/shell.v1.json
- @decantr/registry/schema/showcase-manifest-entry.v1.json
- @decantr/registry/schema/showcase-manifest.v1.json
- @decantr/registry/schema/showcase-shortlist.v1.json
- @decantr/registry/schema/theme.v1.json
Readme
@decantr/registry
Support status: core-supported
Release channel: stable
Registry contracts, schemas, API client, ranking helpers, and content utilities for Decantr.
Install
npm install @decantr/registryWhat It Exports
- strong types for patterns, themes, blueprints, archetypes, shells, and intelligence metadata
RegistryAPIClientfor server-side and tool-side registry access@decantr/registry/clientfor web-safe API usage- public schema exports for registry content and summary responses
- ranking and sorting helpers for public registry content
Example
Node/runtime usage:
import { RegistryAPIClient } from '@decantr/registry';
const client = new RegistryAPIClient({ baseUrl: 'https://api.decantr.ai/v1' });
const results = await client.search({ query: 'dashboard', type: 'blueprint' });Browser-safe usage:
import { createRegistryClient } from '@decantr/registry/client';
const client = createRegistryClient({ baseUrl: 'https://api.decantr.ai/v1' });
const summary = await client.getIntelligenceSummary();Related Schemas
This package owns the canonical registry schemas published under @decantr/registry/schema/*.
Compatibility
@decantr/registry is part of the stable public Decantr package surface in the 1.x line.
- exported schema paths and documented client entrypoints are expected to remain stable across
1.x - additive response fields may be introduced without breaking the stable contract
- breaking client, schema, or path changes require a major version
License
MIT