What problem does it solve? Developers integrating an APIMatic-generated .NET SDK often guess at how to supply credentials, since auth scheme property names are generated per-API and the shared Core.Authentication folder ships every scheme class regardless of what the API actually accepts. This Skill provides the correct patterns for wiring credentials into the client options class and handling token lifecycle behavior. ## Core Features & Use Cases - Scheme-specific credential setup: Covers Basic auth, Bearer tokens, API keys (header, query, or cookie), and all three OAuth 2.0 grants (client credentials, authorization code with PKCE, and resource owner password). - Token caching and refresh guidance: Explains in-memory token caching, automatic refresh, and 401-triggered token invalidation and re-acquisition. - Combined schemes and secret hygiene: Documents AND/OR composition of multiple auth schemes and loading secrets from IConfiguration sources instead of hardcoding. - Use Case: A developer receives a 401 from their APIMatic .NET SDK client and uses this Skill to identify the correct credentials property on the options class and configure OAuth2 client credentials with automatic token refresh. ## Quick Start Ask the agent to configure authentication for your APIMatic .NET SDK client using the credentials properties on its options class before constructing the client.