Fodda (PSFK) · OAuth Scopes

Fodda (PSFK) OAuth Scopes

OAuth 2.0 searched

Fodda (PSFK) publishes 8 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 Fodda (PSFK) API on a user’s behalf.

Tokens are issued from https://clerk.fodda.ai/oauth/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.

Market IntelligenceTrend ResearchKnowledge GraphConsumer InsightsEarnings IntelligenceBrand IntelligenceResearchInstitutional DataMCPA2AAgent-NativeMachine PaymentsCompany
Scopes: 8 Flows: authorizationCode, deviceCode Method: searched

OAuth endpoints

Authorization URL
https://clerk.fodda.ai/oauth/authorize
Token URL
https://clerk.fodda.ai/oauth/token
Flows
authorizationCodedeviceCode

Scopes (8)

ScopeDescriptionFlows
read Read access to the MCP resource https://mcp.fodda.ai/mcp (scopes_supported in the www-hosted RFC 9728 document; bearer_methods_supported [header]). authorizationCode
openid OpenID Connect authentication (id_token, RS256). authorizationCode, deviceCode
profile Profile claims: name, given_name, family_name, picture, preferred_username. authorizationCode, deviceCode
email email and email_verified claims. authorizationCode, deviceCode
public_metadata Clerk user public metadata. authorizationCode, deviceCode
private_metadata Clerk user private metadata. authorizationCode, deviceCode
offline_access Issue a refresh token (grant refresh_token supported). authorizationCode, deviceCode
user:org:read Read the user's organization membership (org_id claim). authorizationCode, deviceCode

Source

OAuth Scopes

Raw ↑
generated: '2026-09-19'
method: searched
source: well-known/fodda-ai-clerk-oauth-authorization-server.json + well-known/fodda-ai-clerk-openid-configuration.json
  + well-known/fodda-ai-www-oauth-protected-resource.json
docs: https://www.fodda.ai/connect
note: derive-oauth-scopes.py found no oauth2 scheme in the OpenAPI (the REST contract declares apiKey + bearer SPT
  only), so this file is built from the provider's published discovery documents. The scopes are identity scopes
  of the Clerk-delegated authorization server plus the single resource scope "read" advertised by the www-hosted
  protected-resource document; no per-tool or per-graph scopes are published, and MCP tool authorization is by account/plan
  rather than scope.
schemes:
- name: oauth2
  source: well-known/fodda-ai-clerk-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://clerk.fodda.ai/oauth/authorize
    tokenUrl: https://clerk.fodda.ai/oauth/token
    pkce: S256
    registrationUrl: https://clerk.fodda.ai/oauth/register
  - flow: deviceCode
    deviceAuthorizationUrl: https://clerk.fodda.ai/oauth/device_authorization
    tokenUrl: https://clerk.fodda.ai/oauth/token
scopes:
- scope: read
  description: Read access to the MCP resource https://mcp.fodda.ai/mcp (scopes_supported in the www-hosted RFC
    9728 document; bearer_methods_supported [header]).
  flows:
  - authorizationCode
  sources:
  - well-known/fodda-ai-www-oauth-protected-resource.json
  kind: resource
- scope: openid
  description: OpenID Connect authentication (id_token, RS256).
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-openid-configuration.json
  kind: identity
- scope: profile
  description: 'Profile claims: name, given_name, family_name, picture, preferred_username.'
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-openid-configuration.json
  kind: identity
- scope: email
  description: email and email_verified claims.
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-openid-configuration.json
  kind: identity
- scope: public_metadata
  description: Clerk user public metadata.
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-oauth-authorization-server.json
  kind: identity
- scope: private_metadata
  description: Clerk user private metadata.
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-oauth-authorization-server.json
  kind: identity
- scope: offline_access
  description: Issue a refresh token (grant refresh_token supported).
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-oauth-authorization-server.json
  kind: identity
- scope: user:org:read
  description: Read the user's organization membership (org_id claim).
  flows:
  - authorizationCode
  - deviceCode
  sources:
  - well-known/fodda-ai-clerk-oauth-authorization-server.json
  kind: identity
claims_supported:
- sub
- iss
- aud
- exp
- iat
- email
- email_verified
- name
- given_name
- family_name
- picture
- preferred_username
- org_id
gaps: No scope-to-tool or scope-to-graph mapping is published; the protected-resource documents on mcp.fodda.ai
  list no scopes at all (only authorization_servers).

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