Lucid Installation and Authentication

Overview

Select the least-privilege credential class for the operation, configure a secretless local contract, and verify identity and scope without exposing credentials.

Prerequisites

• The exact Lucid operation, resource owner, environment, and required scopes
• A registered OAuth application when user or account OAuth is selected
• An approved secret store and rotation owner

Tool Discipline

Use Read, Glob, and Grep to inspect configuration templates, WebFetch for current auth and scope contracts, and Write or Edit only for secretless examples or redacted receipts.

Current Contract

Lucid documents API keys, OAuth user tokens, and OAuth account tokens. OAuth applications use Authorization Code Flow. REST credentials are normally sent as Authorization: Bearer ...; an operation may also require a resource-specific Lucid-Api-Version header.