Aquant · OAuth Scopes

Aquant OAuth Scopes

OAuth 2.0 probed

Aquant publishes 7 OAuth 2.0 scopes via the authorizationCode, implicit, deviceCode, password, and refreshToken flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Aquant API on a user’s behalf.

Tokens are issued from https://login.aquant.ai/oauth2/v1/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyArtificial IntelligenceAgentsField ServiceService ManagementManufacturingMedical DevicesIndustrial EquipmentKnowledge ManagementVoice AIModel Context ProtocolPredictive Maintenance

Scopes: 7 Flows: authorizationCode, implicit, deviceCode, password, refreshToken Method: probed

OAuth endpoints

Authorization URL
https://login.aquant.ai/oauth2/v1/authorize

Token URL
https://login.aquant.ai/oauth2/v1/token

Flows
authorizationCodeimplicitdeviceCodepasswordrefreshToken

Scopes (7)

Scope	Description	Flows
openid	Required to obtain an ID token; identifies the request as an OpenID Connect request.	authorizationCode, implicit, deviceCode, password
profile	Access to default profile claims (name, family_name, given_name, locale, zoneinfo, updated_at).	authorizationCode, implicit, deviceCode, password
email	Access to the email and email_verified claims.	authorizationCode, implicit, deviceCode, password
address	Access to the address claim.	authorizationCode, implicit, deviceCode, password
phone	Access to the phone_number and phone_number_verified claims.	authorizationCode, implicit, deviceCode, password
offline_access	Issues a refresh token so the client can renew access without re-prompting the user.	authorizationCode, deviceCode, password
groups	Includes the user's group memberships as a claim — the Okta-specific scope Aquant uses for role/tenant assignment.	authorizationCode, implicit, deviceCode, password

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-31'
method: probed
source: https://login.aquant.ai/.well-known/openid-configuration
note: >-
  Neither Aquant OpenAPI declares an oauth2 security scheme, so the mechanical derive pass
  (0-working/derive-oauth-scopes.py) returns nothing. The only OAuth/OIDC surface Aquant
  operates is its Okta customer-identity tenant at login.aquant.ai, which is used for human
  sign-in to the Aquant platform rather than for API authorization. The scopes below are the
  standard OIDC set advertised by that discovery document — they are recorded because they are
  real and anonymously discoverable, NOT because they authorize the MCP or ACP APIs.
applies_to: platform sign-in (login.aquant.ai) — not aquant:mcp-server or aquant:acp-voiceai
schemes:
- name: aquant-okta
  type: openIdConnect
  issuer: https://login.aquant.ai
  source: well-known/aquant-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.aquant.ai/oauth2/v1/authorize
    tokenUrl: https://login.aquant.ai/oauth2/v1/token
    pkce: S256
  - flow: implicit
    authorizationUrl: https://login.aquant.ai/oauth2/v1/authorize
  - flow: deviceCode
    deviceAuthorizationUrl: https://login.aquant.ai/oauth2/v1/device/authorize
    tokenUrl: https://login.aquant.ai/oauth2/v1/token
  - flow: password
    tokenUrl: https://login.aquant.ai/oauth2/v1/token
  - flow: refreshToken
    tokenUrl: https://login.aquant.ai/oauth2/v1/token
scopes:
- scope: openid
  description: Required to obtain an ID token; identifies the request as an OpenID Connect request.
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: profile
  description: Access to default profile claims (name, family_name, given_name, locale, zoneinfo, updated_at).
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: email
  description: Access to the email and email_verified claims.
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: address
  description: Access to the address claim.
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: phone
  description: Access to the phone_number and phone_number_verified claims.
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: offline_access
  description: Issues a refresh token so the client can renew access without re-prompting the user.
  flows: [authorizationCode, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
- scope: groups
  description: Includes the user's group memberships as a claim — the Okta-specific scope Aquant uses for role/tenant assignment.
  flows: [authorizationCode, implicit, deviceCode, password]
  sources: [well-known/aquant-openid-configuration.json]
gaps:
- >-
  No API-level scope surface exists. The MCP server and the ACP/VoiceAI API authorize by
  API key/secret and tenant_id, with no scope vocabulary published for either.