A-Mark Precious Metals · OAuth Scopes

A-Mark Precious Metals OAuth Scopes

OAuth 2.0 probed

A-Mark Precious Metals 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.

Precious MetalsTradingWholesaleGoldSilverBullionFinance
Scopes: 0 Flows: Method: probed

Scopes (0)

A-Mark Precious Metals 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

a-mark-precious-metals-scopes.yml Raw ↑ 
generated: '2026-08-29'
method: probed
source: https://portal.amark.com/.well-known/openid-configuration
provider: A-Mark Precious Metals
providerId: a-mark-precious-metals
description: >-
  Scopes advertised by the A-Mark Trading Portal's OAuth 2.0 / OIDC discovery document.
  These are the standard OIDC scope set as emitted by the portal's identity server; A-Mark
  publishes no scope reference page and no product-specific scopes (no trading, pricing,
  order or inventory scopes are advertised). Descriptions below are the RFC/OIDC-standard
  meanings of each scope name, not A-Mark prose — the provider documents none.
docs: null
docs_note: No public scopes/permissions reference page exists on amark.com or gold.com.
schemes:
  - name: OAuth2
    token_url: https://portal.amark.com/connect/token
    source: https://portal.amark.com/.well-known/openid-configuration
scope_count: 6
scopes:
  - name: openid
    standard: OpenID Connect Core 1.0
    description: Requests an OpenID Connect authentication response.
  - name: email
    standard: OpenID Connect Core 1.0
    description: Requests the email and email_verified claims.
  - name: phone
    standard: OpenID Connect Core 1.0
    description: Requests the phone_number and phone_number_verified claims.
  - name: profile
    standard: OpenID Connect Core 1.0
    description: Requests the default profile claims.
  - name: offline_access
    standard: OpenID Connect Core 1.0
    description: Requests a refresh token so the client can act without the user present.
  - name: roles
    standard: non-standard (identity-server convention)
    description: >-
      Requests the caller's portal role assignments. A-Mark does not document what roles
      exist or what each one authorizes.
x-evidence:
  - url: https://portal.amark.com/.well-known/openid-configuration
    http_status: 200
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/a-mark-precious-metals-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.