Mezcal ExplorerMezcalDocs
QuickstartBuildAgentsReference
Open explorer
Documentation homeQuickstartConceptsMonitor 10 Wallets
BuildAPIAdvanced UtilitiesProtocol RoutesAPI Surface PolicySDKTypeScript SDK

Live reference

Interactive API referenceReference hub
AgentsAgent CLIMCP Quickstart
Reference Catalogs
Docs/SDK

SDK

First-party Mezcal SDK guidance and typed client entry points.

API referenceReferenceQuickstartCLI

In this guide

Why use itStart hereInstall mindset
Loading documentation content…
PreviousAPI Surface PolicyWhich Mezcal routes are official public API, advanced utilities, protocol routes, or internal-only.NextTypeScript SDKUse the first-party Mezcal TypeScript client when you want typed explorer reads in application code.

On this page

Why use itStart hereInstall mindset
Mezcal ExplorerMezcalDocumentation

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 explorerAPI referenceBack to top

SDK

The first-party SDK is the cleanest way to consume Mezcal from app code.

Why use it

It gives you:

  • typed responses
  • consistent auth handling
  • request ID propagation
  • the same public transport contract used by the explorer

Start here

  • TypeScript SDK

Install mindset

For external users, the package-manager path is the default path. Artifact installs remain a fallback for controlled distribution and verification.