KYE Discoverability Profile™ · v1.0

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.

category Discovery types layers Six modes schema Schemas apps Apps balance Open / paid
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.

personEntityHumans, organisations, agents, services, wallets, devices, models, tools.
verified_userAuthorityGrants, scopes, delegated chains, approval rules; expiring, stale, over-broad.
extensionCapabilityTools, skills, APIs, workflows, prompts, models, MCP servers; by side effect.
verifiedEvidenceAudit events, Decision Maps™, Evidence Packs™, replay records.
warningRiskHigh-risk chains, stale grants, compromised dependencies, blast radius.
grid_viewEcosystemProfiles, 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: git clone https://github.com/KYE-Protocol/schemas && cd schemas && npm ci && npm test

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.

menu_bookKYE Directory™Searchable directory of entities, agents, capabilities, grants, profiles.
searchKYE Authority Search™Authority-graph traversal for the owner and the auditor.
account_treeKYE Authority Path Finder™Principal → delegation → actor → capability traces.
verifiedKYE Evidence Finder™Search and verify Evidence Packs™ and audit events.
grid_viewKYE 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.

Open source

  • All v1 schemas above
  • Reason-code dictionaries
  • Event / webhook schemas
  • Sample fixtures + examples
  • Conformance test vectors
  • Validator SDK
  • Sample local directory implementation

Proprietary (commercial licence)

  • KYE™ Directory Engine (managed)
  • Policy-filtered graph search
  • Semantic authority search
  • Risk-ranked discovery
  • Over-permissioning detection
  • Stale-grant detection heuristics
  • Cross-tenant masking engine
  • KYE Connector Hub™
handshake Request the procurement pack → timeline Continuity Module™ architecture Protocol overview

Ready to see your AI agents flagged?

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

rocket_launch Apply for pilot → science Try the sandbox →