The Agentic Capabilities Platform
Naftiko elevates the public and private APIs you already own into governed, domain-driven capabilities that developers, copilots, and agents can trust. One declarative spec, three products: two open-source engines (Ikanos + Polychro), and the Naftiko Fleet enterprise layer around them.
Land in the Shipyard
From API to agent tool in three steps
This is the core loop the Fleet wraps — a complete, production-ready path on the two Apache 2.0 engines, Ikanos and Polychro. One declarative capability.yaml is imported, linted, and run without ever leaving the file. Value before you author a line of YAML.
1
Import
ikanos import openapi petstore.yaml
Turn an API you already own into a skeleton capability. Aggregate several upstream calls into one domain-shaped capability — not a 200-tool endpoint dump. No blank YAML file.
2
Lint
polychro lint capability.yaml
Validate deterministically with Polychro, in-process, sub-100 ms — at the speed an agent generates it. Drop it in a PR with the "Fix It" GitHub Action.
3
Run
ikanos run capability.yaml
Serve it with Ikanos as MCP, Skill, and REST from the same spec (plus a Control port for ops). One Docker image, built-in auth, OTel traces + Prometheus metrics.
Three products, one spec
The Agentic Capabilities 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
Spec-Driven Integration
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
Spec-Driven Linting
The OSS deterministic AI-era linter for YAML, JSON, and Markdown specs. The new Spectral for SDI. Apache 2.0.
Naftiko Fleet
Enterprise AI Integration
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.
One capability, many protocols
A single Naftiko spec is exposed simultaneously across REST, MCP, and Skill — and soon A2A — from one Ikanos deployment.
REST API
Clean REST endpoints with per-operation path, method, and parameter mapping.
MCP Server
Tools, resources, and prompts for AI copilots and agents via streamable HTTP or stdio.
Agent Skills
Downloadable skill folders with SKILL.md prompt integration for developer agents.
A2A Protocol
Roadmap
Google's Agent-to-Agent protocol for cross-agent tool discovery and execution. First server adapter shipped in Alpha 4.
The Naftiko Fleet on the surfaces your teams already use
Crafter (VS Code + AI IDEs)
IntelliSense for capability YAML, inline governance diagnostics with Quick Fix, live topology panel, one-click run/stop, JSONPath and Mustache linting.
Warden (Backstage)
Capability scaffolding from templates, auto-catalog from CRDs/Git, scorecards for Cost/Risk/Velocity pillars, fleet explorer with impact tracing.
Skipper (Kubernetes)
Fleet dashboard with health and uptime, visual spec viewer, structured log streaming with filters, secret injection, continuous compliance.
Subscribe to the Naftiko Manifest
Be part of the first wave. Get early access to Naftiko technology and be part of the pioneers in capability-driven integration.
