Supplier-payment agent — Authority Gaps report

Live demoRun this demo at sandbox.kyeprotocol.com/supplier-payment.html; the same governed flow also runs in the terminal and the lab.

Meridian Mutual Bank's AP-automation agent, observed over 30 days. The agent reads invoices, matches them to purchase orders, and proposes payments — but should never execute them, modify vendor records, or change purchase orders. KYE™ caught 12 violations in shadow mode.

Plain Q&A

Plain Q&A

Short questions. Short answers.

• Do I need to sign up? No.
• Is this real? Yes. Real Workers. Real keys.
• Can I see the source? Yes. The runtime is open.
• Where does state go? Public sandbox DB. Resets daily.
• Will it log my IP? No. Logs are scrubbed.
• How many calls free? Up to 200 per hour.
• Curl-friendly? Yes. Every endpoint.
• Bring my own data? Yes. Drop a JSON. Try.

Plain take

Plain take

Try every endpoint. Sign every reply. No signup.

• Real Workers. Real signatures.
• Public test keys. Public test data.
• Reset state with one click.
• Curl-friendly. SDK-friendly.

Sample observed-action stream

Short take. Big idea.

kye-stream observe --scenario=supplier-payment --limit=7 7 of 1,000 shown

Detected Authority Gaps

Short take. Big idea.

Guard Recommendations

Short take. Big idea.

Each Guard Recommendation is a proposed scope change. The "estimated_legitimate_blocked" figure is computed by replaying the 30-day stream against the tightened scope and counting actions that would have been blocked despite being legitimate.

Sample Evidence Pack

Short take. Big idea.

Take this to your CISO

This is exactly the report a KYE™ Cloud tenant would see for their own AI agents. Apply for a pilot → to run this against your real traffic.

kye-sandbox · scenario: supplier-payment · fixture kye:fixture:sandbox:supplier_payment_v1 ← All scenarios

Canonical KYE™ surfaces referenced on this page: Evidence Pack™ · KYE™ Cloud™.