KYE™ Connector Profiles™

Profiles define the rules. Connectors plug into systems.

KYE™ Connector Profiles™ group integrations by domain. Each profile defines the schemas, the authority model, state checks, decision vocabulary, signed webhook events, evidence packs, and conformance tests required for that category. Adopt a profile once; integrate many systems consistently.

KYE™ Connector Profiles™, stage by stage

Demo data

You learn: How it works, one stage at a time. You can: Run it end to end.

  1. L1L1 KYE™ Core Protocol™

    KYE Protocol™

    vocabulary, schemas, runtime, decision codes, audit chain. The base contract.

  2. L2L2 KYE™ Profiles

    KYE Protocol™

    domain rules: kye.payments.v1 , kye.healthcare.v1 , kye.federation.v1 , etc. (58 v1.0 normative)

  3. L3L3 KYE™ Connector Profiles™

    KYE Protocol™

    integration-category rules. This page. Each profile binds a family of connectors to a shared authority model + event family + evidence shape + conformance suite.

  4. L4L4 Individual connectors

    KYE Protocol™

    specific systems (Stripe, Shopify, OpenBankProject, NHS API, etc.) under their parent profile.

  5. L5L5 Apps · Plugins · Widgets

    KYE Protocol™

    KYE™ App Store productises · KYE™ Plugin Marketplace™ extends.

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

Profiles define. Connectors integrate. Apps productise. Plugins extend.

Hierarchy

From Core Protocol to Plugin — one tree.

KYE Protocol™ stacks five layers, each one a clean contract over the layer below. The same authority object travels from spec to runtime to evidence.

  1. L1L1KYE™ Core Protocol™ — vocabulary, schemas, runtime, decision codes, audit chain. The base contract.
  2. L2L2KYE™ Profiles — domain rules: kye.payments.v1, kye.healthcare.v1, kye.federation.v1, etc. (58 v1.0 normative)
  3. L3L3KYE™ Connector Profiles™ — integration-category rules. This page. Each profile binds a family of connectors to a shared authority model + event family + evidence shape + conformance suite.
  4. L4L4Individual connectors — specific systems (Stripe, Shopify, OpenBankProject, NHS API, etc.) under their parent profile.
  5. L5L5Apps · Plugins · Widgets — KYE™ App Store productises · KYE™ Plugin Marketplace™ extends.

Worked example · KYE™ Payments Profile™

KYE™ Core Protocol™
  └── kye.payments.v1 (KYE™ Profile)
        └── KYE™ Payments Profile™ (Connector Profile™)
              ├── KYE™ IPG / MPG Connector™
              ├── KYE™ Stripe Connector™
              ├── KYE™ PayPal Connector™
              ├── KYE™ Wallet Connector™
              ├── KYE™ Card-Token Connector™
              └── KYE™ Open-Banking Payment-Initiation Connector™
                    │
                    └── KYE™ Payment Authority Gateway™  (App)
                          └── KYE™ Signal Verifier Plugin™  (Plugin)

11 profile families

One profile per domain. Authority portable across each.

KYE™ Payments Profile™

Core authority question: Before the payment rail authorises the transaction, was the agent authorised to request it? For: payment gateways · IPG · MPG · card tokens · wallets · payment initiation · agentic payments · issuer pre-checks · refunds · payouts · transaction authority. Connectors: KYE™ Payment Authority Gateway™ · KYE™ IPG / MPG Connector™ · Stripe · PayPal · card-token · wallet · open-banking payment initiation · payment orchestration. Strongest line: Before the payment is authorised, KYE™ proves the agent was authorised.

KYE™ Commerce Profile™

Core authority question: Is this agent authorised to buy this basket, from this merchant, using this payment instrument, under this customer's limits? For: retail checkout · shopping carts · marketplaces · agent-backed purchasing · basket authority · merchant authority · refunds / returns · loyalty accounts · delivery-address controls. Connectors: KYE™ Checkout Guard™ · Shopify-style · WooCommerce-style · Magento-style · Amazon-style commerce · eBay Buy APIs · marketplace checkout · basket / order APIs.

