KYE™ Discoverability Profile™

Make delegated agency findable.

It is not enough that KYE™ records authority. You also need to find it. Every query is purpose-bound, policy-filtered, audited, and masked — so auditors, regulators, and operators see what they need and nothing more.

Discoverability Profile, point by point

Demo data

You learn: The page's points, one at a time. You can: Step through them.

  1. Step 1 of 6

    KYE Protocol™

    private_tenant

    one customer's KYE™ graph ("all active agents in my tenant")

  2. Step 2 of 6

    KYE Protocol™

    workspace

    one team or environment ("production payment capabilities in Finance")

  3. Step 3 of 6

    KYE Protocol™

    cross_workspace

    enterprise scope ("all high-risk agents across business units")

  4. Step 4 of 6

    KYE Protocol™

    federated

    partner organisations ("does this PSP (Payment Service Provider) hold a valid authority assertion?")

  5. Step 5 of 6

    KYE Protocol™

    public_registry

    public profiles, connectors, apps, badges ("all KYE™ Payments Profile™ connectors")

  6. Step 6 of 6

    KYE Protocol™

    certification_registry

    verified vendors ("vendors with active KYE™ Authority Conformant™ status")

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

1 · Six discovery types

Find what exists. Mask what is sensitive.

Six query types cover the surface area of an Authority Graph™. You pick the type. The Directory Engine picks the mask, the audit event, and the JWS (JSON Web Signature) on the result.

Entity

Humans, organisations, agents, services, wallets, devices, models, tools.

Authority

Grants, scopes, delegated chains, approval rules; expiring, stale, over-broad.

Capability

Tools, skills, APIs, workflows, prompts, models, MCP servers; by side effect.

Evidence

Audit events, Decision Maps™, Evidence Packs™, replay records.

Risk

High-risk chains, stale grants, compromised dependencies, blast radius.

Ecosystem

Profiles, connectors, apps, plugins, certified partners.

2 · Six modes, in widening scope

Every mode is policy-filtered.

Pick the scope you can defend. The Directory Engine signs the audit event under DORA (Digital Operational Resilience Act) Art. 18 and GDPR Art. 30 so you can prove every query was bounded.

  • private_tenant — one customer's KYE™ graph ("all active agents in my tenant")
  • workspace — one team or environment ("production payment capabilities in Finance")
  • cross_workspace — enterprise scope ("all high-risk agents across business units")
  • federated — partner organisations ("does this PSP (Payment Service Provider) hold a valid authority assertion?")
  • public_registry — public profiles, connectors, apps, badges ("all KYE™ Payments Profile™ connectors")
  • certification_registry — verified vendors ("vendors with active KYE™ Authority Conformant™ status")

3 · Schemas (Apache 2.0)

Seven normative JSON objects. Validated by ajv in CI.

Each schema is JSON Schema 2020-12 with a stable $id. The same shapes drive your OpenAPI spec, your webhook payloads, and the SDK clients.

Reproduce: curl -fsSL https://kyeprotocol.com/schemas/policy-decision.json | jq '."$id"'

4 · Apps that compose the profile

Five planned apps for five jobs.

Each app is a thin surface over the same Directory Engine. You ship one engine; your auditors, owners, and partners each get the view they need.

KYE™ Directory™

Searchable directory of entities, agents, capabilities, grants, profiles.

KYE™ Authority Search™

Authority-graph traversal for the owner and the auditor.

KYE™ Authority Path Finder™

Principal → delegation → actor → capability traces.

KYE™ Evidence Finder™

Search and verify Evidence Packs™ and audit events.

KYE™ Connector Hub™

Find profiles, connectors, apps, and certified partners.

5 · Open / paid boundary

Contracts are open. The discovery engine is paid.

Apache 2.0 schemas, dictionaries, fixtures, and validators ship in public. The paid Directory Engine adds masking, risk ranking, and stale-grant detection for buyers under ISO 42001 and NIST AI RMF audits.

Request the procurement pack →Continuity Module™Protocol overview

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™ Directory™ · KYE™ MCP Server · KYE Protocol™ · Purpose Permission.