Read it from code

REST

GET /api/v1/launch/<mint>

One launch: labels with reasons, slot-0 buyers with class, rule and proving transactions, early slots, failed attempts, first-hour and 24-hour outcomes. example (test vector)

GET /api/v1/dev/<wallet>

A creator's record across launches, recurring linked wallets with proofs. An unknown wallet queues a 30-day backfill.

GET /api/v1/daily/<YYYY-MM-DD>

One UTC day: shares per label, biggest linked buy, cleanest dev, ready-to-copy text. Without a date: today.

GET /api/v1/feed?since=<unix>&label=&min_mcap=&has_website=1

Newest analyzed launches; pass next_since back as since.

GET /api/v1/stats, GET /api/v1/status

Today's numbers; indexer status, gaps and coverage.

Add ?demo=1 to any of these to get the synthetic test vectors.

MCP

Remote MCP server at https://blockzero.site/mcp (Streamable HTTP, stateless, read-only). Tools: check_launch, dev_record, daily_stats, recent_launches. Each result starts with factual one-line summaries, then structured JSON. Same limits as the API.

{
  "mcpServers": {
    "block-zero": {
      "type": "http",
      "url": "https://blockzero.site/mcp"
    }
  }
}

copy config

API Pro

Opens at token launch. A key without the per-minute limit, for a burn of the site token with the memo blockzero:api:<key_id>.

Badges

/badge/t/<mint>.svg and /badge/dev/<wallet>.svg, with ?size=compact|full and ?theme=light|dark|auto. A badge shows what the record says, including linked buys and partial records.