API Reusability

Turn reuse into a measurable, repeatable practice -- by making capabilities discoverable.

API reuse is not just discipline -- it is visibility and incentives. Teams rebuild what already exists because reuse is invisible. Manual catalog registration goes stale. Reuse metrics are activity-based, not outcome-based.

Naftiko defines reuse by domain, capability, and contract. Measure and communicate reuse in leadership language -- lead time, throughput, reliability. Surface discovery where developers make decisions: IDE and copilot workflows.

Three products, one spec

The Agentic Integration Platform is three products tied together by Spec-Driven Integration (SDI) — a single declarative YAML spec, authored once, that turns an API into an agentic capability. Two open-source engines, Ikanos and Polychro, are Apache 2.0. The Naftiko Fleet is the enterprise layer that wraps them — authored in Crafter, governed by Warden, orchestrated by Skipper, and documented in Shipyard.

Ikanos

The OSS capability engine. Runs a Naftiko spec as a multi-protocol server — REST, MCP, and Skill from the same definition. Apache 2.0.

Polychro

The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs. The new Spectral for SDI. Apache 2.0.

Naftiko Fleet

The governed enterprise layer where capabilities become discoverable, composable, observable, and cost-bounded — authored in Crafter, governed by Warden, orchestrated by Skipper, and documented in Shipyard.

Start small, scale smart

Reuse doesn't scale without discoverability.

Chart your next course

Agent Orchestration