Skip to content

Start building

Integration · Developer

AI agents for ngrok

See and manage what an ngrok account puts online: list endpoints.

Actions
9
Read
4
Write
5

Actions

What your agents can do in ngrok

See and manage what an ngrok account puts online: list endpoints (their public URLs and where they forward), online agent sessions and reserved domains, create a cloud endpoint with a traffic policy, reserve a domain, stop or restart an agent, and delete endpoints, with an ngrok API key.

Read 4

Look things up. Nothing changes.

  • List endpoints

    Lists the account's active endpoints: agent endpoints (a running ngrok agent serving a public URL) and cloud endpoints.

  • Get an endpoint

    Reads one endpoint by ID: its public url, protocol, type, the local address it forwards to, its traffic_policy, bindings, the agent session serving it and its description and metadata.

  • List agent sessions

    Lists the ngrok agents online now (tunnel sessions), as tunnel_sessions: each with its id, agent_version, os, source ip, region, metadata, started_at and the credential it used.

  • List reserved domains

    Lists the account's reserved domains, as reserved_domains.

Write 5

Create, change or send.

  • Create a cloud endpoint

    Creates a cloud endpoint: a public URL (on a reserved domain or an ngrok-owned one) that lives in ngrok's network without an agent, whose traffic policy.

  • Delete a cloud endpointDeletes data

    Deletes a cloud endpoint: its URL stops answering.

  • Stop an agent sessionDeletes data

    Tells the ngrok agent that started a tunnel session to exit: its endpoints go offline until someone starts the agent again.

  • Restart an agent session

    Tells an ngrok agent to restart itself (not supported on Windows); it reconnects with a new session ID and serves its endpoints again.

  • Reserve a domain

    Reserves a domain for the account: an ngrok subdomain (like acme-api.ngrok.app) or your own hostname, which then needs the returned cname_target set as a CNAME in your DNS.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your ngrok account.

What you enter

  • API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your ngrok data

    Ask a question in plain words. The agent can list endpoints, get an endpoint or list agent sessions in ngrok, then answers with what it found.

  • 02

    Let an agent update ngrok

    Have the agent create a cloud endpoint or restart an agent session in ngrok as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent ngrok and Slack: it can list endpoints in ngrok and post a summary to a Slack channel in the same run.

FAQ

ngrok and MyDeepAgents

Can MyDeepAgents connect to ngrok?

Yes. The ngrok connector has 9 actions: 4 read and 5 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect ngrok?

Paste an API key from your ngrok account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in ngrok without asking?

Only if you let it. Each of the 5 actions that change data can be set to wait for a person's approval before it runs, and the 2 that delete data ask first by default.

Can I use ngrok in workflows as well as agents?

Yes. Every ngrok action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put ngrok to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.