KYE Protocol™ ecosystem

Profiles define. Connectors integrate. Apps productise. Plugins extend.

KYE Protocol™ ships four ecosystem surfaces. Each one solves a specific adoption problem. Pick the one that matches what you're trying to do; the right starter, schema, and SDK is one click away.

Ecosystem, stage by stage

Demo data

You learn: How it works, one stage at a time. You can: Run it end to end.

  1. L1L1 KYE™ Core Protocol™

    KYE Protocol™

    vocabulary, schemas, runtime, decision codes, audit chain. The base contract.

  2. L2L2 KYE™ Profiles

    KYE Protocol™

    domain rules: kye.payments.v1 , kye.healthcare.v1 , kye.federation.v1 , etc. (58 v1.0 normative)

  3. L3L3 KYE™ Connector Profiles™

    KYE Protocol™

    integration-category rules. Each profile binds a family of connectors to a shared authority model + event family + evidence shape + conformance suite.

  4. L4L4 Individual connectors

    KYE Protocol™

    specific systems (Stripe, Shopify, OpenBankProject, NHS API, Splunk, …) under their parent profile.

  5. L5L5 Apps · Plugins · Widgets

    KYE Protocol™

    KYE™ App Store productises · KYE™ Plugin Marketplace™ extends.

How this widget is built
Demonstrates
KYE Protocol™
Components
  • The stages this page describes
Flow
Each stage in order, as the page sets it out. Architecture diagram
Used on

Four ecosystem surfaces

One sentence per surface.

KYE™ Connector Profiles™Profiles define the rules. 11 domain profiles — Payment, Commerce, Open Finance, Agent Runtime, Compliance Evidence, Pension, Health, Security & SIEM, Insurance, Utilities, Legal — each binding a family of connectors to a shared authority model + event family + evidence shape + conformance suite.view profiles →KYE™ Connector Hub™Connectors integrate KYE™. six connector families (IPG · MPG · checkout · MCP · IAM · SIEM · GRC · KYC/KYB/KYA …), one canonical kye.connector_manifest.v1 manifest schema, 52 reference connectors searchable in the explorer.view connectors →KYE™ App StoreApps productise KYE™. 21 productised apps grouped by domain — KYE™ Payment Authority Gateway™, KYE™ Checkout Guard™, KYE™ Open Finance Authority Gateway™, KYE™ Evidence Pack Viewer™, KYE™ Contract Authority Gateway™, and 16 more.view apps →KYE™ Plugin Marketplace™Plugins extend KYE™. 9 plugin categories (MCP tools, webhook verifiers, policy packs, evidence exporters, conformance fixtures, dashboard widgets, sandbox flows, approval workflows, SDK extensions) with 18 reference plugins.browse plugins →

Hierarchy

From Core Protocol to Plugin — one tree.

Five layers, each a clean contract over the layer below. The same authority object travels from spec to runtime to evidence.

  1. L1L1KYE™ Core Protocol™ — vocabulary, schemas, runtime, decision codes, audit chain. The base contract.
  2. L2L2KYE™ Profiles — domain rules: kye.payments.v1, kye.healthcare.v1, kye.federation.v1, etc. (58 v1.0 normative)
  3. L3L3KYE™ Connector Profiles™ — integration-category rules. Each profile binds a family of connectors to a shared authority model + event family + evidence shape + conformance suite.
  4. L4L4Individual connectors — specific systems (Stripe, Shopify, OpenBankProject, NHS API, Splunk, …) under their parent profile.
  5. L5L5Apps · Plugins · Widgets — KYE™ App Store productises · KYE™ Plugin Marketplace™ extends.

Five-level hierarchy. Core Protocol → Payments Profile → Payments Connector Profile → four Connectors → App → Plugin.

Pick the surface that matches the job

What are you trying to do?

  • AI want to understand the rules for my domain. → KYE™ Connector Profiles™. Pick the profile that fits (Payment, Commerce, Open Finance, Health, Pension, Agent Runtime, Compliance Evidence, Security & SIEM, Insurance, Utilities, Legal). Each profile lists the authority model, the events it carries, the conformance fixtures.
  • BI want to integrate KYE™ with a specific system I already run. → KYE™ Connector Hub™. Search the explorer by name / type / risk envelope. Pick a connector; ship the manifest; sign + submit.
  • CI want a productised authority surface I can adopt this quarter. → KYE™ App Store. 21 apps across payments, commerce, open finance, sandbox, sector apps, agentic / MCP, audit, certification, legal.
  • DI want to add a small focused module to my existing KYE™ stack. → KYE™ Plugin Marketplace™. MCP tools, webhook verifiers, policy packs, evidence exporters, dashboard widgets — ~half a day of work each.
  • EI want to write code against the runtime. → Build with KYE™ + Quickstart. Three SDKs (TypeScript / Python / Go), 135 conformance fixtures, reference Gateway, KYE™ MCP Server.
  • FI want to see the runtime semantics live before I write anything. → Interactive Widgets. Five live widgets, no signup, no install — Choose-Your-Role router, Agent-Purchase Simulator, Decision Map™ Viewer, Blast Radius Map™, Evidence Pack™ Viewer™. The KYE™ Connector Hub™ explorer lives on connectors.html.

What ships today

Open contracts, ecosystem-wide.

Apache 2.0. Every contract below is implementable today — partners and developers integrate without depending on any hosted service.

SurfaceWhat you get
ProfilesEvery kye.connector_profile.v1 manifest, supported-connector list, conformance suite, dictionaries.
ConnectorsEvery kye.connector_manifest.v1 beneath a profile · sample IPG / checkout / MCP / SIEM connectors · SDK adapters · local test harness.
AppsReference architectures · sample kye.app_manifest.v1 · SDK examples per app.
Pluginskye.plugin_manifest.v1 · sample plugins · permissions dictionary · conformance fixtures.
RuntimeKYE™ Reference Gateway™: PEP middleware · embedded ePDP · conformance runner.

Adjacent reading

Where to go next.

KYE™ Connector Profiles™ →KYE™ Connector Hub™KYE™ App StoreKYE™ Plugin Marketplace™Interactive Widgets

Ready to see your AI agents flagged?

Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.

Apply for pilot →Try the sandbox →

Canonical KYE™ surfaces referenced on this page: Authority Graph™ · Evidence Pack™ · KYE™ MCP Server · KYE Protocol™.