Get Started

Build on Kryptonic

APIs, protocols, SDKs, and a marketplace built for builders

Extend the platform with custom nodes, connectors, and tools. Interoperate with external agents over A2A and with IDEs over MCP. Publish what you build — templates, connectors, skills — and earn from metered usage.

Start buildingExplore A2A & MCP
FIRST-CLASS INTEROPERABILITY
External agentsDeveloper tools & IDEs
A2AAgent Card · signed contractstasks/send · get · cancel
MCPAuthenticated tool accesscatalog · flows · mcp_call
Kryptonic orchestrationWorkflows · agents · systems

Quickstart

From first connection
to what’s next.

Your path from a blank canvas to durable, governed automation.

Create a free workspace
  1. 01

    Connect a system

    Create a free workspace and connect your first system.

  2. 02

    Design your flow

    Create with AI or start from a template — then refine in the builder.

  3. 03

    Run. Inspect. Refine.

    Run a flow; use breakpoints, replay, and tests to harden it.

  4. 04

    Extend your reach

    Call the platform via CLI, REST, A2A, or MCP — or publish to the marketplace.

Open protocols

A2A and MCP — first-class interoperability

Kryptonic speaks the protocols modern agent stacks expect. External agents discover and invoke the platform; developers and IDEs consume tools without custom glue.

A2A

A2A (Agent-to-Agent)

Public Agent Card discovery, JSON-RPC tasks/send|get|cancel, and capabilities for flow execution, diagnosis, and durable agent tasks. Cross-org callers authenticate with a signed contract id — scope, quota, and rate limits enforced.

Discover → authenticate → invoke
MCP

MCP (Model Context Protocol)

The platform exposes an authenticated MCP server for catalog and flow tools. Inside flows, mcp_call nodes consume external MCP servers. Author custom MCP tools with the Tool SDK.

Connect → discover tools → execute

Developer toolkit

Build on the platform.
Make it your own.

Work from your terminal, your application, or the builder. Extend the capabilities your team needs.

>_

CLI (iflow)

Authenticate, manage flows, connections, runs, environments, projects, schedules, and more from the terminal.

{}

API SDKs

Python and TypeScript clients for programmatic access to the Kryptonic API.

◇

Node SDK

Register custom workflow nodes, test them, and package for use across the platform.

↔

Connector SDK

Build credentialed connectors with manifests, validation, certification, and marketplace publishing.

+

Tool & extension SDKs

Author MCP tools and signed extension bundles for controlled platform extensibility.

THE BUILDER ECONOMY
01Templates
02Connectors & nodes
03Tools & agent skills
BuildCertifyPublishEarn

Publishing on entitled plans. Enterprise by default.

Marketplace

Ship once. Install everywhere. Earn on usage.

Publish flow templates, connectors, nodes, tools, and agent skills on entitled plans. Listings support free, flat, usage, and hybrid pricing. Publishers see gross revenue, their share, and payouts in the Developer workspace — with a publisher-majority revenue share by default.

Marketplace-ready extensions, not one-off scripts

The workflow stays the orchestration unit while you add capabilities without forking the core. Certification, Git sync, versioning, and autonomy ceilings keep extensions operable in production.

Talk about publishing

Build what’s next

Build beyond the boundaries of your stack.

Connect your systems. Bring your people. Build with governed intelligence.

Get StartedTalk To An Expert