KYE™ Open Finance Profile™

Core authority question: Which app, agent, TPP, API client, or workflow acted for which customer, under what consent, authority, scope, and evidence? For: open banking · open finance · bank developer portals · TPPs · account access · payment initiation · corporate APIs · treasury agents · sandbox testing. Connectors: KYE™ for OpenBankProject™ · bank developer portal · FCA sandbox harness · KYE™ UAE Open Finance Sandbox Connector™ · corporate-banking API · KYE™ Open Finance Authority Gateway™.

KYE™ Agent Runtime Profile™

Core authority question: Which agent can use which tools, skills, MCP servers, prompts, workflows and capabilities — under what authority, state, scope, and audit trail? For: MCP · agent runtimes · tools · skills · workflows · capabilities · model / tool invocation · agent sandboxes. Connectors: KYE™ MCP Server · tool gateway · agent runtime · capability registry · prompt registry · workflow · model registry.

KYE™ Compliance Evidence Profile™

Core authority question: How does an authority decision project onto SOC 2 / ISO 27001 / EU AI Act / DORA / PSD3 / 249 frameworks — with replayable signed evidence? For: audit packs · control mappings · framework evidence · regulator portals · self-audit · certification · compliance dashboards. Connectors: KYE™ Evidence Pack Viewer™ · KYE™ Certification & Conformance Portal™ · universal evidence importer (Vanta · Drata · OneTrust · Secureframe · CSV / JSON exports → canonical control / obligation / evidence / AI-system entities) · audit portal · KYE™ Regulatory Sandbox Evidence Harness™.

KYE™ Pension Profile™

Core authority question: Who accessed or acted on a member's pension data, on whose authority, for what purpose, inside what consent scope? For: pension dashboards · find / view requests · member consent · adviser authority · scheme / provider APIs · retirement-planning agents · transfer workflows. Connectors: KYE™ Pension Authority Connector™ · KYE™ Pension Sandbox Harness™ · dashboard · scheme / provider · adviser authority · retirement-agent.

KYE™ Health Profile™

Core authority question: Which clinician, app, supplier, device, or AI assistant accessed or acted on patient data, under what consent, role, state, and purpose? For: patient data access · clinician authority · care-team delegation · AI health assistants · remote monitoring · claims / referrals · break-glass access · consent evidence. Connectors: NHS API authority gateway · Bupa-style private health connector · Huma-style RPM connector · health-app connector · clinical AI assistant connector · patient-consent connector.

KYE™ Security & SIEM Profile

Core authority question: Which signed authority, state, revocation, decision, evidence and blast-radius events stream into the SOC, and which trigger an incident? For: SIEM · SOAR · incident response · blast radius · credential compromise · revocation signals · audit exports · risk monitoring. Connectors: Splunk · Microsoft Sentinel · Datadog · CloudWatch · Kafka · SOAR · signed-webhook · EventBridge.

KYE™ Insurance Profile™

Core authority question: Which broker, AI claims handler, partner, repair network, or loss adjuster acted on a claim or payout, under what authority, state, and evidence? For: claims handling · AI claims agents · broker authority · loss adjusters · repair networks · medical evidence · payout approvals · fraud review. Connectors: claims authority gateway · broker connector · loss-adjuster connector · payout authority connector · repair-network connector.

KYE™ Utilities & Critical Infrastructure Profile

Core authority question: Which operator, contractor, vendor, AI workflow, or field engineer acted on a customer account, meter, asset, or safety-critical operation — under what authority and evidence? For: smart meters · field engineers · contractors · vendor access · emergency authority · billing adjustments · supply actions · asset operations. Connectors: meter connector · field-engineer connector · contractor connector · vendor-access connector · emergency-authority connector.

KYE™ Legal Profile™

