Build a KYE™ integration profile for your product.
KYE Protocol™ is an open contract layer. The partner programme exists so identity, KYC/KYB/KYA, payment, agent, MCP, audit, GRC and policy vendors can ship a documented integration with a conformance fixture, a public listing, and a badge their customers can verify with public keys alone.
Vendors whose customers are already asking “does it work with KYE™?”
If you sell into regulated enterprises with AI-agent or delegated-authority workflows, your buyers are already being asked — by their auditors, regulators, or risk teams — how their stack proves the chain. Eight categories of vendor map directly into the protocol surface:
Four tiers, each one a public, verifiable claim.
Every tier is a signed artefact. No tier is a marketing pill — each is reproducible by anyone with public keys and the conformance pack. You can stop at any tier; you do not need to climb.
- L1KYE Self-Tested™ — you run the conformance fixtures locally and self-declare results. No review required. Listed in the registry as “self-tested” with a link to your fixture report.
- L2KYE Self-Attested™ — you publish a signed self-attestation (Ed25519, JWS) bundled with your fixture results. The KYE Protocol™ programme verifies the signature; the claim itself is yours.
- L3KYE Conformant™ — conformance report reviewed end-to-end by the KYE™ programme. Schema, endpoint, behaviour, evidence shape, error codes, and edge-case handling all checked. Badge issued; registry listing upgraded.
- L4KYE Certified™ — full third-party-audited certification by an approved audit firm. Public registry listing. Annual revalidation. The mark a regulated buyer can put in front of their supervisor.
Concrete benefits, not marketing badges.
| Benefit | L1 | L2 | L3 | L4 |
|---|---|---|---|---|
| Listed in public registry | ✓ | ✓ | ✓ | ✓ |
| Use of KYE™ word mark in product copy | ✓ (with disclaimer) | ✓ | ✓ | ✓ |
| Use of conformance badge logo | — | — | ✓ | ✓ |
| Programme-signed attestation | — | ✓ | ✓ | ✓ |
| Third-party audit | — | — | — | ✓ |
| Co-marketing on KYE Protocol™ site | — | — | ✓ | ✓ |
| Direct referral from regulated-buyer pilots | — | — | — | ✓ |
| Annual revalidation required | — | — | — | ✓ |
Trademark policy — including the precise rules for using the KYE™, KYE Protocol™, KYE Conformant™, and KYE Certified™ marks — is documented on the legal page and the legal FAQ.
From handshake to badge in 4–8 weeks.
- P1Discovery call. 30–45 minutes. We map your product surface to KYE Protocol™ primitives. We tell you, on the call, which tier is realistic and what's missing.
- P2Profile draft. You publish a draft integration profile against the spec: which entities you produce, which endpoints you call, which evidence you emit. We review and propose changes.
- P3Conformance run. Run the 38-fixture conformance pack. For L1, self-declare. For L2–L3, sign and submit. For L4, an approved audit firm runs the pack.
- P4Review. L2: signature verification. L3: end-to-end programme review (~5 working days). L4: audit firm produces a signed report.
- P5Listing. Public registry entry created with the signed conformance report attached. Badge artefact issued under the trademark licence.
- P6Maintenance. L4 partners revalidate annually. L3 partners notify the programme on any breaking change to their integration.
Every claim, public-key-verifiable.
The registry is published as a static, signed JSON file plus a human-readable HTML index. Each entry contains the partner identity, tier, conformance-report hash, signing key, and last-revalidation date. Anyone — a regulator, an auditor, a buyer's procurement team — can replay the evidence offline using the published public keys.
The registry is in pre-launch alongside v1.0 of the protocol. Founding partners listed here will be co-announced with the v1.1 release.
Propose a partnership.
If your product fits one of the eight categories above — or you think it should — reach out. The first call is always discovery, never sales. The protocol is Apache 2.0; the certification programme is the only commercial component.