Fix gateway docs links in unified docs

Author: ddanielcruzz

docs/ai-observability.md

@@ -53,7 +53,7 @@ Author, version, and test prompts in the [prompt editor](reference/advanced/prom
 
 ### AI Gateway
 
-Route LLM calls from any SDK through the [AI Gateway](reference/advanced/gateway/index.md) for unified key management, spending limits, provider failover, and automatic tracing of every call — one endpoint across OpenAI, Anthropic, Google, Bedrock, and more.
+Route LLM calls from any SDK through the [AI Gateway](/logfire/manage/ai-gateway/) for unified key management, spending limits, provider failover, and automatic tracing of every call — one endpoint across OpenAI, Anthropic, Google, Bedrock, and more.
 
 ### LLMs Page
 

docs/comparisons/braintrust.md

@@ -23,7 +23,7 @@ Braintrust is an AI evaluation and observability platform focused on LLM testing
 
 ## When to Choose Braintrust
 
-- **Deep Braintrust ecosystem investment:** You've already built your evaluation workflows around Braintrust's tooling (note that Logfire also offers [UI-based evals](https://pydantic.dev/docs/logfire/evaluate/evals/?utm_source=comparison_docs), a [prompt editor](https://pydantic.dev/docs/logfire/prompt-management/?utm_source=comparison_docs), a playground, and an [AI gateway](../reference/advanced/gateway/index.md))
+- **Deep Braintrust ecosystem investment:** You've already built your evaluation workflows around Braintrust's tooling (note that Logfire also offers [UI-based evals](https://pydantic.dev/docs/logfire/evaluate/evals/?utm_source=comparison_docs), a [prompt editor](https://pydantic.dev/docs/logfire/prompt-management/?utm_source=comparison_docs), a playground, and an [AI gateway](/logfire/manage/ai-gateway/))
 - **AI-only scope:** You don't need full application observability
 
 ## Key Differences Explained

docs/comparisons/index.md

@@ -52,7 +52,7 @@ Logfire is a great fit when you:
 - **Have polyglot architectures** - Python backend + TypeScript frontend, microservices in different languages
 - **Want exceptional Python, TS/JS, Rust support** - While also supporting other languages via OTel
 - **Want evals both ways** - [code-first evals with pydantic-evals](https://pydantic.dev/docs/logfire/evaluate/datasets/?utm_source=comparison_docs) that test any Python function, plus a [web UI for datasets, experiments, and live production monitoring](https://pydantic.dev/docs/logfire/evaluate/evals/?utm_source=comparison_docs)
-- **Want the full AI engineering loop in one place** - [prompt management](https://pydantic.dev/docs/logfire/prompt-management/?utm_source=comparison_docs), a playground, and an [AI gateway](../reference/advanced/gateway/index.md) with key management and spending controls, next to your traces
+- **Want the full AI engineering loop in one place** - [prompt management](https://pydantic.dev/docs/logfire/prompt-management/?utm_source=comparison_docs), a playground, and an [AI gateway](/logfire/manage/ai-gateway/) with key management and spending controls, next to your traces
 - **Prefer SQL-based querying** - Familiar PostgreSQL syntax over proprietary query languages
 - **Value simple, predictable pricing** - $2/million spans, scales to billions of spans per month
 - **Need enterprise features** - [SOC2, HIPAA, self-hosting](https://pydantic.dev/pricing?utm_source=comparison_docs#enterprise) options

docs/faq.md

@@ -50,7 +50,7 @@ Yes: Logfire is _built_ for AI observability, and it's better at it because it s
 - Streaming support
 - [Evals](guides/web-ui/evals.md): datasets, experiments, and [live production monitoring](guides/web-ui/live-evals.md) in the web UI, powered by code-first [pydantic-evals](https://github.com/pydantic/pydantic-evals)
 - [Prompt management](reference/advanced/prompt-management/index.md) with versioning, labeled rollouts, and a playground
-- An [AI Gateway](reference/advanced/gateway/index.md) with unified key management, spending limits, and provider failover
+- An [AI Gateway](/logfire/manage/ai-gateway/) with unified key management, spending limits, and provider failover
 
 **Better debugging:** When your AI agent fails, you don't just see the LLM error. You see the database timeout that caused it, the API rate limit that preceded it, and the user request that started it all.
 

docs/gateway-migration.md

@@ -7,7 +7,7 @@ description: "Historical reference: how the legacy gateway.pydantic.dev was migr
 # Pydantic AI Gateway Has Moved to Pydantic Logfire
 
 !!! tip "Looking for the current gateway docs?"
-    For how to enable and use the AI Gateway in Logfire today — providers, API keys, routing, and spending controls — see the [AI Gateway overview](reference/advanced/gateway/index.md).
+    For how to enable and use the AI Gateway in Logfire today — providers, API keys, routing, and spending controls — see the [AI Gateway overview](/logfire/manage/ai-gateway/).
 
 We consolidated the AI Gateway into Logfire. The legacy standalone gateway at [gateway.pydantic.dev](https://gateway.pydantic.dev/) **has been shut down**, and the gateway is now managed through your Logfire account. This page remains as a historical reference for users migrating from the legacy platform.
 

docs/reference/advanced/gateway/index.md

@@ -162,6 +162,6 @@ Or run just the proxy and configure a tool manually with `logfire gateway serve`
 
 ## See also
 
-- [Using the gateway with agent frameworks](./agent-frameworks.md) — route framework model calls through the gateway.
+- [Using the gateway with agent frameworks](/logfire/manage/ai-gateway/agent-frameworks/) — route framework model calls through the gateway.
 - [Prompt Management: Access and Prerequisites](../prompt-management/plan-requirements.md) — prompt runs execute through the gateway and spend gateway budget.
 - [Cost & Usage](../../../logfire-costs.md) — plan tiers and how usage is billed.

docs/reference/advanced/prompt-management/plan-requirements.md

@@ -24,4 +24,4 @@ Prompt Management currently uses variable-level permissions:
 
 Because run history includes model outputs, treat `read_variables` as sensitive if your prompts handle sensitive data.
 
-For pricing details and plan tiers, see [Cost & Usage](../../../logfire-costs.md). For how the gateway itself works — providers, API keys, and spending controls — see the [AI Gateway overview](../gateway/index.md).
+For pricing details and plan tiers, see [Cost & Usage](../../../logfire-costs.md). For how the gateway itself works — providers, API keys, and spending controls — see the [AI Gateway overview](/logfire/manage/ai-gateway/).