Reference Hub

Choose the right Starkscan reference surface and use the API reference as the canonical HTTP contract.

API reference Quickstart TypeScript SDK Agents

In this guide

Start here first Use the right reference by job Current Coverage

Loading documentation content…

PreviousMCP QuickstartConnect Starkscan to Codex, Claude Code, and similar MCP clients without losing the app and API context.

On this page

Start here first Use the right reference by job Current Coverage

MezcalDocumentation

One product surface across the explorer, HTTP API, CLI, SDK, and MCP transport. The docs should guide you into the right path instead of behaving like a separate app.

Open explorer API referenceBack to top

Use this page to choose the right Starkscan reference surface.

If you need exact HTTP endpoints, auth, schemas, and live try-it requests, use the API reference. This page is the routing layer above that deeper reference, not a second API catalog.

Start here first

API reference for the canonical HTTP contract, request shapes, and live authenticated calls
TypeScript SDK for typed client usage in application code
Agent CLI for shell workflows, exports, and operator-facing automation
MCP Quickstart for Codex, Claude Code, Cursor, and similar tool-calling clients
Build lane when you need auth, retry, and pagination guidance across surfaces

Use the right reference by job

Building a direct HTTP integration: start with API reference
Writing app code: start with TypeScript SDK
Running local workflows or exports: start with Agent CLI
Pointing an agent at Starkscan: start with MCP Quickstart
Choosing between surfaces first: start with Build lane

Current Coverage

Backend skills: 0
Frontend skills: 0
Generated from public SKILL.md coverage via bun run --cwd apps/docs sync:skills

Internal implementation catalogs are intentionally excluded from the public docs build.