---
title: "Receipt-signing keys as a JWK Set"
method: GET
path: "/.well-known/jwks.json"
---

# Receipt-signing keys as a JWK Set

`GET /.well-known/jwks.json`

## Request

- Base URL: `https://api.lodestarstamp.com`
- URL: `https://api.lodestarstamp.com/.well-known/jwks.json`
- Auth: one of:
  - none
  - API key in header `X-Lodestar-Key`
  - OAuth 2 (authorization code, authorization URL `https://api.lodestarstamp.com/oauth/authorize`, token URL `https://api.lodestarstamp.com/oauth/token`, scopes: `mcp:read`)
  - API key in header `PAYMENT-SIGNATURE`

The same Ed25519 public keys as /v1/keys, as a standard JWK Set (RFC 7517 §5: {keys: [...]}, JWK members only) at the well-known path verifier libraries fetch. Empty when no signing key is bound.

## Response `200`

JWK Set; keys may be empty

---

[API](https://skmtc.dev/lodestarstamp/apis/lodestar-trust-api.md) · [All operations](https://skmtc.dev/lodestarstamp/apis/lodestar-trust-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lodestarstamp/apis/lodestar-trust-api/revisions/af78368ab7a5?raw)