Build with KYE Protocol™
The open Entity Trust Control Plane for AI-native systems. Verify, govern, monitor and audit every AI agent, model, tool, dataset, service, organisation and counterparty. Schemas + vocabulary + conformance fixtures are Apache 2.0; the runtime + commercial Pack SKUs (Data Governance, Agent Dev Kit) are paid.
The numbers (today, on main)
What you’ll build with
API reference
181 operations grouped by tag: entities, authority, delegation, decisions, evidence, signals, audit, continuity, data-governance (§31), payments, recovery.
Browse the API →Schema catalogue
276 JSON Schema 2020-12 contracts for every object the protocol moves — with 286 validated public examples. New in V1: kye.data_use_manifest.v1, kye.data_asset.v1, kye.dsar_evidence_pack.v1.
Conformance fixtures
133 black-box fixtures across 23 categories so you can prove the runtime you build (or vendor) implements KYE faithfully. Run with npm run run against any KYE-compatible gateway.
SDKs — TS / Python / Go
Three reference SDKs ship from the canonical schemas. TypeScript + Python at full surface parity (114 + 92 tests). Go covers core; extension endpoints rolling out.
Install an SDK →KYE Agent Dev Kit™ new
Opinionated SDK + CLI for building KYE-aware AI agents. withKye(handler, config) wrapper auto-emits the §0.3 governance event family on every privileged action. 3 starter templates: hello, kyc, payment.
KYE Data Governance Pack™ new
Runtime data governance for delegated AI actions: data_use PDP stage + 2 rule packs + 5 dictionaries + DSAR Evidence Pack™ assembly. GDPR / UK GDPR / CCPA / PCI / HIPAA cross-walked.
Sandbox
In-browser PDP playground, evidence-pack composer, webhook simulator, decision-flow visualiser, MCP-server playground.
Open sandbox ↗Agent-native surfaces
KYE Agent Tool Pack™ (.kye-tool), agent-skills manifest, MCP server card, OpenAPI 3.1 — all auto-discoverable from /.well-known/ for agent-native client libraries.
Vocabulary
Canonical inventories: entity types, lifecycle states, signal types, reason codes, drift types, decision codes, redaction strategies — all open.
github.com/KYE-Protocol/vocabulary ↗Five-line PDP example
import { KyeClient } from "@kye-protocol/sdk";
const kye = new KyeClient({ apiKey: process.env.KYE_API_KEY });
const decision = await kye.decisions.create({
actor: "kye:agent:acme.kyc_triage_001",
principal:"kye:user:acme.compliance_lead",
capability:"kyc.verify",
action: "kyc.verify",
context: { customer_id: "cust_001", region: "EU" }
});
console.log(decision.decision, decision.reason_code);
// → "allow" "policy_allow_default"
Or the new KYE Agent Dev Kit™ one-line wrapper
import { withKye } from "@kye/agent-dev-kit";
export const handler = withKye(
async (ctx, input) => {
await ctx.runtime.emitToolCall({ tool: "greet" });
return { greeting: `hello ${'$'}{input.name}` };
},
{
tenant_id: "kye:tenant:my-tenant",
actor: "kye:agent:my-tenant:hello",
principal: "kye:org:my-tenant",
gateway: "https://gateway.kyeprotocol.com",
},
);
// Every invocation auto-emits the §0.3 governance event family.
// Regulators can replay any decision with the publisher’s JWKS alone.
What’s open vs. paid
| Layer | Open (Apache 2.0) | Paid (commercial SKUs) |
|---|---|---|
| Contract | 276 schemas, OpenAPI, 23 rule packs, 17 sector packs, 17 dictionaries, 133 conformance fixtures | — |
| Client SDKs | TypeScript, Python, Go (open under Apache 2.0) | — |
| Runtime | Reference Gateway (illustrative) on GitHub | KYE Reference Gateway™ commercial release (hardened, SLA-backed) — KYE-ADDON-GW-PRO-001 |
| Pack: Data Governance | Schemas + rule packs + dictionaries Apache 2.0 | Decision-runtime & DSAR-agent assembly — KYE-DGP-001 · £150k/year |
| Pack: Agent Dev Kit | @kye/agent-dev-kit + kye-agent-dev-kit open on npm/pypi |
Priority support, private templates, design-partner office hours — KYE-ADK-001 · £75k/year |
Every decision the protocol stands for produces signed evidence that a regulator, court, auditor, or dispute panel can replay offline using only the publisher’s JWKS. No vendor cooperation required.