Get the public keys the Runtime's tokens are signed with
A JSON Web Key Set, to verify a token the Runtime signed without calling it. No credential is needed.
AuthorizationBearer <token>An application key of the Tenant (PUT /v1/tenant/keys/{keyId}), or Studio's key, derived from the admin key. With Nylorun-Subject and Nylorun-Scopes, it acts for that person, narrowed to those scopes. Never accepted from a browser (Origin).
Nylorun-Protocol*stringThe protocol version, 18
Nylorun-Subject?stringThe person an application key acts for
Nylorun-Scopes?stringThe subject's space-separated scopes; required with a subject
The public keys
application/json- response
keys*array<>import { createClient } from "@nylorun/agents";const client = await createClient();const jwks = await client.access.jwks();{ "keys": [ { "kty": "EC", "crv": "P-256", "x": "string", "y": "string", "kid": "string", "alg": "ES256", "use": "sig" } ]}Get the protected resource metadata GET
OAuth 2.0 Protected Resource Metadata (RFC 9728): the identity providers whose access tokens the Runtime API accepts (the identity file's trusted issuers) and their scopes. Nylorun is never the authorization server: a client signs in at one of `authorization_servers` and presents its token as `Authorization: Bearer`. A `401` from the Runtime API names this document in `WWW-Authenticate` (`resource_metadata`). Needs no key or `Nylorun-Protocol`, and accepts an `Origin`.
Get the Runtime API's document GET
This document. `/openapi.json` is the same.