Fetch an environment's public keys
The public half of the verification path: the JWKS document your backend checks session JWTs against.
Addressed by publishable key — the one identifier your backend already holds in config — rather than by an internal id you would have to look up. Public and unauthenticated by design: these are public keys. There is no Origin gate either, because the caller is a server and servers send no Origin.
The response carries Cache-Control: public, max-age=300, stale-while-revalidate=86400. That is deliberate: a verifier must keep verifying through our bad five minutes, so a CDN or an in-process cache should keep answering while a refetch is retried.
Keys are minted on first read, so the document is never empty for a configured environment. When JWT minting is unavailable on the server, the answer is an empty key set rather than an error — the JWKS shape stays valid.
Rate limited to 120 requests per minute per IP; a backend may poll it.