Zen Planner OAuth Scopes
Zen Planner 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.
Tokens are issued from https://api.partners.daxko.com/v3/partners/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.
OAuth endpoints
https://api.partners.daxko.com/v3/partners/oauth2/token
clientCredentials
Scopes (0)
The Daxko Partners platform (which hosts the Zen Planner API) does not publish named OAuth permission scopes - its client_credentials token flow uses the scope field as a customer/client identifier rather than a permissions scope, per https://docs.partners.daxko.com/tutorials/authentication/.
📄 Provider scope reference: https://docs.partners.daxko.com/tutorials/authentication/
Source
OAuth Scopes
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/zenplanner-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.