Binske · OAuth Scopes

Binske OAuth Scopes

OAuth 2.0 probed

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

CannabisConsumer Packaged GoodsDirect to ConsumerE-CommerceRetailShopifyAgent CommerceUCPMCPStorefront
Scopes: 0 Flows: Method: probed

Scopes (0)

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

Scopes are advertised by the Shopify customer-account authorization server that binske's storefront delegates to via RFC 9728 protected-resource metadata. binske publishes no scope reference of its own; these are read verbatim from `scopes_supported` in the RFC 8414 metadata document.

📄 Provider scope reference:

Source

OAuth Scopes

binske-scopes.yml Raw ↑ 
generated: '2026-08-07'
method: probed
source: https://shopbinske.com/.well-known/oauth-authorization-server
authorization_server: https://shopify.com/authentication/64216269035
protected_resource: https://shopbinske.com
note: >-
  Scopes are advertised by the Shopify customer-account authorization server that
  binske's storefront delegates to via RFC 9728 protected-resource metadata.
  binske publishes no scope reference of its own; these are read verbatim from
  `scopes_supported` in the RFC 8414 metadata document.
scopes:
- name: openid
  description: OpenID Connect — request an id_token identifying the buyer.
  standard: true
- name: email
  description: Release the buyer's email address and email_verified claim.
  standard: true
- name: customer-account-api:full
  description: Full access to the Shopify Customer Account API for the signed-in buyer.
  standard: false
- name: customer-account-mcp-api:full
  description: >-
    Full access to the Customer Account MCP API for the signed-in buyer — the
    authenticated counterpart to the anonymous UCP shopping MCP endpoint.
  standard: false
granularity: coarse
x-observation: >-
  Both non-standard scopes are `:full`. There is no read/write split and no
  per-resource scope, so an agent granted buyer access on this storefront holds
  the whole customer-account surface.
x-evidence:
  fetched: '2026-08-07'
  probes:
  - url: https://shopbinske.com/.well-known/oauth-authorization-server
    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/binske-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.