VEIR · OAuth Scopes

VEIR OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://veir.com/oauth/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.

CompanyEnergyElectricityData CentersInfrastructureSuperconductorsContent

Scopes: 3 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://veir.com/oauth/authorize

Token URL
https://veir.com/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (3)

Scope	Description	Flows
openid	OpenID Connect subject identifier. Declared in scopes_supported.	authorizationCode
profile	Basic profile claims. Declared in scopes_supported.	authorizationCode
read	Read access. Declared in scopes_supported; the resource it reads is not documented publicly.	authorizationCode, clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-05'
method: searched
source: https://veir.com/.well-known/openid-configuration
docs: null
schemes:
- name: OpenIDConnect
  source: well-known/veir-openid-configuration.json
  issuer: https://veir.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://veir.com/oauth/authorize
    tokenUrl: https://veir.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://veir.com/oauth/token
scopes:
- scope: openid
  description: OpenID Connect subject identifier. Declared in scopes_supported.
  flows: [authorizationCode]
  sources: [well-known/veir-openid-configuration.json, well-known/veir-oauth-protected-resource.json]
- scope: profile
  description: Basic profile claims. Declared in scopes_supported.
  flows: [authorizationCode]
  sources: [well-known/veir-openid-configuration.json, well-known/veir-oauth-protected-resource.json]
- scope: read
  description: Read access. Declared in scopes_supported; the resource it reads is not documented publicly.
  flows: [authorizationCode, clientCredentials]
  sources: [well-known/veir-openid-configuration.json, well-known/veir-oauth-protected-resource.json]
caveats:
- >-
  These three scopes are the provider's own published scopes_supported values, recorded verbatim.
  VEIR publishes no scopes/permissions reference page, and the authorization and token endpoints
  the discovery document names both returned 404 on 2026-08-05, so no scope could be exercised.
x-evidence:
  fetched: '2026-08-05'
  url: https://veir.com/.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/veir-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.