labelprefixscopestatusexpireslast usedcreated

Your first call — an Authority Finality™ decision in one request

Mint a key with the runtime:write scope, export it as KYE_API_KEY, and evaluate one agent action. Every call returns a governed decision — allow, require_approval or deny — with a replay-stable decision_id and a verifiable Finality receipt.

Endpoint: POST https://app.kyeprotocol.com/api/v1/runtime/evaluate

Request
curl -s https://app.kyeprotocol.com/api/v1/runtime/evaluate \
  -H "Authorization: Bearer $KYE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "kye:agent:acme:kyc-triage",
    "action":  "payments.transfer",
    "purpose": "kyc.onboarding",
    "context": { "amount": 25000, "jurisdiction": "EU" }
  }'
Response — one of three outcomes
{
  "decision": "require_approval",        // or "allow" | "deny"
  "reason_code": "approval_threshold_breach",
  "decision_id": "kye:decision:9f2ab41c77d0e3b6",
  "evidence": {
    "kind": "audit_reference",
    "id": "kye:decision:9f2ab41c77d0e3b6",
    "outcome": "require_approval",
    "reason": "approval_threshold_breach",
    "verify_url": "https://kyeprotocol.com/trust-self-audit.html"
  },
  "verify_url": "https://app.kyeprotocol.com/evidence.html?receipt=kye:decision:9f2ab41c77d0e3b6",
  "evidence_pack": { "signature": { "alg": "Ed25519" } }
}

allow — the agent may act · require_approval — held for a recorded human approval · deny — refused with a canonical reason code. Open the verify_url to see your first Finality receipt.

Identifiers on this page are illustrative. They are shaped like real KYE Protocol™ identifiers but do not resolve to a governed record. Published references that do resolve are indexed at /trust.html.