2X · OAuth Scopes

2X OAuth Scopes

OAuth 2.0 probed

2X publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the 2X API on a user’s behalf.

Tokens are issued from https://mcp.knownwell.com/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.

CompanyMarketingMarketing as a ServiceB2BMarTechMarketing OperationsConsultingArtificial IntelligenceGo-To-MarketRevenue OperationsCommercial IntelligenceCustomer SuccessAgentic AIDemand Generation

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://mcp.knownwell.com/authorize

Token URL
https://mcp.knownwell.com/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
knownwell.read	Read access to Knownwell commercial-intelligence data. The only scope the authorization server advertises; description inferred from the scope name because no scopes reference page is published.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://mcp.knownwell.com/.well-known/oauth-authorization-server
note: >-
  The OpenAPI for the Knownwell REST API declares no oauth2 security scheme, so
  derive-oauth-scopes.py found nothing there. The OAuth surface belongs to the remote MCP
  server on mcp.knownwell.com, whose RFC 8414 authorization-server metadata publishes the
  scope list below. Recorded from that live document, not from the spec. 2X publishes no
  human-readable scopes reference page, so the descriptions are the plain reading of the
  scope name and are marked as such.
schemes:
- name: KnownwellMCPOAuth
  source: well-known/2x-oauth-authorization-server.json
  issuer: https://mcp.knownwell.com/
  protected_resource: https://mcp.knownwell.com/mcp
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.knownwell.com/authorize
    tokenUrl: https://mcp.knownwell.com/token
    pkce: S256
scopes:
- scope: knownwell.read
  description: >-
    Read access to Knownwell commercial-intelligence data. The only scope the authorization
    server advertises; description inferred from the scope name because no scopes reference
    page is published.
  description_source: inferred-from-name
  flows: [authorizationCode]
  sources: [well-known/2x-oauth-authorization-server.json]
summary:
  scope_count: 1
  write_scopes: 0
  note: >-
    A single read-only scope, consistent with the REST API being entirely GET operations
    apart from API-key administration.
x-evidence:
  fetched: '2026-08-13'
  url: https://mcp.knownwell.com/.well-known/oauth-authorization-server
  http_status: 200

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/2x-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.