Open Source Capability Engine
Ikanos integrates data and APIs you already own into agentic capabilities you can trust. One declarative YAML spec, authored once, served as MCP, Skill, and REST from a single deployment.
Spec-Driven Integration is the method the engine runs on. Each capability is a coarse-grained piece of a domain: it consumes the HTTP APIs you already have, then exposes them across several protocols so AI agents and self-integrating systems can consume them directly. Ikanos ships as a specification, an engine, and a CLI — Apache 2.0, no Java required.
Features
Spec-Driven Integration
Declare a whole capability in YAML — no Java, no glue code.
Multi-Protocol Servers
Serve the same spec as MCP, Skill, and REST out of the box, plus a Control port for ops.
HTTP API Consumption
Connect to any HTTP-based API, with Bearer, API Key, Basic, Digest, and OAuth 2.1 built in.
Mapping & Transformation
Mustache templates, JSONPath queries, sandboxed JavaScript / Python / Groovy, and conversion from XML, CSV, Avro, Protobuf, and Markdown into JSON.
OpenAPI Interoperability
Import Swagger 2.0 and OAS 3.0 / 3.1 into consumes adapters; export REST adapters back out as OpenAPI documents.
Cloud Native Operations
OpenTelemetry tracing and RED metrics, Prometheus scrape, health and status endpoints, one Docker image for every capability.
The capability spec
Ikanos runs a single declarative YAML file that defines the full lifecycle of a capability — from the APIs it consumes through the protocols it exposes. Validated by JSON Schema, linted by Polychro, committed to Git.
Consumption
Declare which APIs you consume, how you authenticate, and what formats you convert — HTTP/REST, JSON, XML, Avro, Protobuf, CSV, YAML.
Orchestration
Chain multiple API calls into a single operation with multi-step workflows, JSONPath extraction, in-memory lookup joins, and reusable aggregates.
Exposure
Expose capabilities simultaneously as REST APIs, MCP servers (tools, resources, prompts), and Agent Skills — from a single deployment.
Operation semantics — safe, idempotent, cacheable — are declared once on an aggregate and derived automatically into MCP tool hints, so an agent knows what a tool is allowed to do before it calls it.
See how Polychro enforces it
Ikanos across the rest of the Platform
The engine is the core, and it is Apache 2.0 everywhere. Crafter is free in every edition; Warden and Skipper are Enterprise components that carry the same capability spec onto the surfaces your teams already use.
VS Code Extension | Crafter
Author and lint Ikanos capabilities in the editor, with schema-driven completion and live Polychro diagnostics as you type. Free in every edition.
Backstage Integration | Warden
Scaffold Ikanos capabilities from Backstage templates, then catalog them and their provided APIs alongside the rest of your software. Enterprise edition.
Kubernetes Integration | Skipper
Run Ikanos capabilities as a Capability CRD, with drift detection, GitOps deployment, and Prometheus observability. Enterprise edition.
Learn more in the Shipyard
Installation, tutorials, schema reference, and the full Ikanos documentation.
Run a capability spec on Ikanos
Apache 2.0, Docker-ready, community-driven. Start with the README on GitHub or follow the Shipyard tutorials.
