generated: '2026-07-25'
method: searched
source: https://auth.artificialos.com/.well-known/openid-configuration
docs: https://docs.artificial.io/docs-site/
note: |
  Artificial Labs publishes no OpenAPI, so this profile is not derived from
  securitySchemes — it is read verbatim from the one authentication surface the
  company does expose anonymously: the Auth0 UK tenant that fronts both the
  product documentation (via oauth2-proxy) and, by inference, the platform
  itself. Partner API credentials for Smart Underwriting, Smart Placement and
  Contract Builder are issued out of band under a contract; there is no public
  self-serve key issuance and no documented API-key scheme.
summary:
  types:
  - oauth2
  - openIdConnect
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  - clientCredentials
  - implicit
  - password
  - refreshToken
  - deviceCode
  - tokenExchange
  - jwtBearer
  public_self_serve_signup: false
  credential_issuance: out of band, under partner/customer contract
schemes:
- name: Auth0 OpenID Connect
  type: openIdConnect
  openIdConnectUrl: https://auth.artificialos.com/.well-known/openid-configuration
  issuer: https://auth.artificialos.com/
  tenant: artificial.uk.auth0.com
  sources:
  - well-known/artificial-labs-openid-configuration.json
  endpoints:
    authorization: https://auth.artificialos.com/authorize
    token: https://auth.artificialos.com/oauth/token
    userinfo: https://auth.artificialos.com/userinfo
    jwks: https://auth.artificialos.com/.well-known/jwks.json
    revocation: https://auth.artificialos.com/oauth/revoke
    registration: https://auth.artificialos.com/oidc/register
    device_authorization: https://auth.artificialos.com/oauth/device/code
    backchannel_authentication: https://auth.artificialos.com/bc-authorize
    mfa_challenge: https://auth.artificialos.com/mfa/challenge
    global_token_revocation: https://auth.artificialos.com/oauth/global-token-revocation/connection/{connectionName}
  grant_types_supported:
  - client_credentials
  - authorization_code
  - refresh_token
  - password
  - implicit
  - urn:ietf:params:oauth:grant-type:device_code
  - urn:ietf:params:oauth:grant-type:token-exchange
  - urn:ietf:params:oauth:grant-type:jwt-bearer
  - http://auth0.com/oauth/grant-type/password-realm
  - http://auth0.com/oauth/grant-type/passwordless/otp
  - http://auth0.com/oauth/grant-type/mfa-oob
  - http://auth0.com/oauth/grant-type/mfa-otp
  - http://auth0.com/oauth/grant-type/mfa-recovery-code
  response_types_supported:
  - code
  - token
  - id_token
  - code token
  - code id_token
  - token id_token
  - code token id_token
  token_endpoint_auth_methods_supported:
  - client_secret_basic
  - client_secret_post
  - private_key_jwt
  - none
  code_challenge_methods_supported:
  - S256
  - plain
  id_token_signing_alg_values_supported:
  - HS256
  - RS256
  - PS256
  dpop_signing_alg_values_supported:
  - ES256
  backchannel_logout_supported: true
  mfa: true
observed_clients:
- name: docs.artificial.io (oauth2-proxy)
  client_id: doz61CY73D2YYnTftWiDXl5j31Npm7b7
  flow: authorizationCode
  scope: openid profile email
  redirect_uri: https://docs.artificial.io/oauth2/callback
  entry_point: https://docs.artificial.io/oauth2/start
  note: Observed on the 302 from every gated documentation path. Public client id
    only; no secret is exposed.
gaps:
- No public API-key issuance or API-key documentation.
- No published mTLS / FAPI client-authentication guidance, although private_key_jwt
  and DPoP (ES256) are advertised by the tenant.
- No published domain/product scopes — only standard OIDC scopes (see
  scopes/artificial-labs-scopes.yml).