Mezcal ExplorerMezcalDocs
Open explorer

Protocol routes API

Use the separate reference for bridge-analytics protocol extensions.

These routes are real Mezcal product surfaces, but they are not part of the default explorer contract. Keep them separate from the core reference so new integrators do not confuse specialized protocol routes with the baseline API.

Core API referenceProtocol routes guideMCP transport docs

Scope

Treat this as the advanced public surface, not the default onboarding path.

  1. Validate the core explorer routes first.
  2. Only move here when you truly need bridge analytics reads.
  3. Do not use this reference as the default contract for new public integrators.

Included families

  • GET /api/v1/SN_MAIN/analytics/wrappers
  • GET /api/v1/SN_MAIN/analytics/wrappers/txs
  • GET /api/v1/SN_MAIN/analytics/netflows
  • GET /api/v1/SN_MAIN/analytics/netflows/assets

Auth contract

These routes use the same X-Mezcal-Api-Key contract and the same X-Request-Id debugging flow as the core API. The interactive client below executes against the hosted /api base on this same deployment.

Keep protocol-route usage explicit in your integration docs and code paths.

Why separate this?

These routes are specialized and protocol-aware. Keeping them out of the main reference helps new integrators start with the core API first.

What stays outside both references

Infra probes, Prometheus metrics, MCP transport, frontend helper endpoints, private protocol validation routes, and private mutation helpers stay out of the public REST explorers entirely.

Protocol routes

Launch the protocol routes reference on demand

Load the separate protocol routes contract only when you need the specialized routes.

Download protocol routes OpenAPI