Evertune · Authentication Profile

Evertune Authentication

Authentication

Evertune secures its APIs with openIdConnect and oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, implicit, clientCredentials, deviceCode, refreshToken, tokenExchange, jwtBearer, and password flow(s).

CompanyGenerative Engine OptimizationAI SearchBrand MonitoringMarketing IntelligenceAI VisibilityAnalyticsArtificial Intelligence
Methods: openIdConnect, oauth2 Schemes: 1 OAuth flows: authorizationCode, implicit, clientCredentials, deviceCode, refreshToken, tokenExchange, jwtBearer, password API key in:

Security Schemes

Auth0OIDC openIdConnect

Source

Authentication Profile

evertune-authentication.yml Raw ↑ 
generated: '2026-08-13'
method: probed
source: https://auth.evertune.ai/.well-known/openid-configuration
scope_of_this_artifact: >-
  This profile describes the identity surface Evertune actually publishes: the
  Auth0 tenant it runs on its own domain (auth.evertune.ai) to sign users in to
  the Evertune web application at app.evertune.ai. Evertune publishes NO
  first-party developer API, so this is NOT an API authorization contract --
  there is no documented developer client registration, no API audience, no
  documented API scopes, and no published token-issuance guidance for
  third-party integrators. It is recorded because the discovery document is
  real, anonymous, machine-readable, and served by Evertune.
summary:
  types:
  - openIdConnect
  - oauth2
  api_key_in: []
  oauth2_flows:
  - authorizationCode
  - implicit
  - clientCredentials
  - deviceCode
  - refreshToken
  - tokenExchange
  - jwtBearer
  - password
schemes:
- name: Auth0OIDC
  type: openIdConnect
  openIdConnectUrl: https://auth.evertune.ai/.well-known/openid-configuration
  issuer: https://auth.evertune.ai/
  provider: Auth0 (custom domain on evertune.ai)
  sources:
  - well-known/evertune-openid-configuration.json
  endpoints:
    authorization: https://auth.evertune.ai/authorize
    token: https://auth.evertune.ai/oauth/token
    userinfo: https://auth.evertune.ai/userinfo
    jwks: https://auth.evertune.ai/.well-known/jwks.json
    registration: https://auth.evertune.ai/oidc/register
    revocation: https://auth.evertune.ai/oauth/revoke
    device_authorization: https://auth.evertune.ai/oauth/device/code
    end_session: https://auth.evertune.ai/oidc/logout
    backchannel_authentication: https://auth.evertune.ai/bc-authorize
    mfa_challenge: https://auth.evertune.ai/mfa/challenge
  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
  - 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
  - urn:ietf:params:oauth:grant-type:jwt-bearer
  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
  mfa: true
x-evidence:
- url: https://auth.evertune.ai/.well-known/openid-configuration
  http_status: 200
  content_type: application/json
  fetched: '2026-08-13'
- url: https://auth.evertune.ai/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/json
  fetched: '2026-08-13'
- url: https://auth.evertune.ai/.well-known/jwks.json
  http_status: 200
  content_type: application/json
  fetched: '2026-08-13'