Core authority question: Who or what took a legally relevant action, on behalf of whom, under what authority, inside what scope, in what state, with what evidence? For: contract execution · e-signature authority · agent-negotiated contracts · AI legal-assistant actions · board / director authority · power of attorney · corporate approval chains · legal-matter authority · legal hold · DSAR / privacy-request authority · dispute evidence · litigation evidence packs · procurement authority · settlement authority · regulatory-submission authority. Connectors: KYE™ Contract Authority Gateway™ · KYE™ Signature Authority Connector™ · KYE™ Power of Attorney & Delegation App™ · KYE™ Legal Evidence Pack Viewer™ · KYE™ Matter Authority Workspace™ · KYE™ Legal Hold & Preservation App™ · KYE™ Settlement Authority App™. Non-goal: KYE™ does not replace lawyers, courts, e-signature platforms, or legal agreements. It provides the technical authority and evidence layer that legal validity, enforceability, dispute resolution, and audit defensibility depend on.

Manifest schema

Every profile ships kye.connector_profile.v1.

A connector profile manifest declares the supported KYE™ Profiles, the required objects, the decision types, the event families, and the conformance suite. Schema: https://kyeprotocol.com/schemas/connector-profile.json.

{
  "schema_version":  "kye.connector_profile.v1",
  "profile_id":      "kye:connector-profile:payment",
  "display_name":    "KYE™ Payments Profile™",
  "category":        "payments",
  "version":         "1.0.0",
  "description":     "Authority, scope, state, decision, event and evidence rules for payment-related integrations.",
  "supported_connectors": [
    "kye:connector:ipg-mpg", "kye:connector:stripe",
    "kye:connector:paypal",  "kye:connector:wallet",
    "kye:connector:card-token"
  ],
  "required_kye_profiles": [
    "kye.core.v1", "kye.authority.v1", "kye.capability.v1",
    "kye.webhooks.v1", "kye.evidence.v1"
  ],
  "required_objects": [
    "KYEEntity", "KYEAuthorityGrant", "KYEScope",
    "KYEPaymentInstrument", "KYEPolicyDecision",
    "KYEAuditEvent", "KYEEvidencePack"
  ],
  "decision_types": [
    "allow", "deny", "require_approval",
    "require_step_up", "quarantine"
  ],
  "event_families": [
    "kye.payment_authority.*", "kye.purchase_authority.*",
    "kye.authority.*", "kye.decision.*", "kye.evidence_pack.*"
  ],
  "risk_level":         "high",
  "side_effect_level":  "move_money",
  "conformance_suite":  "kye.payment_profile.conformance.v1",
  "status":             "active"
}

What ships today

Profiles are open. Apache 2.0.

Profiles are adoption infrastructure. If partners can't see the contracts, they can't build. Every contract below is implementable today.

SurfaceWhat you get
Profile schemasEvery kye.connector_profile.v1 manifest, dictionaries, supported-connector list
Connector contractsEvery kye.connector_manifest.v1 beneath a profile, sample connectors, SDK adapters
ConformancePer-profile conformance suite, test fixtures, signature verifier
AppsReference architectures + sample app manifests
PluginsPlugin manifests, sample plugins, local test harness

Launch order

Five at v1.0; six at v1.1.

Payment, Commerce, Open Finance, Agent Runtime, and Compliance Evidence are the strongest immediate KYE™ story; they ship at v1.0. Pension, Health, Security & SIEM, Insurance, and Utilities follow at v1.1.

  1. v1.0 #1KYE™ Payments Profile™ — the strongest opener.
  2. v1.0 #2KYE™ Commerce Profile™ — agentic checkout.
  3. v1.0 #3KYE™ Open Finance Profile™ — bank-grade authority.
  4. v1.0 #4KYE™ Agent Runtime Profile™ — MCP & tool governance.
  5. v1.0 #5KYE™ Compliance Evidence Profile™ — audit + certification.
  6. v1.1 #6KYE™ Pension Profile™
  7. v1.1 #7KYE™ Health Profile™
  8. v1.1 #8KYE™ Security & SIEM Profile
  9. v1.1 #9KYE™ Insurance Profile™
  10. v1.1 #10KYE™ Utilities & Critical Infrastructure Profile
  11. v1.1 #11KYE™ Legal Profile™ — contract authority, e-signature authority, power of attorney, legal hold, settlement authority, litigation evidence packs.

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