CarMD · OAuth Scopes

CarMD OAuth Scopes

OAuth 2.0 probed

CarMD 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.

AutomobilesCarsDiagnosticsVehiclesAutomotiveOBD-IIAgentic CommerceMCPE-Commerce
Scopes: 0 Flows: Method: probed

Scopes (0)

CarMD 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-27'
method: probed
source: https://carmd.com/.well-known/openid-configuration
provider: CarMD
providerId: carmd
description: >-
  OAuth 2.0 / OpenID Connect scopes CarMD's domain advertises. These come from the customer-accounts
  authorization server discovery document served at carmd.com/.well-known/openid-configuration (identical
  body is served at /.well-known/oauth-authorization-server). The authorization server is Shopify's
  customer-accounts issuer for CarMD's store (issuer https://shopify.com/authentication/93440671876); the
  scopes govern shopper identity and the customer-account APIs for the CarMD storefront. The CarMD Vehicle
  API on api.carmd.com does not use OAuth — and could not be probed at all, because that host refused
  connections.
authorization_server:
  issuer: https://shopify.com/authentication/93440671876
  authorization_endpoint: https://shopify.com/authentication/93440671876/oauth/authorize
  token_endpoint: https://shopify.com/authentication/93440671876/oauth/token
  jwks_uri: https://shopify.com/authentication/93440671876/.well-known/jwks.json
  end_session_endpoint: https://shopify.com/authentication/93440671876/logout
  grant_types_supported:
    - authorization_code
    - refresh_token
    - 'urn:ietf:params:oauth:grant-type:jwt-bearer'
  response_types_supported:
    - code
  code_challenge_methods_supported:
    - S256
  token_endpoint_auth_methods_supported:
    - client_secret_basic
    - client_secret_post
  id_token_signing_alg_values_supported:
    - RS256
scope_count: 4
scopes:
  - name: openid
    description: Standard OpenID Connect scope; requests an ID token identifying the shopper.
  - name: email
    description: Releases the shopper's email address and email_verified claim.
  - name: 'customer-account-api:full'
    description: Full access to the customer-account API for the authenticated shopper.
  - name: 'customer-account-mcp-api:full'
    description: >-
      Full access to the customer-account MCP API for the authenticated shopper — the authenticated
      counterpart to the anonymous UCP commerce MCP endpoint at https://carmd.com/api/ucp/mcp.
claims_supported: [iss, sub, aud, exp, iat, nonce, sid, email, email_verified]
docs: null
docs_note: CarMD publishes no scope reference page of its own; the scope list is machine-read from its discovery document.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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