---
title: "Openid Configuration"
method: GET
path: "/.well-known/openid-configuration"
tags: ["discovery"]
---

# Openid Configuration

`GET /.well-known/openid-configuration`

## Request

- Base URL: `https://api.bitpoort.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.bitpoort.com/.well-known/openid-configuration`
- Auth: none required

Minimal OIDC discovery alias.

We don't issue ``id_token`` JWTs at MVP -- the userinfo endpoint
is enough for the OIDC clients we currently support (Anthropic
directory, Open WebUI). When/if we add JWT id_tokens, this
payload will pick up ``id_token_signing_alg_values_supported``
and ``jwks_uri``.

## Response `200`

Successful Response

- unknown

---

[API](https://skmtc.dev/bitpoort/apis/bitpoort-api.md) · [All operations](https://skmtc.dev/bitpoort/apis/bitpoort-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitpoort/apis/bitpoort-api/revisions/1a51d8566777?raw)