---
title: Why don't I see Gateway pages like Models, Keys, and Analytics?
seoTitle: "AI Gateway Models, Gateway keys, or Analytics missing? How to fix it"
description: The Models, Gateway keys, and Analytics tabs of the Langfuse AI Gateway stay disabled until a project is set. On self-hosted Langfuse with the NONE ingestion mode, Analytics has no data to show.
tags: [ai-gateway, ai-gateway-get-started]
---

# Why don't I see Gateway pages like Models, Keys, and Analytics?

Under **Organization settings → AI Gateway**, the gateway has a **Setup** tab and the **Models**, **Gateway keys**, and **Analytics** tabs. If those tabs are disabled or empty, check the following.

## Is a project set? [#no-project]

The gateway records every call in one project of your organization. Until an admin chooses that project, the **Models**, **Gateway keys**, and **Analytics** tabs stay disabled.

To fix this, go to **Organization settings → AI Gateway → Setup** and choose a project. See [Set up Gateway as an admin](/docs/gateway/get-started/admin-setup#configure-the-gateway).

## Does your role include Analytics? [#analytics-role]

Owners, admins, and people with the AI Gateway role see the **Analytics** tab. People with the AI Gateway role only see their own usage. See [Analytics](/docs/gateway/features/analytics).

## Are you self-hosting with the `NONE` ingestion mode? [#none-mode]

On self-hosted Langfuse, the `NONE` ingestion mode routes requests without recording them. You don't need a project in this mode, but **Analytics** shows "Gateway requests are not recorded" instead of charts, because there is no data to chart.

To see analytics, switch to the `USAGE` or `FULL` [ingestion mode](/docs/gateway/features/tracing#ingestion-modes) and choose a project.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/ai-gateway-pages-missing.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.