Routing & Resilience
Carbon scoring
Per-request carbon estimates and carbon-aware routing are on the roadmap. Today, Meridian Blue exposes the routed provider/region in response headers so you can correlate to your own grid-intensity dataset.
What works today
Each response identifies the upstream provider that served it (X-Meridian-Provider, X-Meridian-Model). To compute a carbon estimate, join those values to your own grid-intensity dataset (e.g. Electricity Maps, Climatiq) using the provider's published region as the bridge.
Token counts are reported in the response's usage object — multiply by your model's energy-per-token estimate plus the grid intensity to get gCO2e per request.
Roadmap
- Per-request gCO2e — Computed at the gateway and surfaced as
X-Meridian-Carbon-G. - Carbon-aware routing strategy — A load-balancing strategy that prefers low-intensity regions when request latency permits.
- CSRD export — A monthly carbon roll-up suitable for Scope 3 reporting.