No Client Identity
Create one to connect to servers
Create Identity

Diagnostic Reference

KYA-OS failures are snake_case reason codes riding error.data.reason - clients dispatch on the reason, never on the numeric JSON-RPC code. Paste an error response or search by code to understand what happened and how to resolve it.

Paste Error to Detect

Showing 35 of 35 error codes

Understanding the Error Surface

  • - Only two numeric codes are fixed by the spec: -32021 (required extension not declared, with data.requiredCapabilities) and -32602 (present-but-malformed declaration)
  • - Every other failure is a reason string in error.data.reason; fine-grained verification diagnostics may also appear under error.data.reasons
  • - The v1 proof window is tight: 60s max TTL with ±5s clock-skew tolerance - expired usually means a proof was reused on retry instead of re-minted
  • - Step through the Proof Explorer to see where a failing proof diverges; validate identities in the Identity tool