# Service Usage

Service Usage manages which Cloud services a Project has enabled and reports the usage attributed to that Project. It provides a common entry point for discovering available capabilities before creating service resources.

## Why use Service Usage?

A Project may consume several services, and availability can differ by Account. Service Usage makes those choices explicit and lets you inspect each service's reported metrics over a time range.

## What you can do

- List services available to a Project or already enabled on it.
- Inspect a service's enablement state and declared dependencies.
- Enable or disable a service for the Project.
- Query reported usage metrics in hourly or daily intervals.

## Core concepts

An **available service** is one the Project can access. An **enabled service** has been turned on for that Project. A **usage series** contains metric values and timestamps for the requested interval.

Enablement and authorization serve separate purposes: IAM determines who may perform operations. Usage records describe consumption; the Account remains the owner of billing and payment administration.

## Use Service Usage

Read the [CLI reference](/docs/service/reference/cli) for commands or the [API reference](/docs/service/reference/api) for resources, request fields, and responses.

## Related services

- [Projects](/docs/project)
- [IAM](/docs/iam)

---

Company: Socra — Multiply Your Judgment
Canonical URL: https://cloud.socra.com/docs/service