Telecom Consent Authority — see a governed agent decision live
You pick a telecom-consent scenario and run it. KYE Protocol™ checks the agent's mandate at the action boundary and returns a real decision — it admits a consent.verify, holds an irreversible line disconnect for approval, and denies a self-escalation.
Live demoRun this demo at sandbox.kyeprotocol.com/telecom-consent-authority.html; the same governed flow also runs in the terminal and the lab.
Honest scope: this runs on a fixed demo tenant (kye:tenant:sandbox-demo), persists nothing, and is a demonstration only — never a partnership or deployment with any telecom operator or vendor.
1 · Pick a scenario
Three telecom-consent actions a governed agent might attempt.
2 · Request
Ready.
3 · Live decision
— No decision run yet. Pick a scenario and click Run.
4 · Evidence
The endpoint returns a patent-safe evidence reference (opaque id + outcome + reason + verify link) and the full sealed Evidence Pack™. Paste the pack into the offline verifier to check it from public keys alone.
Run a scenario to see the evidence reference and sealed pack.What this proves
Same deterministic three-outcome engine as the authenticated Authority API (POST app.kyeprotocol.com/api/v1/runtime/evaluate). The consent-verify action is admitted; an irreversible line-disconnect with no recorded approval is held for a human step-up; an attempt by the agent to grant itself admin is denied outright at the policy layer. Apply for a pilot → to run this against your own AI-agent traffic.
kye-sandbox · scenario: telecom-consent-authority · endpoint POST /api/v1/pdp/decide ← All scenarios