What problem does it solve? Working with APIMatic-generated .NET SDK models involves non-obvious shapes—union types without object-initializers, string/int enums with inconsistent FromValue support, and nullability rules—that cause compile errors and incorrect request payloads when developers guess at the API surface. ## Core Features & Use Cases - Union Type Handling: Construct OneOf/AnyOf unions via static factory methods and read them back with TryGet variant accessors, including implicit conversions for primitive AnyOf variants. - Enum Guidance: Use type-safe StringEnum/IntEnum constants, FromValue for unknown values, and TryGetKnownValue guards, with warnings about enums that lack the public FromValue helper. - Collections, Dates & Nullability: Assign IReadOnlyList/IReadOnlyDictionary properties, work with DateTimeOffset for ISO-8601 wire formats, and understand null-versus-empty serialization semantics. - Use Case: When building a request payload for a payments endpoint whose amount field is a string-or-decimal AnyOf union, use the generated factory methods and confirm exact CLR types from the contract sheet instead of assuming double. ## Quick Start Ask the agent to build a request model for an APIMatic .NET SDK endpoint, constructing any union fields with their static factory methods and setting enum properties from the generated constants.
