---
title: "Oauth Metadata Root"
method: GET
path: "/.well-known/oauth-authorization-server/{path}"
---

# Oauth Metadata Root

`GET /.well-known/oauth-authorization-server/{path}`

## Request

- Base URL: `https://api.humwork.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.humwork.ai/.well-known/oauth-authorization-server/{path}`
- Auth: none declared
- TypeScript: <https://skmtc.dev/humwork/apis/humwork-ai/docs/.well-known/oauth-authorization-server/:path/get.ts> (a function with typed inputs; its response is checked against the schema)

OAuth 2.0 Authorization Server Metadata (RFC 8414).

Pure OAuth 2.0 only — no OIDC fields. We previously included
subject_types_supported / op_policy_uri / op_tos_uri (all OIDC
Discovery fields), which signaled to OpenAI's MCP App Directory
scanner that we were an OpenID Connect server. The scanner then
fetched /.well-known/openid-configuration, got a 404, and
classified us as 'unsupported OAuth config type' (visible in
Render logs around 2026-05-07 03:28 UTC: 3x consecutive
openid-configuration 404s during a failed scan).

## Path parameters

- `path` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/humwork/apis/humwork-ai.md) - [All operations](https://skmtc.dev/humwork/apis/humwork-ai/llms.txt) - [OpenAPI document](https://skmtc.dev/humwork/apis/humwork-ai/revisions/38d9dc5f27e6?raw)