Agilitas Sports · OAuth Scopes

Agilitas Sports OAuth Scopes

OAuth 2.0 probed

Agilitas Sports uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

CompanyCommerceE-CommerceRetailSportswearFootwearAthleisureManufacturingAgentic CommerceUniversal Commerce ProtocolModel Context ProtocolShopifyIndia

Scopes: 0 Flows: Method: probed

Scopes (0)

Agilitas Sports implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

No client registration endpoint is published and no public client_id is documented, so these scopes are not requestable by a third-party integrator today. They are recorded as probed fact, not as an available developer surface.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-12'
method: probed
source: https://agilitas.com/.well-known/openid-configuration (HTTP 200, fetched 2026-09-12)
name: Agilitas OAuth scopes
slug: agilitassports
docs: null
docs_note: >-
  Agilitas publishes no scope reference page of its own. The scope list below is read verbatim from
  the scopes_supported array of the OIDC discovery document served at the Agilitas domain; the
  descriptions are Shopify customer-account semantics, marked as such.

authorization_server: https://shopify.com/authentication/99796025642
operator: Shopify (customer-account identity provider for shop 99796025642)
applies_to: >-
  Shopper sign-in to a customer account. NOT the anonymous UCP/MCP commerce surface, which requires
  no token at all — see authentication/agilitassports-authentication.yml.

scope_count: 4
scopes:
- name: openid
  standard: OpenID Connect Core
  description: Request an ID token identifying the signed-in shopper.
  source: discovery
- name: email
  standard: OpenID Connect Core
  description: Release the shopper's email and email_verified claims.
  source: discovery
- name: customer-account-api:full
  standard: Shopify
  description: >-
    Full access to the Shopify Customer Account API on behalf of the signed-in shopper (orders,
    addresses, profile). Semantics are Shopify's; Agilitas documents none of it.
  source: discovery
- name: customer-account-mcp-api:full
  standard: Shopify
  description: >-
    Full access to the authenticated Shopify customer-account MCP API on behalf of the signed-in
    shopper. Not documented or advertised anywhere on an Agilitas host; listed here only because the
    discovery document served on agilitas.com names it.
  source: discovery

claims_supported: [iss, sub, aud, exp, iat, nonce, sid, email, email_verified]
code_challenge_methods_supported: [S256]
response_types_supported: [code]

note: >-
  No client registration endpoint is published and no public client_id is documented, so these
  scopes are not requestable by a third-party integrator today. They are recorded as probed fact,
  not as an available developer surface.

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/agilitassports-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.