---
title: "Read the caller's org mu ledger entries"
method: GET
path: "/billing/mu/ledger"
tags: ["Mu"]
---

# Read the caller's org mu ledger entries

`GET /billing/mu/ledger`

## Request

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

The customer's own mu account statement: every ledger entry (grant / hold / settle / release / burn / refund / adjustment) with its `lot_allocations` provenance and entry hash. This is what makes purchase RECEIPTS and itemized usage possible — a balance without it is a number with no explanation behind it. Identical org-context + RBAC discipline to `GET /billing/mu`: RBAC is enforced before any read, and the account id is the SERVER-RESOLVED `billing_account_id`, never client-supplied (a NULL one is 409, matching the balance route rather than falling back to a personal account the way the internal resolver does). `cursor` / `from` / `to` / `limit` pass through verbatim to the frozen mnemom-mu upstream `GET /v1/accounts/{accountId}/ledger`, which bounds `limit` itself (default 100, max 500). Read-only by construction: api presents its own `mu:check` service key, which carries no spend or grant scope. 503 when the mnemom-mu binding/URL is unconfigured (fail-closed).

## Query parameters

- `org_id` string
- `cursor` string
- `from` string, date-time
- `to` string, date-time
- `limit` integer
- `product` 'research' | 'design' | 'develop' | 'operate' | 'canon' | 'unattributed' | 'all'

## Response `200`

A page of ledger entries plus `nextCursor` (mnemom-mu response, passed through verbatim unless `product` is supplied).

- 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)