---
title: "KYE Protocol™ — Connector Hub™ | IPG · MPG · Checkout · MCP · IAM · SIEM · GRC · KYC/KYB/KYA"
description: "The KYE™ Connector Hub™. Plug KYE Protocol™ into payment gateways, internet/mobile payment gateways, checkout, shopping carts, wallets, MCP servers, agent…"
url: https://kyeprotocol.com/connectors/
lang: en
source: "KYE Protocol"
---

> The KYE™ Connector Hub™. Plug KYE Protocol™ into payment gateways, internet/mobile payment gateways, checkout, shopping carts, wallets, MCP servers, agent…

KYE™ Connector Hub™

# Plug KYE™ into the systems you already run.

One canonical manifest schema. Six families. A public registry. Apache 2.0. You ship a signed connector and your buyers wire it in.

Six families

## Six connector families.

Six families cover the gateways, runtimes, identity stacks, policy engines, security pipes, and verification vendors you already deploy. Pick a family. Ship a manifest. Bind to KYE™.

### Payments & commerce

`internet_payment_gateway` · `mobile_payment_gateway` · `payment_gateway` · `checkout` · `shopping_cart` · `card_token` · `wallet` · `open_banking` · `merchant_risk` · `chargeback`

### AI & agent runtime

`mcp_server` · `agent_runtime` · `tool_gateway` · `capability_registry` · `model_registry` · `prompt_registry` · `workflow`

### Identity & access

`oauth_oidc` · `saml` · `scim` · `spiffe_spire` · `iam` · `pam` · `passkey` · `credential_issuer`

### Policy & governance

`opa` · `cerbos` · `aws_cedar` · `grc` · `control_mapping` · `certification` · `self_audit`

### Security & observability

`siem` · `soar` · `splunk` · `sentinel` · `datadog` · `cloudwatch` · `kafka` · `eventbridge` · `webhook`

### Verification

`kyc_provider` · `kyb_provider` · `kya_provider` · `agent_passport` · `credential_verification`

Connector explorer

## Search the Connector Hub™ reference set.

Search by name, type, or description. Filter by family. Each row shows the type, the current status, and the side-effect level — so you pick the right connector for the right risk envelope.

Flagship connectors

## Three flagships. Three top pain points.

Payments, checkout, and agent tooling are where buyers feel the gap first. These three connectors solve the most common KYE™ wiring jobs and ship as Apache 2.0 reference builds.

