1 · Gateway health
GET https://api.kyeprotocol.com/health
One click. Full flow. Signed end to end.
Live demoRun this demo at sandbox.kyeprotocol.com/demo.html; the same governed flow also runs in the terminal and the lab.
Runs a sample Action Request through every production Worker in the KYE™ runtime chain — kye-gateway → kye-pdp → back to your browser — and shows the response from each hop. No sign-up. No install. Uses the same public URLs you would use from your own code.
Plain Q&A
Short questions. Short answers.
GET https://api.kyeprotocol.com/health
GET https://pdp.kyeprotocol.com/health
GET https://edge.kyeprotocol.com/health
GET https://mcp.kyeprotocol.com/health
GET /v1/directory/widgets
POST /v1/decisions/evaluate
Idle. Click "Run" to fire all 6 probes.
{
"action": {
"id": "kye:action:demo:purchase:001",
"verb": "submit_payment",
"subject": "kye:agent:demo-sandbox-agent",
"object": "kye:invoice:acme:2026-Q2-099",
"amount": { "currency": "USD", "value": 4800.00 },
"context": { "channel": "sandbox-demo", "now_iso": "2026-05-14T22:00:00Z" }
},
"policy_set_id": "kye:policy-set:demo:public-purchase-v1"
}
No probe run yet.
stepstatusendpointlatency
The decision step requires a bearer token. The demo's call lands at kye-gateway's POST /v1/decisions/evaluate without one, so the expected response is 401 unauthorized — that's the deny-by-default guard surface working as designed. To run a real signed decision, mint an API key via the Customer Cloud → API keys panel and inject it as Authorization: Bearer ….
Canonical KYE™ surfaces referenced on this page: KYE™ Edge Governance™ · KYE™ MCP Server · KYE Protocol™.