# Costory Documentation

## Docs

- [Welcome to Costory](https://docs.costory.io/get-started/welcome.md): Cloud cost reporting for DevOps: connect AWS, GCP, and Azure billing, use Costory MCP with Claude or Cursor, and automate FinOps updates.
- [Quickstart: How to set up automated cloud cost reporting in 30 minutes](https://docs.costory.io/get-started/quickstart.md): Step-by-step guide to connect AWS, GCP, Azure and Datadog to Costory. Set up automated FinOps Slack & Teams cost reports in 30 minutes, free trial included.
- [Billing Data](https://docs.costory.io/setup/billing.md): Set up cloud billing data sources in Costory via Terraform or manual configuration. Supports AWS CUR 2.0, GCP BigQuery, Azure Cost Management, Snowflake, and SaaS providers.
- [AWS Billing Setup](https://docs.costory.io/setup/billing/aws.md): Connect AWS CUR 2.0 billing data to Costory via CloudFormation, manual setup, or Terraform.
- [GCP Billing Setup](https://docs.costory.io/setup/billing/gcp.md): Connect GCP BigQuery billing export with detailed usage costs to Costory via Terraform or manual setup.
- [Azure Billing Setup](https://docs.costory.io/setup/billing/azure.md): Connect Azure Cost Management exports to Costory via Terraform or manual setup.
- [Custom Billing Format (FOCUS) in BigQuery](https://docs.costory.io/setup/billing/focus.md): Import any FOCUS-compliant billing data from a BigQuery table into Costory.
- [Confluent Billing Setup](https://docs.costory.io/setup/billing/confluent.md): Connect Confluent Cloud billing data to Costory.
- [Aiven Billing Setup](https://docs.costory.io/setup/billing/aiven.md): Connect Aiven billing data to Costory via the Aiven Billing API.
- [Cursor Billing Setup](https://docs.costory.io/setup/billing/cursor.md): Connect Cursor usage and billing data to Costory via Admin API key or Terraform.
- [Anthropic Billing Setup](https://docs.costory.io/setup/billing/anthropic.md): Connect Anthropic API and subscription billing data to Costory via Admin API key or Terraform.
- [GCP CUD Metadata](https://docs.costory.io/setup/billing/gcp-cud-metadata.md): Import GCP Committed Use Discount metadata from BigQuery into Costory.
- [Datadog Billing Setup](https://docs.costory.io/setup/billing/datadog.md): Connect Datadog usage and billing estimates to Costory.
- [Elastic Cloud Billing Setup](https://docs.costory.io/setup/billing/elastic-cloud.md): Connect Elastic Cloud organization billing to Costory with an Organization API key. Covers setup, historical sync, and what cost grain and dimensions you get in Explorer.
- [Snowflake Billing Setup](https://docs.costory.io/setup/billing/snowflake.md): Connect Snowflake account usage and billing data to Costory using key-pair authentication and a reusable Snowflake integration.
- [ClickHouse Billing Setup](https://docs.costory.io/setup/billing/clickhouse.md): Connect ClickHouse Cloud billing data to Costory to analyze compute, storage, and data transfer costs.
- [Correlate your costs with technical or business metrics](https://docs.costory.io/setup/usage-metrics.md): Link costs to technical or business metrics
- [CSV](https://docs.costory.io/setup/usage-metrics/csv.md): Upload usage metrics as a flat or columnar CSV file in Costory
- [Google Sheet](https://docs.costory.io/setup/usage-metrics/google-sheet.md): Sync usage metrics directly from a Google Sheet into Costory
- [Datadog](https://docs.costory.io/setup/usage-metrics/datadog.md): Query Datadog metrics with rollups and import them into Costory
- [Datadog CI Visibility](https://docs.costory.io/setup/usage-metrics/datadog-ci.md): Pull CI visibility metrics from Datadog into Costory
- [BigQuery](https://docs.costory.io/setup/usage-metrics/bigquery.md): Import usage metrics from BigQuery tables into Costory for unit economics and shared cost allocation.
- [GCS Inventory (Parquet)](https://docs.costory.io/setup/usage-metrics/gcs-inventory.md): Use GCS inventory Parquet exports as usage metrics in Costory
- [Amplitude](https://docs.costory.io/setup/usage-metrics/amplitude.md): Bring product analytics metrics from Amplitude into Costory
- [Parquet file (AWS S3)](https://docs.costory.io/setup/usage-metrics/s3-parquet.md): Import Parquet metrics files from AWS S3 into Costory
- [AWS CloudWatch](https://docs.costory.io/setup/usage-metrics/aws-cloudwatch.md): Connect AWS CloudWatch metrics to Costory and import custom usage metrics.
- [Tsuga](https://docs.costory.io/setup/usage-metrics/tsuga.md): Import metrics, logs, and traces from Tsuga into Costory
- [BigQuery Data Exports](https://docs.costory.io/setup/destinations/bigquery.md): Set up BigQuery data exports in Costory so analysts can query dashboard widget data from Looker, notebooks, dbt, and custom SQL.
- [Connect Engineering Events to Costory (GitHub, CI/CD, Custom API)](https://docs.costory.io/setup/events.md): Save the cause of a cost change as an event linked to a dashboard, and push deploy events from CI/CD so Costory's AI analysis knows what you shipped.
- [Connect GitHub Events](https://docs.costory.io/setup/events/github.md): Use the GitHub integration to capture deploys, PR merges, and releases as event markers in Costory.
- [Send Events from CI/CD Pipelines](https://docs.costory.io/setup/events/ci-cd.md): Post build and deploy events from your CI/CD pipelines to Costory using the Events API.
- [Send Custom Events via API](https://docs.costory.io/setup/events/custom-api.md): Send any event that explains cloud spend to Costory using the Events API and Python.
- [Provider Events](https://docs.costory.io/setup/events/provider.md): Automatically track AWS Savings Plans, Reserved Instances, marketplace renewals, and SKU price changes in Costory.
- [Slack](https://docs.costory.io/setup/collaboration/slack.md): Configure the Costory Slack integration to send scheduled cost reports and alerts to your Slack channels.
- [Microsoft Teams](https://docs.costory.io/setup/collaboration/teams.md): Configure the Costory Microsoft Teams integration to send scheduled reports and alerts to Teams channels.
- [Email](https://docs.costory.io/setup/collaboration/email.md): Configure email delivery in Costory for scheduled cloud cost reports and alert notifications.
- [FinOps MCP: Cloud Cost Automation for AI Assistants](https://docs.costory.io/features/mcp.md): Use the Costory FinOps MCP to query AWS, GCP, and Azure spend from Claude, Cursor, or VS Code. Investigate cost spikes, create alerts, and send Cost Reports via Model Context Protocol.
- [Explorer](https://docs.costory.io/features/cost-explorer.md): Use Costory Explorer to query AWS, GCP, and Azure costs with filters, group-bys, comparison periods, and saved context before turning the result into dashboards, alerts, reports, or MCP prompts.
- [Cloud Cost Dashboards](https://docs.costory.io/features/dashboards.md): Build cloud cost dashboards from Explorer queries to monitor AWS, GCP, and Azure spend, usage metrics, budgets, events, and FinOps KPIs in one place.
- [Create and Organize Dashboards](https://docs.costory.io/features/dashboards/create-dashboard.md): Create cloud cost dashboards from Explorer queries, add widgets manually, duplicate widgets, and organize dashboards with tags and teams.
- [Dashboard Templates](https://docs.costory.io/features/dashboards/templates.md): Use pre-built FinOps dashboard templates for executive cloud cost reporting, team showback, Savings Plan coverage, Kubernetes cost allocation, network costs, and storage optimization.
- [Dashboard Widgets and Chart Types](https://docs.costory.io/features/dashboards/widgets.md): Choose dashboard widgets and chart types for cloud cost dashboards, including bar charts, line charts, waterfall charts, doughnut charts, tables, KPI cards, budget trackers, and BigQuery SQL export.
- [Events](https://docs.costory.io/features/events.md): Overlay deploy events, Savings Plan purchases, provider changes, and saved business context on Costory cost charts to explain cloud cost changes.
- [Unit Economics](https://docs.costory.io/features/unit-economics.md): Build cloud unit economics in Costory Explorer by combining cloud cost metrics, usage metrics, and formulas such as cost per user, cost per API call, or ROI.
- [Tag & Allocate Cloud Costs](https://docs.costory.io/features/tagging.md): FinOps cost allocation made simple. Create dimensions, allocate untagged resources, and split shared costs across AWS, GCP, and Azure without touching your cloud console.
- [Dimensions](https://docs.costory.io/features/tagging/dimensions.md): Create cloud cost allocation dimensions that merge native AWS, GCP, and Azure tags, normalize values, and define rule-based virtual dimensions for team, product, or environment reporting.
- [Split Shared Infrastructure Costs Across Teams](https://docs.costory.io/features/tagging/shared-cost-allocation.md): Allocate shared cloud infrastructure costs like Cloud SQL, RDS, or network to teams based on actual usage metrics from Datadog, BigQuery, Snowflake, or Google Sheets.
- [Cost Reports](https://docs.costory.io/v2/Automate/reports.md): Schedule recurring cloud cost reports to Slack, Microsoft Teams, or email from a dashboard, widget, or Explorer view, in the UI, from chat, or via the API.
- [Cost Digest: automate your FinOps reporting](https://docs.costory.io/features/digest.md): Automatically surface and triage the cloud cost changes that matter for FinOps reporting. Digest ranks every significant cost shift by dollar impact and generates AI incident reports with root cause analysis.
- [Quick Share](https://docs.costory.io/features/dashboards/quickshare.md): Share a Costory dashboard or dashboard widget with a public link for ad-hoc cloud cost collaboration in Slack, Microsoft Teams, pull requests, or incident threads.
- [Alerts](https://docs.costory.io/features/alerts.md): Monitor cloud spend and custom formulas against a single trigger condition. Build alerts in the UI or through the Costory MCP with the same condition string, then get notified in Slack, Teams, or email.
- [Teams](https://docs.costory.io/features/teams.md): Scope cloud costs, default metrics, and dashboards per team so every stakeholder sees the data that matters to them.
- [Cloud Cost Budgets and Budget Alerts](https://docs.costory.io/features/budgets.md): Create monthly cloud cost budgets by team, track versions, and trigger Slack or email budget alerts before overruns.
- [Cost Metrics](https://docs.costory.io/docs/cost-metrics.md): How we compute the different metrics on top of your billing data
- [Contracted Cost vs Billed Cost: Savings Plan discount sharing issues](https://docs.costory.io/docs/savings-plan-cost-fluctuation.md): Learn why Contracted Cost gives platform and engineering teams a stable, usage-driven view of AWS and GCP cloud spending, avoiding misleading Savings Plan cost fluctuations.
- [Cloud Cost Currency Conversion](https://docs.costory.io/docs/currency-conversion.md): Cloud cost currency conversion and reporting currency rules for AWS, GCP, Azure, and Datadog in Costory.
- [Standard Columns](https://docs.costory.io/docs/standard-columns.md): Costory normalizes billing data from AWS, GCP, Azure, Datadog, and Elastic Cloud into a unified schema. Here is how each column is populated per provider.
- [Billing Data Refresh Schedule and Cloud Cost Data Freshness](https://docs.costory.io/docs/data-refresh.md): Costory's billing data refresh schedule, including the monthly refresh window and AWS/GCP billing data freshness.
- [Settings](https://docs.costory.io/get-started/settings.md): Find Costory settings, account settings, organization settings, Teams, data integrations, API keys, subscription, plans, and invoices.
- [Identity and Access](https://docs.costory.io/docs/sso-access-control.md): Compare Costory identity and access options across Copilot and Copilot Pro, including auto-join, single sign-on, directory sync, role-based access control, and security scope.
- [Glossary](https://docs.costory.io/docs/glossary.md): Definitions for FinOps, cloud billing, and Costory-specific terms used throughout this documentation
- [Overview](https://docs.costory.io/use-cases/overview.md): Explore practical guides to get the most out of Costory
- [LLM Cost Allocation: Track AI Spend by Team, Feature, and Customer](https://docs.costory.io/use-cases/llm-ai-cost.md): Allocate and track LLM costs from Anthropic, OpenAI, Azure OpenAI, AWS Bedrock, GCP Vertex, and Mistral across teams and features. Learn cost per token attribution, showback, and chargeback strategies for shared API keys.
- [Hourly Granularity for Bursty Workloads](https://docs.costory.io/use-cases/hourly-cost-granularity.md): Use hourly cloud cost granularity to measure bursty workloads, price each event, and connect optimization work to per-event cost.
- [AWS EKS Cost Allocation](https://docs.costory.io/use-cases/eks-cost-allocation.md): Compare EKS cost allocation methods for Kubernetes cost visibility, including AWS Split Cost Allocation, AWS-managed usage metrics, and Kubecost or OpenCost.
- [Kubernetes Cost Visibility: Measure Waste, Allocate Costs, Reduce Over-Provisioning](https://docs.costory.io/use-cases/k8s_waste/visibility.md): Kubernetes cost visibility for granular insight into waste, over-provisioned resources, and cost reallocation across teams
- [Increase visibility on your BigQuery costs with dbt](https://docs.costory.io/use-cases/dbt_bigquery_visibility/increase_visibility.md): Track and allocate BigQuery processing and storage costs at the dbt model level using labels, then visualize them in Costory.
- [Split Shared API Costs Across Teams Using Usage Metrics](https://docs.costory.io/use-cases/reallocate_api_costs.md): Allocate untagged or shared API costs to the right teams based on actual usage data. This guide walks you through usage-based shared cost allocation with Costory, from importing an external metric to building a reusable chargeback model.
- [Allocate the cost of a shared Cloud SQL database to the teams using it](https://docs.costory.io/use-cases/allocate_shared_cloud_sql_database/allocate.md): Use Costory's virtual dimensions and usage metrics to split a shared Cloud SQL database cost across consuming teams, based on actual storage or compute usage.
- [Automated env allocation](https://docs.costory.io/use-cases/automated_env_allocation/visibility.md): How to easily allocate your costs per environment using all the metadatas available in your billing data
- [Event Correlations](https://docs.costory.io/automate-reporting/event-correlation.md): Connect cost spikes to the events that caused them
- [Correlate Cloud Costs with Active Users Using Amplitude](https://docs.costory.io/use-cases/amplitude/cost_per_active_users.md): Understand whether your cloud costs scale with your business. Connect Amplitude active users to Costory and track cost per thousand users over time.
- [Track Unit Economics to Justify Cloud Cost Increases](https://docs.costory.io/automate-reporting/unit-economics.md): Link cloud cost increases to business growth by importing usage metrics into Costory and building unit economics formulas. Defend scaling decisions with data.
- [Cloud budget management: define and automate cloud budgets](https://docs.costory.io/use-cases/automate_budget.md): Learn how to set up cloud budget management per team with automated alerts, monthly reports, and FinOps budgeting best practices.
- [Share the correct cost for each persona](https://docs.costory.io/use-cases/show_the_correct_cost_metric_to_each_persona.md): Learn how to share the correct cost for each persona
- [Show the correct metrics to your exec team](https://docs.costory.io/use-cases/what_your_exec_team_wants/value.md): Learn how to show the correct metrics to your exec team
- [Automate Monthly Cloud Cost Reporting](https://docs.costory.io/automate-reporting/monthly-reviews.md): Stop spending hours building monthly cloud cost reports. Use a Cost digest inside Costory Reports to generate executive summaries, root-cause analyses, and shareable Slack or email digests.
- [Decentralize FinOps with Per-Team Cost Reports](https://docs.costory.io/automate-reporting/decentralize-finops.md): Scale cost visibility across engineering teams by scoping automated reports to each squad. Deliver cloud cost insights via Slack, Teams, or email, no billing console access needed.
- [API overview](https://docs.costory.io/api-reference/overview.md): Authenticate and call the Costory HTTP API. Use a bearer token from the Costory app for every request.
- [Query Costs API](https://docs.costory.io/api-reference/queries/overview.md): Run Costory Explorer cost queries over HTTP. Filter with CEL, group by dimensions, compare periods, and pull the same series the app and MCP use.
- [Run a cost query](https://docs.costory.io/api-reference/queries/run-a-cost-query.md): Executes a CEL query and returns either a time series (`kind: series`) or a period-over-period comparison (`kind: comparison`) when `compare.enabled` is true. Organization comes from the authenticated principal (Clerk session JWT or `ak_*` API key). When `datePreset` is sent alongside `from`/`to`, t…
- [Run a cost-change diff tree](https://docs.costory.io/api-reference/queries/run-a-cost-change-diff-tree.md): Returns a `GROUP BY ROLLUP` tree of current vs previous cost per node for exactly one `cost` or `usage` series. Requires an enabled comparison period, a non-hourly `aggBy`, and at least one `groupBy` axis on that series. Pre-condition failures return `400 INVALID_QUERY` with today's message in `reas…
- [List queryable dimensions](https://docs.costory.io/api-reference/queries/list-queryable-dimensions.md): Group-by axes and their values accepted by `groupBy` on cost/usage/metric series. Strict public shape — no react-querybuilder filter-widget fields.
- [List business metrics](https://docs.costory.io/api-reference/queries/list-business-metrics.md): Business `metricId` values accepted by `metric` series, grouped by datasource. `status` is a stored value and is not refreshed on read for API-key callers.
- [List usage metrics](https://docs.costory.io/api-reference/queries/list-usage-metrics.md): Usage `metricId` values (and units) accepted by `usage` series.
- [Reports API](https://docs.costory.io/api-reference/reports/overview.md): Create, schedule, preview, and run Costory cost reports over HTTP. The same API powers scheduling from the UI and from chat via the Costory MCP.
- [Create a report](https://docs.costory.io/api-reference/reports/create-a-report.md): Creates a report. Rules not captured by the field types: at least one `destinations` entry is required; when `scheduledPeriod` is `WEEKLY`, `scheduledWeekday` (0=Sunday…6=Saturday) is required; EMAIL destinations must be a valid address (or `ALL_ACTIVE_USERS`); and a DIGEST widget rendered as a `tab…
- [List reports](https://docs.costory.io/api-reference/reports/list-reports.md): Returns reports visible to the authenticated user. Optional `recentExecutionsLimit` embeds recent execution rows per report.
- [Get a report](https://docs.costory.io/api-reference/reports/get-a-report.md)
- [Update a report](https://docs.costory.io/api-reference/reports/update-a-report.md): Partially updates a report; omitted fields are left unchanged. `widgets` and `destinations`, when provided, replace the existing lists wholesale. Same conditional rules as create apply: a WEEKLY cadence needs a `scheduledWeekday` (from this body or already stored), EMAIL destinations must be valid a…
- [Duplicate a report](https://docs.costory.io/api-reference/reports/duplicate-a-report.md)
- [Archive a report](https://docs.costory.io/api-reference/reports/archive-a-report.md): Soft-archives the report (sets `archivedAt`).
- [Run a report now](https://docs.costory.io/api-reference/reports/run-a-report-now.md): Enqueues and synchronously runs pending executions for every destination.
- [Send a test report](https://docs.costory.io/api-reference/reports/send-a-test-report.md)
- [Preview a report widget](https://docs.costory.io/api-reference/reports/preview-a-report-widget.md)
- [List cost and budget alerts](https://docs.costory.io/api-reference/alerts-v2/list-cost-and-budget-alerts.md): Returns the current Alerts V2 table payload. This camelCase route is the supported application contract; canonical public resource naming is a separate follow-up.
- [List alert templates](https://docs.costory.io/api-reference/alerts-v2/list-alert-templates.md)
- [Get an alert template](https://docs.costory.io/api-reference/alerts-v2/get-an-alert-template.md)
- [List budgets eligible for alerts](https://docs.costory.io/api-reference/alerts-v2/list-budgets-eligible-for-alerts.md)
- [Snooze an alert](https://docs.costory.io/api-reference/alerts-v2/snooze-an-alert.md)
- [Unsnooze an alert](https://docs.costory.io/api-reference/alerts-v2/unsnooze-an-alert.md)
- [Archive an alert](https://docs.costory.io/api-reference/alerts-v2/archive-an-alert.md)
- [Restore an alert](https://docs.costory.io/api-reference/alerts-v2/restore-an-alert.md)
- [Delete an archived alert](https://docs.costory.io/api-reference/alerts-v2/delete-an-archived-alert.md)
- [List cost alerts](https://docs.costory.io/api-reference/alerts-v2/list-cost-alerts.md)
- [Create a cost alert](https://docs.costory.io/api-reference/alerts-v2/create-a-cost-alert.md): Creates either a condition-based alert (`condition` plus `dedup`) or a legacy threshold-based alert. The example monitors production AWS compute spend using Costory dimensions.
- [Get cost alert destination options](https://docs.costory.io/api-reference/alerts-v2/get-cost-alert-destination-options.md)
- [Get cost alert editor data](https://docs.costory.io/api-reference/alerts-v2/get-cost-alert-editor-data.md)
- [Send a cost alert test notification](https://docs.costory.io/api-reference/alerts-v2/send-a-cost-alert-test-notification.md)
- [Update a cost alert](https://docs.costory.io/api-reference/alerts-v2/update-a-cost-alert.md)
- [Get cost alert widget data](https://docs.costory.io/api-reference/alerts-v2/get-cost-alert-widget-data.md)
- [Get cost alert firing history](https://docs.costory.io/api-reference/alerts-v2/get-cost-alert-firing-history.md)
- [Create a budget alert](https://docs.costory.io/api-reference/alerts-v2/create-a-budget-alert.md): Creates an alert for budget lines visible to the caller. Threshold percentages are ordered from highest severity to lowest.
- [Get budget alert destination options](https://docs.costory.io/api-reference/alerts-v2/get-budget-alert-destination-options.md)
- [Update a budget alert](https://docs.costory.io/api-reference/alerts-v2/update-a-budget-alert.md)
- [Send a budget alert test notification](https://docs.costory.io/api-reference/alerts-v2/send-a-budget-alert-test-notification.md)
- [List queryable dimensions](https://docs.costory.io/api-reference/dimensions/list-queryable-dimensions.md): Returns every dimension available to filter and group by today, with its values and supported operators. Served from the cached dimension list refreshed by the compute pipeline, so a dimension published moments ago may not appear yet.
- [Search dimension values](https://docs.costory.io/api-reference/dimensions/search-dimension-values.md): Full-text search across dimension names and their values. Unlike `GET /dimensions` this queries the billing warehouse live, so it is slower and costlier — use it for type-ahead, not to enumerate dimensions.
- [List label keys that could become dimensions](https://docs.costory.io/api-reference/dimensions/list-label-keys-that-could-become-dimensions.md): Label keys found in the billing data with the cost-allocation stats used to judge whether promoting them is worthwhile: the share of cost carrying the key, its values, a per-month cost series, and the month-over-month change. Property names are snake_case because they come straight from the billing…
- [Get published label transformations](https://docs.costory.io/api-reference/dimensions/get-published-label-transformations.md): The currently published label configuration: which source columns are merged into each engineered dimension and how their values are mapped. This is the live configuration, not a draft — the client holds label edits until it calls `POST /dimensions/publish`.
- [Publish pending dimension changes](https://docs.costory.io/api-reference/dimensions/publish-pending-dimension-changes.md): Promotes pending dimension changes: the label configuration supplied inline in `labels`, and every pending virtual-dimension draft in the organization. `scope` narrows the publish to labels or virtual dimensions only.
- [List usage metrics](https://docs.costory.io/api-reference/metrics/list-usage-metrics.md): Consumed units available for usage-based queries, with the services that report each unit.
- [Get a report execution](https://docs.costory.io/api-reference/reports/get-a-report-execution.md)
- [Retry a failed report execution](https://docs.costory.io/api-reference/reports/retry-a-failed-report-execution.md)
- [Transfer a rendered execution to new destinations](https://docs.costory.io/api-reference/reports/transfer-a-rendered-execution-to-new-destinations.md)
- [Send a test report delivery](https://docs.costory.io/api-reference/reports/send-a-test-report-delivery.md)
- [Preview digest summary markdown](https://docs.costory.io/api-reference/reports/preview-digest-summary-markdown.md)
- [Run a cost query](https://docs.costory.io/api-reference/query-costs/run-a-cost-query.md): Executes a CEL query and returns either a time series (`kind: series`) or a period-over-period comparison (`kind: comparison`) when `compare.enabled` is true. Organization comes from the authenticated principal (Clerk session JWT or `ak_*` API key). When `datePreset` is sent alongside `from`/`to`, t…
- [Run a cost-change diff tree](https://docs.costory.io/api-reference/query-costs/run-a-cost-change-diff-tree.md): Returns a `GROUP BY ROLLUP` tree of current vs previous cost per node for exactly one `cost` or `usage` series. Requires an enabled comparison period, a non-hourly `aggBy`, and at least one `groupBy` axis on that series. Pre-condition failures return `400 INVALID_QUERY` with today's message in `reas…
- [List queryable dimensions](https://docs.costory.io/api-reference/query-costs/list-queryable-dimensions.md): Group-by axes and their values accepted by `groupBy` on cost/usage/metric series. Strict public shape — no react-querybuilder filter-widget fields.
- [List usage metrics](https://docs.costory.io/api-reference/query-costs/list-usage-metrics.md): Usage `metricId` values (and units) accepted by `usage` series.
- [List business metrics](https://docs.costory.io/api-reference/query-costs/list-business-metrics.md): Business `metricId` values accepted by `metric` series, grouped by datasource. `status` is a stored value and is not refreshed on read for API-key callers.
- [Create a new event](https://docs.costory.io/api-reference/events/create-a-new-event.md): Endpoint to create a new event using public API.
- [Get event tags](https://docs.costory.io/api-reference/events/get-event-tags.md)
- [Get an event by ID](https://docs.costory.io/api-reference/events/get-an-event-by-id.md)
- [Update an event](https://docs.costory.io/api-reference/events/update-an-event.md)
- [Delete an event](https://docs.costory.io/api-reference/events/delete-an-event.md)
- [Aggregate events](https://docs.costory.io/api-reference/events/aggregate-events.md)
- [Create a new event](https://docs.costory.io/api-reference/events/create-a-new-event-1.md): Endpoint to create a new event from the internal API.
- [Get service account details](https://docs.costory.io/api-reference/admin/get-service-account-details.md): Returns service account information for the Admin API.
- [Create a billing datasource](https://docs.costory.io/api-reference/admin-billing-datasources/create-a-billing-datasource.md)
- [Get a billing datasource](https://docs.costory.io/api-reference/admin-billing-datasources/get-a-billing-datasource.md)
- [Archive a billing datasource](https://docs.costory.io/api-reference/admin-billing-datasources/archive-a-billing-datasource.md)
- [Validate billing datasource configuration](https://docs.costory.io/api-reference/admin-billing-datasources/validate-billing-datasource-configuration.md)
- [Create a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/create-a-metrics-datasource.md)
- [Validate metrics datasource configuration](https://docs.costory.io/api-reference/admin-metrics-datasources/validate-metrics-datasource-configuration.md)
- [Get a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/get-a-metrics-datasource.md)
- [Archive a metrics datasource](https://docs.costory.io/api-reference/admin-metrics-datasources/archive-a-metrics-datasource.md)
- [Update an AWS S3 v2 metrics datasource definition](https://docs.costory.io/api-reference/admin-metrics-datasources/update-an-aws-s3-v2-metrics-datasource-definition.md)
- [List teams in the organization via Admin API](https://docs.costory.io/api-reference/admin-teams/list-teams-in-the-organization-via-admin-api.md): Returns all non-archived teams for the authenticated organization (admin IAM — same list service as SPA `/teams`).
- [Create a team via Admin API](https://docs.costory.io/api-reference/admin-teams/create-a-team-via-admin-api.md)
- [Get a team via Admin API](https://docs.costory.io/api-reference/admin-teams/get-a-team-via-admin-api.md): The path parameter may be the team id or the team name (case-insensitive). Returns full team detail including members (with user) and pending invites.
- [Archive a team via Admin API](https://docs.costory.io/api-reference/admin-teams/archive-a-team-via-admin-api.md): The path parameter may be the team id or the team name (case-insensitive).
- [Update a team via Admin API](https://docs.costory.io/api-reference/admin-teams/update-a-team-via-admin-api.md): The path parameter may be the team id or the team name (case-insensitive).
- [Add a member to a team via Admin API](https://docs.costory.io/api-reference/admin-teams/add-a-member-to-a-team-via-admin-api.md): The path parameter may be the team id or the team name (case-insensitive).
- [Remove a member from a team via Admin API](https://docs.costory.io/api-reference/admin-teams/remove-a-member-from-a-team-via-admin-api.md): The path parameter may be the team id or the team name (case-insensitive).
- [Sync all members of a team via Admin API](https://docs.costory.io/api-reference/admin-teams/sync-all-members-of-a-team-via-admin-api.md): Replaces the full member list of a team. Existing members not in the payload are removed, new ones are added or invited. The path parameter may be the team id or the team name (case-insensitive).
- [Changelog](https://docs.costory.io/changelog.md): Product updates and announcements
- [ ](https://docs.costory.io/docs/finops-memes.md)

## OpenAPI Specs

- [openapi](https://docs.costory.io/api-reference/openapi.json)