MC-1 DOCS
API ReferenceCookbook
Docs/Intelligence FinOps/Usage attribution
PublishedGALAST REVIEWED · 30 AUG 2026

Usage attribution

Attribute requests, tokens, charges, routes, providers, projects, and outcomes over the same accounting window.

Overview

Attribute requests, tokens, charges, routes, providers, projects, and outcomes over the same accounting window.

  • Select the accountable organization and project.
  • Use one explicit measurement window.
  • Preserve route and provider attribution.
  • Compare cost with quality, latency, and success evidence.
  • Label projections and measured values separately.

Production checklist

  • Keep credentials in a server-side secret store.
  • Set explicit cost, latency, privacy, provider, and regional constraints.
  • Capture route and evaluation evidence for incident review.
  • Test timeouts, cancellation, fallback, and denied-policy paths before rollout.
End of guide
Was this page helpful?