auto-parts marketplace · cross-vendor fulfilment · Authority Finality

Collision Marketplace Authority — see a governed agent decision live

You pick a collision-marketplace scenario and run it. KYE Protocol checks who authorised the agent at the action boundary and returns a real decision — it admits a listing check, holds an irreversible parts-order release for approval, and denies a self-escalation.

This is Authority Finality: a marketplace agent can be a registered principal yet still be unauthorised to finalise the effect. Visibility never creates permission.

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 marketplace operator or parts vendor.

1 · Pick a scenario

Three marketplace 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.

Open the offline Evidence Pack™ verifier →

What this proves

Same deterministic three-outcome engine as the authenticated Authority API (POST app.kyeprotocol.com/api/v1/runtime/evaluate). The listing provenance check is admitted; an irreversible cross-vendor parts-order release with no recorded approval is held for a human step-up — the registered-but-unauthorised moment; an attempt by the agent to grant itself pricing-override admin is denied outright at the policy layer. Apply for a pilot → to run this against your own AI-agent traffic.