Skip to main content
Mirador is an OTLP-native observability platform. Point an existing OpenTelemetry SDK or Collector at Mirador to ingest traces, metrics, and logs without replacing your instrumentation or adding a Mirador SDK. All three signals use the same endpoint and authentication. Data is isolated to the project that owns the API key.

​
Endpoints

Mirador accepts OTLP over HTTP and gRPC in production and development: For OTLP/HTTP, replace {signal} with traces, metrics, or logs. The gateway accepts application/x-protobuf and application/json, with optional gzip compression.
When OTEL_EXPORTER_OTLP_ENDPOINT is set to https://otel.mirador.org, standards-compliant HTTP exporters append /v1/traces, /v1/metrics, or /v1/logs automatically. Signal-specific endpoint variables must include the full path.

​
Authentication

Send a Mirador API key in the standard OTLP Authorization header:
Both key types are accepted:
  • Server keys (mir_srv_*) are intended for backend services and Collectors.
  • Web keys (mir_web_*) are intended for browsers and are validated against the key’s allowed origins.
The canonical Bearer form is also accepted. In environment variables, URL-encode the space:
Create or rotate keys from your project’s API keys page in the Mirador dashboard.

​
Configure an existing SDK

For OTLP/HTTP with protobuf:
For OTLP/gRPC:
Your language’s OpenTelemetry autoinstrumentation or SDK reads these standard variables. Restart the instrumented service after applying them.

​
Use an OpenTelemetry Collector

Add Mirador as an exporter and send one or more pipelines to it:
If a pipeline already has another exporter, keep it and append otlp/mirador to fan out the same telemetry to both destinations.

​
OTLP or the Mirador SDK?

Both feed Mirador’s trace pipeline, so you can choose per service:
  • Use OpenTelemetry for vendor-neutral instrumentation, existing OTel deployments, logs, and metrics.
  • Use the Mirador SDK (@miradorlabs/web-sdk or @miradorlabs/nodejs-sdk) for typed web3 APIs, provider integration, and browser-specific features.
OTel applications can still trigger Mirador’s external-system enrichment by adding reserved span events. See Enrichment hints.

​
Machine-readable contract

The live gateway publishes its canonical, agent-friendly integration contract at otel.mirador.org/llms.txt. It contains the exact enrichment event names, required attributes, endpoint rules, and complete examples.

​
Next steps

Traces

Export spans, events, attributes, and status

Metrics

Export counters, gauges, and distributions

Logs

Export structured logs and correlate them with traces

Enrichment hints

Track onchain and external actions from OTel spans