# UsageDailyPoint

```ts
type UsageDailyPoint = {
  bytesStored: number;
  date: string;
  deletes: number;
  lists: number;
  processes: number;
  reads: number;
  videoEncodes: number;
  videoMinutes: number;
  writes: number;
};
```

Defined in: packages/sdk/src/index.ts:1354

⚠️ REMOVED 2026-08-17: `bytesIn` on `UsageWindow`/`UsageDailyPoint` and
`bytesTotal` on `UsagePerKey`.

All three were structurally zero: the field behind them was never populated,
on any row. They could not be instrumented in place either — uploads go to
object storage through presigned URLs, so the payload never passes through
the API, and the only figure measurable there is a JSON envelope of a few
hundred bytes.

A field that always reads `0` is worse than an absent field, because absent
is honest — a `0` next to a real `storage.totalBytes` reads as a measurement.
The byte number that IS true is still served: `storage.totalBytes`.

## Properties

### bytesStored

```ts
bytesStored: number;
```

Defined in: packages/sdk/src/index.ts:1361

***

### date

```ts
date: string;
```

Defined in: packages/sdk/src/index.ts:1355

***

### deletes

```ts
deletes: number;
```

Defined in: packages/sdk/src/index.ts:1359

***

### lists

```ts
lists: number;
```

Defined in: packages/sdk/src/index.ts:1358

***

### processes

```ts
processes: number;
```

Defined in: packages/sdk/src/index.ts:1360

***

### reads

```ts
reads: number;
```

Defined in: packages/sdk/src/index.ts:1356

***

### videoEncodes

```ts
videoEncodes: number;
```

Defined in: packages/sdk/src/index.ts:1364

***

### videoMinutes

```ts
videoMinutes: number;
```

Defined in: packages/sdk/src/index.ts:1363

See `UsageWindow.videoMinutes`. Minutes transcoded on this day.

***

### writes

```ts
writes: number;
```

Defined in: packages/sdk/src/index.ts:1357