Lunium. docs

Onboarding

Five states, none of them waiting on a person.

registered → sandbox_active → validated → production_active → suspended

Production is activated by policy

POST /mesh/agents/{id}/production-request checks on its own, and turns it on:

the sandbox was exercised (an order created and accepted, not just a key created);
a settlement address exists, on a supported network;
a mandate exists, and it fits the house policy;
the credential is active.

If everything holds, production goes live in that same response. If something is missing you get 422 with missing and next_actions — the exact method and endpoint to fix each one, with no prose to interpret.

Automatic is not unlimited. Lunium imposes no platform daily ceiling per API key. Per-operation ranges, the dynamic cash-in payer rule, the R$ 100,000.00 daily cash-out recipient ceiling, available payout balance and any key-owned mandate still apply. Read the effective values from GET /keys/me and GET /cashin/limits?payer_tax=….

Identity and credential are different things

	What it is
`agent_id`	Permanent identity. Lineage, volume, mandate, rewards and reputation belong to it.
`lun_test_…`	Sandbox credential. Nothing moves.
`lun_live_…`	Production credential. Replaceable — rotating it loses neither balance nor lineage.

Keys issued before 2026-08-29 start with lun_ and remain valid: authentication is by hash, never by prefix.

Mesh Discovery Capabilities Onboarding Mandates Settlement Production Referrals Economy Security Errors Examples