Veradermics · OAuth Scopes
Veradermics OAuth Scopes
OAuth 2.0
probed
Veradermics 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.
CompanyBiotechnologyPharmaceuticalsLife SciencesHealthcareDermatologyClinical TrialsDrug Development
Scopes: 0
Flows:
Method: probed
Scopes (0)
Veradermics 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.
Not derived from an OpenAPI — this provider publishes none — and not searched from a docs scopes reference, because no developer documentation exists. The single scope below is read verbatim from the scopes_supported array in the RFC 8414 metadata the WordPress MCP Adapter serves on the corporate host, and is corroborated by the scopes_supported array in the RFC 9728 protected-resource metadata.
Not derived from an OpenAPI — this provider publishes none — and not searched from a docs scopes reference, because no developer documentation exists. The single scope below is read verbatim from the scopes_supported array in the RFC 8414 metadata the WordPress MCP Adapter serves on the corporate host, and is corroborated by the scopes_supported array in the RFC 9728 protected-resource metadata.
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.