create-api-adapter

To generate an API adapter scaffold for Clean Architecture, provide a provider name and request/response types. The tool automatically creates interface skeletons, concrete HttpClient adapters, DI registration, and retry policies across application and infrastructure layers.

Structuring external API integration interfaces requires defining provider adapter contracts in the application layer. This scaffold generates these interface skeletons alongside concrete infrastructure adapters using HttpClient to enforce consistent layering and testability.

Yes, the API adapter scaffold includes retry policies for HttpClient. It automatically implements resilient service wrappers in the infrastructure layer to handle transient failures and satisfy resilience requirements for external API integration.

Yes, you can use this to automatically register API adapters for dependency injection. The scaffold generates DI registration code and observability hooks, promoting testability and seamless integration within your .NET application pipeline.

You need an API adapter scaffold when connecting to external APIs within a Clean Architecture project. It reduces boilerplate by standardizing layering, generating interface contracts, and wrapping HttpClient calls with resilient retry policies.