Notice · OAuth Scopes

Notice OAuth Scopes

OAuth 2.0 probed

Notice 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.

CompanyPrivate MarketsMarket DataFinancial DataInvestingPre-IPOSecondary MarketsValuationsFintechMCP

Scopes: 0 Flows: Method: probed

Scopes (0)

Notice 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-26'
method: probed
source: https://api.stytch.notice.co/.well-known/oauth-authorization-server
also_source:
  - https://api.stytch.notice.co/.well-known/openid-configuration
  - https://api.notice.co/.well-known/oauth-protected-resource
summary: >-
  Every scope below was read from a document Notice serves anonymously, not from a docs page - no
  scope reference is published. Note the divergence between the three documents: the protected
  resource (the MCP endpoint) advertises three scopes, the RFC 8414 authorization-server metadata
  five, and the OIDC discovery document six. The union is recorded, with the source of each.
authorization_server: https://api.stytch.notice.co
protected_resource: https://api.notice.co/mcp
scopes:
  - name: openid
    description: OpenID Connect authentication; issues an ID token.
    declared_in: [protected-resource, authorization-server, openid-configuration]
  - name: profile
    description: Basic profile claims for the authenticated Notice member.
    declared_in: [protected-resource, authorization-server, openid-configuration]
  - name: email
    description: Email address claim for the authenticated Notice member.
    declared_in: [protected-resource, authorization-server, openid-configuration]
  - name: phone
    description: Phone number claim.
    declared_in: [authorization-server, openid-configuration]
  - name: offline_access
    description: Refresh-token issuance for long-lived agent/client sessions.
    declared_in: [authorization-server, openid-configuration]
  - name: full_access
    description: >-
      Declared only by the OIDC discovery document. No published definition of what it grants
      against Notice data; not described on any Notice page.
    declared_in: [openid-configuration]
scope_count: 6
docs: null
divergence_note: >-
  scopes_supported differs across the three discovery documents on the same auth plane. A client
  reading only the protected-resource metadata would never learn that offline_access or
  full_access exist.

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/notice-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 email required.

GitHub Google LinkedIn

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