ngrok.ai valid

ngrok AI Gateway console

app.ngrok.ai is the authenticated console for the ngrok AI Gateway. Create and scope access keys, connect providers and self-hosted models, chat with models in a playground, watch per-request logs and spend, and manage prepaid credits.

For agents: Authenticated console for ngrok AI Gateway to manage access keys, connect model providers, test models, and review request logs and spend; sign-in required.

ai gatewayllm access keysmodel providersai request logsprepaid creditsself-hosted models

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T13:52:20.470Z. Cached copy · Source on ngrok.ai

# ngrok AI Gateway console

> app.ngrok.ai is the authenticated console for the ngrok AI Gateway. Create and scope access keys, connect providers and self-hosted models, chat with models in a playground, watch per-request logs and spend, and manage prepaid credits.

Important notes:

- Apart from signup and login, every console page requires a session; unauthenticated requests redirect to the ngrok login flow. The public documents on this host are this file, `/auth.md`, `/robots.txt`, and `/sitemap.xml`. How an agent gets and uses an AI Gateway credential is at https://ngrok.ai/auth.md.
- To automate what the console does, use the AI Gateway API at api.ngrok.ai instead of driving the UI. The OpenAPI spec is at https://ngrok.com/docs/openapi/ai-gateway.yaml and the per-operation reference starts at https://ngrok.com/docs/ai-gateway/api-reference/access-keys/list.md
- After a person signs in, every console page registers WebMCP tools through `navigator.modelContext`: `get_credit_balance`, `list_access_keys`, `list_models`, `get_usage_overview`, `list_catalog_providers`, `get_pricing`, and `open_page`. All but `open_page` are read-only, and no tool returns a key value. Each runs with the person's session.
- Applications never call this host. They call the gateway at https://gateway.ngrok.ai, authenticated with an access key created in this console.
- The public site for the AI Gateway is https://ngrok.ai/ (indexed at https://ngrok.ai/llms.txt), the documentation starts at https://ngrok.com/docs/ai-gateway/overview.md, and https://ngrok.com/llms.txt indexes the ngrok platform as a whole. Every docs page has a plain-markdown twin: append `.md` to the URL.

## Console pages

Sign-up and log-in are public; everything else requires a session.

- [Sign up](https://app.ngrok.ai/signup): Create an ngrok account or sign in with an existing one. One account works across ngrok.com and ngrok.ai.
- [Log in](https://app.ngrok.ai/login): Sign in to the console with your ngrok account.
- [Overview](https://app.ngrok.ai/overview): Gateway setup steps plus usage and performance at a glance.
- [Getting started](https://app.ngrok.ai/getting-started): Copy an SDK snippet prefilled with a real access key.
- [Playground](https://app.ngrok.ai/playground): Chat with models through the gateway from the browser, with matching code to copy.
- [Access keys](https://app.ngrok.ai/keys): Create and revoke the keys applications use to call the gateway. A key without a configuration is unrestricted.
- [Access key configurations](https://app.ngrok.ai/keys/configurations): Reusable scopes that limit which providers and models a key can call, and attach provider credentials.
- [Providers](https://app.ngrok.ai/providers): Built-in providers plus custom ones you add: a public OpenAI-compatible URL, or a local Ollama or LM Studio instance connected through ngrok.
- [Models](https://app.ngrok.ai/models): The models available to your account, with the `provider/model` IDs to use in requests
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=ngrok.ai · GET /v1/domain/ngrok.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ngrok.ai:
1. POST https://agentwebmap.com/v1/sites/ngrok.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ngrok.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ngrok.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ngrok.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.