1mind · OAuth Scopes

1mind OAuth Scopes

OAuth 2.0 probed

1mind 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.

CompanyArtificial IntelligenceAI AgentsSalesGo-To-MarketConversational AISales EnablementRevenue Operations
Scopes: 0 Flows: Method: probed

Scopes (0)

1mind 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.

The advertised set is the Ory Hydra default and contains NO product scopes — there is no 1mind-specific scope (no read/write, no resource-scoped permission) published anywhere anonymously. Product scopes may exist and simply not be advertised in scopes_supported, which the OAuth 2.0 authorization server metadata spec (RFC 8414 §2) permits as OPTIONAL. Nothing is inferred or invented here: this file records exactly what the server publishes.

📄 Provider scope reference:

Source

OAuth Scopes

1mind-scopes.yml Raw ↑ 
generated: '2026-08-13'
method: probed
source: https://auth.1mind.com/.well-known/openid-configuration (HTTP 200) —
  scopes_supported
name: 1mind OAuth Scopes
authorization_server: https://auth.1mind.com
authentication_reference: ../authentication/1mind-authentication.yml
docs: null
docs_note: >-
  No public scope/permission reference page exists. These are the only scopes
  1mind's authorization server advertises anonymously.
scope_count: 3
scopes:
- name: openid
  description: OpenID Connect — request an ID token and identify the end user.
    Required for any OIDC flow against this issuer.
  standard: OpenID Connect Core 1.0
  source: scopes_supported
- name: offline_access
  description: Request a refresh token so the client can obtain new access
    tokens without user interaction.
  standard: OpenID Connect Core 1.0
  source: scopes_supported
- name: offline
  description: Legacy Ory Hydra alias for offline_access; grants a refresh
    token.
  standard: Ory Hydra (vendor alias)
  source: scopes_supported
note: >-
  The advertised set is the Ory Hydra default and contains NO product scopes —
  there is no 1mind-specific scope (no read/write, no resource-scoped
  permission) published anywhere anonymously. Product scopes may exist and
  simply not be advertised in scopes_supported, which the OAuth 2.0
  authorization server metadata spec (RFC 8414 §2) permits as OPTIONAL. Nothing
  is inferred or invented here: this file records exactly what the server
  publishes.

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/1mind-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.