Reference Hub
Choose the right Starkscan reference surface and use the API reference as the canonical HTTP contract.
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, 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
Internal implementation catalogs are intentionally excluded from the public docs build.