The spending estimate is limited to 10 requests per user per minute and 20 per organisation per minute, so it is not something to poll. For large reports, the queued path pages at 30,000 rows against 10,000 for the synchronous one and has no timeout, which is the difference between a report that completes and one that dies halfway. Also worth knowing before you parse anything: responses use the Cloudability v3 envelope, so the fields sit under a result object rather than at the top level.
A wide client for the Cloudability v3 API, weighted towards container cost allocation — which namespace, workload or team is actually consuming the cluster spend — with budgets, forecasts and general cost reporting alongside.
- `containers_report` is the centre of it: fairshare and allocated cost by namespace, workload, cluster or label, with filtering and pagination
- Container support tools: `get_container_resource_usage` for daily trends and rightsizing, `discover_container_labels` for the labels available to group by, `get_detailed_cluster_info`, `list_clusters`, `provision_kubernetes_cluster` and `get_cluster_deployment_yaml`
- Spend projection: `get_spending_estimate` for the current month with service-level drivers and daily progression, `get_spending_forecast` for multiple months with configurable history and options to strip credits and one-time charges
- Budgets: `list_budgets`, `get_budget`, `create_new_budget`, `modify_budget`, `remove_budget`, plus `create_budget_alert`, `list_budget_alerts`, `modify_budget_alert` and `remove_budget_alert`
- Cost reporting: `execute_cost_report` with up to 15 dimensions, up to 8 metrics, twelve filter operators, multi-column sorting and relative dates; `queue_cost_report` with `check_report_status` and `get_queued_report_results` for large runs
- Discovery: `get_available_measures` and `get_filter_operators`, plus `list_saved_cost_reports`
- Vendor account listings for AWS, Azure, GCP, IBM Cloud and OCI
Python 3.14+ and uv — clone the repository, run uv sync, and launch main.py. CLOUDABILITY_API_URL selects the region among US, EU, APAC and ME. Authentication is one of three: Frontdoor API keys in CLOUDABILITY_KEY_ACCESS and CLOUDABILITY_KEY_SECRET, which lets the server acquire tokens itself; a bearer token passed per call; or legacy basic auth. CLOUDABILITY_ENVIRONMENT_ID comes from your Access Administration environment, and CLOUDABILITY_DEFAULT_VIEW_ID is required for the container and cluster calls.
Build from source — clone the repository and build it, then point your client at the binary