Customer-support agent — clean baseline

Sample agent flow. Tool call. Approval. Evidence.

Open playground →DemoOpen playground →

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

← Sandbox

Cobalt Energy Retail's customer-care agent, observed over 30 days. 5,000 actions, only 2 minor Authority Gaps. This fixture shows what "healthy" looks like — the agent stays within scope, every customer interaction is recorded with a Consent Receipt, and PII is redacted at log time.

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=support-agent --limit=5 5 of 5,000 shown

Detected Authority Gaps

Short take. Big idea.

Guard Recommendations

Short take. Big idea.

Short take. Big idea.

Every interaction with a customer records a signed Consent Receipt before the agent reads any account state. Receipts are bound to a purpose, a scope, and a TTL.

Sample Evidence Pack

Short take. Big idea.

kye-sandbox · scenario: support-agent · fixture kye:fixture:sandbox:support_agent_v1 ← All scenarios

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