APIMatic ContextMatic
SDK-native API context, delivered directly into your AI coding agent.
What is ContextMatic?
Coding agents hallucinate APIs. APIMatic Context gives them curated, versioned API and SDK docs.
When a developer asks their agent to "integrate the payments API," it normally guesses, pulling from outdated training data or generic patterns that don't match the actual SDK. ContextMatic solves this by giving the agent authoritative, version-aware, SDK-native context at the exact moment it's needed.
Try It Now
One-click install into your IDE:
After installing, use the /onboard-context-matic skill to get an interactive guided tour. The agent will explain the four MCP tools, show you all available APIs, let you pick one to explore, and demonstrate live lookups with runnable code samples:
/onboard-context-matic
Supported APIs
The plugin gives the agent SDK-native context for the following APIs, available in TypeScript, C#, Python, Java, PHP, and Ruby:
| API | Description |
|---|
| Adyen API | Payment processing: retrieve payment methods, create orders, manage stored payment tokens |
| Google Maps APIs | Location services: geocoding, directions, distance matrix, elevation, roads, and places |
| PayPal Server SDK | Payment flows: orders, payments, vault, transaction search, and subscriptions |
| PayQuicker API | Payment and financial services: program agreements, bank accounts, spendback quotes |
| Slack API | Workspace automation: OAuth bots, messaging, conversation management |
| Spotify Web API | Music and podcasts: library management, playback control, discovery |
| Tesla Fleet Management API | Vehicle and fleet operations: charging history, vehicle commands, energy management |
| Tesser API Portal | Digital payments: payment intents, onchain payments, app management |
| Twilio API | Communications: SMS, voice, video, and verification services |
This list is growing. Suggest a new API to request support for one not listed here.
What the Plugin Gives the Agent
Once installed, the plugin exposes four tools to the agent. Each tool is mapped to a specific stage of the integration workflow:
| Tool | Developer task it enables |
|---|
fetch_api | Lists all available APIs with their name, key, and description. The agent calls this first to discover which APIs are available for your project's language. |
ask | Chat with API Copilot for step-by-step integration guidance and general API questions: authentication setup, client initialization, feature behavior, framework-specific patterns (e.g. "How do I initialize the Twilio client in Laravel?"), and idiomatic SDK code samples. |
endpoint_search | Returns an SDK endpoint method's description, input parameters, and response shape by method name. |
model_search | Returns an SDK model's full definition and its typed properties by name. Call this before writing code that constructs request bodies or reads response objects. |
For step-by-step guidance on using these tools together, invoke the /integrate-context-matic skill in your agent. It tells the agent when and how to call each tool throughout your integration workflow.
From Prompt to Code: How the Tools Work Together
The four tools are designed to chain together in a natural integration workflow. Here is a concrete example of what happens under the hood when the agent receives a real task:
Your prompt: "/integrate-context-matic Add Twilio SMS notifications to my Next.js app. Send a text when an order ships."
| Step | Tool called | What it returns |
|---|
| 1 | fetch_api (language=typescript) | Discovers Twilio is available; returns its key |
| 2 | ask (key=twilio, query="How do I initialize the Twilio TypeScript client?") | Returns exact SDK setup code with auth configuration |
| 3 | endpoint_search (query=createMessage) | Returns the method signature, required parameters, and auth requirements for the SMS send endpoint |
| 4 | model_search (query=CreateMessageRequest) | Returns the full typed request model with every available field |
apimatic