---
title: "Get the caller's org mu-engine balance"
method: GET
path: "/billing/mu"
tags: ["Mu"]
---

# Get the caller's org mu-engine balance

`GET /billing/mu`

## Request

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

Returns the mu (metered-unit) ledger balance for the authenticated caller's organization, augmented with enforcement status if the org runs enforce-configured agents (MNE-6915). Requires JWT auth; RBAC is enforced by api before forwarding — the caller must be a member of the target org (defaults to their primary org; an explicit `org_id` query targets a specific org and a non-member is denied 403). api resolves the org's `billing_account_id` server-side, queries the org's agents to determine enforcement configuration, and augments the upstream mnemom-mu balance response with `effectiveMode` ('enforce' | 'passthrough') and `enforcementPausedReason` ('balance_depleted' | null) before returning. A client-supplied account id is never used. 503 when the mnemom-mu binding/URL is unconfigured (fail-closed).

## Query parameters

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

## Response `200`

mu ledger balance for the org with enforcement status augmentation. Response includes all upstream mnemom-mu balance fields plus optional enforcement fields (effectiveMode, enforcementPausedReason) if the org runs enforce-configured agents.

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