Seyond · OAuth Scopes
Seyond OAuth Scopes
OAuth 2.0
probed
Seyond 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.
CompanyLiDARSensorsAutonomous DrivingIntelligent TransportationRoboticsPerceptionSmart CitiesAutomotiveHardware
Scopes: 0
Flows:
Method: probed
Scopes (0)
Seyond 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.
derive-oauth-scopes.py found no OpenAPI oauth2 securityScheme for this provider (there is no OpenAPI at all). The scope list below is not derived — it is read verbatim from the RFC 8414 authorization-server metadata and the RFC 9728 protected-resource metadata that seyond.com serves anonymously. Seyond publishes no scopes or permissions reference page; a docs URL is recorded as null rather than guessed.
derive-oauth-scopes.py found no OpenAPI oauth2 securityScheme for this provider (there is no OpenAPI at all). The scope list below is not derived — it is read verbatim from the RFC 8414 authorization-server metadata and the RFC 9728 protected-resource metadata that seyond.com serves anonymously. Seyond publishes no scopes or permissions reference page; a docs URL is recorded as null rather than guessed.
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.