Context Plugins Overview

AI coding agents are good at writing code. They struggle with API integrations. The problem isn't code generation; it's context. When an agent draws on stale training data or scraped docs, it produces code that calls endpoints that don't exist, uses wrong SDK versions, or mishandles authentication.

APIMatic context plugins solve this by giving AI coding agents deterministic, version-aware context grounded in your OpenAPI definition. The plugin delivers your current SDK, code samples, integration workflows, and documentation to the agent at the time it writes code, not from model memory. Developers get accurate, production-ready integrations without needing to read your docs or switch context.

The result: developers go from your portal to a working integration in minutes, not hours. In production use, teams have seen a 63% reduction in implementation time and a 78% decrease in rework.

How context plugins work

You generate a context plugin from the APIMatic CLI, covering the SDKs you have published. The plugin delivers:

• Your full API reference: endpoints, parameters, and request and response models
• Authentication requirements for every endpoint
• Versioned SDK code in the developer's language of choice
• Integration workflows and code samples drawn from your portal documentation

When a developer loads the plugin into their AI coding agent, such as Claude Code or Cursor, the agent gains task-aware, grounded context. It can suggest the correct endpoint, generate type-safe SDK calls, handle authentication properly, and surface real integration patterns, without the developer leaving their IDE.

See it live

Try out Shell's Context Plugins

Install Shell's context plugin into Claude Code or Cursor, and watch your AI agent generate accurate Shell SDK integrations in seconds.

Generate a context plugin

Context plugins are generated with the APIMatic CLI. For each language you want the plugin to cover, publish an SDK and include source code publishing, which pushes the SDK to GitHub. The plugin points AI agents at that GitHub repository for the SDK source code, so a language published only to a package registry can't be covered. Once your SDKs are published, generate the plugin:

apimatic plugin generate

The CLI asks for an ID, a display name, and a version for the plugin, then writes it to ./plugin. To share it with your developers, apimatic plugin publish prints the git commands that publish the plugin to a public GitHub repository, for you to review and run yourself.

For the full list of flags and options, see Plugin Commands.