VEIR · Authentication Profile

Veir Authentication

Authentication

VEIR secures its APIs with openIdConnect and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

CompanyEnergyElectricityData CentersInfrastructureSuperconductorsContent

Methods: openIdConnect, oauth2 Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

OpenIDConnect openIdConnect

OAuth2 oauth2

· flows: authorizationCode, clientCredentials

Source

Authentication Profile

generated: '2026-08-05'
method: searched
source: https://veir.com/.well-known/openid-configuration
docs: null
summary:
  types: [openIdConnect, oauth2]
  api_key_in: []
  oauth2_flows: [authorizationCode, clientCredentials]
  status: advertised-but-unresolvable
schemes:
- name: OpenIDConnect
  type: openIdConnect
  openIdConnectUrl: https://veir.com/.well-known/openid-configuration
  issuer: https://veir.com
  id_token_signing_alg_values_supported: [RS256]
  subject_types_supported: [public]
  response_types_supported: [code]
  sources: [well-known/veir-openid-configuration.json]
- name: OAuth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://veir.com/oauth/authorize
    tokenUrl: https://veir.com/oauth/token
    scopes:
      openid: OpenID Connect subject identifier
      profile: Basic profile claims
      read: Read access
  - flow: clientCredentials
    tokenUrl: https://veir.com/oauth/token
    scopes:
      read: Read access
  sources: [well-known/veir-openid-configuration.json]
protected_resource:
  source: well-known/veir-oauth-protected-resource.json
  resource: https://veir.com
  authorization_servers: [https://veir.com]
  scopes_supported: [openid, profile, read]
caveats:
- >-
  VEIR publishes a syntactically valid OIDC discovery document, but none of the endpoints it
  advertises resolve. Probed 2026-08-05: /oauth/authorize returned 404, /oauth/token returned
  404, and the advertised jwks_uri /.well-known/jwks.json returned 404. The metadata is
  present; the authorization server behind it is not reachable anonymously.
- >-
  No developer registration, client-credential issuance, or token documentation was found
  anywhere on veir.com. Nothing on the public site explains what these scopes grant access to.
x-evidence:
  fetched: '2026-08-05'
  probes:
  - url: https://veir.com/.well-known/openid-configuration
    status: 200
  - url: https://veir.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://veir.com/oauth/authorize
    status: 404
  - url: https://veir.com/oauth/token
    status: 404
  - url: https://veir.com/.well-known/jwks.json
    status: 404

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/veir-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.