Skip to main content
InkyPump exposes on-chain contracts and a server-side read API. They serve different jobs.

Which surface to use

Start with the Launchpad Quickstart if you are adding InkyPump to another launchpad.

Production networks

Deployment addresses can change. Existing tokens remain on their original hook. Do not use one global hardcoded hook for both new and historical tokens.

InkyPump read API

Core server-side routes: Read API Policies before building. Always pass chainId, keep exact decimal strings, and call the API from your backend.

Contract writes

Use a browser wallet or another user-controlled signer. The caller becomes the launch creator and fee recipient. For native launches:
For xStocks launches:
Simulate the exact call, save the transaction hash, verify the receipt event, then wait for indexed discovery. API indexing is not part of transaction success.

InkySwap API

The InkySwap API covers the wider DEX on Ink: These routes are separate from InkyPump’s curve and market-routing services.

MCP status

@inkyswap/pump-mcp is an operator tool that signs with a configured hot wallet. Its published 0.1.1 release still pins the older Ink hook and is not the recommended path for a new launchpad integration. Use the wallet quickstart and runtime deployment discovery instead.

Version and proof

The partner docs were checked against production and source on September 21, 2026. Runtime responses remain authoritative for feature flags and deployment identities.

Launchpad Quickstart

A receipt-safe, browser-wallet launch flow.

API Policies

Chain, CORS, precision, error, and retry rules.