Acelab · OAuth Scopes

Acelab OAuth Scopes

OAuth 2.0 probed

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

CompanyConstructionArchitectureBuilding MaterialsDesignSustainabilityProduct DataAECORevitSpecification

Scopes: 0 Flows: Method: probed

Scopes (0)

Acelab 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 only OAuth scope Acelab publishes anywhere is the single scope advertised by the authorization server backing the documentation MCP server on docs.acelabusa.com. There is no scope or permissions reference page for the Acelab product API — that API answers WWW-Authenticate: Bearer with no published authorization model at all. This file deliberately records one scope rather than inventing a product-API scope surface.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-06'
method: probed
source: https://docs.acelabusa.com/.well-known/oauth-authorization-server
docs: null
note: >-
  The only OAuth scope Acelab publishes anywhere is the single scope advertised by the
  authorization server backing the documentation MCP server on docs.acelabusa.com. There is no
  scope or permissions reference page for the Acelab product API — that API answers
  WWW-Authenticate: Bearer with no published authorization model at all. This file deliberately
  records one scope rather than inventing a product-API scope surface.
authorization_server: https://docs.acelabusa.com/mcp/oauth
grant_types:
- authorization_code
- client_credentials
- refresh_token
code_challenge_methods:
- S256
dynamic_client_registration: true
scope_count: 1
scopes:
- name: mcp:search
  description: >-
    Search and retrieve Acelab documentation content through the MCP server at
    https://docs.acelabusa.com/mcp. Anonymous callers can already list and call the read-only
    tools; this scope gates authenticated/private documentation content.
  resource: https://docs.acelabusa.com
x-evidence:
  fetched: '2026-09-06'
  url: https://docs.acelabusa.com/.well-known/oauth-authorization-server
  http_status: 200
  content_type: application/json

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/acelab-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 email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.