Get who the caller is
The subject, scopes and Agent grants of the credential that sends it: an application key (alone or acting for a subject), a management key (via: management:<principalId>, no scopes, no agents), or a trusted issuer's token (via: issuer:<name>).
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 caller
application/json- response
subject?stringThe person the request acts for; absent for an application key alone
scopes*array<>agents*|array<>via*stringHow the caller authenticated: application:<principalId>, management:<principalId>, subject or issuer:<name>
curl -X GET "https://example.com/v1/me" \ -H "Nylorun-Protocol: string"{ "subject": "string", "scopes": [ "agents:read" ], "agents": "*", "via": "string"}Check the Runtime is ready GET
The listener, the Tenant (open), Postgres, Restate and S2, and the open Tenant's harnesses.
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`.