[**IPG / MPG connector** Add KYE™ authority checks to internet and mobile payment gateways. KYE™ authorises the agent before the gateway charges the card. _view payment connector →_](https://kyeprotocol.com/agent-purchasing/) [**Checkout Guard™** Detect agent-backed checkouts. Verify the agent is allowed to buy this basket, from this merchant, for this customer. Signed Decision Map™ per checkout. _explore checkout →_](https://kyeprotocol.com/open-banking/) [**MCP server & connector** Expose KYE™ authority checks, schemas, and Evidence Packs™ to MCP-compatible agents and IDEs. Enforcement stays inside the KYE™ Gateway™. _explore MCP →_](https://kyeprotocol.com/mcp/)

Connector manifest

## One canonical schema. Every connector.

Every connector ships a `kye.connector_manifest.v1` document. The manifest declares what it does, which profiles it supports, what it subscribes to, what it publishes, and how it authenticates.

```
{
  "schema_version": "kye.connector_manifest.v1",
  "connector_id":   "kye:connector:ipg:example_gateway",
  "name":           "Example IPG Connector",
  "display_name":   "Example Internet Payment Gateway Connector",
  "connector_type": "internet_payment_gateway",
  "category":       "payments",
  "version":        "1.0.0",
  "publisher": {
    "publisher_entity_id":  "kye:org:kye_protocol",
    "maintainer_entity_ids": ["kye:user:maintainer_001"]
  },
  "description": "Adds KYE™ authority pre-checks to IPG flows.",
  "supported_profiles": [
    "kye.core.v1", "kye.payment_authority.v1",
    "kye.agent_purchasing.v1", "kye.webhooks.v1", "kye.evidence.v1"
  ],
  "integration_points": [
    { "name": "pre_authorisation_check", "direction": "outbound_to_kye",
      "method": "POST", "path": "/v1/authority:decide", "required": true },
    { "name": "payment_result_webhook",  "direction": "inbound_to_kye",
      "method": "POST", "path": "/v1/events", "required": false }
  ],
  "capabilities": [
    "agent_purchase_check", "payment_authority_check",
    "basket_hash_binding", "merchant_category_scope",
    "approval_threshold", "evidence_pack_generation"
  ],
  "auth": {
    "auth_type": "api_key_or_oauth_client_credentials",
    "supports_key_rotation": true,
    "supports_mtls": true
  },
  "events": {
    "subscribes_to": [
      "kye.authority.revoked", "kye.decision.requires_approval",
      "kye.payment_authority.revoked"
    ],
    "publishes": [
      "kye.purchase_authority.allowed",
      "kye.purchase_authority.denied",
      "kye.purchase_authority.requires_approval"
    ]
  },
  "risk": {
    "risk_level":                    "high",
    "side_effect_level":             "move_money",
    "requires_signature_verification": true,
    "requires_idempotency":          true,
    "requires_audit_event":          true
  },
  "runtime": {
    "deployment_modes":   ["hosted", "byoc", "on_prem"],
    "supported_languages": ["typescript", "python", "go"]
  },
  "integrity": {
    "manifest_hash":     "...",
    "signature_required": true,
    "signature_ref":     "kye:signature:connector_manifest_001"
  },
  "status":     "active",
  "created_at": "2026-05-06T00:00:00Z",
  "updated_at": "2026-05-06T00:00:00Z"
}
```

Dictionaries

## Stable enums. Governed openly.

Five dictionaries underpin the manifest. New values land via the public RFC process. Existing values never change meaning, so your audit trail stays valid under DORA Art. 6.

- **`connector_type`** — the 30+ types listed in the family cards above.
- **`connector_category`** — payments · commerce · agent\_runtime · identity · policy · security · observability · governance · verification · audit · compliance · developer\_tools.
- **`connector_status`** — draft · submitted · validating · active · deprecated · quarantined · revoked · archived.
- **`integration_point_type`** — pre\_authorisation\_check · decision\_request · event\_subscription · webhook\_receiver · webhook\_sender · evidence\_export · audit\_import · policy\_sync · identity\_sync · approval\_callback.
- **`side_effect_level`** — read\_only · audit\_only · decision\_only · write\_internal · send\_external\_message · execute\_transaction · move\_money · modify\_authority · admin\_action · destructive.

Endpoints

## Register, install, monitor, replay.

Three endpoint families cover the lifecycle. Publishers register and version connectors. Operators install and rotate credentials. Subscribers replay events when an audit firm asks.

**Publisher endpoints:**

- `POST /v1/connectors` · `GET /v1/connectors` · `GET /v1/connectors/{id}` · `PATCH`
- `POST /v1/connectors/{id}:validate` · `:publish` · `:deprecate` · `:quarantine` · `:revoke`

**Operator endpoints:**

- `POST /v1/connector-installations` · `GET` · `GET .../{id}` · `PATCH` · `DELETE`
- `POST /v1/connector-installations/{id}:test` · `:rotate-credentials`

**Event endpoints:**

- `POST /v1/connectors/{id}/events` · `GET /v1/connectors/{id}/events` · `POST /v1/connectors/{id}:replay-events`

Connector events

## Twelve lifecycle events.

Lifecycle events fan out on the KYE™ Signal Bus™ over signed webhooks. You monitor health, gate installs behind validation, and rotate keys before signatures expire. (The signature suite is proprietary and not disclosed here; SDK helpers ship the verification path.)

- `kye.connector.registered` · `validated` · `validation_failed` · `published`
- `kye.connector.deprecated` · `quarantined` · `revoked`
- `kye.connector.installed` · `installation_failed` · `health_degraded`
- `kye.connector.credential_rotation_required` · `event_replay_requested`

What ships today

## Open contracts. Apache 2.0.

The schema must be open or the ecosystem will not grow. You can author, test, and publish a connector against the manifest without paying for a hosted service.

| Surface | What you get |
| --- | --- |
| Schemas | Connector manifest schema, five dictionaries, event schemas |
| Reference connectors | Sample IPG, sample checkout, sample MCP, sample SIEM — full source, Apache 2.0 |
| Test harness | Local connector test harness, conformance fixtures, signature verifier |
| Self-hosted runtime | KYE™ Reference Gateway™: PEP middleware, embedded ePDP, conformance runner |

Publish a connector

## Five steps. Idea to registry.

From draft to public registry in roughly five working days. Each step is signed and audited under ISO 42001 plus the KYE™ Conformance Pack™.

1. P1 **Author the manifest.** Fill in type, supported profiles, integration points, capabilities, side-effect level, and auth modes.
2. P2 **Run conformance.** The local test harness validates the manifest, the integration points, and the event signatures.
3. P3 **Sign & submit.** `POST /v1/connectors` with the signed manifest. The program runs `:validate`.
4. P4 **Program review.** Schema, behaviour, side-effect class, auth, and audit emission. About five working days.
5. P5 **Publish.** `:publish` — your connector lands in the public registry and the Connector Hub™.

[Partner program →](https://kyeprotocol.com/partners/) [Certification](https://kyeprotocol.com/certification/) [Reference connectors](https://github.com/KYE-Protocol) Talk to the program

Adjacent reading

## Where to go next.

If you want to build first, head to Build. If you want to integrate with adjacent standards, head to Integrations. If you want to partner, head to Partners.

[Build →](https://kyeprotocol.com/build/) [MCP server](https://kyeprotocol.com/mcp/) [Adjacent standards](https://kyeprotocol.com/integrations/)

## 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 →](https://kyeprotocol.com/pilot-apply/) [Try the sandbox →](https://kyeprotocol.com/sandbox/demos/)

Canonical KYE™ surfaces referenced on this page: [Evidence Pack™](https://kyeprotocol.com/evidence-pack/) · [KYE™ Conformance Pack™](https://kyeprotocol.com/compliance/) · [KYE Protocol™](https://kyeprotocol.com/).
