Connect agents, coding runtimes, and application code to Apiosk through three official surfaces — each built for a different integration style.
The gateway is not the whole story anymore. Apiosk now has an official MCP surface for agent clients, an installable gateway skill for coding agents, and a JavaScript SDK for application code, so discovery and paid execution live in the same workflow.
A remote MCP endpoint that exposes Apiosk discovery and execution as agent-native tools. It generates dynamic tool entries from listing metadata, so new APIs become available without hand-maintained wrappers.
Claude Code install command: claude mcp add --transport http apiosk https://apiosk-mcp.fly.dev/mcp
Catalog-backed discovery with search, listing detail, and generic execute tools
Dynamic API-specific tools generated from Apiosk listing metadata
Payment-aware runtime that surfaces x402 challenges cleanly for agent clients
claude mcp add --transport http apiosk \ https://apiosk-mcp.fly.dev/mcp claude mcp get apiosk
Discovery, metadata, passthrough, and uniform /execute helpers with typed 402 errors and optional x402 auto-pay for Base wallets.
Install the Apiosk gateway skill in supported coding-agent runtimes to browse listings and call paid APIs with saved connect-token access.
Publish payable APIs, make them discoverable for agents, and build a cleaner commercial layer around machine-native usage.