Prox · OAuth Scopes

Prox OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://signin.useprox.com/oauth2/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.

CompanyArtificial IntelligenceMCPManufacturingProduct SupportKnowledge BaseDocumentationAgents

Scopes: 4 Flows: authorizationCode, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://signin.useprox.com/oauth2/authorize

Token URL
https://signin.useprox.com/oauth2/token

Flows
authorizationCodedeviceCode

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect authentication; issue an ID token for the signed-in user.	authorizationCode, deviceCode
profile	Access the user's basic profile claims.	authorizationCode, deviceCode
email	Access the user's email address claim.	authorizationCode, deviceCode
offline_access	Issue a refresh token so the client can obtain new access tokens without re-prompting.	authorizationCode, deviceCode

📄 Provider scope reference: https://useprox.com/docs/mcp

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://mcp.useprox.com/.well-known/oauth-authorization-server
docs: https://useprox.com/docs/mcp
schemes:
  - name: OAuth2
    source: https://signin.useprox.com/.well-known/oauth-authorization-server
    issuer: https://signin.useprox.com
    flows:
      - flow: authorizationCode
        authorizationUrl: https://signin.useprox.com/oauth2/authorize
        tokenUrl: https://signin.useprox.com/oauth2/token
      - flow: deviceCode
        deviceAuthorizationUrl: https://signin.useprox.com/oauth2/device_authorization
        tokenUrl: https://signin.useprox.com/oauth2/token
scopes:
  - scope: openid
    description: OpenID Connect authentication; issue an ID token for the signed-in user.
    flows: [authorizationCode, deviceCode]
    sources: [https://signin.useprox.com/.well-known/openid-configuration]
  - scope: profile
    description: Access the user's basic profile claims.
    flows: [authorizationCode, deviceCode]
    sources: [https://signin.useprox.com/.well-known/openid-configuration]
  - scope: email
    description: Access the user's email address claim.
    flows: [authorizationCode, deviceCode]
    sources: [https://signin.useprox.com/.well-known/openid-configuration]
  - scope: offline_access
    description: Issue a refresh token so the client can obtain new access tokens without re-prompting.
    flows: [authorizationCode, deviceCode]
    sources: [https://signin.useprox.com/.well-known/openid-configuration]
notes: >-
  Prox's authorization server (WorkOS AuthKit) advertises the standard OIDC scope
  set only. Prox does not publish product-level (resource) scopes; MCP access is
  gated per user by the signed-in workspace's own permissions rather than by OAuth
  scope, and every tool call is attributed to the user's identity.

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