Authorization-server metadata (RFC 8414)
GET
/.well-known/oauth-authorization-server
const url = 'https://api.aerandil.com/.well-known/oauth-authorization-server';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.aerandil.com/.well-known/oauth-authorization-serverDiscovery document for interactive OAuth 2.1 on this cell — the authorization, token and dynamic-registration endpoints, the scopes on offer, and the PKCE methods required.
Public — no authentication. MCP clients MUST read this document (MCP 2025-06-18 §Server Metadata Discovery) after following the resource_metadata pointer on a 401 from the MCP endpoint. Returns 404 when the cell has no AERANDIL_PUBLIC_BASE_URL: every endpoint here is absolute, and deriving one from the request Host would let a caller point other clients at a host of their choosing.
Responses
Section titled “Responses”Authorization-server metadata.
Media typeapplication/json
object
Examplegenerated
{}This cell publishes no metadata (no public base URL configured).