Baker Hughes · OAuth Scopes

Baker Hughes OAuth Scopes

OAuth 2.0 probed

Baker Hughes 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.

Energy TechnologyIndustrial IoTOil and GasAsset Performance ManagementDigital EnergyFortune 500

Scopes: 0 Flows: Method: probed

Scopes (0)

Baker Hughes 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_supported read verbatim from the Keycloak realm's OIDC discovery document. Baker Hughes publishes no scope reference page, so descriptions are limited to what the OIDC Core spec defines (openid/profile/email) and what the scope NAME says for the two custom ones; nothing about what tenant-scope or abac_scope grants is asserted.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-17'
method: probed
source: https://auth-developer.bakerhughes.com/auth/realms/dedicated/.well-known/openid-configuration
provider: Baker Hughes
providerId: baker-hughes
issuer: https://auth-developer.bakerhughes.com/auth/realms/dedicated
docs: null
note: scopes_supported read verbatim from the Keycloak realm's OIDC discovery document. Baker Hughes publishes no
  scope reference page, so descriptions are limited to what the OIDC Core spec defines (openid/profile/email) and
  what the scope NAME says for the two custom ones; nothing about what tenant-scope or abac_scope grants is asserted.
scopes:
- name: openid
  description: OpenID Connect authentication request (OIDC Core 3.1.2.1).
  standard: true
- name: profile
  description: Standard OIDC profile claims (name, family_name, given_name, ...).
  standard: true
- name: email
  description: Standard OIDC email + email_verified claims.
  standard: true
- name: tenant-scope
  description: Custom realm scope. Name suggests tenant selection for the multi-tenant Cordant platform; semantics
    not published.
  standard: false
- name: abac_scope
  description: Custom realm scope. Name suggests attribute-based access control claims; semantics not published.
  standard: false
observed_requests:
- client_id: app-cdp
  scope: openid profile email
  context: developer.bakerhughes.com sign-in

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/baker-hughes-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.