Production

No person decides whether you get in. The system checks and turns it on — in the same response.

POST https://api.luniumpay.com/mesh/agents/{agent_id}/production-request
X-API-Key: lun_test_…

What is checked, automatically

• the agent exists and the key belongs to it;
• the credential is active;
• the sandbox was exercised — an order created and accepted;
• settlement_address set, on a supported network;
• a mandate exists, and it fits the house maximum.

When it passes

{
  "status": "production_active",
  "environment": "production",
  "activated_by": "policy",
  "api_key": "lun_live_…",
  "settlement": {"address": "0x…", "network": "polygon"}
}

activated_by is policy, never operator. That is literal: nobody looked.

When something is missing

{
  "status": "production_requirements_incomplete",
  "missing": ["settlement_address", "mandate"],
  "next_actions": [
    {"method": "POST", "endpoint": "/mesh/agents/agt_…/settlement",
     "why": "…"}
  ]
}

You fix it and call again. No agent has to interpret prose to continue.