maxio-getting-started

Grounds Maxio Advanced Billing .NET SDK integrations in a bundled operation and model map.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/apimatic/plugin-marketplace --skill maxio-getting-started-apimatic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maxio-getting-started
Source: https://github.com/apimatic/plugin-marketplace/tree/main/plugins/maxio-sdk/skills/maxio-getting-started
Command: npx skills add https://github.com/apimatic/plugin-marketplace --skill maxio-getting-started-apimatic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding agents hallucinate SDK signatures, namespaces, and error types when integrating the Maxio Advanced Billing (formerly Chargify) .NET SDK, producing code that fails to compile. This Skill provides the SDK identity facts and a generated map of all 247 operations, 555 record models, 98 enums, and 163 typed error classes so every name is looked up rather than guessed. ## Core Features & Use Cases - SDK Identity & Setup: Supplies the NuGet package id (AsadAli.AdvancedBilling.Sdk), root namespace (MaxioAdvancedBilling), Basic auth pattern (API key as username, "x" as password), and US/EU environment configuration. - Bundled SDK Map: Indexes every operation by controller with exact C# signatures, must-pass-explicitly parameters, return types, error accessors, and pagination details, plus model, union, and enum reference pages. - Grounded Integration Workflow: Directs the agent to load companion skills (client initialization, authentication, calling endpoints, models, error handling, resilience, testing) at each step and to clone the pinned v1.0.2 source only when the map cannot answer a question. - Use Case: When asked to create a subscription with coupon validation, the agent looks up the exact CreateSubscription and ValidateCoupon signatures and their typed error accessors from the map instead of inventing method names. ## Quick Start Ask your agent to integrate the Maxio Advanced Billing .NET SDK into your project and have it follow this skill to ground every signature in the bundled SDK map.

Frequently Asked Questions about maxio-getting-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate the Maxio Advanced Billing .NET SDK into my project?▼

Install the AsadAli.AdvancedBilling.Sdk NuGet package, then construct a MaxioAdvancedBillingClient with an HttpClient and options setting BasicAuth credentials and the environment. The skill's SDK map provides exact signatures for all 247 operations across 33 controllers.

How does authentication work in the Maxio Advanced Billing SDK?▼

The SDK uses HTTP Basic authentication where the username is your Maxio/Chargify API key and the password is the literal string "x". Set options.BasicAuth with a BasicAuthCredentials instance before constructing the client or in the DI registration callback.

What is the difference between the NuGet package id and the namespace?▼

The NuGet package id is AsadAli.AdvancedBilling.Sdk but the root namespace you import is MaxioAdvancedBilling. Install by package id, then write using MaxioAdvancedBilling in code, adding separate usings for Models, Enums, AnyOf, OneOf, and Errors namespaces.

Does the Maxio SDK support typed error handling?▼

Yes, 163 of 247 operations throw SdkException with a typed error class exposing TryGet accessors per HTTP status, while 84 operations throw SdkException of RawError with StatusCode and ReadAsString methods. Every operation is throw-only with no no-throw Result variants.

Which .NET versions does the Maxio Advanced Billing SDK support?▼

The SDK targets netstandard2.0, so it works on .NET Framework 4.6.1+, .NET Core 2.0+, and .NET 5 through 10+. Runtime dependencies including Polly and Microsoft.Extensions.Http are pulled in transitively.

Why do I get CS0103 or CS0246 errors when using the Maxio SDK?▼

These errors occur because C# does not import child namespaces transitively, so using MaxioAdvancedBilling.Models alone does not expose enums, unions, or error types. Add a separate using directive for each namespace listed in the SDK map row for the type you reference.