Naftiko Capability

A NaftikoCapability property references a Naftiko capability YAML specification — a single declarative file that defines what APIs are consumed upstream, what surfaces are exposed (REST, MCP, Agent Skills), and what governance, identity, and telemetry rules apply. Capability specs are the deployable unit of the Naftiko platform: each one is validated by JSON Schema, committed to Git, and serves as both the implementation artifact and the governance contract. Publishing a capability spec makes it possible for AI agents, orchestration tools, and developer portals to discover and invoke governed API capabilities without direct knowledge of the underlying provider APIs.

Also known as: Capability Spec, Naftiko Capability YAML

Example

- type: NaftikoCapability
  url: https://developers.example.com/naftiko/capability.yaml
  mediaType: application/yaml

Standards

apis.io project (community) Naftiko Framework
apis.io project (community) Naftiko Sandbox
IETF (draft) / JSON Schema Org JSON Schema 2020-12
OpenAPI Initiative / Linux Foundation OpenAPI Specification 3.x
Anthropic / community Model Context Protocol (MCP)
AsyncAPI Initiative / Linux Foundation AsyncAPI 3.x

Media Types

application/yaml — Canonical Naftiko capability serialization.
application/json — Equivalent JSON form for tooling and validation.

Governance Rules

capability-schema-valid (Naftiko JSON Schema) — Capability YAML must validate against the published Naftiko schema.
capability-upstream-declared (Naftiko Framework) — Upstream APIs consumed must be enumerated with identity and scope.
capability-surfaces-declared (Naftiko Framework) — Exposed surfaces (REST, MCP, Agent Skills) must be declared explicitly.
capability-identity-bound (Naftiko Framework) — An identity or credential reference must be bound to each upstream call.

Risk & Compliance

Security: Capability specs concentrate routing, identity, and policy in one artifact — treat them as production configuration. Store secrets via references (vault, env, OIDC federation), never inline. Review schema-validated diffs in PRs and require approvals before deploy. Provenance of the framework is the Naftiko project itself (a community apis.io-adjacent effort), not an industry standards body — adopt with that maturity in mind.

Tools

Naftiko Framework — Capability runtime
Naftiko Sandbox — Local development / examples
JSON Schema validators (ajv, jsonschema) — Spec validation
Spectral — Linting OpenAPI references inside capabilities (Apache-2.0)
MCP SDKs — Surface bridging
Git — Capability source of truth (GPL-2.0)

Suggested Metrics

capability_count — Capability YAML files under management.
schema_validation_failures — Validation errors caught in CI before merge.
upstream_apis_per_capability — Distribution of upstream dependencies per capability.
surface_invocations_total — Calls served per exposed surface (REST / MCP / Agent Skill).

Example Implementations

Naftiko — Canonical framework, schema, and example capabilities.

Related Properties

Openapi
Asyncapi
Schema
Mcp
Agent skills