Human Longevity · OAuth Scopes
Human Longevity OAuth Scopes
OAuth 2.0
probed
Human Longevity 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.
CompanyHealthHealthcareGenomicsPrecision MedicineDiagnosticsArtificial IntelligenceLongevityLife SciencesMedical Imaging
Scopes: 0
Flows:
Method: probed
Scopes (0)
Human Longevity 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.
These are the scopes_supported values Human Longevity's own OpenID Connect discovery document advertises for the HLI client-portal authorization server. They are the standard OIDC scope set plus Auth0's per-claim scopes; there are NO product or API scopes, because Human Longevity publishes no API for a third party to be authorized against. No scope reference page exists on the provider's site — this artifact is derived entirely from the machine-readable discovery document.
These are the scopes_supported values Human Longevity's own OpenID Connect discovery document advertises for the HLI client-portal authorization server. They are the standard OIDC scope set plus Auth0's per-claim scopes; there are NO product or API scopes, because Human Longevity publishes no API for a third party to be authorized against. No scope reference page exists on the provider's site — this artifact is derived entirely from the machine-readable discovery document.
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.