LanceDB · OAuth Scopes
LanceDB OAuth Scopes
OAuth 2.0
derived
LanceDB 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.
Tokens are issued from /oauth/token.
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.
Vector DatabaseMulti-ModalLance FormatLakehouseRAGAgent MemoryOpen-SourceEmbeddingsFull-Text SearchHybrid SearchColumnar StorageArrowAI Infrastructure
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
/oauth/token
/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
LanceDB 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.
LanceDB does not publish OAuth scopes; all requests to LanceDB Cloud/Enterprise APIs authenticate with an x-api-key header and no scope-based permissions are documented (https://docs.lancedb.com/api-reference/rest).
LanceDB does not publish OAuth scopes; all requests to LanceDB Cloud/Enterprise APIs authenticate with an x-api-key header and no scope-based permissions are documented (https://docs.lancedb.com/api-reference/rest).
📄 Provider scope reference: https://docs.lancedb.com/api-reference/rest
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.