Grafana Cloud

What Plutus imports

• Amount due per billing dimension (Metrics, Logs, Traces, Profiles, k6, IRM, …), monthly
• Cost attributed to each stack in the org, monthly

Connecting

Method: Cloud Access Policy Token

1. Go to grafana.com and sign in, then open your organization.
2. Go to Security > Access Policies and click Create access policy.
3. Scope the policy to your organization and grant exactly two scopes: orgs:read and org-billing-info:read. No other scopes are needed — this connection never reads dashboards, metrics, or logs.
4. Add a token to the policy and copy it. It’s shown only once.
5. In Plutus, paste the token into Access Policy Token.
6. Find your organization slug in the grafana.com URL (grafana.com/orgs/<slug>) and enter it in Organisation Slug. Billing is tracked at the org level, not per stack, so one connection covers every stack the org owns.
7. Select the currency your Grafana Cloud invoices are issued in under Billing Currency. Grafana’s billing API doesn’t report a currency, so this can’t be detected automatically. You can’t change it after the first sync — the spend already collected is converted to Plutus’s USD base using this value, and changing it later would misstate your history. To switch currencies, disconnect (which removes the collected data) and reconnect.
8. Save the connection. Plutus lists the org’s billed months and pulls each month’s billed usage from grafana.com.

Notes

Covers Grafana Cloud bought directly from grafana.com. A subscription bought through the AWS, Azure or GCP marketplace is billed by that marketplace and does not appear in this API at all — it shows up in your AWS/Azure/GCP cost source instead, so a marketplace customer will see a low or empty total here rather than a duplicate.