Set or remove one org member's monthly mu spending limit
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.
Request
- Base URL: https://api.mnemom.ai/v1
- URL: https://api.mnemom.ai/v1/mu/member-budgets
- Auth: HTTP bearer
Query parameters
Target org id. REQUIRED — a mu write never falls back to the caller's primary org. A non-member, or a member outside owner/admin, is denied 403.
Request body
Response
Limit set or removed. {budget: <mnemom-billing Budget row>}.
Changes
No recorded changes to this operation across all 1 revision of this API.