internal

Raise Daily Cap

Raise a conglomerate's daily credit cap — the internal platform's only write.

The decision is core.billing.resolve_support_daily_cap — the same function margot_actions.raise_daily_cap calls, not a copy of it, so the two surfaces cannot drift: raise-only (never lowers), never re-imposes a finite cap on an unlimited (0) conglomerate, clamped to SUPPORT_DAILY_CAP_CEILING, and a non-finite ask (NaN/±inf, which would defeat every comparison and land an uncapped row) resolves to no change. Worst case for a compromised internal service is therefore nudging a 24h rate limit up to the ceiling — real spend stays bounded by the credit balance.

clamped flags an ask above the ceiling so the caller can offer a human. changed reflects the value actually persisted, so it is False for every no-op. Unknown conglomerate → 404.

post/internal/service/raise_daily_cap

Request body

conglomerate_idstring uuid required

The conglomerate whose daily credit cap to raise.

target_daily_creditsnumber nullable

Desired new daily credit cap. Omit to bump by a default step. Clamped to the support ceiling; never lowers the cap or sets it unlimited.

Response

Successful Response

changedboolean required
clampedboolean required
previous_max_daily_creditsnumber required
max_daily_creditsnumber required
ceilingnumber required

Changes

No recorded changes to this endpoint across all 1 revision of this API.