---
title: "Read the caller's org mnemom-native monthly usage statement"
method: GET
path: "/billing/mu/statement"
tags: ["Mu"]
---

# Read the caller's org mnemom-native monthly usage statement

`GET /billing/mu/statement`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/billing/mu/statement`
- Auth: HTTP bearer

The mnemom-NATIVE monthly usage statement for the authenticated caller's organization — the itemized statement mnemom itself produces from its OWN ledger (`mu_view_statement_lines`), independent of Stripe's hosted invoice PDF. This is what backs the first-party downloadable PDF/CSV: a customer can obtain a record of their metered usage even when they have no Stripe invoices at all (the common prepay case). Same org-context + RBAC discipline as `GET /billing/mu`: RBAC is enforced before any read, and the account id is the SERVER-RESOLVED `billing_account_id`, never client-supplied. `period` is a required `YYYY-MM` month. READ-ONLY by construction: api presents its own `mu:check` service key, which carries no spend or grant scope, and the statement is a pure projection of already-recorded usage — nothing is minted or mutated. Forwards to the frozen mnemom-billing upstream `GET /v1/accounts/{accountId}/statement`; the `{accountId, period, lines, totalUsd}` body is passed through verbatim. 503 when the mnemom-mu binding/URL is unconfigured (fail-closed).

## Query parameters

- `org_id` string
- `period` string, required
- `product` 'research' | 'design' | 'develop' | 'operate' | 'canon' | 'unattributed' | 'all'

## Response `200`

The native monthly statement (mnemom-billing response, passed through verbatim): `{accountId, period, lines, totalUsd}`.

- object

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.
- `502`: An upstream dependency returned an invalid response.
- `503`: An upstream dependency is currently unavailable. The request was not processed; retry after the cooldown window.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)