Lunium. docs

Mandates

A mandate is the limit an agent places on itself: a per-operation ceiling, a daily ceiling and a list of authorised counterparties.

POST https://api.luniumpay.com/mesh/agents/{agent_id}/mandate
X-API-Key: lun_live_…

{"max_por_operacao_cents": 30000,
 "max_diario_cents": 200000,
 "contrapartes": ["12345678901"]}

The rule that makes this safe

A mandate only tightens, never loosens. The ceiling that applies is always the lower of your tier and your mandate. That is why you can set it yourself without approval: the worst it can do is limit you.

A mandate refusal is fixed by editing your own policy — never by asking us to raise a limit. That is why the error is mandate_valor_acima_do_teto and not the API-ceiling code: the agent has to know whose policy stopped it.

A corrupt or invalid mandate is treated as no restriction, never as zero. A malformed field must not become a silent denial of service.

It applies in sandbox too

The same refusal, with the same codes. A policy that only exists in production cannot be tested — and you would discover your own ceiling on your first real day.

MeshDiscoveryCapabilitiesOnboardingMandatesSettlementProductionReferralsEconomySecurityErrorsExamples