openapi: 3.2.0 info: title: AI Gateway MCP Server .well Known API description: Universal MCP Gateway with OAuth integration - Modern Architecture version: 2.0.3290 tags: - name: .well Known paths: /.well-known/oauth-authorization-server: get: summary: Oauth Authorization Server description: OAuth 2.0 Authorization Server Metadata operationId: oauth_authorization_server__well_known_oauth_authorization_server_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/openid-configuration: get: summary: Openid Configuration description: 'OpenID Provider Metadata (OpenID Connect Discovery 1.0). The scopes the gateway advertises include ``openid``, so a relying party such as ChatGPT reads THIS document after the token exchange to find the UserInfo endpoint. Without it the party treats the connection as failed and starts the authorize flow over.' operationId: openid_configuration__well_known_openid_configuration_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/jwks.json: get: summary: Openid Jwks description: The key set behind ``jwks_uri`` — empty, the gateway signs no ID Token. operationId: openid_jwks__well_known_jwks_json_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/oauth-authorization-server/sse: get: summary: Oauth Authorization Server Sse description: OAuth 2.0 Authorization Server Metadata for SSE endpoint operationId: oauth_authorization_server_sse__well_known_oauth_authorization_server_sse_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/oauth-authorization-server/mcp: get: summary: Oauth Authorization Server Mcp description: OAuth 2.0 Authorization Server Metadata for MCP endpoint operationId: oauth_authorization_server_mcp__well_known_oauth_authorization_server_mcp_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/oauth-protected-resource: get: summary: Oauth Protected Resource description: 'OAuth 2.0 Protected Resource Metadata (default: /mcp for ChatGPT Agent compatibility)' operationId: oauth_protected_resource__well_known_oauth_protected_resource_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/oauth-protected-resource/sse: get: summary: Oauth Protected Resource Sse description: OAuth 2.0 Protected Resource Metadata for SSE endpoint operationId: oauth_protected_resource_sse__well_known_oauth_protected_resource_sse_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/client-vault/mcp: post: summary: Client Vault Resolve description: 'Vault references: a local vault fetches the values behind PII keys. Accepts the vault''s own secret only, never an OAuth token. Spec and status codes: src/security/client_vault.py.' operationId: client_vault_resolve__well_known_client_vault_mcp_post responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/oauth-protected-resource/mcp: get: summary: Oauth Protected Resource Mcp description: OAuth 2.0 Protected Resource Metadata for MCP endpoint operationId: oauth_protected_resource_mcp__well_known_oauth_protected_resource_mcp_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/mcp-server-card: get: summary: Mcp Server Card description: MCP Server Card at the normative SEP-2127 well-known path. operationId: mcp_server_card__well_known_mcp_server_card_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known /.well-known/mcp/server-card.json: get: summary: Mcp Server Card Json Alias description: 'Alias for the `.json` form used by earlier (SEP-1649) tooling. The SEP-2127 path naming is not yet settled; serving both forms keeps discovery working regardless of which path a client probes.' operationId: mcp_server_card_json_alias__well_known_mcp_server_card_json_get responses: '200': description: Successful Response content: application/json: schema: {} tags: - .well Known