DeveloperHub · OAuth Scopes

DeveloperHub OAuth Scopes

OAuth 2.0 probed

DeveloperHub 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.

API ReferenceDeveloper PortalsDocumentationKnowledge BaseOpenAPIDocs as CodeModel Context ProtocolAgent Skills

Scopes: 0 Flows: Method: probed

Scopes (0)

DeveloperHub 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 REST API declares no OAuth flows — it is X-Api-Key only. OAuth exists on exactly one surface: the hosted Editor MCP server at https://ai.developerhub.io/mcp, whose RFC 8414 / RFC 9728 discovery documents are served anonymously and declare a single scope. Alongside that, API keys carry a separate, finer-grained permission vocabulary that the OpenAPI names per operation; those are recorded here as api_key_permissions because they are not OAuth scopes.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-06'
method: probed
source: >-
  https://ai.developerhub.io/.well-known/oauth-authorization-server and
  https://ai.developerhub.io/.well-known/oauth-protected-resource , fetched 2026-09-06;
  permission names read from https://docs.developerhub.io/api.md
provider: DeveloperHub
providerId: developerhub
note: >-
  The REST API declares no OAuth flows — it is X-Api-Key only. OAuth exists on exactly one surface:
  the hosted Editor MCP server at https://ai.developerhub.io/mcp, whose RFC 8414 / RFC 9728
  discovery documents are served anonymously and declare a single scope. Alongside that, API keys
  carry a separate, finer-grained permission vocabulary that the OpenAPI names per operation; those
  are recorded here as api_key_permissions because they are not OAuth scopes.
authorization_server:
  issuer: https://ai.developerhub.io/
  authorization_endpoint: https://ai.developerhub.io/authorize
  token_endpoint: https://ai.developerhub.io/token
  registration_endpoint: https://ai.developerhub.io/register
  grant_types_supported:
  - authorization_code
  - refresh_token
  response_types_supported:
  - code
  code_challenge_methods_supported:
  - S256
  token_endpoint_auth_methods_supported:
  - client_secret_post
  - none
  dynamic_client_registration: true
  document: well-known/developerhub-oauth-authorization-server.json
protected_resource:
  resource: https://ai.developerhub.io/
  resource_name: DeveloperHub
  authorization_servers:
  - https://ai.developerhub.io/
  document: well-known/developerhub-oauth-protected-resource.json
scope_count: 1
scopes:
- name: editor
  description: >-
    Act as the signed-in DeveloperHub editor on the Editor MCP server. The agent reaches only the
    projects that person can already edit, and only those with the Editor MCP server turned on.
  surface: https://ai.developerhub.io/mcp
  source: oauth-authorization-server + oauth-protected-resource metadata
api_key_permissions:
  note: >-
    Separate from OAuth. The OpenAPI names a permission on individual operations; only the changelog
    operations state one explicitly, and no published permissions reference page enumerates the rest.
  documented:
  - name: changelog.edit
    operations:
    - create_changelog_post
  - name: changelog.read
    operations:
    - list_changelog_posts
  undocumented_note: >-
    https://docs.developerhub.io/support-center/api-key says "Each API Key can have different
    permissions. Consult the API to know which permissions you need", so the full permission
    vocabulary is only visible in the key-creation UI.
  docs: https://docs.developerhub.io/support-center/api-key

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