---
title: "view: usage"
description: "a tenant, a kind, a provider, a window to quantity and cost by kind, by tenant, by provider and by period, with each provider's reconciliation state"
section: reference
address: /reference/view/usage
contract: 0476e35e6e275db5
---

# view: usage

a tenant, a kind, a provider, a window to quantity and cost by kind, by tenant, by provider and by period, with each provider's reconciliation state

[figure: The caller sends UsageInput to /v1/view/usage. The platform returns a card whose body is UsageReport.]

<span class="op-method">POST</span><span class="op-path">/v1/view/usage</span>

Read usage. The call needs the tenant rung under a token with the read grant, and it is served by the platform.

The route takes [UsageInput](/concepts/usageinput) and returns a card whose body is [UsageReport](/concepts/usagereport).



## Request body
The request body is [UsageInput](/concepts/usageinput).



| field | type | required | note |
|---|---|---|---|
| `tenant` | `id` | no |  |
| `kind` | [KindOfUsage](/concepts/kindofusage) | no |  |
| `provider` | `text` | no |  |
| `window` | [Window](/concepts/window) | yes |  |



## Response
The route returns a card whose body is [UsageReport](/concepts/usagereport). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the tenant rung and a token with the read grant. The platform serves this route.

## Example
The example sends the smallest body that UsageInput allows. The build validates it against the schema of UsageInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/view/usage \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "window": { "from": "…", "to": "…" } }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.view.usage({
    "window": {
      "from": "…",
      "to": "…"
    }
  });
// answer.body is a UsageReport. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/view/usage",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "window": {
        "from": "…",
        "to": "…"
      }
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/view/usage")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&UsageInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.view.usage` takes the same input and returns the same card. The tool only reads data. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/UsageReport`. The [tool's page](/reference/tools/si-view-usage) describes it.
