---
name: cloud-and-costs
description: >-
  Look up cloud servers, domains, DNS, cloud access grants and every kind
  of cost in Helix (cloud spend, AI/API-key spend, software costs, my
  attributed cost). Use when the user mentions 云服务器/域名/DNS/云权限/
  成本/账单/花费/AI spending, asks who owns a server, or wants cost
  breakdowns and forecasts.
---

# Helix cloud & costs

Read `using-helix` first. Cost questions are answered by purpose-built
tools — never estimate money numbers from raw resource lists.

## Cloud resources (CMDB)

- Servers: `list_cloud_servers` / `get_cloud_server` (owner, scope,
  billing tags). Domains: `list_cloud_domains` / `get_cloud_domain`;
  registrar-level objects are `domains`, DNS records are separate:
  `list_dns_records`.
- Stats/overviews: `get_cmdb_stats`, `get_my_cmdb_analytics`,
  `get_cmdb_billing_summary`.
- Sync freshness: if data looks stale, check `get_cloud_sync_status` /
  `get_cloud_scope_last_sync_summary` before concluding anything is
  wrong.

## My cloud access

- `list_my_cloud_grants` — what I can reach and until when.
- New access: goes through a scope request (`list_my_cloud_scope_requests`
  to track). Grant history/timeline: `get_cloud_access_grant_timeline`.

## Cost & spend

| Question | Tool |
|---|---|
| 我花了多少 / 归到我头上的成本 | `finance_my_attributed_cost`, `finance_my_expenses` |
| 云成本拆解（按账号/服务/标签） | `cost_breakdown`, `cost_timeseries`, `cost_top_resources`, `cost_tag_keys` |
| 团队/下属成本 | `cost_subordinates_breakdown` (manager scope) |
| 异常与预测 | `cost_anomalies`, `cost_forecast` |
| AI / API-key 花费 | `ai_spending_overview`, `ai_spending_by_bu`, `ai_spending_movers`, `ai_spending_forecast`, `get_api_key_spend`, `get_api_key_spend_detail` |
| BU 口径 | `finance_bu_costs` (finance role), `finance_my_bu_costs` |

- Currency: Helix reports CNY and USD with a platform-wide FX rate;
  quote the currency the tool returns, never convert on your own.
- Cost data lags the provider by up to ~1-2 days; say so when the user
  asks about "today".

## Ownership questions

"这台服务器是谁的" → `get_cloud_server` (owner fields) and, for
attribution disputes, `cost_resolve_resource_creator`. Do not guess
owners from naming conventions.