Noded AI · OAuth Scopes

Noded AI OAuth Scopes

OAuth 2.0 searched

Noded AI publishes 4 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Noded AI API on a user’s behalf.

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.

CompanyAi MlCustomer SuccessCustomer DataChurnRetentionRevenue OperationsSoftware-as-a-ServiceAI AgentsGraphQLMCPagent-nativeCustomer Context Graph
Scopes: 4 Flows: Method: searched

Scopes (4)

ScopeDescriptionFlows
openid Requests an ID token for the signed-in Noded user.
profile Basic profile claims for the signed-in Noded user.
email Email claim for the signed-in Noded user.
offline_access Refresh token so the SDK can silently refresh without re-prompting.

Source

OAuth Scopes

noded-ai-scopes.yml Raw ↑
generated: '2026-08-13'
method: searched
source: https://www.getnoded.ai/developers
docs: https://www.getnoded.ai/developers
note: >-
  Noded publishes no scope/permission reference page. The only scopes visible in public are the
  OIDC scopes the first-party SDK requests by default against the Noded Auth0 tenant — these are
  standard OpenID Connect scopes, not Noded-specific API permissions. Authorization in Noded is
  expressed as tenant + per-user permissions enforced server-side (and, on the MCP layer, as
  per-agent tool scoping), not as named OAuth scopes a developer selects. Derivation from an
  OpenAPI was not possible: Noded publishes no OpenAPI. Recorded as an honest partial.
issuer: https://login.getnoded.ai/
audience: provisioned per customer (the Noded API audience)
scopes:
  - scope: openid
    standard: true
    spec: OpenID Connect Core 1.0
    description: Requests an ID token for the signed-in Noded user.
  - scope: profile
    standard: true
    spec: OpenID Connect Core 1.0
    description: Basic profile claims for the signed-in Noded user.
  - scope: email
    standard: true
    spec: OpenID Connect Core 1.0
    description: Email claim for the signed-in Noded user.
  - scope: offline_access
    standard: true
    spec: OpenID Connect Core 1.0
    description: Refresh token so the SDK can silently refresh without re-prompting.
scope_count: 4
provider_specific_scope_count: 0
authorization_model: >-
  Tenant-scoped, permission-aware. Every call runs as the signed-in user and the API enforces
  that user's permissions; the MCP layer additionally provisions tools per agent identity, so
  what an agent may see is scoped to the agent rather than to the organization.

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/noded-ai-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.

A second provider on the same verified email joins the account you already have.