dotnet-client-initialization

What problem does it solve? Developers integrating an APIMatic-generated .NET SDK often mismanage HttpClient lifetimes, misconfigure DI registrations, or miss critical settings like Timeout and PooledConnectionLifetime, leading to socket exhaustion, stale DNS, or hung requests in production. ## Core Features & Use Cases - Client Construction Guidance: Explains the single public client class shape, its options object, and correct direct instantiation with a long-lived HttpClient. - Dependency Injection Registration: Covers the generated Add{Api}Client extension, its transient-vs-singleton lifetime implications, and how to register over a named HttpClient instead. - Resilience-Aware Defaults: Highlights load-bearing settings like Timeout and PooledConnectionLifetime so DNS changes and hung providers do not cause outages. - Use Case: When wiring a payments SDK into an ASP.NET Core service, use this Skill to register the client over a named HttpClient with a bounded timeout and pooled connection lifetime, avoiding the shared default-client pitfalls. ## Quick Start Ask the agent to register the APIMatic .NET SDK client in your ASP.NET Core service collection using a named HttpClient with a configured timeout.