AiFi · OAuth Scopes

AiFi OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://auth.aifi.com/realms/aifi/protocol/openid-connect/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.

CompanyComputer-VisionRetailAutonomous CheckoutSpatial IntelligenceArtificial IntelligenceAnalyticsIdentityFraud PreventionPoint-of-Sale

Scopes: 10 Flows: authorizationCode, clientCredentials, deviceCode Method: probed

OAuth endpoints

Authorization URL
https://auth.aifi.com/realms/aifi/protocol/openid-connect/auth

Token URL
https://auth.aifi.com/realms/aifi/protocol/openid-connect/token

Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (10)

Scope	Description	Flows
openid	Required OpenID Connect scope; requests an ID token.
profile	Basic profile claims (name, given_name, family_name, preferred_username).
email	Email address and email_verified claim.
address	Physical address claim.
phone	Phone number claims.
roles	Realm and client role mappings for the subject.
offline_access	Issues a refresh token usable while the user is offline.
acr	Authentication context class reference; carries the acr claim.
web-origins	Keycloak scope that adds allowed CORS web origins to the token.
microprofile-jwt	MicroProfile JWT claim set (upn, groups) for Java service consumers.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-06'
method: probed
source: https://auth.aifi.com/realms/aifi/.well-known/openid-configuration
docs: null
scope: identity-provider-realm
note: >-
  These are the scopes advertised by AiFi's Keycloak realm `aifi` in its OIDC
  discovery document — the identity provider in front of docs.aifi.com and
  partners.aifi.com. They are the standard OIDC/Keycloak realm scopes, NOT
  application scopes for the OASIS retailer APIs. AiFi publishes no public scope or
  permission reference, and no OASIS API scope is asserted here. Recorded because
  they are the only authorization surface AiFi exposes anonymously.
schemes:
- name: aifi-keycloak
  source: well-known/aifi-openid-configuration.json
  issuer: https://auth.aifi.com/realms/aifi
  flows:
  - flow: authorizationCode
    authorizationUrl: https://auth.aifi.com/realms/aifi/protocol/openid-connect/auth
    tokenUrl: https://auth.aifi.com/realms/aifi/protocol/openid-connect/token
  - flow: clientCredentials
    tokenUrl: https://auth.aifi.com/realms/aifi/protocol/openid-connect/token
  - flow: deviceCode
    deviceAuthorizationUrl: https://auth.aifi.com/realms/aifi/protocol/openid-connect/auth/device
    tokenUrl: https://auth.aifi.com/realms/aifi/protocol/openid-connect/token
scopes:
- scope: openid
  description: Required OpenID Connect scope; requests an ID token.
  sources: [well-known/aifi-openid-configuration.json]
- scope: profile
  description: Basic profile claims (name, given_name, family_name, preferred_username).
  sources: [well-known/aifi-openid-configuration.json]
- scope: email
  description: Email address and email_verified claim.
  sources: [well-known/aifi-openid-configuration.json]
- scope: address
  description: Physical address claim.
  sources: [well-known/aifi-openid-configuration.json]
- scope: phone
  description: Phone number claims.
  sources: [well-known/aifi-openid-configuration.json]
- scope: roles
  description: Realm and client role mappings for the subject.
  sources: [well-known/aifi-openid-configuration.json]
- scope: offline_access
  description: Issues a refresh token usable while the user is offline.
  sources: [well-known/aifi-openid-configuration.json]
- scope: acr
  description: Authentication context class reference; carries the acr claim.
  sources: [well-known/aifi-openid-configuration.json]
- scope: web-origins
  description: Keycloak scope that adds allowed CORS web origins to the token.
  sources: [well-known/aifi-openid-configuration.json]
- scope: microprofile-jwt
  description: MicroProfile JWT claim set (upn, groups) for Java service consumers.
  sources: [well-known/aifi-openid-configuration.json]
x-evidence:
  fetched: '2026-08-06'
  url: https://auth.aifi.com/realms/aifi/.well-known/openid-configuration
  http_status: 200

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/aifi-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.