---
title: "Set or remove one org member's monthly mu spending limit"
method: POST
path: "/mu/member-budgets"
tags: ["Mu"]
---

# Set or remove one org member's monthly mu spending limit

`POST /mu/member-budgets`

## Request

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

Allocates spend authority out of the org's shared mu pool by setting ONE member's monthly hard cap (a `user`-scoped budget row), or removes it. This is how an org admin 'distributes' mu to their team: mu is a closed-loop instrument that is neither cash-redeemable nor transferable between accounts, and there is no member-level ledger account — one org, one balance — so per-member control is a cap, never a balance move. Owner/admin of the target org only; every other role, and any caller who is not a member of `org_id`, is denied 403. `org_id` is REQUIRED (no primary-org fallback: a write must never land on a different tenant than the admin is looking at). api resolves the org's `billing_account_id` server-side from the proven membership and authors the upstream `POST /v1/budgets` body itself; client-supplied `account`, `accountId`, `actor`, `cell`, `scopeType`, `scopeRef` or soft-cap fields are rejected 400 rather than ignored. The `userId` being capped must itself be a member of the same org (else 404). Presents api's budget-scoped identity (`MU_BUDGET_SERVICE_TOKEN`), never the grant-capable admin token; unset ⇒ 503 fail-closed.

## Query parameters

- `org_id` string, required

## Request body

- object
  - `userId` string, required: The org member whose limit is being set. Must be a member of `org_id`.
  - `hardCapMmuPerMonth` string, nullable, required: Monthly hard cap in millimu as a whole-number string (billing casts it to bigint, so it is not sent as a JSON number). `"0"` is a real setting — this member may spend nothing this month — and is deliberately distinct from `null`, which REMOVES the limit. The field is required: a missing field is a 400, never a silent removal.

## Response `200`

Limit set or removed. `{budget: <mnemom-billing Budget row>}`.

- object
  - `budget` 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)