# modal.billing | Modal Docs

- **URL:** https://modal.com/docs/sdk/py/latest/modal.billing
- **Summary:** BillingReportItem(object_id: str, description: str, environment_name: str, interval_start: datetime.datetime, cost: decimal.Decimal, cost_by_resource: dictstr, decimal.Decimal, tags: dictstr, str)

Copy page

modal.billing
=============

modal.billing.BillingReportItem 

    class BillingReportItem(object)

BillingReportItem(object_id: str, description: str, environment_name: str, interval_start: datetime.datetime, cost: decimal.Decimal, cost_by_resource: dict\[str, decimal.Decimal\], tags: dict\[str, str\])

    __init__(self, object_id, description, environment_name, interval_start, cost,
        cost_by_resource, tags)

### keys 

    keys(self)

mdmd:ignore

### values 

    values(self)

mdmd:ignore

### items 

    items(self)

mdmd:ignore

modal.billing.WorkspaceBillingReportItem 

    class WorkspaceBillingReportItem(TypedDict):
        object_id: str
        description: str
        environment_name: str
        interval_start: datetime.datetime
        cost: decimal.Decimal
        tags: dict[str, str]

modal.billing.workspace_billing_report 

    workspace_billing_report(*, start, end=None, resolution="d", tag_names=None,
        client=None)

Generate a tabular report of workspace usage by object and time.

The result will be a list of dictionaries for each interval (determined by `resolution`) between the `start` and `end` limits. The dictionary represents a single Modal object that billing can be attributed to (e.g., an App) along with metadata (including user-defined tags) for identifying that object. The dictionary also contains a breakdown of the cost value attributed to individual resources (for an App, this can be CPU, Memory, specific GPU types, etc.). The specific resource types included in the breakdown are subject to change as Modal’s billing model evolves.

The `start` and `end` parameters are required to either have a UTC timezone or to be timezone-naive (which will be interpreted as UTC times). The timestamps in the result will be in UTC. Cost will be reported for full intervals, even if the provided `start` or `end` parameters are partial: `start` will be rounded to the beginning of its interval, while partial `end` intervals will be excluded.

Additional user-provided metadata can be included in the report if the objects have tags and `tag_names` (i.e., keys) are specified in the request. Alternatively, pass `tag_names=["*"]` to include all tags in the report. Note that tags will be attributed to the entire interval even if they were added or removed at some point within it. If the tag name was not in use during an interval, it will be absent from the tags dictionary in that output row.

It’s also possible to generate reports using the [`modal billing report`](https://modal.com/docs/cli/latest/billing)
 CLI command. The CLI has a few convenience features for generating reports across relative time ranges.

[modal.billing](https://modal.com/docs/sdk/py/latest/modal.billing#modalbilling)
[BillingReportItem](https://modal.com/docs/sdk/py/latest/modal.billing#modalbillingbillingreportitem)
[keys](https://modal.com/docs/sdk/py/latest/modal.billing#keys)
[values](https://modal.com/docs/sdk/py/latest/modal.billing#values)
[items](https://modal.com/docs/sdk/py/latest/modal.billing#items)
[WorkspaceBillingReportItem](https://modal.com/docs/sdk/py/latest/modal.billing#modalbillingworkspacebillingreportitem)
[workspace_billing_report](https://modal.com/docs/sdk/py/latest/modal.billing#modalbillingworkspace_billing_report)