The C# v4 SDK (beta) has picked up a wave of improvements over the past few weeks, spanning streaming, dependency injection, documentation, error handling, and file handling.

Previously, in order for an API provider to use Context Plugins for their API, their SDKs had to be published to a public package manager such as npm, NuGet, or PyPI. That left teams whose SDKs live behind a private host — internal APIs, partner integrations, or APIs that aren't yet ready for public distribution — without a way to offer the same AI-assisted integration experience.

We've now added self-hosted SDK support in Context Plugins. Instead of pulling the SDK from a package manager, the AI agent downloads the SDK package from your portal, installs it locally in the developer's workspace, and wires it into their project — all without the SDK ever needing to be published.

Developers increasingly don't read API documentation page by page — they build with AI coding tools like Claude Code, Cursor, and VS Code. And these tools are only as good as the context they have. Without accurate, current knowledge of your API, they guess: invented endpoints, stale parameters, and integration code that takes hours to hand-fix.

We've brought your API into that workflow. Right from your developer portal, developers can now load your full API context — docs, SDKs, code samples, and setup instructions — into their AI coding environments in a single step, using Context Plugins.

Our SDKs are now more AI ready than ever. Model reference docs now show idiomatic, language-specific code samples, complete with imports, instead of serialized payloads. They cover how to initialize a structure, reference an enum value, and catch errors across all seven SDK languages.

Developers frequently switch between APIMatic documentation and external AI chat tools to understand APIs — a workflow that required manually copying page content and pasting it each time. This release eliminates that friction entirely.

We've introduced the AI Assist Menu, a one-click dropdown available on every documentation page that sends the current page's content directly to your preferred AI tool as context.

The new C# SDK is now available in beta. You can generate it today using the APIMatic CLI. Try it out and share your feedback with us.

We've added new validation and linting rules that flag API entity names exceeding 100 characters in OpenAPI specifications. Names exceeding 100 characters now produce an Error-severity violation that blocks Code Generation, Docs Generation, and Portal Generation.

The Developer Portal's toc.yml now supports a custom slug option, giving you full control over the URL paths generated for your documentation pages.

We've improved llms.txt and llms-full.txt for developer portals and added per-page Markdown exports. These updates make the documentation easier for AI tools to read and help them return answers that are more accurate, relevant, and grounded in the same content users see in the portal.

We've added two new commands to the @apimatic/cli that make it easy to publish SDKs and list your publishing profiles directly from the CLI.