Build the agentic AI. Prove it had authority to act.

You are a consultancy, digital agency, systems integrator, or transformation team shipping agentic AI for regulated buyers. The KYE Protocol™ Certified Agentic Delivery Pack™ is your delivery channel: your team builds the product, and KYE™ proves every consequential action it takes had authority — cutting a regulated buyer's audit-evidence prep from days to minutes. It is the authority layer over the agent-interop rails (MCP, A2A, A2UI, AP2/UCP), never a competitor to them.

KYE™ Certified Agentic Delivery Pack™, point by point

Demo data

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

  1. Step 1 of 3

    KYE Protocol™

    The authority gap

    Tool-call, agent-hire, and payment protocols move the action; none of them prove the agent was permitted to take it under EU AI Act™ Article 14 human oversight or ISO/IEC 42001 clause 6.

  2. Step 2 of 3

    KYE Protocol™

    The evidence gap

    A regulated buyer needs a replay-verifiable record per action; a chat log is not evidence a supervisor will accept.

  3. Step 3 of 3

    KYE Protocol™

    The trust gap

    You are asking a bank, insurer, or hospital to trust an agent your team wrote weeks ago — with nothing between the agent and the consequential action.

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

Apply as a delivery partner See the authority stack

The problem you keep hitting

Your regulated buyer loves the demo, then legal asks the question that stalls the deal: when the agent acted, who authorised it, and can you prove it to an examiner? Answering that by hand is what turns a six-week build into a six-month procurement.

  • The authority gap. Tool-call, agent-hire, and payment protocols move the action; none of them prove the agent was permitted to take it under EU AI Act™ Article 14 human oversight or ISO/IEC 42001 clause 6.
  • The evidence gap. A regulated buyer needs a replay-verifiable record per action; a chat log is not evidence a supervisor will accept.
  • The trust gap. You are asking a bank, insurer, or hospital to trust an agent your team wrote weeks ago — with nothing between the agent and the consequential action.

What the pack gives your team

The Certified Agentic Delivery Pack™ is a bundle assembled entirely from KYE Protocol™'s existing rails, so you wire authority into your build instead of inventing governance. Each deliverable binds one canonical rail — you integrate it, you never re-implement it.

  • Agent-manifest templates — starter scaffolds from the KYE™ Agent Dev Kit™ so every agent you ship is a first-class governed principal.
  • Tool-call authority policies — bind an agent's tool-calls, messages, external representations, data reads, and deployments to the five canonical action classes via an allow-list.
  • Delegated approval workflows — human-over-the-loop approval for consequential actions, reusing the six locked GovernedUI™ approval modes.
  • Evidence-capture templates — emit an Evidence Pack™ at every action, sealed and Replay-Proof™ from public keys alone.
  • Regulated-sector checklists — map the built product's obligations to real KYE™ artefacts across finance, health, and insurance, honestly (a mapping counts only when a cited artefact backs it).
  • Release-gate authority checks — a pre-release check that fails the pipeline if any consequential action path ships ungoverned.
  • Audit-bundle generator — assemble a WORM-retained, replay-verifiable evidence bundle for the whole product on demand.
  • KYE-Certified Delivery badge — a revocable licensed mark that renders only while a named lead on your team holds a current KYE™ certification.

Authority over interop — the honest positioning

KYE Protocol™ does not replace the protocols your agents already speak. It sits above them and answers the one question they cannot: may this action become final? That is the boundary a regulated buyer actually pays for.

  • MCP moves a tool-call — KYE™ decides whether the agent was permitted to call it and records the verdict.
  • A2A hires another agent — KYE™ binds the delegated authority and its scope.
  • A2UI renders a surface — KYE™ governs the human approval on that surface.
  • AP2 / UCP settles a transaction — KYE™ proves the agent held authority to transact before the money moved.

How the partnership works

The pack is a KYE™ partner engagement, so your firm joins through the same reviewed intake every KYE™ partner uses — no separate portal, no per-partner subdomain. Admission is application-reviewed; meeting the profile qualifies your team to apply.

  • Apply. Your firm applies through the shared engagement intake as a delivery partner (specialization: agentic delivery).
  • Certify. At least one named delivery lead earns and maintains a current KYE™ certification for every active engagement.
  • Deliver. Your team builds the agentic AI on the pack's templates; KYE™ proves each action had authority and mints the buyer's audit bundle.
  • Badge. While a named lead stays certified, your firm renders the KYE-Certified Delivery badge — suspended the moment certification lapses.

Start your delivery-partner application

Where it sits in KYE™

This pack is the consultancy and integrator delivery channel of Authority Finality™ — the same rails KYE™ runs on itself, packaged for the firms that build for regulated buyers. Explore the related programs to place it in the wider picture.

Canonical KYE™ surfaces referenced on this page: KYE™ Agent Dev Kit™.