For developers

Build on ZASH

Everything on ZASH is open to read: projects, prices, holders, milestones, votes. Pull it three ways: a public REST API (no keys, no sign-up), a hosted remote MCP server so any AI platform can browse ZASH on its own, and a CLI for your terminal and scripts.

REST API

Read-only, no authentication. Every endpoint is a plain GET. Base URL: https://zash.xyz/api/v1

EndpointWhat it returns
GET /projectsMarketplace listing, paginated (12/page). Filter by status, category, search and sort.
GET /projects/{id}Full project detail: metadata, milestones, 20 latest investments, live market fields.
GET /projects/by-address/{tokenAddress}Canonical lookup by TokenSale contract address. Same shape as /projects/{id}.
GET /projects/by-ticker/{ticker}Deprecated ticker lookup (tickers can collide), prefer by-address.
GET /projects/{id}/ohlcvOHLCV candles from trades. Timeframes from 1s to 1W, plus all (default 1h).
GET /projects/{id}/activityLatest 50 events: buys, sells and governance (votes, fund releases, proofs).
GET /projects/{id}/holdersTop 100 token holders with share %, role and lock flags.
GET /projects/{id}/commentsUp to 100 top-level comments with author identity and holdings badges.
GET /projects/{projectId}/milestonesAll milestones: tranches, deadlines, statuses, vote tallies, proof metadata.
curl
curl "https://zash.xyz/api/v1/projects?status=live_trading&sort=most-raised"
  • Big numbers arrive as decimal strings. USDC amounts are raw 6-decimal integers, divide by 1,000,000 for display.
  • Rate limit: 100 requests per minute per IP. Going over returns 429.

Connect any AI platform (MCP)

One hosted remote MCP server, live and ready. Point any MCP-capable AI client at a single URL and it can browse ZASH projects, prices, holders and milestones on its own, nothing to install, no API key, no build step. Streamable HTTP transport.

Hosted endpoint

mcp endpoint
https://zash.xyz/mcp

list_projects

Compact marketplace list: id, name, ticker, status, raise + price summary.

get_project

Full project detail by id, ticker or contract address.

get_ohlcv

OHLCV candles in USDC, any timeframe.

get_activity

Latest buys, sells and governance events.

get_holders

Top 100 holders with share %, role and lock flags.

get_milestones

All milestones: tranches, deadlines, statuses, vote tallies.

get_comments

Latest top-level community comments.

Claude Code

bash
claude mcp add --transport http zash https://zash.xyz/mcp

Claude Desktop

Settings → Developer → Edit Config, then add the remote server:

json
{
  "mcpServers": {
    "zash": {
      "url": "https://zash.xyz/mcp"
    }
  }
}

On an older desktop build without native remote support, bridge it with mcp-remote instead:

bash
npx mcp-remote https://zash.xyz/mcp

ChatGPT / OpenAI

OpenAI's Agents / Responses API and ChatGPT Developer Mode connectors both support remote MCP servers, point them at the same https://zash.xyz/mcp endpoint. For a Custom GPT with no MCP at all, import the OpenAPI spec as a GPT Action instead:

openapi spec (gpt action)
https://zash.xyz/api/v1/openapi.json

OpenAI Codex CLI

Codex CLI speaks MCP over stdio, so the mcp-remote bridge connects it to the hosted URL, no install of ZASH code needed. Add this to ~/.codex/config.toml:

toml
# ~/.codex/config.toml
[mcp_servers.zash]
command = "npx"
args = ["-y", "mcp-remote", "https://zash.xyz/mcp"]

Cursor / Windsurf / other IDEs

The standard MCP JSON most clients accept, same url shape as Claude Desktop:

json
{
  "mcpServers": {
    "zash": {
      "url": "https://zash.xyz/mcp"
    }
  }
}

Self-host (optional)

The hosted URL above is the easy path, most people never need this. If you'd rather run the server against your own deployment, set the ZASH_API_URL environment variable to point at it. Source access on request, the repo is private; reach us at Support@zash.xyz.

CLI

Prices, charts and milestones straight in your terminal. Read-only, no API key. Needs Node.js 18 or newer.

Install

bash
git clone <repo-url> && cd zash-launchpad/cli
npm install
npm run build
npm link   # puts `zash` on your PATH
CommandWhat it does
zash projectsMarketplace listing, filter with --status, cap with --limit.
zash project <p>Full detail card: price, raise progress, milestones, contracts, links.
zash price <p>One-line price + 24h change.
zash chart <p>Braille price chart in your terminal (--tf for timeframe, --last for candles).
zash holders <p>Top token holders with share %, role and lock flags.
zash milestones <p>Milestone tranches, deadlines, statuses and vote tallies.
zash activity <p>Latest buys, sells and governance events.

<p> is any project, ticker (ZGEN), uuid, or 0x TokenSale address.

Example

output
$ zash price ZGEN
ZGEN  $0.00007309  ▼ -50.71% (24h)

Scripting

Every command takes --json and prints the raw API payload, ideal for piping into jq, scripts, or AI agents.

bash
zash price ZGEN --json | jq .currentPrice

Source code

The repository (API, MCP server, CLI and this site) is currently private. Source access on request, reach us at Support@zash.xyz.