Provision isolated access per sandbox

The job: a controlplane creates an environment - a sandbox, a container, a customer appliance - and each one needs its own reachable, isolated entry point. Not one shared endpoint with routing, but a separate set of ngrok resources per workload, created and destroyed with it.

This differs from expose-localhost in lifecycle and trust. There, a developer exposes their own machine and trusts themselves. Here, a platform exposes someone else's workload, at machine speed, and must assume the code inside it is hostile.

Before you start

You need an ngrok API key (not an agent authtoken) in the controlplane. See ngrok-setup. The provisioning calls are documented in ngrok-surfaces (ngrok-surfaces/references/api.md and ngrok-surfaces/references/api-resources.md); this skill is the recipe, those are the mechanics.

The shape