Learn → Review → Build → Pilot → Conform → Certify.

The model in one diagram

Six stages, seven audiences.

1. 1LearnRead the protocol, the concepts, the open-banking flow.
2. 2ReviewExperts critique the authority / on-behalf-of / scope / state / audit model.
3. 3BuildDevelopers run the schemas, the SDKs, the conformance fixtures.
4. 4Pilot2–4-week KYE™ Authority Finality™ Pilot in one regulated use case.
5. 5ConformRun the conformance pack against your gateway. KYE™ Conformant™ badge.
6. 6CertifyAudited certification. KYE™ Certified™ registry listing.

Path 1 / 7 · Experts

Review the authority & on-behalf-of model.

You are: open-banking architect, payments specialist, identity / IAM lead, OAuth/OIDC committee member, AI-governance researcher, audit / cybersecurity / regulated-finance expert, legal-tech reviewer.

You want: the protocol primitives surfaced clearly enough that you can critique the model end-to-end — and tell us where it breaks.

What we ask: not “what do you think?” — specific questions, against specific artefacts.

• Does the chain actor → principal → capability → scope → state → decision → evidence map cleanly to your domain?
• Is on-behalf-of modelled correctly — particularly for delegated authority, consent, payment initiation, agent operations?
• What breaks in open banking, payments, regulated finance, healthcare, critical infrastructure?
• What should be mandatory in the spec vs. optional in a profile overlay?
• What would make this credible to banks, auditors, regulators, infrastructure providers in your jurisdiction?

Path 2 / 7 · Developers

Try KYE™ in 10 minutes.

You are: engineer, architect, platform-team lead, agentic-runtime developer, MCP integrator.

You want: to touch the protocol — not read marketing — in one sitting.

The 10-minute path:

1. Create an actor entity — POST /v1/entities
2. Create a principal entity — same endpoint, different class
3. Create a delegation binding actor to principal — POST /v1/delegations
4. Grant a capability authority with attenuated scope — POST /v1/authority-grants
5. Request a decision — POST /v1/runtime/authorize
6. Receive allow_with_constraints / require_approval / deny
7. Inspect the Decision Map™ — GET /v1/decisions/{id}/map
8. Export an evidence pack — GET /v1/proof-bundles/{id}

Path 3 / 7 · Buyers

Map your first agent authority chain.

Path 4 / 7 · Auditors

Inspect a replayable evidence pack.

Path 5 / 7 · Regulators

Review the control mappings.

Path 6 / 7 · Partners

Build a KYE™ integration profile.

You are: IAM vendor, KYC/KYB/KYA vendor, open-banking platform, payment gateway, agent platform, MCP host, wallet provider, policy engine, SIEM/GRC tool, audit firm, consultancy.

You want: KYE™ to recognise your product as a first-class integration with a documented profile, a conformance fixture, and a public listing.

The integration ladder:

• L1KYE™ Self-Tested™ — you pass the conformance fixtures locally; self-declared.
• L2KYE™ Self-Attested™ — signed self-attestation published to the registry.
• L3KYE™ Conformant™ — conformance report reviewed by the KYE™ program; badge issued.
• L4KYE™ Certified™ — full third-party-audited certification with public registry listing.

Commercial SKU ladder — the partnership-economics track that sits alongside the L1–L4 conformance ladder (Universal Engagement Rail):

• T0KYE™ Strategic Partner™ · Tier-1 / Custom — a scoped engagement for global SIs, Big-4, sovereign integrators. NDA + scoping call set the boundary. Contact for pricing. Apply for review →
• T3KYE™ Strategic Partner™ — top-tier public partner; from £75k/year. Apply →
• T2KYE™ Solutions Partner™ — mid-tier; from £15k/year. Apply →
• T1KYE™ Referral Partner™ — entry tier; £0/year. Apply →

Path 7 / 7 · Enterprises

Run a KYE™ Authority Finality™ Pilot.

You are: a regulated enterprise — bank, insurer, asset manager, custody desk, hospital network, telecom, energy operator, federal agency — with at least one AI agent in production or imminent.

You want: a 2–4 week proof that KYE™ answers who acted, on whose behalf, with what authority, in what state, with what evidence for a real flow.

The pilot scope — pick one:

• AI payment agent (open-banking / payment-initiation)
• Open-banking consent + delegation
• MCP tool governance
• Internal service-account authority
• Healthcare data-access agent
• Critical-infrastructure operator action

Deliverables — produced live, not slides:

• Authority model · entity graph · delegation chain · capability registry
• Live /v1/runtime/authorize decision endpoint
• Per-decision Decision Map™
• Audit-event stream into your SIEM
• Signed evidence pack (replayable)
• Conformance report against the 129-fixture pack
• Gap report · sector-overlay recommendation

Outcome: a single-paragraph artefact you can put in front of your regulator, board, or external auditor — “Here is exactly how KYE™ proves who or what acted, on behalf of whom, using which capability, under what authority, in what state, and with what evidence.”

Working groups · open governance

Where the protocol gets shaped.

KYE Protocol™ is governed in the open. Six working groups meet on GitHub Discussions; minutes + decisions are public; profile RFCs are accepted via the standard contribution process. Membership is open to anyone with operational expertise in the relevant domain.

RFC contribution

Propose a profile, an endpoint, a binding.

1. RFC-1Open a discussion. File a GitHub Discussion in the relevant working group. Describe the gap, the proposed shape, the worked example.
2. RFC-2Spec PR. Once the WG has consensus, open a PR against the relevant public mirror repo (kyeprotocol.com/schemas/ or kyeprotocol.com/developers/api/) with the schema + OpenAPI op + at least one example.
3. RFC-3Conformance fixture. Add at least one black-box fixture to kyeprotocol.com/compliance/.
4. RFC-4Sign-off. Two WG maintainers approve. Schema gets a stable $id. Profile lands in the next minor release.
5. v2.0Foundation track. Move governance to a neutral foundation (Linux Foundation / OpenWallet Foundation candidate) at v2.0; royalty-free IP grant; trademark policy unchanged.

Security disclosure: see SECURITY.md. Trademark policy: see legal page.

Procurement pack · under NDA

Procurement detail — on request, under NDA.

Tier-1 banks and government procurement teams need detail beyond the public surface: the full Reference-Gateway hardening register (env-var inventory, middleware modules, audit-chain backends), the operator runbook bundle (Tier-1 onboarding, incident response, DR/BCP, GDPR DPA / ROPA / DSR, customer SLA, sub-processor inventory, key rotation, regulator comms templates), the attestation roadmap (SOC 2 / ISO 27001 / FedRAMP timing), the HSM / KMS integration matrix, and the supply-chain controls. We don’t publish that on the open web. We package it.

Two ways to receive it

1. Standard MNDA path — we send our standard mutual NDA via DocuSign / Concord countersignature. Counter-signed pack delivered within 1 business day of MNDA execution.
2. Your-paper path — you send your firm’s MNDA template; we counter-sign within 48 hours and deliver. Suitable for procurement teams that require their own paper.

No click-through NDAs. Real countersignature, real audit trail, real delivery SLA. Procurement teams expect this; we won’t pretend otherwise.

Where to go next

Adjacent reading.

Ready to see your AI agents flagged?

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

Canonical KYE™ surfaces referenced on this page: Authority Graph™ · Evidence Pack™ · KYE Protocol™ · Universal Engagement Rail.