API Overview

InkyPump exposes three things you can integrate against:

1. The V2 smart contracts on Ink mainnet
2. The InkyPump REST API at inkypump.com
3. The InkyPump MCP server, a stdio server for editors like Claude Code and Codex

Pick based on what you are building.

​

When to use each

​

V2 contracts

Direct contract integration. Read state, broadcast trades, listen for events. For full surface and examples, see Contracts Overview.

​

InkyPump REST API

JSON over HTTPS at https://inkypump.com. No auth required for read endpoints. Image uploads require a captcha token. See the InkyPump API section for per endpoint pages.

​

InkySwap REST API

Separate from InkyPump. Covers the wider InkySwap DEX on Ink. See InkySwap API.

​

MCP server

A stdio MCP at the @inkyswap/pump-mcp npm package. Runs locally. Connects to your editor and exposes V2 tools (launch_token, preview_launch, wallet_info, recent_launches, launch_status). See MCP Server.

​

Versions

The V2 contracts are the current launch system. V1 contracts still respond to read calls. Anything tagged “V2” on this page is the live system. Anything tagged “V1” is documented for compatibility.