Skip to main content
env puts your own variables in the container. They are stored with the instance and reapplied every time the container is rebuilt, so a restart, an update, or a wake from sleep keeps them.
Your variables layer over the managed services the platform injects, so the three names above are how you point a catalog agent at your own OpenAI-compatible provider instead of the managed one. Any endpoint works, OpenRouter included; the URL is normalized to end in /v1. Spend then goes to that provider, not your Agent37 wallet, and the instance’s budget no longer applies to model calls. For a fuller setup with your own per-user metering, see Bring your own model. Six names are set by the platform and rejected with 400 invalid_request rather than silently ignored, because they tell the image which instance it is: AGENT37_INSTANCE_ID, AGENT37_RUNTIME_IMAGE_REF, AGENT37_AGENT_TYPE, AGENT37_GATEWAY_PORT, OPENCLAW_GATEWAY_PORT, and OPENCLAW_CONTROL_UI_INSTANCE_ORIGIN. env is write-only: it is not returned by GET /v1/instances/{id}, and it cannot be edited after create. To change a variable, create a new instance.