---
title: "Storage used by an app"
method: POST
path: "/v1/files/usage"
tags: ["v1", "App Files"]
---

# Storage used by an app

`POST /v1/files/usage`

## Request

- Base URL: `https://memory.papr.ai`
- URL: `https://memory.papr.ai/v1/files/usage`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

## Request body

- UsageRequest
  - `app_id` string, required
  - `namespace_id` string, nullable

## Response `200`

Successful Response

- UsageResponse: Quota is org-wide; namespace_used_bytes is this namespace's share. ``quota_bytes`` is the whole subscription storage allowance. App files and Papr Memory share it, so clients should show ``total_used_bytes`` against the quota and use the two lanes for the breakdown. Without those fields a client sees app files measured against a limit Memory is also consuming, and cannot tell how much of the plan is actually left.
  - `used_bytes` integer, required
  - `reserved_bytes` integer
  - `quota_bytes` integer, required
  - `plan_tier` string
  - `enforcement_enabled` boolean
  - `organization_id` string, nullable
  - `namespace_used_bytes` integer
  - `memory_used_bytes` integer
  - `total_used_bytes` integer

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-16** `0e7a5c0d125d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/papr-ai/apis/papr-memory-api/changes/v1/files/usage/post.md)

---

[API](https://skmtc.dev/papr-ai/apis/papr-memory-api.md) - [All operations](https://skmtc.dev/papr-ai/apis/papr-memory-api/llms.txt) - [OpenAPI document](https://skmtc.dev/papr-ai/apis/papr-memory-api/revisions/6fc381dc78b3?raw)
