> ## Documentation Index > Fetch the complete documentation index at: https://docs.decimal.ai/llms.txt > Use this file to discover all available pages before exploring further. # Usage time-series for a public registry skill (npm-style chart data) > Returns a multi-series usage time-series for a public registry skill, summed across all consuming orgs' forks. The npm-style chart on the public detail page reads from this. No authentication required. Privacy-preserving: rolls up across orgs, no per-org breakdown. Zero-filled buckets so the chart can render without gap handling. Response shape: { "skill_id": "...", "window_days": 30, "bucket": "day", "series": [ {"date": "2026-05-01", "activations": 42, "distinct_orgs": 8, "router_decisions": 100, "router_activated": 70}, ... ], "totals": {"activations": 1240, "distinct_orgs_max": 19, ...}, } ## OpenAPI ````yaml /openapi.json get /api/v1/registry/skills/{skill_id}/activations openapi: 3.1.0 info: title: DecimalAI Platform description: Agent Dataset Lifecycle Platform — Backend API version: 0.1.0 servers: [] security: - BearerAuth: [] tags: - name: traces description: >- Ingest, search, and inspect agent execution traces. A trace is the atomic unit of the platform — every other feature (evaluation, compatibility scoring, dataset building) operates on traces. Each trace is auto-tagged with the manifest hash of the agent that produced it. - name: eval-scores description: >- Push, fetch, and aggregate per-trace evaluation scores. Scores carry source provenance (built-in, DeepEval, LangSmith, custom) and feed the unified decision engine, which produces a keep / repair / replay / drop verdict per trace. - name: skills description: >- Manage reusable instruction blocks (SKILL.md files) that modify agent behavior. Skills are first-class manifest components — changes to a skill appear in your regression-check impact reports. Use these endpoints to create, version, fork, and sync skills with your local SKILL.md files. - name: manifests description: >- Register and inspect manifest versions. A manifest is a snapshot of your agent's structural identity (tools, prompts, models, skills) at a point in time. The SDK registers manifests automatically; these endpoints expose the underlying records. - name: datasets description: >- Build versioned SFT/DPO training datasets from manifest-classified, eval-scored traces. Datasets are reproducible — each version locks the manifest and filter set used to build it. Export as JSONL, Parquet, or push to HuggingFace Hub. - name: replay description: >- Re-execute historical traces against a new manifest version. Replay is the deferred-future capability for behavioral verification of agent changes. The SDK creates a replay batch, your worker executes each task, then submits results back here for eval scoring. - name: registry description: >- Browse and install community skills from the public skills registry. Each registry skill carries a SkillScore — an evidence-tiered quality composite computed from real-world evals, benchmarks, and ratings across organizations. Installing creates a fork in your org — edits don't affect the public version. - name: agents description: >- List and inspect agents, plus their multi-agent topology (orchestrator → sub-agent edges discovered from traces). Agents are identified by a stable agent_name string set in your SDK init() call. - name: import description: >- Bulk-import historical traces from another observability platform or a JSONL backup. Useful for migrating from LangSmith / Braintrust / Langfuse. Duplicate trace IDs are silently skipped — re-running an import is safe. paths: /api/v1/registry/skills/{skill_id}/activations: get: tags: - registry summary: Usage time-series for a public registry skill (npm-style chart data) description: |- Returns a multi-series usage time-series for a public registry skill, summed across all consuming orgs' forks. The npm-style chart on the public detail page reads from this. No authentication required. Privacy-preserving: rolls up across orgs, no per-org breakdown. Zero-filled buckets so the chart can render without gap handling. Response shape: { "skill_id": "...", "window_days": 30, "bucket": "day", "series": [ {"date": "2026-05-01", "activations": 42, "distinct_orgs": 8, "router_decisions": 100, "router_activated": 70}, ... ], "totals": {"activations": 1240, "distinct_orgs_max": 19, ...}, } operationId: >- get_registry_skill_activations_api_v1_registry_skills__skill_id__activations_get parameters: - name: skill_id in: path required: true schema: type: string title: Skill Id - name: window_days in: query required: false schema: type: integer maximum: 365 minimum: 1 description: Trailing window in days (max 365) default: 30 title: Window Days description: Trailing window in days (max 365) - name: bucket in: query required: false schema: type: string description: 'Bucket granularity: day | week | month' default: day title: Bucket description: 'Bucket granularity: day | week | month' - name: include in: query required: false schema: type: string description: >- Comma-separated optional series. Supported values: `distinct_orgs`, `router_decisions`, `router_activated`. The base `activations` series is always returned. default: '' title: Include description: >- Comma-separated optional series. Supported values: `distinct_orgs`, `router_decisions`, `router_activated`. The base `activations` series is always returned. responses: '200': description: Successful Response content: application/json: schema: {} '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' components: schemas: HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type input: title: Input ctx: type: object title: Context type: object required: - loc - msg - type title: ValidationError securitySchemes: BearerAuth: type: http scheme: bearer description: Enter your API key (e.g. dai_sk_test_key_001) ````