The ngrok engine: endpoints and Traffic Policy

Two decisions sit behind almost every ngrok task:

1. What kind of endpoint? Agent, cloud, or internal - and on what protocol.
2. What should happen to the traffic? The Traffic Policy that runs at the edge.

This skill answers both at the level a job skill needs, and holds the detail in references/. Where to apply the result is a separate question - see ngrok-surfaces.

Make these decisions from the user's intent. Do not ask them to choose an endpoint type; they should not have to know the taxonomy.

1. Endpoint type

• Agent endpoint - created by a running agent or SDK process, lives only as long as that process. Ephemeral, local, demos, tests.
• Cloud endpoint - created via API, dashboard, or IaC, independent of any agent. Always-on, stable URL. Production front doors, and anything a third party connects to on its own schedule.
• Internal endpoint - no public URL. Reachable only through a forward-internal action. This is how a receiver stays off the public internet.

The composed shape most jobs land on: