From your first call to a production-grade agent. Pick your path:
Sign up to access the dashboard, API keys (sandbox & production), usage logs, and the catalog.
Create accountOne key for the entire catalog. Use a sandbox key while you build, switch to a production key when you ship.
callio_a1b2c3d4e5f6...Hit the proxy from any HTTP client, or skip straight to MCP setup if your agent runs in Cursor / Claude / Antigravity.
curl -X GET "https://callio.dev/api/proxy/jsonplaceholder/posts/1" \ -H "Authorization: Bearer callio_your_key_here"
All API requests through Callio are authenticated using your Callio API key. Pass it as a Bearer token in the Authorization header:
Authorization: Bearer callio_your_key_here
For APIs that require provider authentication (e.g., OpenAI, SendGrid), save your provider API key in the API detail page. Callio will automatically attach it when proxying your requests.
Callio acts as a proxy between your application and upstream APIs. The proxy URL pattern is:
https://callio.dev/api/proxy/<api-slug>/<path>
For APIs with custom base URLs, you can also use the forwarding mode:
https://callio.dev/api/proxy/<api-slug>/forward?target=<encoded-url>
Callio proxy responses include these headers:
x-callio-proxy: truex-callio-api: <slug>x-callio-upstream-status: <status>MCP (Model Context Protocol) lets an AI client talk to external tools over a standard channel. Callio ships an MCP server so your agent can use the marketplace without a separate integration per API. Product overview: callio.dev/mcp.
npx … callio-mcp or node on the server file). Cursor / Antigravity start it and list its tools./api/browse) and the authenticated proxy (/api/proxy/…) when a tool needs to execute a request.| MCP tool | Purpose | Callio key? |
|---|---|---|
| search_apis | Search the catalog (like Browse). Optional query / category. | No |
| get_api_info | Full detail for one API: endpoints, params, auth notes. Pass slug. | No |
| call_api | HTTP call through the proxy: slug, path, method, optional body / query. | Yes — set CALLIO_API_KEY in MCP env. |
Project file: .cursor/mcp.json. Set CALLIO_API_KEY and restart MCP (or restart Cursor). Settings → Tools & MCP should show callio connected with three tools.
Same JSON shape: mcpServers.callio with command, args, and env.CALLIO_API_KEY. Paths differ by app (Antigravity: MCP settings; Claude Code: ~/.claude/claude_desktop_config.json).
Advanced/self-hosted: set CALLIO_BASE_URL (default https://callio.dev).
npx vs local node).For Cursor, Antigravity, and Claude Code, use the MCP section above — that is the supported way to give agents catalog + proxy access with one config.
For custom agents or apps that call HTTP directly, use your Callio API key with the proxy URL:
{
"callio": {
"api_key": "callio_your_key_here",
"proxy_url": "https://callio.dev/api/proxy"
}
}You can also use the "Add to Agent" flow on individual API pages where available.
For Node.js and TypeScript environments, we provide an official SDK to make interacting with the Callio proxy even easier.
npm install callio-sdk
import { CallioClient } from 'callio-sdk';
// Initialize with your single Callio API Key
const callio = new CallioClient('callio_your_api_key');
// Make a request to any supported API
const response = await callio.post('openai', 'v1/chat/completions', {
model: 'gpt-4',
messages: [{ role: 'user', content: 'Hello!' }]
});
console.log(response);import requests
headers = {"Authorization": "Bearer callio_your_key"}
response = requests.get(
"https://callio.dev/api/proxy/jsonplaceholder/posts/1",
headers=headers
)
print(response.json())const response = await fetch(
"https://callio.dev/api/proxy/jsonplaceholder/posts/1",
{ headers: { Authorization: "Bearer callio_your_key" } }
);
const data = await response.json();
console.log(data);Need help? Contact us