Kymeta · OAuth Scopes

Kymeta OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://access.kymeta.io/connect/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.

SatelliteSatellite CommunicationsConnectivityTelecommunicationsNetworkingAntennasMetamaterialsAerospace and DefenseMaritimeRemote MonitoringHardware

Scopes: 11 Flows: authorizationCode, clientCredentials, deviceCode Method: probed

OAuth endpoints

Authorization URL
https://access.kymeta.io/connect/authorize

Token URL
https://access.kymeta.io/connect/token

Flows
authorizationCodeclientCredentialsdeviceCode

Scopes (11)

Scope	Description	Flows
openid	Standard OpenID Connect scope; requests an ID token.
profile	Standard OpenID Connect scope; profile claims.
email	Standard OpenID Connect scope; email and email_verified claims.
offline_access	Standard OpenID Connect scope; issues a refresh token.
partners-api
enterprisebroker
ksn
kpp
grapevine
live-stream
absorblms

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-23'
method: probed
source: https://access.kymeta.io/.well-known/openid-configuration
note: >-
  The eleven scopes below are published verbatim in scopes_supported by Kymeta's own identity
  provider. Kymeta publishes no scope/permission reference page, so the descriptions are limited
  to what can be stated from first-party evidence — the scope name itself and, where corroborated,
  the matching service name in the api.kymeta.io /status roll-up. Nothing here is inferred beyond
  that; scopes with no corroborating evidence are marked description: null rather than guessed.
docs: null
docs_note: No public scopes or permissions reference is published by Kymeta.
schemes:
  - name: KymetaAccessOIDC
    source: well-known/kymeta-access-openid-configuration.json
    issuer: https://access.kymeta.io
    flows:
      - flow: authorizationCode
        authorizationUrl: https://access.kymeta.io/connect/authorize
        tokenUrl: https://access.kymeta.io/connect/token
      - flow: clientCredentials
        tokenUrl: https://access.kymeta.io/connect/token
      - flow: deviceCode
        deviceAuthorizationUrl: https://access.kymeta.io/connect/deviceauthorization
        tokenUrl: https://access.kymeta.io/connect/token
scopes:
  - scope: openid
    description: Standard OpenID Connect scope; requests an ID token.
    standard: oidc-core
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: profile
    description: Standard OpenID Connect scope; profile claims.
    standard: oidc-core
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: email
    description: Standard OpenID Connect scope; email and email_verified claims.
    standard: oidc-core
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: offline_access
    description: Standard OpenID Connect scope; issues a refresh token.
    standard: oidc-core
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: partners-api
    description: null
    description_note: >-
      Named partner API scope. This is the clearest published evidence that Kymeta operates a
      partner-facing API, but no reference documents what it grants.
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: enterprisebroker
    description: null
    description_note: >-
      Corresponds to the enterpriseBroker service reported by https://api.kymeta.io/status.
    sources: [well-known/kymeta-access-openid-configuration.json, 'probe:https://api.kymeta.io/status']
  - scope: ksn
    description: null
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: kpp
    description: null
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: grapevine
    description: null
    description_note: >-
      Corresponds to https://grapevine.kymeta.io, which redirects into the access.kymeta.io
      sign-in flow (observed 200 after redirect to login.microsoftonline.com with
      redirect_uri https://access.kymeta.io/signin-microsoft).
    sources: [well-known/kymeta-access-openid-configuration.json, 'probe:https://grapevine.kymeta.io/']
  - scope: live-stream
    description: null
    sources: [well-known/kymeta-access-openid-configuration.json]
  - scope: absorblms
    description: null
    description_note: >-
      Federation scope for the Absorb LMS tenant at academy.kymeta.io (vendor-operated).
    sources: [well-known/kymeta-access-openid-configuration.json]

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/kymeta-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.