Documentation
Trancepad docs

Protocol, integration, and security for launches on Robinhood Chain.

Integration overview

On-chain truth, REST index, Socket.IO realtime, read-only MCP.

Integrators talk to Trancepad in four layers: on-chain contracts (source of truth for launches and trades), the JSON REST API (indexing, discovery, auth), Socket.IO (realtime updates), and a read-only MCP server for agents. There is no published npm SDK yet. Use ABIs under shared/abis with viem or ethers, or wire MCP for agents.

Trust path

Trades and launches are signed by the user's wallet. POST /buy, POST /sell, and POST /tokens/create sync confirmed receipts into the index. They do not submit swaps. MCP never signs or submits transactions.

First success path

  1. Hit GET /health against your API base.
  2. Complete SIWE auth for JWT-protected writes.
  3. List tokens with GET /tokens, or launch via Router then sync create.
  4. Optional: wire MCP for Cursor or Claude against the same API base.
bashhealth.sh
curl -sS "${API_URL}/health" | jq .

Routes mount at both / and /api/*. Prefer one prefix consistently. Envelope: { "success": true, "data": T }.

Labs bot control and admin pause routes exist for operators. They are not covered in these public pages. See repo runbooks if you operate a deployment.