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/Build

Build

Choose the right Mezcal integration surface for code and automation.

API referenceReferenceQuickstartTypeScript SDK

In this guide

Surface mapStart hereShared envClient rulesPaginationConcurrency
Loading documentation content…
PreviousMonitor 10 WalletsCanonical REST, SDK, and CLI starter for monitoring a fixed wallet set with recent activity, transactions, holdings, and token flows.NextAPIREST API for exact request shapes, auth, pagination, and retries.

On this page

Surface mapStart hereShared envClient rulesPaginationConcurrency
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

Build

Choose the Mezcal surface by job.

Surface map

If you need...Use...
exact HTTP contract, auth, retries, paginationREST API
typed application codeTypeScript SDK
shell workflows or local exportsAgent CLI
tool-calling access for an agentMCP

Start here

  • API guide
  • API reference
  • TypeScript SDK
  • Agent CLI
  • Monitor 10 wallets

Shared env

export MEZCAL_BASE_URL="https://<your-mezcal-host>/api"
export MEZCAL_API_KEY="mzk_test_your_key_here"
export MEZCAL_CHAIN="SN_MAIN"

All build surfaces use the same hosted contract underneath.

Client rules

  • always send X-Mezcal-Api-Key
  • treat 401 as missing or invalid credentials
  • treat 403 as a real scope or route-tier mismatch
  • honor Retry-After on 503
  • log X-Request-Id
  • do not assume hidden /v1/* app routes are external

Pagination

High-cardinality routes are cursor-based.

Expect:

  • bounded limit parameters
  • items arrays
  • nextCursor when another page exists
  • repeated query parameters where documented, for example multiple address= filters on token transfers

Representative routes:

  • GET /v1/{chain}/address/{address}/activity?limit=50
  • GET /v1/{chain}/token/{token}/transfers?address=0xA&address=0xB&limit=100

Concurrency

Treat the hosted /api lane as a bounded external service:

  • keep concurrency bounded
  • page deliberately
  • honor Retry-After
  • prefer incremental monitoring loops over chain-scale refetches

For multi-wallet monitoring, use Monitor 10 wallets.