generated: '2026-08-13'
method: searched
source: openapi/hilberts-ai-program-api-openapi.yml + https://hilbert-app.us.auth0.com/.well-known/openid-configuration
summary:
  types:
  - apiKey
  - http
  - oauth2
  - openIdConnect
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  - clientCredentials
  - deviceCode
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/hilberts-ai-program-api-openapi.yml
- name: apiKey
  type: apiKey
  in: header
  parameter: x-api-key
  description: API key for server to server authentication
  sources:
  - openapi/hilberts-ai-program-api-openapi.yml
- name: auth0-oidc
  type: openIdConnect
  openIdConnectUrl: https://hilbert-app.us.auth0.com/.well-known/openid-configuration
  issuer: https://hilbert-app.us.auth0.com/
  audience: https://app-api.hilberts.ai
  token_endpoint: https://hilbert-app.us.auth0.com/oauth/token
  jwks_uri: https://hilbert-app.us.auth0.com/.well-known/jwks.json
  id_token_signing_alg:
  - HS256
  - RS256
  - PS256
  token_endpoint_auth_methods:
  - client_secret_basic
  - client_secret_post
  - private_key_jwt
  - none
  pkce: true
  sources:
  - https://hilbert-app.us.auth0.com/.well-known/openid-configuration
  note: Issuer of the bearerAuth JWT declared in the OpenAPI. Not declared as a securityScheme
    in the spec; established by probe.
docs: null
note: The two schemes below are declared verbatim in the provider's own OpenAPI. The
  bearer JWT is issued by Hilbert's Auth0 tenant hilbert-app.us.auth0.com (audience
  https://app-api.hilberts.ai), confirmed from the app.hilberts.ai JavaScript bundle
  and from the tenant's live OIDC discovery document. Hilbert publishes no authentication
  guide, no key-issuance page and no developer portal, so how an x-api-key is obtained
  is not documented anywhere public.
scopes: scopes/hilberts-ai-scopes.yml
x-evidence:
  fetched: '2026-08-13'
  url: https://hilbert-app.us.auth0.com/.well-known/openid-configuration
  http_status: 200