OpenRouter Details Sticky Containers, Network Controls, and Pricing for Hosted Code Execution

Key Info

OpenRouter is rolling out hosted Linux containers for code execution on any model, and this post details container reuse, network isolation, and pricing.

Highlights

• Containers are sticky: reuse one by including the last shell result in the next request, or set environment to container_reference with a container_id to keep files.
• Outbound network is off by default; you can enable it per run via network_policy, such as an allowlist of specific URLs.
• Sandbox time costs $0.0001 per active second, with inference billed separately.