From 8f74d150dfde1d68df72d8980ec2f4ade3199b37 Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Thu, 8 Oct 2026 15:55:05 +0100
Subject: [PATCH 1/9] Changed API references in English prose text to use
 ApiRefernce.astro where appropriate.

---
 .../app-host/certificate-configuration.mdx    | 11 ++---
 .../content/docs/app-host/container-files.mdx |  9 ++--
 .../docs/app-host/container-registry.mdx      |  5 ++-
 .../src/content/docs/app-host/eventing.mdx    | 13 +++---
 .../docs/app-host/executable-resources.mdx    |  9 ++--
 .../app-host/migrate-from-docker-compose.mdx  | 23 +++++-----
 .../docs/app-host/resource-lifetimes.mdx      | 15 ++++---
 .../docs/app-host/typescript-apphost.mdx      |  5 ++-
 .../content/docs/app-host/with-terminal.mdx   |  7 +--
 .../content/docs/app-host/withdockerfile.mdx  | 11 ++---
 .../multi-language-architecture.mdx           |  5 ++-
 .../architecture/resource-api-patterns.mdx    |  3 +-
 .../docs/architecture/resource-examples.mdx   |  4 +-
 .../architecture/resource-hierarchies.mdx     |  7 +--
 .../docs/architecture/resource-publishing.mdx |  3 +-
 .../docs/dashboard/ephemeral-terminals.mdx    |  4 +-
 .../src/content/docs/dashboard/explore.mdx    |  5 ++-
 .../dashboard/telemetry-after-deployment.mdx  |  3 +-
 .../src/content/docs/dashboard/terminals.mdx  |  5 ++-
 .../docs/deployment/azure/app-service.mdx     |  5 ++-
 .../deployment/azure/azure-developer-cli.mdx  |  5 ++-
 .../azure/azure-security-best-practices.mdx   |  5 ++-
 .../docs/deployment/azure/container-apps.mdx  |  9 ++--
 .../docs/deployment/azure/sandboxes.mdx       | 15 ++++---
 .../docs/deployment/custom-deployments.mdx    |  5 ++-
 .../docs/deployment/deploy-with-aspire.mdx    |  3 +-
 .../docs/deployment/docker-compose.mdx        | 23 +++++-----
 .../content/docs/deployment/environments.mdx  |  5 ++-
 .../docs/deployment/javascript-apps.mdx       | 27 +++++------
 .../deployment/kubernetes-gateway-aks.mdx     |  9 ++--
 .../deployment/kubernetes-ingress-aks.mdx     |  9 ++--
 .../docs/deployment/kubernetes-ingress.mdx    |  7 +--
 .../docs/deployment/kubernetes/aks.mdx        | 25 ++++++-----
 .../docs/deployment/kubernetes/clusters.mdx   |  9 ++--
 .../deployment/kubernetes/helm-charts.mdx     |  3 +-
 .../kubernetes/persistent-volumes.mdx         |  9 ++--
 .../src/content/docs/deployment/pipelines.mdx |  9 ++--
 .../docs/diagnostics/aspireacadomains001.mdx  |  3 +-
 .../docs/diagnostics/aspireacanaming001.mdx   |  3 +-
 .../docs/diagnostics/aspireazure002.mdx       |  3 +-
 .../docs/diagnostics/aspireazure003.mdx       |  3 +-
 .../docs/diagnostics/aspireblazor001.mdx      |  3 +-
 .../docs/diagnostics/aspirebrowserlogs001.mdx |  3 +-
 .../diagnostics/aspirecertificates001.mdx     |  5 ++-
 .../docs/diagnostics/aspirecommand001.mdx     |  3 +-
 .../docs/diagnostics/aspirecompute002.mdx     |  3 +-
 .../docs/diagnostics/aspirecompute003.mdx     |  3 +-
 .../docs/diagnostics/aspirecosmosdb001.mdx    |  3 +-
 .../docs/diagnostics/aspirecsharpapps001.mdx  |  3 +-
 .../aspiredockerfilebuilder001.mdx            |  3 +-
 .../diagnostics/aspiredotnetproject001.mdx    |  5 ++-
 .../docs/diagnostics/aspiredotnettool001.mdx  |  3 +-
 .../docs/diagnostics/aspiredurabletask001.mdx | 11 ++---
 .../docs/diagnostics/aspireextension001.mdx   |  3 +-
 .../diagnostics/aspirehostingpython001.mdx    |  3 +-
 .../docs/diagnostics/aspirejavascript001.mdx  | 11 ++---
 .../content/docs/diagnostics/aspiremcp001.mdx |  3 +-
 .../docs/diagnostics/aspirepersistence001.mdx |  9 ++--
 .../docs/diagnostics/aspirepipelines003.mdx   |  3 +-
 .../docs/diagnostics/aspirepostgres001.mdx    |  5 ++-
 .../docs/diagnostics/aspireprobes001.mdx      |  3 +-
 .../diagnostics/aspireprocesscommand001.mdx   |  3 +-
 .../docs/diagnostics/aspireprojects001.mdx    |  3 +-
 .../docs/diagnostics/aspireradius003.mdx      |  3 +-
 .../docs/diagnostics/aspireterminal001.mdx    |  3 +-
 .../docs/diagnostics/aspireusersecrets001.mdx |  5 ++-
 .../src/content/docs/diagnostics/overview.mdx | 14 +++---
 .../docs/extensibility/custom-resources.mdx   |  5 ++-
 .../extensibility/interaction-service.mdx     |  3 +-
 .../multi-language-integration-authoring.mdx  |  3 +-
 .../fundamentals/annotations-overview.mdx     |  9 ++--
 .../fundamentals/container-networking.mdx     |  3 +-
 .../fundamentals/custom-resource-commands.mdx |  5 ++-
 .../fundamentals/custom-resource-urls.mdx     | 11 ++---
 .../fundamentals/environment-variables.mdx    |  5 ++-
 .../docs/fundamentals/external-parameters.mdx | 13 +++---
 .../docs/fundamentals/health-checks.mdx       |  7 +--
 .../docs/fundamentals/http-commands.mdx       |  3 +-
 .../docs/fundamentals/networking-overview.mdx |  9 ++--
 .../fundamentals/persist-data-volumes.mdx     | 13 +++---
 .../docs/fundamentals/service-discovery.mdx   |  5 ++-
 .../get-started/add-aspire-existing-app.mdx   |  2 +-
 .../docs/get-started/ai-coding-agents.mdx     |  3 +-
 .../content/docs/get-started/aspire-sdk.mdx   |  3 +-
 .../get-started/aspire-vscode-extension.mdx   |  3 +-
 .../ai/github-models/github-models-host.mdx   |  5 ++-
 .../integrations/ai/ollama/ollama-connect.mdx |  3 +-
 .../integrations/ai/ollama/ollama-host.mdx    |  9 ++--
 .../integrations/ai/openai/openai-host.mdx    |  9 ++--
 .../caching/garnet/garnet-connect.mdx         |  3 +-
 .../caching/garnet/garnet-host.mdx            |  7 +--
 .../redis-distributed-get-started.mdx         |  3 +-
 .../redis-distributed-host.mdx                | 11 ++---
 .../integrations/caching/redis-extensions.mdx |  5 ++-
 .../caching/redis/redis-connect.mdx           |  3 +-
 .../integrations/caching/redis/redis-host.mdx |  9 ++--
 .../caching/valkey/valkey-connect.mdx         |  3 +-
 .../caching/valkey/valkey-host.mdx            |  9 ++--
 .../integrations/cloud/azure/aks/index.mdx    |  9 ++--
 .../azure-ai-foundry-connect.mdx              |  3 +-
 .../azure-ai-foundry-get-started.mdx          |  5 ++-
 .../azure-ai-foundry-host.mdx                 | 43 +++++++++---------
 .../azure-ai-inference-host.mdx               |  3 +-
 .../azure-ai-search/azure-ai-search-host.mdx  |  9 ++--
 .../azure-app-configuration-host.mdx          | 19 ++++----
 .../azure-app-service-get-started.mdx         |  3 +-
 .../azure-app-service-host.mdx                | 13 +++---
 .../azure/azure-application-insights.mdx      |  9 ++--
 .../azure-cache-redis-connect.mdx             |  5 ++-
 .../azure-cache-redis-host.mdx                | 13 +++---
 .../cloud/azure/azure-connector-namespace.mdx |  5 ++-
 .../azure-container-registry-connect.mdx      |  5 ++-
 .../azure-container-registry-get-started.mdx  |  3 +-
 .../azure-container-registry-host.mdx         | 15 ++++---
 .../azure-cosmos-db-connect.mdx               |  5 ++-
 .../azure-cosmos-db/azure-cosmos-db-host.mdx  | 27 +++++------
 .../cloud/azure/azure-data-explorer.mdx       | 11 ++---
 .../cloud/azure/azure-default-credential.mdx  |  3 +-
 .../azure-event-hubs-host.mdx                 | 19 ++++----
 .../cloud/azure/azure-front-door.mdx          | 11 ++---
 .../azure-functions-connect.mdx               |  3 +-
 .../azure-functions-get-started.mdx           |  3 +-
 .../azure-functions/azure-functions-host.mdx  | 15 ++++---
 .../azure-key-vault/azure-key-vault-host.mdx  | 17 +++----
 .../cloud/azure/azure-log-analytics.mdx       |  7 +--
 .../azure/azure-openai/azure-openai-host.mdx  | 13 +++---
 .../azure-postgresql-connect.mdx              |  3 +-
 .../azure-postgresql-get-started.mdx          |  3 +-
 .../azure-postgresql-host.mdx                 | 19 ++++----
 .../azure-service-bus-host.mdx                | 21 ++++-----
 .../azure-signalr/azure-signalr-connect.mdx   |  3 +-
 .../azure-signalr/azure-signalr-host.mdx      | 13 +++---
 .../azure-sql-database-connect.mdx            |  5 ++-
 .../azure-sql-database-get-started.mdx        |  5 ++-
 .../azure-sql-database-host.mdx               | 19 ++++----
 .../azure-storage-blobs-connect.mdx           |  7 +--
 .../azure-storage-blobs-host.mdx              | 21 ++++-----
 .../cloud/azure/azure-storage-datalake.mdx    |  7 +--
 .../azure-storage-queues-connect.mdx          |  3 +-
 .../azure-storage-queues-get-started.mdx      |  3 +-
 .../azure-storage-queues-host.mdx             | 13 +++---
 .../azure-storage-tables-connect.mdx          |  3 +-
 .../azure-storage-tables-get-started.mdx      |  3 +-
 .../azure-storage-tables-host.mdx             | 21 ++++-----
 .../cloud/azure/azure-virtual-network.mdx     | 37 +++++++--------
 .../azure-web-pubsub-connect.mdx              |  3 +-
 .../azure-web-pubsub-host.mdx                 | 13 +++---
 .../cloud/azure/configure-container-apps.mdx  | 17 +++----
 .../cloud/azure/container-app-jobs.mdx        |  9 ++--
 .../cloud/azure/customize-resources.mdx       | 15 ++++---
 .../cloud/azure/local-provisioning.mdx        |  5 ++-
 .../integrations/cloud/azure/overview.mdx     | 13 +++---
 .../cloud/azure/user-assigned-identity.mdx    |  7 +--
 .../docs/integrations/compute/docker.mdx      | 31 ++++++-------
 .../docs/integrations/compute/floci.mdx       |  7 +--
 .../content/docs/integrations/compute/k3s.mdx | 17 +++----
 .../docs/integrations/compute/kubernetes.mdx  | 13 +++---
 .../hosting-integrations.mdx                  |  7 +--
 .../secure-communication.mdx                  |  3 +-
 .../clickhouse/clickhouse-connect.mdx         |  3 +-
 .../databases/clickhouse/clickhouse-host.mdx  |  5 ++-
 .../azure-cosmos-db/azure-cosmos-db-host.mdx  | 11 ++---
 .../azure-sql/azure-sql-get-started.mdx       |  3 +-
 .../efcore/azure-sql/azure-sql-host.mdx       | 11 ++---
 .../databases/efcore/migrations.mdx           |  9 ++--
 .../efcore/mongodb/mongodb-efcore-connect.mdx |  3 +-
 .../databases/efcore/mysql/mysql-connect.mdx  |  3 +-
 .../databases/efcore/oracle/oracle-host.mdx   |  9 ++--
 .../efcore/postgres/postgresql-connect.mdx    |  3 +-
 .../databases/efcore/seed-database.mdx        |  5 ++-
 .../efcore/sql-server/sql-server-connect.mdx  |  3 +-
 .../elasticsearch/elasticsearch-connect.mdx   |  5 ++-
 .../elasticsearch/elasticsearch-host.mdx      |  3 +-
 .../databases/kurrentdb/kurrentdb-connect.mdx |  3 +-
 .../meilisearch/meilisearch-connect.mdx       |  3 +-
 .../meilisearch/meilisearch-host.mdx          |  7 +--
 .../databases/milvus/milvus-host.mdx          |  5 ++-
 .../databases/mongodb/mongodb-extensions.mdx  |  5 ++-
 .../databases/mongodb/mongodb-host.mdx        | 25 ++++++-----
 .../databases/mysql/mysql-extensions.mdx      |  7 +--
 .../databases/mysql/mysql-get-started.mdx     |  3 +-
 .../databases/mysql/mysql-host.mdx            |  9 ++--
 .../databases/postgres/postgres-host.mdx      | 13 +++---
 .../postgres/postgresql-extensions.mdx        |  9 ++--
 .../databases/ravendb/ravendb-connect.mdx     |  3 +-
 .../databases/ravendb/ravendb-host.mdx        |  3 +-
 .../sql-server/sql-server-extensions.mdx      |  7 +--
 .../databases/sql-server/sql-server-host.mdx  |  9 ++--
 .../databases/sqlite/sqlite-connect.mdx       |  3 +-
 .../databases/sqlite/sqlite-get-started.mdx   |  3 +-
 .../databases/sqlite/sqlite-host.mdx          |  5 ++-
 .../databases/surrealdb/surrealdb-connect.mdx |  3 +-
 .../databases/surrealdb/surrealdb-host.mdx    |  7 +--
 .../integrations/devtools/browser-logs.mdx    |  3 +-
 .../integrations/devtools/dab/dab-host.mdx    |  3 +-
 .../integrations/devtools/dev-tunnels.mdx     |  7 +--
 .../devtools/flagd/flagd-host.mdx             |  5 ++-
 .../devtools/goff/goff-connect.mdx            |  3 +-
 .../integrations/devtools/goff/goff-host.mdx  |  9 ++--
 .../docs/integrations/devtools/k6/k6-host.mdx | 11 ++---
 .../devtools/mailpit/mailpit-connect.mdx      |  3 +-
 .../sql-projects/sql-projects-host.mdx        | 13 +++---
 .../integrations/dotnet/blazor-connect.mdx    |  3 +-
 .../dotnet/blazor-get-started.mdx             |  5 ++-
 .../integrations/dotnet/blazor-hosting.mdx    |  2 +-
 .../dotnet/csharp-file-based-apps.mdx         |  5 ++-
 .../dotnet/dotnet-tool-resources.mdx          | 15 ++++---
 .../integrations/dotnet/launch-profiles.mdx   |  7 +--
 .../content/docs/integrations/dotnet/maui.mdx |  5 ++-
 .../integrations/dotnet/project-resources.mdx | 15 ++++---
 .../docs/integrations/frameworks/bun-apps.mdx |  5 ++-
 .../frameworks/deno/deno-get-started.mdx      |  3 +-
 .../frameworks/deno/deno-host.mdx             | 11 ++---
 .../frameworks/dotnet/dotnet-get-started.mdx  |  5 ++-
 .../frameworks/dotnet/dotnet-host.mdx         |  9 ++--
 .../frameworks/go/go-get-started.mdx          |  3 +-
 .../integrations/frameworks/go/go-host.mdx    | 19 ++++----
 .../frameworks/java/java-connect.mdx          |  4 +-
 .../integrations/frameworks/javascript.mdx    | 31 ++++++-------
 .../frameworks/nodejs-extensions.mdx          | 11 ++---
 .../docs/integrations/frameworks/orleans.mdx  |  5 ++-
 .../frameworks/perl/perl-get-started.mdx      |  3 +-
 .../frameworks/perl/perl-host.mdx             | 23 +++++-----
 .../frameworks/powershell/powershell-host.mdx | 11 ++---
 .../docs/integrations/frameworks/python.mdx   | 25 ++++++-----
 .../frameworks/rust/rust-host.mdx             |  2 +-
 .../integrations/frameworks/wpf-winforms.mdx  |  3 +-
 .../apache-kafka/apache-kafka-host.mdx        |  3 +-
 .../messaging/lavinmq/lavinmq-host.mdx        |  5 ++-
 .../messaging/nats/nats-get-started.mdx       |  3 +-
 .../integrations/messaging/nats/nats-host.mdx |  3 +-
 .../messaging/rabbitmq/rabbitmq-connect.mdx   |  3 +-
 .../messaging/rabbitmq/rabbitmq-host.mdx      |  7 +--
 .../observability/seq/seq-connect.mdx         |  3 +-
 .../integrations/reverse-proxies/yarp.mdx     | 11 ++---
 .../docs/integrations/security/keycloak.mdx   | 19 ++++----
 .../cli/commands/aspire-docs-api-search.mdx   |  3 +-
 .../reference/cli/commands/aspire-init.mdx    |  3 +-
 .../docs/testing/accessing-resources.mdx      |  3 +-
 .../docs/testing/advanced-scenarios.mdx       |  7 +--
 .../docs/testing/write-your-first-test.mdx    |  3 +-
 .../content/docs/whats-new/aspire-13-1.mdx    | 11 ++---
 .../content/docs/whats-new/aspire-13-2.mdx    | 35 ++++++++-------
 .../content/docs/whats-new/aspire-13-3.mdx    | 33 +++++++-------
 .../content/docs/whats-new/aspire-13-4.mdx    | 33 +++++++-------
 .../content/docs/whats-new/aspire-13-5.mdx    | 19 ++++----
 .../content/docs/whats-new/aspire-13-6.mdx    | 43 +++++++++---------
 .../src/content/docs/whats-new/aspire-13.mdx  | 45 ++++++++++---------
 .../src/content/docs/whats-new/aspire-9-1.mdx |  5 ++-
 .../src/content/docs/whats-new/aspire-9-2.mdx | 13 +++---
 .../src/content/docs/whats-new/aspire-9-3.mdx | 33 +++++++-------
 .../src/content/docs/whats-new/aspire-9-4.mdx | 21 ++++-----
 .../src/content/docs/whats-new/aspire-9-5.mdx | 23 +++++-----
 .../src/content/docs/whats-new/aspire-9.mdx   | 13 +++---
 254 files changed, 1230 insertions(+), 977 deletions(-)

diff --git a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
index 7acf8fc54a..3ade07657c 100644
--- a/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
+++ b/src/frontend/src/content/docs/app-host/certificate-configuration.mdx
@@ -6,13 +6,14 @@ description: Configure HTTPS endpoints and certificate trust for Aspire resource
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire provides two complementary sets of certificate APIs:
 
 1. **HTTPS endpoint APIs**: Configure the certificates that resources use for their own HTTPS endpoints (server authentication)
 2. **Certificate trust APIs**: Configure which certificates resources trust when making outbound HTTPS connections (client authentication)
 
-Both sets of APIs work together to enable secure HTTPS communication during local development. For example, a Vite frontend might use `WithHttpsDeveloperCertificate` to serve HTTPS traffic, while also using `WithDeveloperCertificateTrust` to trust the dashboard's <abbr title="OpenTelemetry Protocol" data-tooltip-placement="top">OTLP</abbr> endpoint certificate.
+Both sets of APIs work together to enable secure HTTPS communication during local development. For example, a Vite frontend might use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsDeveloperCertificate" /> to serve HTTPS traffic, while also using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithDeveloperCertificateTrust" /> to trust the dashboard's <abbr title="OpenTelemetry Protocol" data-tooltip-placement="top">OTLP</abbr> endpoint certificate.
 
 <Aside type="caution">
   Certificate customization only applies at run time. Custom certificates aren't
@@ -151,7 +152,7 @@ HTTPS endpoint configuration determines which certificate a resource presents wh
 
 ### Default behavior
 
-For resources that have a certificate configuration defined with `WithHttpsCertificateConfiguration`, Aspire attempts to configure it to use the development certificate if available. This automatic configuration works for many common resource types including YARP, Redis, and Keycloak containers; Vite based JavaScript apps; and Python apps using Uvicorn.
+For resources that have a certificate configuration defined with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsCertificateConfiguration" />, Aspire attempts to configure it to use the development certificate if available. This automatic configuration works for many common resource types including YARP, Redis, and Keycloak containers; Vite based JavaScript apps; and Python apps using Uvicorn.
 
 You can control this behavior using the HTTPS endpoint APIs described below.
 
@@ -291,7 +292,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-Use `WithoutHttpsCertificate` when:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithoutHttpsCertificate" /> when:
 
 - The resource doesn't support HTTPS
 - You want to manually configure certificates
@@ -480,7 +481,7 @@ In the preceding example, the certificate bundle is created with custom certific
 
 Certificate trust scopes control how custom certificates interact with a resource's default trusted certificates. Different scopes provide flexibility in managing certificate trust based on your application's requirements.
 
-The `WithCertificateTrustScope` API accepts a `CertificateTrustScope` value to specify the trust behavior.
+The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCertificateTrustScope" /> API accepts a `CertificateTrustScope` value to specify the trust behavior.
 
 #### Available trust scopes
 
@@ -677,7 +678,7 @@ Default implementations are provided for Node.js, Python, and container resource
 
 #### Configure container certificate paths
 
-For container resources, you can customize where certificates are stored and accessed using `WithContainerCertificatePaths`:
+For container resources, you can customize where certificates are stored and accessed using <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerCertificatePaths" />:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/app-host/container-files.mdx b/src/frontend/src/content/docs/app-host/container-files.mdx
index 8e02c0f3b2..8db656de87 100644
--- a/src/frontend/src/content/docs/app-host/container-files.mdx
+++ b/src/frontend/src/content/docs/app-host/container-files.mdx
@@ -5,11 +5,12 @@ description: Inject files and directories into Aspire container resources at dev
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire provides APIs to inject files and directories into containers, enabling you to configure containerized resources with custom configuration files, scripts, certificates, and other assets. There are two complementary APIs:
 
-- **`WithContainerFiles`**: Injects files into containers at development time when they start during `aspire run`.
-- **`PublishWithContainerFiles`**: Copies files from one resource's container into another resource's container as build artifacts at publish time during `aspire publish`.
+- **<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerFiles" />**: Injects files into containers at development time when they start during `aspire run`.
+- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" />**: Copies files from one resource's container into another resource's container as build artifacts at publish time during `aspire publish`.
 
 ## Inject files at development time
 
@@ -417,7 +418,7 @@ This produces a self-contained Nginx container that serves the frontend applicat
 
 ### Customize the source path
 
-By default, the source resource exports files from its container based on its configured output paths. Use `WithContainerFilesSource` to specify which path inside the source container to copy from:
+By default, the source resource exports files from its container based on its configured output paths. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithContainerFilesSource" /> to specify which path inside the source container to copy from:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -436,7 +437,7 @@ The `withContainerFiles` API is not yet available in the TypeScript AppHost SDK.
 </TabItem>
 </Tabs>
 
-Use `ClearContainerFilesSources` to remove any previously configured source paths before adding new ones.
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ClearContainerFilesSources" /> to remove any previously configured source paths before adding new ones.
 
 ## See also
 
diff --git a/src/frontend/src/content/docs/app-host/container-registry.mdx b/src/frontend/src/content/docs/app-host/container-registry.mdx
index 318d365821..28809f66e4 100644
--- a/src/frontend/src/content/docs/app-host/container-registry.mdx
+++ b/src/frontend/src/content/docs/app-host/container-registry.mdx
@@ -6,6 +6,7 @@ description: Configure container registries for Aspire — generic registries, D
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.1 introduced explicit container registry configuration, giving developers control over where and when container images are pushed during deployment. This article explains how to configure container registries for your Aspire applications.
 
@@ -24,7 +25,7 @@ When deploying Aspire applications to production environments, your containerize
   This API is experimental and may change in future releases. Use diagnostic code `ASPIRECOMPUTE003` to suppress the experimental warning. For more information, see [ASPIRECOMPUTE003](/diagnostics/aspirecompute003/).
 </Aside>
 
-Use the `AddContainerRegistry` method to configure a generic container registry for your application. This works with any Docker-compatible registry including DockerHub, GitHub Container Registry, Harbor, and private registries.
+Use the <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.AddContainerRegistry" /> method to configure a generic container registry for your application. This works with any Docker-compatible registry including DockerHub, GitHub Container Registry, Harbor, and private registries.
 
 ### Basic usage
 
@@ -303,7 +304,7 @@ In the preceding example:
 
 ### Using an existing ACR
 
-To use an existing Azure Container Registry, call the `PublishAsExisting` method when you add the ACR:
+To use an existing Azure Container Registry, call the <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> method when you add the ACR:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/app-host/eventing.mdx b/src/frontend/src/content/docs/app-host/eventing.mdx
index ba6dafd55d..f45685daa8 100644
--- a/src/frontend/src/content/docs/app-host/eventing.mdx
+++ b/src/frontend/src/content/docs/app-host/eventing.mdx
@@ -6,6 +6,7 @@ description: Use the Aspire AppHost eventing APIs for lifecycle events, custom e
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 In Aspire, eventing allows you to publish and subscribe to events during various AppHost life cycles. Eventing is more flexible than life cycle events. Both let you run arbitrary code during event callbacks, but eventing offers finer control of event timing, publishing, and provides supports for custom events.
 
@@ -110,7 +111,7 @@ builder.Eventing.Subscribe<AfterResourcesCreatedEvent>(
   `builder.Eventing.Subscribe<TEvent>()` API. Use the named callback APIs
   generated for each supported event, such as `subscribeBeforeStart`,
   `subscribeAfterResourcesCreated`, `addEventingSubscriber`, and resource
-  callbacks like `onResourceReady`.
+  callbacks like <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceReady" />.
 </Aside>
 
 <Aside type="caution">
@@ -278,12 +279,12 @@ The preceding code subscribes to the `InitializeResourceEvent`, `ResourceReadyEv
   and `await event.services()` when you need the resource or service provider.
 </Aside>
 
-- `OnInitializeResource` / `onInitializeResource`: Subscribes to the `InitializeResourceEvent`.
-- `OnResourceEndpointsAllocated` / `onResourceEndpointsAllocated`: Subscribes to the `ResourceEndpointsAllocatedEvent` event.
-- `OnConnectionStringAvailable` / `onConnectionStringAvailable`: Subscribes to the `ConnectionStringAvailableEvent` event.
-- `OnBeforeResourceStarted` / `onBeforeResourceStarted`: Subscribes to the `BeforeResourceStartedEvent` event.
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnInitializeResource" />: Subscribes to the `InitializeResourceEvent`.
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceEndpointsAllocated" />: Subscribes to the `ResourceEndpointsAllocatedEvent` event.
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnConnectionStringAvailable" />: Subscribes to the `ConnectionStringAvailableEvent` event.
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnBeforeResourceStarted" />: Subscribes to the `BeforeResourceStartedEvent` event.
 - `OnResourceReady` / `onResourceReady`: Subscribes to the `ResourceReadyEvent` event.
-- `OnResourceStopped` / `onResourceStopped`: Subscribes to the `ResourceStoppedEvent` event.
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceStopped" />: Subscribes to the `ResourceStoppedEvent` event.
 
 When the AppHost is run, by the time the Aspire dashboard is displayed, you should see the following log output in the console:
 
diff --git a/src/frontend/src/content/docs/app-host/executable-resources.mdx b/src/frontend/src/content/docs/app-host/executable-resources.mdx
index d02b1ead88..118f282e60 100644
--- a/src/frontend/src/content/docs/app-host/executable-resources.mdx
+++ b/src/frontend/src/content/docs/app-host/executable-resources.mdx
@@ -4,8 +4,9 @@ description: Host external executable applications in your Aspire AppHost using
 ---
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
-In Aspire, you can host external executable applications alongside your projects using the `AddExecutable` method. This capability is useful when you need to integrate executable applications or tools into your distributed application, such as Node.js applications, Python scripts, or specialized CLI tools.
+In Aspire, you can host external executable applications alongside your projects using the <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.AddExecutable" /> method. This capability is useful when you need to integrate executable applications or tools into your distributed application, such as Node.js applications, Python scripts, or specialized CLI tools.
 
 ## When to use executable resources
 
@@ -122,7 +123,7 @@ const app = await builder.addExecutable("worker", "python", ".", ["worker.py"])
 </TabItem>
 </Tabs>
 
-When one resource depends on another, `WithReference` passes along environment variables containing the dependent resource's connection details. For example, the `worker` executable's reference to `redis` and `postgres` provides it with the `ConnectionStrings__cache` and `ConnectionStrings__appdb` environment variables, which contain connection strings to these resources.
+When one resource depends on another, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> passes along environment variables containing the dependent resource's connection details. For example, the `worker` executable's reference to `redis` and `postgres` provides it with the `ConnectionStrings__cache` and `ConnectionStrings__appdb` environment variables, which contain connection strings to these resources.
 
 ### Access specific endpoint information
 
@@ -282,7 +283,7 @@ When upgrading to Aspire 13.3, replace every earlier per-kind environment helper
 
 ## Publishing with PublishAsDockerFile
 
-For production deployment, executable resources need to be containerized. Use the `PublishAsDockerFile` method to specify how the executable should be packaged:
+For production deployment, executable resources need to be containerized. Use the <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.PublishAsDockerFile" /> method to specify how the executable should be packaged:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -353,7 +354,7 @@ When working with executable resources:
 
 1. **Use explicit paths**: For better reliability, use full paths to executables when possible.
 1. **Handle dependencies**: Use `WithReference` to establish proper dependency relationships.
-1. **Configure explicit start**: Use `WithExplicitStart()` for executables that shouldn't start automatically.
+1. **Configure explicit start**: Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> for executables that shouldn't start automatically.
 1. **Prepare for deployment**: Always use `PublishAsDockerFile()` for production scenarios.
 1. **Environment isolation**: Use environment variables rather than command-line arguments for sensitive configuration.
 1. **Resource naming**: Use descriptive names that clearly identify the executable's purpose.
diff --git a/src/frontend/src/content/docs/app-host/migrate-from-docker-compose.mdx b/src/frontend/src/content/docs/app-host/migrate-from-docker-compose.mdx
index 249a486453..c69a2f18d4 100644
--- a/src/frontend/src/content/docs/app-host/migrate-from-docker-compose.mdx
+++ b/src/frontend/src/content/docs/app-host/migrate-from-docker-compose.mdx
@@ -5,6 +5,7 @@ description: Compare Aspire and Docker Compose for local development, service di
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Docker Compose and Aspire both describe and run multi-service applications. This guide compares their local development workflows and maps Compose services, dependencies, and configuration to an Aspire AppHost written in TypeScript or C#.
 
@@ -157,17 +158,17 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="note" title="build: services become project or Dockerfile resources">
-In Docker Compose, the `build:` directive creates container images from Dockerfiles. In Aspire, .NET services are added directly as project references with `AddProject<T>()`, providing better debugging, hot reload, and telemetry integration. For services that still build from Dockerfiles, use `AddDockerfile()` for an existing Dockerfile or `AddDockerfileBuilder()` when the AppHost should generate the Dockerfile programmatically.
+In Docker Compose, the `build:` directive creates container images from Dockerfiles. In Aspire, .NET services are added directly as project references with <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />, providing better debugging, hot reload, and telemetry integration. For services that still build from Dockerfiles, use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfile" /> for an existing Dockerfile or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> when the AppHost should generate the Dockerfile programmatically.
 </Aside>
 
 **Key differences explained:**
 
 - **Build vs. project** — Docker Compose `build:` services become `AddProject<T>()` for .NET apps, which runs them directly instead of in containers
 - **Ports** — Both examples explicitly map ports (3000 and 5000)
-- **Startup order** — Docker Compose uses `depends_on` with health conditions; Aspire uses `WaitFor()` for startup ordering
-- **Service discovery** — `WithReference()` only configures service discovery and connection strings; it doesn't control startup order
-- **Connection strings** — By default, `WithReference(database)` provides `ConnectionStrings__myapp` using the resource name from `AddDatabase()`. To match a different name like `DefaultConnection`, use a named reference: `.WithReference(database, "DefaultConnection")`
-- **Volumes** — `WithDataVolume()` must be called explicitly to add persistent storage; it's not automatic
+- **Startup order** — Docker Compose uses `depends_on` with health conditions; Aspire uses <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> for startup ordering
+- **Service discovery** — <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> only configures service discovery and connection strings; it doesn't control startup order
+- **Connection strings** — By default, `WithReference(database)` provides `ConnectionStrings__myapp` using the resource name from <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddDatabase" />. To match a different name like `DefaultConnection`, use a named reference: `.WithReference(database, "DefaultConnection")`
+- **Volumes** — <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> must be called explicitly to add persistent storage; it's not automatic
 - **Image versions** — `WithImageTag("15")` pins PostgreSQL to version 15
 
 ### Container-based services
@@ -277,13 +278,13 @@ Aspire generates .NET-format connection strings, which differ from Docker Compos
 - Docker Compose: `DATABASE_URL=postgresql://postgres:secret@postgres:5432/main`
 - Aspire: `ConnectionStrings__main=Host=localhost;Port=12345;Username=postgres;Password=<generated>;Database=main`
 
-If your application expects URL-format environment variables, construct them manually with `WithEnvironment()`. See [Environment variables and configuration](#environment-variables-and-configuration) for details.
+If your application expects URL-format environment variables, construct them manually with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Environment variables and configuration](#environment-variables-and-configuration) for details.
 </Aside>
 
 **Key differences explained:**
 
-- **Image versions** — Explicitly specified with `WithImageTag()` to match Docker Compose
-- **Dockerfile builds** — Docker Compose `build: .` maps to `AddDockerfile("web", ".")`, which builds a container image from a Dockerfile. Use `AddContainer()` for pre-built images that use `image:` in Docker Compose
+- **Image versions** — Explicitly specified with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImageTag" /> to match Docker Compose
+- **Dockerfile builds** — Docker Compose `build: .` maps to `AddDockerfile("web", ".")`, which builds a container image from a Dockerfile. Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" /> for pre-built images that use `image:` in Docker Compose
 - **Ports** — `WithHostPort()` maps to a static host port; without it, Aspire assigns a random port
 - **Volumes** — `WithDataVolume()` must be called explicitly to add persistent storage
 - **Startup ordering** — `WaitFor()` controls startup order, similar to Docker Compose `depends_on` with conditions
@@ -462,7 +463,7 @@ await builder.build().run();
 **Key differences:**
 
 - **Named volumes** — Created with `AddVolume()` and shared between containers
-- **Bind mounts** — Use `WithBindMount()` for host directory access
+- **Bind mounts** — Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBindMount" /> for host directory access
 
 ### Networking
 
@@ -532,14 +533,14 @@ Successfully migrating from Docker Compose to Aspire requires a systematic appro
    - **Configure dependencies** with `WithReference()` for service discovery
    - **Add startup ordering** with `WaitFor()` to match `depends_on` behavior
    - **Set up environment variables** — Note that connection string formats will differ
-   - **Migrate health checks** — Use `WithHttpHealthCheck()` or `WithHealthCheck()` for custom checks
+   - **Migrate health checks** — Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHealthCheck" /> for custom checks
 
 4. ### Handle data migration
 
    For persistent data:
 
    - Use `WithDataVolume()` for automatic volume management with integrations
-   - Use `WithVolume()` for named volumes that need to persist data
+   - Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithVolume" /> for named volumes that need to persist data
    - Use `WithBindMount()` for host directory mounts when you need direct access to host files
 
 5. ### Test and validate
diff --git a/src/frontend/src/content/docs/app-host/resource-lifetimes.mdx b/src/frontend/src/content/docs/app-host/resource-lifetimes.mdx
index a39514c1c6..22214da3de 100644
--- a/src/frontend/src/content/docs/app-host/resource-lifetimes.mdx
+++ b/src/frontend/src/content/docs/app-host/resource-lifetimes.mdx
@@ -10,6 +10,7 @@ import LearnMore from '@components/LearnMore.astro';
 import persistentContainer from '@assets/fundamentals/persistent-container-dark.png';
 import persistentContainerLight from '@assets/fundamentals/persistent-container-light.png';
 import persistentContainerDocker from '@assets/whats-new/aspire-9/persistent-container-docker-desktop.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire resources support a number of different lifetime modes. For example, the default **session lifetime** starts a resource when the AppHost starts and shuts it down when the AppHost exits. A **persistent lifetime** leaves a resource running when the AppHost exits and can reuse the same instance on the next run.
 
@@ -29,11 +30,11 @@ A session lifetime creates the resource when the AppHost starts and disposes of
 
 Use session lifetime for resources that should only exist while the AppHost is running, such as local test dependencies, temporary containers, or processes that don't need stable state across runs. Session resources also default to proxied endpoints, which are available while the AppHost is running.
 
-If you previously configured another lifetime and want to return a resource to the default behavior, call `WithSessionLifetime()`. For container resources, `WithLifetime(ContainerLifetime.Session)` is still supported.
+If you previously configured another lifetime and want to return a resource to the default behavior, call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithSessionLifetime" />. For container resources, `WithLifetime(ContainerLifetime.Session)` is still supported.
 
 ### Persistent lifetime
 
-A persistent lifetime reuses a previously created resource when possible and doesn't dispose of it when the AppHost stops. Configure this behavior with `WithPersistentLifetime()`, or with the existing container-specific `WithLifetime(ContainerLifetime.Persistent)` API for container resources.
+A persistent lifetime reuses a previously created resource when possible and doesn't dispose of it when the AppHost stops. Configure this behavior with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithPersistentLifetime" />, or with the existing container-specific `WithLifetime(ContainerLifetime.Persistent)` API for container resources.
 
 Use persistent lifetime for resources that are expensive to initialize, need stable local endpoints, or should remain available while you restart or rebuild the AppHost. Common examples include databases, message brokers, emulators, long-running executables, and project resources that should continue running after the AppHost exits.
 
@@ -80,9 +81,9 @@ Aspire evaluates the source resource's lifetime when it prepares the application
 
 ## Defer resource start with explicit start
 
-Use `WithExplicitStart()` to prevent a resource from starting automatically with the rest of the AppHost. The resource appears in the dashboard but remains stopped until you start it manually.
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> to prevent a resource from starting automatically with the rest of the AppHost. The resource appears in the dashboard but remains stopped until you start it manually.
 
-Starting in Aspire 13.5, `WithExplicitStart()` also affects when execution configuration callbacks (for example, `WithEnvironment` and `WithArgs`) are evaluated, depending on whether the resource is session-scoped or persistent.
+Starting in Aspire 13.5, `WithExplicitStart()` also affects when execution configuration callbacks (for example, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" />) are evaluated, depending on whether the resource is session-scoped or persistent.
 
 ### Session-scoped explicit-start resources
 
@@ -257,7 +258,7 @@ Persistent project and executable resources are run by Aspire's orchestrator so
 
 ## Match another resource's lifetime
 
-Use `WithLifetimeOf` when a companion resource should follow another resource's lifetime. This is useful when a sidecar, helper process, or supporting service should become persistent only when its source resource is persistent.
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithLifetimeOf" /> when a companion resource should follow another resource's lifetime. This is useful when a sidecar, helper process, or supporting service should become persistent only when its source resource is persistent.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -305,7 +306,7 @@ The dependent resource's lifetime is evaluated when Aspire prepares the applicat
 
 ## Scope cleanup to a parent process
 
-Use `WithParentProcessLifetime` when a resource should survive AppHost restarts but be cleaned up when another process exits. Aspire records the parent process identity instead of retaining a live process handle, so the cleanup scope follows the specific process instance instead of a reused process ID.
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithParentProcessLifetime" /> when a resource should survive AppHost restarts but be cleaned up when another process exits. Aspire records the parent process identity instead of retaining a live process handle, so the cleanup scope follows the specific process instance instead of a reused process ID.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -413,7 +414,7 @@ For example, if you have a service named `"postgres"` in an AppHost project loca
 
 ### Custom container names
 
-For advanced scenarios, you can set a custom container name using the `WithContainerName` method:
+For advanced scenarios, you can set a custom container name using the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerName" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx
index 27c4a361ce..6728fe5fc2 100644
--- a/src/frontend/src/content/docs/app-host/typescript-apphost.mdx
+++ b/src/frontend/src/content/docs/app-host/typescript-apphost.mdx
@@ -7,6 +7,7 @@ description: Learn the files and configuration that make up a TypeScript AppHost
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import FileTree from 'starlight-plugin-icons/components/FileTree.astro';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 When you create a TypeScript AppHost with `aspire new`, the CLI scaffolds a project with the following structure:
 
@@ -295,7 +296,7 @@ The Aspire CLI supports the following package managers at the **AppHost root** 
 | Deno | `packageManager`, `deno.lock`, `deno.json`, or `deno.jsonc` | Deno 2 or later |
 | Yarn Classic (v1) | `yarn.lock` with `# yarn lockfile v1` or `packageManager` with `yarn@1.x` | Not supported |
 
-This policy governs the **AppHost root only**. Apps the AppHost orchestrates — for example, a Node.js service added with `addNodeApp`, a Bun guest app, or a workspace package — can use any package manager their own tooling requires; they are independent of the AppHost-root toolchain.
+This policy governs the **AppHost root only**. Apps the AppHost orchestrates — for example, a Node.js service added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" />, a Bun guest app, or a workspace package — can use any package manager their own tooling requires; they are independent of the AppHost-root toolchain.
 
 Aspire end-to-end tests cover TypeScript AppHosts with representative `packageManager` pins such as `npm@10.0.0`, `pnpm@10.0.0`, `yarn@4.14.1`, and `bun@1.2.0`. These tested versions are representative points within the supported ranges, not the only versions you can use.
 
@@ -456,7 +457,7 @@ Bun has built-in TypeScript support, so it runs `apphost.mts` directly without `
 
 ### Use Deno as the AppHost runtime
 
-Install Deno 2 or later and select it with a Deno configuration file, lockfile, or a `packageManager` entry such as `"deno@2.0.0"`. The generated AppHost module and resource APIs stay the same. This is distinct from [hosting a Deno application](/integrations/frameworks/deno/deno-host/): `addDenoApp` models a guest resource and doesn't choose the AppHost runtime.
+Install Deno 2 or later and select it with a Deno configuration file, lockfile, or a `packageManager` entry such as `"deno@2.0.0"`. The generated AppHost module and resource APIs stay the same. This is distinct from [hosting a Deno application](/integrations/frameworks/deno/deno-host/): <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddDenoApp" /> models a guest resource and doesn't choose the AppHost runtime.
 
 Aspire restores dependencies with `deno install` and validates the AppHost with `deno check`. Deno uses its own configuration rather than `tsconfig.apphost.json`. Watch mode uses Deno's native watcher and checks types on every restart, without `tsx` or `nodemon`. The CLI rejects Deno 1.x.
 
diff --git a/src/frontend/src/content/docs/app-host/with-terminal.mdx b/src/frontend/src/content/docs/app-host/with-terminal.mdx
index 3f7ebb3199..40f341228e 100644
--- a/src/frontend/src/content/docs/app-host/with-terminal.mdx
+++ b/src/frontend/src/content/docs/app-host/with-terminal.mdx
@@ -10,8 +10,9 @@ import terminalResourceDark from '@assets/dashboard/terminals/terminal-resource-
 import terminalResourceLight from '@assets/dashboard/terminals/terminal-resource-light.png';
 import terminalDetachedDark from '@assets/dashboard/terminals/terminal-detached-dark.png';
 import terminalDetachedLight from '@assets/dashboard/terminals/terminal-detached-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
-If you have a terminal user interface (TUI) application or a shell-based experience that you want to exercise while it runs under Aspire, add `WithTerminal(...)` to the resource. Aspire then exposes an interactive terminal session that you can attach to from the [Aspire dashboard](/dashboard/overview/) or from the [`aspire terminal`](/reference/cli/commands/aspire-terminal/) CLI command.
+If you have a terminal user interface (TUI) application or a shell-based experience that you want to exercise while it runs under Aspire, add <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" /> to the resource. Aspire then exposes an interactive terminal session that you can attach to from the [Aspire dashboard](/dashboard/overview/) or from the [`aspire terminal`](/reference/cli/commands/aspire-terminal/) CLI command.
 
 For an introduction to the resource Terminal view, terminal dock, and detached windows, start with [Dashboard terminals](/dashboard/terminals/).
 
@@ -78,7 +79,7 @@ Reach for `WithTerminal` when a resource is interactive rather than a plain back
 
 The [TypeScript terminal basics sample](https://github.com/microsoft/aspire-samples/tree/main/samples/terminals/basics-typescript) and [C# terminal basics sample](https://github.com/microsoft/aspire-samples/tree/main/samples/terminals/basics-csharp) demonstrate this with a containerized REST client, an API, and Redis.
 
-The [TypeScript AppHost](https://github.com/microsoft/aspire-samples/blob/main/samples/terminals/basics-typescript/apphost.mts) and [C# AppHost](https://github.com/microsoft/aspire-samples/blob/main/samples/terminals/basics-csharp/apphost.cs) build the client's image with `AddDockerfile`, pass the API endpoint through `BASE_URL`, wait for the API, and enable the terminal with `WithTerminal()`. The client runs as the resource's main process; there is no separate client session to create.
+The [TypeScript AppHost](https://github.com/microsoft/aspire-samples/blob/main/samples/terminals/basics-typescript/apphost.mts) and [C# AppHost](https://github.com/microsoft/aspire-samples/blob/main/samples/terminals/basics-csharp/apphost.cs) build the client's image with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfile" />, pass the API endpoint through `BASE_URL`, wait for the API, and enable the terminal with `WithTerminal()`. The client runs as the resource's main process; there is no separate client session to create.
 
 Follow either sample's README to send a request from the resource terminal, change the stored data through Redis's separate REPL command, and read it back through the API. This illustrates the distinction between an interactive resource and an [ephemeral terminal](/dashboard/ephemeral-terminals/) without requiring host installations of the client tools.
 
@@ -170,7 +171,7 @@ builder.Build().Run();
 
 ## Terminals and replicas
 
-Each replica of a resource gets its own independent terminal session. Aspire creates one terminal host per parent replica, so requesting three replicas yields three separate terminals. The order of `WithReplicas` and `WithTerminal` does not matter. For a project-based interactive app in `../Agent/Agent.csproj`:
+Each replica of a resource gets its own independent terminal session. Aspire creates one terminal host per parent replica, so requesting three replicas yields three separate terminals. The order of <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithReplicas" /> and `WithTerminal` does not matter. For a project-based interactive app in `../Agent/Agent.csproj`:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/app-host/withdockerfile.mdx b/src/frontend/src/content/docs/app-host/withdockerfile.mdx
index df30b82577..0c1cbab721 100644
--- a/src/frontend/src/content/docs/app-host/withdockerfile.mdx
+++ b/src/frontend/src/content/docs/app-host/withdockerfile.mdx
@@ -5,8 +5,9 @@ description: Add Dockerfiles to your Aspire app model with WithDockerfile — bu
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
-With Aspire it's possible to specify a _Dockerfile_ to build when the [AppHost](/get-started/app-host/) is started using either the `AddDockerfile` or `WithDockerfile` extension methods.
+With Aspire it's possible to specify a _Dockerfile_ to build when the [AppHost](/get-started/app-host/) is started using either the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfile" /> or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfile" /> extension methods.
 
 These two methods serve different purposes:
 
@@ -126,7 +127,7 @@ await pgsql.withPgAdmin(); // Still works because it's still a PostgreSQL resour
 
 ## Generate a Dockerfile programmatically
 
-Use `AddDockerfileBuilder` or `WithDockerfileBuilder` when you need Aspire to generate a Dockerfile from AppHost code. These APIs are useful when the Dockerfile depends on AppHost configuration, when you want to compose Dockerfile fragments, or when you want to keep multi-stage image build logic near the resource definition.
+Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" /> when you need Aspire to generate a Dockerfile from AppHost code. These APIs are useful when the Dockerfile depends on AppHost configuration, when you want to compose Dockerfile fragments, or when you want to keep multi-stage image build logic near the resource definition.
 
 <Aside type="caution">
   The Dockerfile builder APIs are experimental and may change in future
@@ -249,7 +250,7 @@ await builder.build().run();
 
 ## Generate a Dockerfile with a factory function
 
-Use `AddDockerfileFactory` or `WithDockerfileFactory` when you need to generate a Dockerfile as a string from AppHost code. Unlike the [Dockerfile builder APIs](#generate-a-dockerfile-programmatically) that use a fluent API to compose Dockerfile instructions, the factory APIs let you return Dockerfile content directly as a string — useful when you already have string-based Dockerfile generation logic or want to construct content conditionally.
+Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileFactory" /> or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileFactory" /> when you need to generate a Dockerfile as a string from AppHost code. Unlike the [Dockerfile builder APIs](#generate-a-dockerfile-programmatically) that use a fluent API to compose Dockerfile instructions, the factory APIs let you return Dockerfile content directly as a string — useful when you already have string-based Dockerfile generation logic or want to construct content conditionally.
 
 The factory callback receives a `DockerfileFactoryContext` parameter that provides access to the resource and DI services when needed.
 
@@ -344,7 +345,7 @@ await builder.build().run();
 
 ## Pass build arguments
 
-The `WithBuildArg` method can be used to pass arguments into the container image build.
+The <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildArg" /> method can be used to pass arguments into the container image build.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -419,7 +420,7 @@ CMD ["./mygoapp"]
 
 ## Pass build secrets
 
-In addition to build arguments it's possible to specify build secrets using `WithBuildSecret` which are made selectively available to individual commands in the _Dockerfile_ using the `--mount=type=secret` syntax on `RUN` commands.
+In addition to build arguments it's possible to specify build secrets using <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildSecret" /> which are made selectively available to individual commands in the _Dockerfile_ using the `--mount=type=secret` syntax on `RUN` commands.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/architecture/multi-language-architecture.mdx b/src/frontend/src/content/docs/architecture/multi-language-architecture.mdx
index 0709757d1f..241dafec22 100644
--- a/src/frontend/src/content/docs/architecture/multi-language-architecture.mdx
+++ b/src/frontend/src/content/docs/architecture/multi-language-architecture.mdx
@@ -5,6 +5,7 @@ description: Understand how Aspire uses a guest/host architecture, ATS, SDK gene
 ---
 
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire supports writing AppHosts in multiple languages. While the orchestration engine is built on .NET, a guest/host architecture allows AppHosts written in TypeScript today, and additional languages in the future, to access Aspire integrations, service discovery, and the dashboard.
 
@@ -12,7 +13,7 @@ Aspire supports writing AppHosts in multiple languages. While the orchestration
 
 Aspire's hosting integrations and deployment publishers are written in .NET and have already accumulated the runtime behavior needed for local orchestration, diagnostics, and publishing. Rewriting those integrations for every guest language would duplicate a large amount of behavior and significantly increase maintenance cost.
 
-Instead, guest languages only declare resources such as `addRedis`, `addPostgres`, and `withReference`, while the .NET host handles orchestration concerns such as starting containers, wiring service discovery, running health checks, and generating deployment artifacts. The trade-off is a local IPC hop, which is much cheaper than maintaining the same integration surface independently in multiple languages.
+Instead, guest languages only declare resources such as <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" />, <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" />, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, while the .NET host handles orchestration concerns such as starting containers, wiring service discovery, running health checks, and generating deployment artifacts. The trade-off is a local IPC hop, which is much cheaper than maintaining the same integration surface independently in multiple languages.
 
 ## Guest/host model
 
@@ -55,7 +56,7 @@ flowchart TB
 2. The ATS scanner inspects assemblies for exports and generates the TypeScript SDK into `.aspire/modules/`.
 3. The CLI starts the host process and creates the local socket or pipe endpoint.
 4. The CLI starts the guest process and passes connection details through environment variables.
-5. The guest connects and invokes capabilities such as `createBuilder`, `addRedis`, `build`, and `run`.
+5. The guest connects and invokes capabilities such as <ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" />, `addRedis`, `build`, and <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" />.
 6. The host orchestrates resources, starts the dashboard, and manages the application lifecycle.
 
 ## Token-based authentication
diff --git a/src/frontend/src/content/docs/architecture/resource-api-patterns.mdx b/src/frontend/src/content/docs/architecture/resource-api-patterns.mdx
index 9b48d32c59..d7f68914d9 100644
--- a/src/frontend/src/content/docs/architecture/resource-api-patterns.mdx
+++ b/src/frontend/src/content/docs/architecture/resource-api-patterns.mdx
@@ -5,6 +5,7 @@ description: Discover common API resource patterns in Aspire, including how to a
 ---
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire's resource model allows you to define and configure resources in a structured way, enabling seamless integration and management of your application's components. This guide provides details the common patterns for adding and configuring resources in Aspire.
 
@@ -294,7 +295,7 @@ Custom value objects defer evaluation and allow the framework to discover depend
 | `IValueWithReferences` _(opt.)_ | `IEnumerable<object> References { get; }` | Both (if needed) | Declare dependencies on other resources |
 
 - **Implement** `IValueProvider` and `IManifestExpressionProvider` on all structured value types.  
-- **Implement** `IExpressionValue` when a structured value type should be accepted by APIs such as `WithEnvironment(...)`.
+- **Implement** `IExpressionValue` when a structured value type should be accepted by APIs such as <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />.
 - **Implement** `IValueWithReferences` only when your type holds resource references.
 
 ### Attaching to resources
diff --git a/src/frontend/src/content/docs/architecture/resource-examples.mdx b/src/frontend/src/content/docs/architecture/resource-examples.mdx
index 63bce99be0..b8ea7321de 100644
--- a/src/frontend/src/content/docs/architecture/resource-examples.mdx
+++ b/src/frontend/src/content/docs/architecture/resource-examples.mdx
@@ -5,6 +5,8 @@ description: "Explore complete, runnable examples that demonstrate Aspire's reso
 next: false
 ---
 
+import ApiReference from '@components/ApiReference.astro';
+
 Aspire provides a flexible resource model that allows you to define and configure resources in a structured way. This guide explores common patterns for adding and configuring resources, including examples of custom resources and how to implement them.
 
 ## Example: Derived Container Resource (Redis)
@@ -13,7 +15,7 @@ This example shows how to create a custom resource (`RedisResource`) that derive
 
 - Defining a data-only resource class.
 - Implementing `IResourceWithConnectionString` with deferred evaluation using `ReferenceExpression`.
-- Creating an `AddRedis` extension method that handles parameter validation, password management, event subscription, health checks, and container configuration using fluent APIs.
+- Creating an <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> extension method that handles parameter validation, password management, event subscription, health checks, and container configuration using fluent APIs.
 
 ```csharp title="RedisResourceExtensions.cs"
 public static class RedisResourceExtensions
diff --git a/src/frontend/src/content/docs/architecture/resource-hierarchies.mdx b/src/frontend/src/content/docs/architecture/resource-hierarchies.mdx
index 1182c06d7e..3de40dcfac 100644
--- a/src/frontend/src/content/docs/architecture/resource-hierarchies.mdx
+++ b/src/frontend/src/content/docs/architecture/resource-hierarchies.mdx
@@ -5,6 +5,7 @@ description: Model parent-child resource relationships in Aspire to express owne
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire supports modeling **parent-child relationships** between resources to express ownership, containment, and grouping.
 
@@ -28,7 +29,7 @@ When a resource implements the `IResourceWithParent` interface, it declares **tr
 
 ## Visual grouping (without lifecycle impact)
 
-Aspire also supports **visual-only parent-child relationships** using the `WithParentRelationship()` method during resource construction.
+Aspire also supports **visual-only parent-child relationships** using the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithParentRelationship" /> method during resource construction.
 
 Visual relationships:
 
@@ -113,7 +114,7 @@ Endpoints are modeled as **external entities**:
 
 Resources connect to each other through:
 
-- **`WithReference()` calls**: Direct resource-to-resource dependencies.
+- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> calls**: Direct resource-to-resource dependencies.
 - **Environment variables and CLI arguments**: Configuration values containing structured references.
 - **Other configuration sources**: Settings populated with structured value references.
 
@@ -361,7 +362,7 @@ Error accessing Url: Endpoint has not been allocated.
 ```
 
 <Aside type="tip">
-  The overloads of `WithEnvironment` that take a callback run after endpoints
+  The overloads of <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> that take a callback run after endpoints
   have been allocated.
 </Aside>
 
diff --git a/src/frontend/src/content/docs/architecture/resource-publishing.mdx b/src/frontend/src/content/docs/architecture/resource-publishing.mdx
index eece9edb0e..ff91418a81 100644
--- a/src/frontend/src/content/docs/architecture/resource-publishing.mdx
+++ b/src/frontend/src/content/docs/architecture/resource-publishing.mdx
@@ -5,6 +5,7 @@ description: Learn how Aspire publishes resource manifests as JSON for deploymen
 ---
 
 import { Steps } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire provides a flexible mechanism for publishing resource manifests, enabling seamless integration with various deployment environments. Resources are serialized into JSON format, which can be consumed by deployment tools.
 
@@ -18,7 +19,7 @@ Custom resources that publish JSON manifest entries must:
 
 </Steps>
 
-Resources can opt-out of being included in the publishing manifest entirely by calling the `ExcludeFromManifest()` extension method on the `IResourceBuilder<T>`. Resources marked this way will be omitted when generating publishing assets like Docker Compose files or Kubernetes manifests.
+Resources can opt-out of being included in the publishing manifest entirely by calling the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" /> extension method on the `IResourceBuilder<T>`. Resources marked this way will be omitted when generating publishing assets like Docker Compose files or Kubernetes manifests.
 
 ## Registering the callback
 
diff --git a/src/frontend/src/content/docs/dashboard/ephemeral-terminals.mdx b/src/frontend/src/content/docs/dashboard/ephemeral-terminals.mdx
index 219df74176..f946cd2c95 100644
--- a/src/frontend/src/content/docs/dashboard/ephemeral-terminals.mdx
+++ b/src/frontend/src/content/docs/dashboard/ephemeral-terminals.mdx
@@ -3,6 +3,8 @@ title: Create ephemeral terminals from your AppHost
 description: Use TerminalService to launch interactive processes, display docked terminals, and manage their lifetime independently of resources in your AppHost.
 ---
 
+import ApiReference from '@components/ApiReference.astro';
+
 Ephemeral terminals let AppHost code launch an interactive process for a specific task and display it in the dashboard. Redis's `WithRepl()` is one example: it adds a resource command that opens an authenticated `redis-cli` session inside the running container.
 
 The same building blocks are available for your own commands. Use `Aspire.Hosting.ApplicationModel.TerminalService` to create a terminal, configure its executable and placement, start its process, and show it in the dock. The [custom docked SQL REPL sample](https://github.com/microsoft/aspire-samples/tree/main/samples/terminals/docked-repl-csharp) demonstrates this with rqlite's SQL client.
@@ -75,7 +77,7 @@ The same mechanism can launch other interactive programs, not just REPLs. For ex
 
 ## Open a database or cache REPL
 
-A read-eval-print loop (REPL) accepts commands and displays their results interactively. The built-in `WithRepl()` methods are examples of this command-driven experience: they add an opt-in **REPL** resource command that opens the integration's bundled client in the dashboard terminal dock. They don't replace the database server's process or require `WithTerminal()`.
+A read-eval-print loop (REPL) accepts commands and displays their results interactively. The built-in `WithRepl()` methods are examples of this command-driven experience: they add an opt-in **REPL** resource command that opens the integration's bundled client in the dashboard terminal dock. They don't replace the database server's process or require <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" />.
 
 For a complete TypeScript or C# Redis example, follow [Use the terminal dock](/dashboard/terminals/#use-the-terminal-dock). It covers setup, opening the **REPL** command, checking the connection with `PING`, and exiting cleanly.
 
diff --git a/src/frontend/src/content/docs/dashboard/explore.mdx b/src/frontend/src/content/docs/dashboard/explore.mdx
index 469382ca4e..b01bbcadb4 100644
--- a/src/frontend/src/content/docs/dashboard/explore.mdx
+++ b/src/frontend/src/content/docs/dashboard/explore.mdx
@@ -127,6 +127,7 @@ import terminalDockDark from '@assets/dashboard/terminals/terminal-dock-dark.png
 import terminalDockLight from '@assets/dashboard/terminals/terminal-dock-light.png';
 import dashboardRunSelector from '@assets/dashboard/explore/dashboard-run-selector.png';
 import dashboardRunSelectorExpanded from '@assets/dashboard/explore/dashboard-run-selector-expanded.png';
+import ApiReference from '@components/ApiReference.astro';
 
 In the upcoming sections, you discover how to create an Aspire project and embark on the following tasks:
 
@@ -350,11 +351,11 @@ You can download any console log to your local machine and use your preferred te
 
 <ThemeImage dark={downloadConsoleLogs} light={downloadConsoleLogsLight} alt="A screenshot of the Aspire dashboard Console logs page showing how to download a log to your local machine." />
 
-Resources configured with `WithTerminal` also provide an interactive **Terminal** view. For resource terminals, the AppHost terminal dock, detached windows, and keyboard controls, see [Dashboard terminals](/dashboard/terminals/).
+Resources configured with <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" /> also provide an interactive **Terminal** view. For resource terminals, the AppHost terminal dock, detached windows, and keyboard controls, see [Dashboard terminals](/dashboard/terminals/).
 
 #### Resource replicas
 
-When project resources are replicated using the `WithReplicas` API, they're represented in the resource selector under a top-level named resource entry with an icon to indicator. Each replicated resource is listed under the top-level resource entry, with its corresponding unique name. Consider the following example screenshot of a replicated project resource:
+When project resources are replicated using the <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithReplicas" /> API, they're represented in the resource selector under a top-level named resource entry with an icon to indicator. Each replicated resource is listed under the top-level resource entry, with its corresponding unique name. Consider the following example screenshot of a replicated project resource:
 
 <ThemeImage dark={consoleLogsWithReplicas} light={consoleLogsWithReplicasLight} alt="Aspire dashboard: Console logs page resource selector with nested replica resources." />
 
diff --git a/src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx b/src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx
index 148dc37e1c..ba3a52380d 100644
--- a/src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx
+++ b/src/frontend/src/content/docs/dashboard/telemetry-after-deployment.mdx
@@ -5,6 +5,7 @@ description: Understand how telemetry and the Aspire dashboard work after you de
 
 import { Aside, Steps } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 The Aspire dashboard is designed for local development and short-term diagnostics. It offers configurable persistence and built-in limits on how much data it retains, but it isn't intended for long-term production observability. After deploying your app to a production environment, configure a durable telemetry backend.
 
@@ -100,7 +101,7 @@ If some or all logs don't appear in your telemetry backend after deployment, che
 
 ### OTEL environment variables not set
 
-Verify that the OTEL environment variables are correctly set in your deployed containers. When deploying to Azure Container Apps, Aspire sets these variables automatically when you use `WithReference` for Application Insights or when you configure the OTEL endpoint.
+Verify that the OTEL environment variables are correctly set in your deployed containers. When deploying to Azure Container Apps, Aspire sets these variables automatically when you use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> for Application Insights or when you configure the OTEL endpoint.
 
 Check for these environment variables in your deployed container:
 
diff --git a/src/frontend/src/content/docs/dashboard/terminals.mdx b/src/frontend/src/content/docs/dashboard/terminals.mdx
index 830159b2c2..3ff8c2994b 100644
--- a/src/frontend/src/content/docs/dashboard/terminals.mdx
+++ b/src/frontend/src/content/docs/dashboard/terminals.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import resourceTerminal from '@assets/dashboard/terminals/resource-terminal.png';
 import terminalDock from '@assets/dashboard/terminals/redis-repl-dock.png';
 import detachedTerminal from '@assets/dashboard/terminals/detached-terminal.png';
+import ApiReference from '@components/ApiReference.astro';
 
 The Aspire dashboard can display interactive terminal applications as well as logs. A terminal lets you type into a running process, respond to its prompts, and use a terminal user interface (TUI) without leaving the dashboard.
 
@@ -22,8 +23,8 @@ Aspire has two kinds of terminals: those attached to resources in your app model
 
 | Kind | Purpose | Where it appears |
 | ---- | ------- | ---------------- |
-| **Resource terminal** | Interact with a resource's own process, such as a TUI or shell, configured with `WithTerminal()`. | The resource's **Terminal** view on the **Console logs** page. |
-| **Ephemeral terminal** | Run a purpose-specific tool, such as a database REPL opened with `WithRepl()`. The AppHost owns this separate process. | The terminal dock. |
+| **Resource terminal** | Interact with a resource's own process, such as a TUI or shell, configured with <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" />. | The resource's **Terminal** view on the **Console logs** page. |
+| **Ephemeral terminal** | Run a purpose-specific tool, such as a database REPL opened with <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithRepl" />. The AppHost owns this separate process. | The terminal dock. |
 
 Ephemeral terminals aren't resources in the app model. They can remain available for a task or session; their lifetime is controlled by the AppHost code that creates them or by closing their dock tab. Opening a resource or dock terminal in a separate window changes only its presentation, not its kind or process.
 
diff --git a/src/frontend/src/content/docs/deployment/azure/app-service.mdx b/src/frontend/src/content/docs/deployment/azure/app-service.mdx
index 258a1f3dfd..b70345b7c3 100644
--- a/src/frontend/src/content/docs/deployment/azure/app-service.mdx
+++ b/src/frontend/src/content/docs/deployment/azure/app-service.mdx
@@ -6,6 +6,7 @@ description: "Deploy Aspire applications to Azure App Service with the `aspire d
 
 import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="🧪 Preview" variant="note" size="large" class="mb-1" />
 
@@ -75,7 +76,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-For a standard App Service deployment, you only need the environment and a supported app resource. Use `PublishAsAzureAppServiceWebsite` only when you want to customize the generated website or deployment slot.
+For a standard App Service deployment, you only need the environment and a supported app resource. Use <ApiReference name="Aspire.Hosting.AzureAppServiceComputeResourceExtensions.PublishAsAzureAppServiceWebsite" /> only when you want to customize the generated website or deployment slot.
 
 ## How Aspire maps your app to Azure App Service
 
@@ -270,7 +271,7 @@ await builder.build().run();
 
 ### Environment-variable name validation
 
-Azure App Service application settings accept only letters, numbers, and underscores. If a connection name contains dashes and you intentionally want to bypass App Service name validation for that website, call `SkipEnvironmentVariableNameChecks()` after `PublishAsAzureAppServiceWebsite`.
+Azure App Service application settings accept only letters, numbers, and underscores. If a connection name contains dashes and you intentionally want to bypass App Service name validation for that website, call <ApiReference name="Aspire.Hosting.AzureAppServiceComputeResourceExtensions.SkipEnvironmentVariableNameChecks" /> after `PublishAsAzureAppServiceWebsite`.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/deployment/azure/azure-developer-cli.mdx b/src/frontend/src/content/docs/deployment/azure/azure-developer-cli.mdx
index 9a271f3139..db4e35a437 100644
--- a/src/frontend/src/content/docs/deployment/azure/azure-developer-cli.mdx
+++ b/src/frontend/src/content/docs/deployment/azure/azure-developer-cli.mdx
@@ -9,6 +9,7 @@ topic: deployment
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 The Azure Developer CLI (`azd`) is still supported with Aspire for existing workflows, but it is no longer the recommended default deployment path.
 
@@ -37,7 +38,7 @@ This page does not duplicate `azd`'s full operational workflow. For install, ini
 
 ## Resource naming
 
-The `aspire deploy` path and `azd` use different resource naming schemes by default. If you're upgrading from an existing `azd` deployment to `aspire deploy`, use `WithAzdResourceNaming()` to preserve the original naming convention. This avoids creating duplicate Azure resources:
+The `aspire deploy` path and `azd` use different resource naming schemes by default. If you're upgrading from an existing `azd` deployment to `aspire deploy`, use <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithAzdResourceNaming" /> to preserve the original naming convention. This avoids creating duplicate Azure resources:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -85,7 +86,7 @@ Aspire parameters and `azd` inputs follow different paths:
 
 | Parameter type                                     | How it reaches Azure resources                                                                                                                     |
 | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Aspire parameters** (`AddParameter`)             | Resolved by the AppHost through .NET configuration when generating the manifest. Use `appsettings.{env}.json` or environment variables.            |
+| **Aspire parameters** (<ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" />)             | Resolved by the AppHost through .NET configuration when generating the manifest. Use `appsettings.{env}.json` or environment variables.            |
 | **`azd` infrastructure inputs (Bicep parameters)** | Prompted by `azd provision` and stored in `.azure/{name}/config.json`. Used by `azd` directly during Bicep deployment — not passed to the AppHost. |
 | **Secrets**                                        | Prompted by `azd provision` and stored in a local vault. Injected into Bicep parameters during provisioning.                                       |
 
diff --git a/src/frontend/src/content/docs/deployment/azure/azure-security-best-practices.mdx b/src/frontend/src/content/docs/deployment/azure/azure-security-best-practices.mdx
index dcf3f31b4f..b2bd56d87d 100644
--- a/src/frontend/src/content/docs/deployment/azure/azure-security-best-practices.mdx
+++ b/src/frontend/src/content/docs/deployment/azure/azure-security-best-practices.mdx
@@ -6,6 +6,7 @@ description: Harden Aspire deployments to Azure with private networking, managed
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 When you deploy Aspire apps to Azure, the base security posture comes from the deployment target you choose and the Azure resources you provision. This guide explains what Aspire configures for you by default and how to work with either the standard public networking model or the private-networked model, then harden the deployment with managed identities, Key Vault, and monitoring.
 
@@ -84,8 +85,8 @@ await builder.build().run();
 
 This pattern has a few important behaviors:
 
-- `WithDelegatedSubnet` configures the subnet delegation Azure Container Apps environments require.
-- `AddPrivateEndpoint` automatically creates the private DNS zone, virtual network link, and DNS zone group the target service needs.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithDelegatedSubnet" /> configures the subnet delegation Azure Container Apps environments require.
+- <ApiReference name="Aspire.Hosting.AzurePrivateEndpointExtensions.AddPrivateEndpoint" /> automatically creates the private DNS zone, virtual network link, and DNS zone group the target service needs.
 - In publish and deploy flows, adding a private endpoint also disables public network access on the target Azure resource by default.
 - Resources that reference the target keep using the same connection information; private DNS resolves the hostname to the private IP inside the virtual network.
 
diff --git a/src/frontend/src/content/docs/deployment/azure/container-apps.mdx b/src/frontend/src/content/docs/deployment/azure/container-apps.mdx
index 7bcbc42771..ecb27e11b5 100644
--- a/src/frontend/src/content/docs/deployment/azure/container-apps.mdx
+++ b/src/frontend/src/content/docs/deployment/azure/container-apps.mdx
@@ -6,6 +6,7 @@ description: "Deploy Aspire applications to Azure Container Apps with the `aspir
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Use `aspire deploy` to deploy Aspire applications to Azure Container Apps. Aspire provisions the Container Apps environment, Azure Container Registry, managed identity, and the Container Apps resources needed for the compute resources in your AppHost.
 
@@ -232,7 +233,7 @@ await builder.build().run();
 
 ### Custom domains
 
-Use `ConfigureCustomDomain` when you want Aspire to configure a custom domain and managed certificate on the generated Container App.
+Use <ApiReference name="Aspire.Hosting.ContainerAppExtensions.ConfigureCustomDomain" /> when you want Aspire to configure a custom domain and managed certificate on the generated Container App.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -278,7 +279,7 @@ await builder.build().run();
 
 ### Internal service discovery
 
-Services deployed to Azure Container Apps use internal DNS for service discovery. Use `WithExternalHttpEndpoints()` only for endpoints you want reachable outside the Container Apps environment.
+Services deployed to Azure Container Apps use internal DNS for service discovery. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" /> only for endpoints you want reachable outside the Container Apps environment.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -358,7 +359,7 @@ await env.withDashboard(false);
 
 <Aside type="danger" title="Experimental">
   Express environments are experimental and may change in future releases. The
-  `AsExpress` API reports [ASPIREACAEXPRESS001](/diagnostics/aspireacaexpress001/),
+  <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AsExpress" /> API reports [ASPIREACAEXPRESS001](/diagnostics/aspireacaexpress001/),
   which you must suppress to build. Check the
   [Azure Container Apps Express overview](https://learn.microsoft.com/azure/container-apps/express-overview)
   for current availability and supported features before you adopt it.
@@ -419,7 +420,7 @@ The following limitations apply when you use Express:
 - **Referenced endpoints must be public.** Express apps have no private `.internal` hostname, so a referenced endpoint must be explicitly exposed with `WithExternalHttpEndpoints`. Referencing an internal-only endpoint fails during deployment rather than emitting an address that can't resolve. Exposing an endpoint doesn't add authentication — enforce authorization in the app.
 - **HTTPS ingress is required.** Combining `AsExpress` with `WithHttpsUpgrade(false)` is rejected, in either call order.
 
-You can combine `AsExpress` with `AsExisting` or `PublishAsExisting` to declare that an existing environment already uses Express. Aspire doesn't verify or convert the deployed environment's mode.
+You can combine `AsExpress` with <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> or <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> to declare that an existing environment already uses Express. Aspire doesn't verify or convert the deployed environment's mode.
 
 ## Deploy with aspire deploy
 
diff --git a/src/frontend/src/content/docs/deployment/azure/sandboxes.mdx b/src/frontend/src/content/docs/deployment/azure/sandboxes.mdx
index 8eaea27858..b7a80d7049 100644
--- a/src/frontend/src/content/docs/deployment/azure/sandboxes.mdx
+++ b/src/frontend/src/content/docs/deployment/azure/sandboxes.mdx
@@ -6,6 +6,7 @@ description: "Deploy Aspire compute resources to Azure Container Apps Sandboxes
 
 import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="Preview" variant="caution" size="large" class="mb-1" />
 
@@ -85,7 +86,7 @@ builder.Build().Run();
 
 The sandbox group only affects publish and deploy. When you run the AppHost locally with `aspire run`, Aspire adds the sandbox group to the app model but doesn't provision Azure sandbox resources, so your resources run locally as usual.
 
-For a standard deployment, you only need the sandbox group and your compute resources. Use `PublishAsAzureSandbox` only when you want to customize the sandbox runtime options for a resource.
+For a standard deployment, you only need the sandbox group and your compute resources. Use <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.PublishAsAzureSandbox" /> only when you want to customize the sandbox runtime options for a resource.
 
 ## Customize sandbox runtime options
 
@@ -184,7 +185,7 @@ Durations must use whole-second precision. C# AppHosts use `TimeSpan` values, an
 
 ## Endpoints and access
 
-Aspire creates sandbox ports only for endpoints that are marked external, such as with `WithExternalHttpEndpoints`. Each exposed port gets a public HTTPS URL on the sandbox proxy, which terminates TLS and forwards traffic to the container's target port.
+Aspire creates sandbox ports only for endpoints that are marked external, such as with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" />. Each exposed port gets a public HTTPS URL on the sandbox proxy, which terminates TLS and forwards traffic to the container's target port.
 
 - **Authenticated by default.** External endpoints require Microsoft Entra ID authentication by default. The sandbox port doesn't use an allow-list, so any authenticated Entra ID user can access it.
 - **Anonymous access is opt-in.** To allow anonymous access, set `Anonymous` to `true` for the endpoint in `AzureSandboxOptions.Endpoints`, as shown in the preceding example.
@@ -204,7 +205,7 @@ Sandbox egress uses full traffic inspection with a deny-by-default policy. Aspir
 
 ## Deploy to multiple compute environments
 
-When an AppHost contains more than one compute environment, assign each compute resource explicitly with `WithComputeEnvironment`. `PublishAsAzureSandbox` uses that assignment and doesn't select an environment on its own:
+When an AppHost contains more than one compute environment, assign each compute resource explicitly with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" />. `PublishAsAzureSandbox` uses that assignment and doesn't select an environment on its own:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
@@ -267,15 +268,15 @@ When you run `aspire deploy` directly, Aspire binds the role assignment to the a
 
 For a new sandbox group, Aspire creates a dedicated user-assigned managed identity, attaches it to the sandbox group, and grants it only the `AcrPull` role on the group's Azure Container Registry. The service uses this identity to import private images from the registry. Public registry images are imported without it, and registry credentials aren't sent to the service or stored in deployment state.
 
-Use `WithAcrPullIdentity` to supply a different user-assigned identity. For sandbox groups that Aspire creates, the identity is attached automatically, but you're responsible for granting it `AcrPull` on the registry.
+Use <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.WithAcrPullIdentity" /> to supply a different user-assigned identity. For sandbox groups that Aspire creates, the identity is attached automatically, but you're responsible for granting it `AcrPull` on the registry.
 
 ### Workload identities
 
 The image pull identity isn't exposed to sandbox workloads. To give workloads a managed identity, configure it on the sandbox group:
 
-- `WithSystemAssignedIdentity` adds a system-assigned managed identity for sandbox workloads.
-- `WithUserAssignedIdentity` adds a user-assigned managed identity for sandbox workloads.
-- `WithNoManagedIdentity` clears the workload identities configured on the sandbox group.
+- <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.WithSystemAssignedIdentity" /> adds a system-assigned managed identity for sandbox workloads.
+- <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.WithUserAssignedIdentity" /> adds a user-assigned managed identity for sandbox workloads.
+- <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.WithNoManagedIdentity" /> clears the workload identities configured on the sandbox group.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/deployment/custom-deployments.mdx b/src/frontend/src/content/docs/deployment/custom-deployments.mdx
index 0b7e34ff69..4838e50f59 100644
--- a/src/frontend/src/content/docs/deployment/custom-deployments.mdx
+++ b/src/frontend/src/content/docs/deployment/custom-deployments.mdx
@@ -5,6 +5,7 @@ description: Build container images from your Aspire resources and create custom
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire provides powerful APIs for building container images from your resources during publishing and deployment operations. This article covers the key components that enable programmatic container image creation and progress reporting.
 
@@ -46,7 +47,7 @@ The `IResourceContainerImageManager` is the core service in the `Aspire.Hosting.
 
 ### Configure container builds
 
-Configure each compute resource with `WithContainerBuildOptions`. The callback receives a `ContainerBuildOptionsCallbackContext` that allows you to specify:
+Configure each compute resource with <ApiReference name="Aspire.Hosting.ApplicationModel.ResourceExtensions.WithContainerBuildOptions" />. The callback receives a `ContainerBuildOptionsCallbackContext` that allows you to specify:
 
 - **Destination**: Push the image to a registry or save it as an archive.
 - **Image format**: Docker or Open Container Initiative (OCI) format.
@@ -76,7 +77,7 @@ The progress reporter uses a hierarchical model with guaranteed ordering and thr
 The reporter API provides structured access to progress reporting with the following characteristics:
 
 - **Acquisition**: The pipeline runner creates an `IReportingStep` for each pipeline step and exposes it through `PipelineStepContext.ReportingStep`.
-- **Step creation**: Register steps with `WithPipelineStepFactory` or `builder.Pipeline.AddStep`. The pipeline runner creates the corresponding reporting step during execution.
+- **Step creation**: Register steps with <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" /> or `builder.Pipeline.AddStep`. The pipeline runner creates the corresponding reporting step during execution.
 - **Task creation**: `IReportingStep.CreateTaskAsync(title, ct)` returns an `IReportingTask`.
 - **State transitions**: `SucceedAsync`, `WarnAsync`, `FailAsync` methods accept a summary message.
 - **Completion**: Complete individual tasks in the callback. The runner disposes the reporting step after the callback and completes the overall pipeline operation.
diff --git a/src/frontend/src/content/docs/deployment/deploy-with-aspire.mdx b/src/frontend/src/content/docs/deployment/deploy-with-aspire.mdx
index c30a44d140..aa715cfc1c 100644
--- a/src/frontend/src/content/docs/deployment/deploy-with-aspire.mdx
+++ b/src/frontend/src/content/docs/deployment/deploy-with-aspire.mdx
@@ -9,6 +9,7 @@ import {
   TabItem,
   Tabs,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import LearnMore from '@components/LearnMore.astro';
 
 Aspire deployment is pipeline-based. Add a deployment target to your AppHost, and Aspire gains the steps needed for that target. `aspire publish`, `aspire deploy`, and `aspire do <step>` are different ways of entering that pipeline.
@@ -162,7 +163,7 @@ The placeholder name in published output is target-specific, but the mapping sta
 
 This `.env` example is specific to Docker Compose publish output. It illustrates the **publish artifact handoff** path. `aspire deploy` does not consume this `.env` file; Aspire resolves the parameter before applying changes directly.
 
-Because this example has only one matching compute environment, the project resource attaches to it automatically. Use `WithComputeEnvironment` only when you need to disambiguate between multiple matching targets.
+Because this example has only one matching compute environment, the project resource attaches to it automatically. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" /> only when you need to disambiguate between multiple matching targets.
 
 Parameters answer **what values does this pipeline need?**
 
diff --git a/src/frontend/src/content/docs/deployment/docker-compose.mdx b/src/frontend/src/content/docs/deployment/docker-compose.mdx
index b55a1a80c5..015452f658 100644
--- a/src/frontend/src/content/docs/deployment/docker-compose.mdx
+++ b/src/frontend/src/content/docs/deployment/docker-compose.mdx
@@ -6,6 +6,7 @@ description: Publish and deploy your Aspire application using Docker Compose wit
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Docker Compose is a deployment target for Aspire applications. When you add a Docker Compose environment to your AppHost, Aspire generates Docker Compose files, environment variable configurations, and container images from your app model. You can then deploy these artifacts to any machine running Docker or Podman.
 
@@ -57,7 +58,7 @@ When Podman is the active runtime, Aspire uses `podman-compose` (or the Docker C
 
 ## Prerequisites
 
-To deploy with Docker Compose, add a Docker Compose environment resource to your AppHost using `AddDockerComposeEnvironment`:
+To deploy with Docker Compose, add a Docker Compose environment resource to your AppHost using <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.AddDockerComposeEnvironment" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -217,7 +218,7 @@ When you publish or deploy, Aspire generates the following artifacts in the `asp
 
 ## Generate Dockerfiles from your AppHost
 
-Docker Compose deployments can build images from Dockerfiles that are generated by your AppHost. Use `AddDockerfileBuilder` to create a new container resource from a generated Dockerfile, or `WithDockerfileBuilder` to replace the image for an existing container resource with a generated Dockerfile build.
+Docker Compose deployments can build images from Dockerfiles that are generated by your AppHost. Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> to create a new container resource from a generated Dockerfile, or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" /> to replace the image for an existing container resource with a generated Dockerfile build.
 
 <Aside type="caution">
   The Dockerfile builder APIs are experimental and may change in future
@@ -301,7 +302,7 @@ The Docker hosting integration captures environment variables from your app mode
 
 ### Customize environment file
 
-For advanced scenarios, use `ConfigureEnvFile` to customize the generated `.env` file:
+For advanced scenarios, use <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureEnvFile" /> to customize the generated `.env` file:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -346,7 +347,7 @@ This is useful when you need to add custom environment variables to the generate
 
 ## Customize the Docker Compose file
 
-Use `ConfigureComposeFile` to customize the generated `docker-compose.yml` model before Aspire writes it to disk:
+Use <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureComposeFile" /> to customize the generated `docker-compose.yml` model before Aspire writes it to disk:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -390,7 +391,7 @@ await builder.build().run();
 
 ## Customize Docker Compose services
 
-To customize the generated Docker Compose service for a specific resource, use the `PublishAsDockerComposeService` method. This is optional — all resources are automatically included in the Docker Compose output. Use this method only when you need to modify the generated service definition:
+To customize the generated Docker Compose service for a specific resource, use the <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.PublishAsDockerComposeService" /> method. This is optional — all resources are automatically included in the Docker Compose output. Use this method only when you need to modify the generated service definition:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -437,11 +438,11 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The `configure` callback receives the `DockerComposeServiceResource` and the generated `Service` object, allowing you to modify properties like labels, restart policy, container name, or other Docker Compose service settings. Use `AsEnvironmentPlaceholder` for values that should be written as Compose environment variable placeholders in the generated YAML and `.env` files.
+The `configure` callback receives the `DockerComposeServiceResource` and the generated `Service` object, allowing you to modify properties like labels, restart policy, container name, or other Docker Compose service settings. Use <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.AsEnvironmentPlaceholder" /> for values that should be written as Compose environment variable placeholders in the generated YAML and `.env` files.
 
 ## Resolve Docker Compose service host names
 
-Use `GetHostAddressExpression` when you need the host name that another Docker Compose service should use for an endpoint. In Docker Compose deployments, this expression resolves to the generated service name on the Compose network.
+Use <ApiReference name="Aspire.Hosting.Docker.DockerComposeEnvironmentResource.GetHostAddressExpression" /> when you need the host name that another Docker Compose service should use for an endpoint. In Docker Compose deployments, this expression resolves to the generated service name on the Compose network.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -476,7 +477,7 @@ const apiHost = await compose.getHostAddressExpression(apiEndpoint);
 
 ## Image pull policy
 
-Container resources support an `ImagePullPolicy` that controls when the container runtime pulls an image. Use the `WithImagePullPolicy` extension method to set the policy on a container resource:
+Container resources support an `ImagePullPolicy` that controls when the container runtime pulls an image. Use the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImagePullPolicy" /> extension method to set the policy on a container resource:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -520,7 +521,7 @@ When deploying containers, you can customize how container images are named, tag
 
 ### Set remote image name and tag
 
-Use `WithRemoteImageName` and `WithRemoteImageTag` to customize the image reference:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithRemoteImageName" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithRemoteImageTag" /> to customize the image reference:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -556,7 +557,7 @@ await api.withRemoteImageTag('v1.0.0');
 
 ### Advanced customization with callbacks
 
-For more complex scenarios, use `WithImagePushOptions` to register a callback that dynamically configures push options:
+For more complex scenarios, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithImagePushOptions" /> to register a callback that dynamically configures push options:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -606,7 +607,7 @@ Multiple callbacks can be registered on the same resource, and they are invoked
 
 ### Configure a container registry
 
-Use the `AddContainerRegistry` method to define a container registry and `WithContainerRegistry` to associate resources with it:
+Use the <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.AddContainerRegistry" /> method to define a container registry and <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" /> to associate resources with it:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/deployment/environments.mdx b/src/frontend/src/content/docs/deployment/environments.mdx
index 49b6366cb6..9ed32e74cf 100644
--- a/src/frontend/src/content/docs/deployment/environments.mdx
+++ b/src/frontend/src/content/docs/deployment/environments.mdx
@@ -6,6 +6,7 @@ description: Use Aspire environments to configure your application for developme
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 When you run or deploy an Aspire application, the **environment** determines how the AppHost configures resources, what parameter values are used, and how your deployment is organized. Environments let you use the same AppHost to target different deployment contexts — development, staging, production, or any custom name — without duplicating your application model.
 
@@ -121,7 +122,7 @@ The following convenience methods are available:
 
 ### Set environment variables on child resources
 
-Your services often need to know which environment they're running in. Different frameworks use different environment variables — use `WithEnvironment` to set the appropriate one for each service:
+Your services often need to know which environment they're running in. Different frameworks use different environment variables — use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> to set the appropriate one for each service:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -197,7 +198,7 @@ Common environment variable conventions by framework and ecosystem:
 | Java (Spring)   | `SPRING_PROFILES_ACTIVE`   | `dev`, `test`, `prod`                  |
 
 <Aside type="tip">
-  `AddNodeApp` automatically sets `NODE_ENV` to `development` or `production`
+  <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" /> automatically sets `NODE_ENV` to `development` or `production`
   based on whether the AppHost environment is `Development`. If you need a
   different value (such as `staging`), override it with an explicit
   `WithEnvironment("NODE_ENV", ...)` call as shown above.
diff --git a/src/frontend/src/content/docs/deployment/javascript-apps.mdx b/src/frontend/src/content/docs/deployment/javascript-apps.mdx
index 70446c878c..cb81f93ead 100644
--- a/src/frontend/src/content/docs/deployment/javascript-apps.mdx
+++ b/src/frontend/src/content/docs/deployment/javascript-apps.mdx
@@ -6,6 +6,7 @@ description: Learn the main production deployment models for JavaScript app reso
 
 import { Aside, TabItem, Tabs } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 JavaScript app resources can represent static browser frontends, Node.js servers, SSR frameworks, and specialized resources such as Next.js apps. The deployment decision is less about which AppHost API you started with and more about **which resource owns the public HTTP surface in production**.
 
@@ -13,12 +14,12 @@ Use this table as the starting point:
 
 | What are you deploying?                               | Production entrypoint       | Aspire pattern              |
 | ----------------------------------------------------- | --------------------------- | --------------------------- |
-| Static frontend served by a backend                   | Backend, API, or web server | `PublishWithContainerFiles` |
-| Static frontend served by a gateway or BFF            | Reverse proxy               | `PublishWithStaticFiles`    |
-| Static frontend served by its own JavaScript resource | JavaScript app resource     | `PublishAsStaticWebsite`    |
-| SSR or Node.js app with a built server artifact       | JavaScript app resource     | `PublishAsNodeServer`       |
-| SSR or Node.js app started by a package script        | JavaScript app resource     | `PublishAsPackageScript`    |
-| Next.js standalone app                                | Next.js app resource        | `AddNextJsApp`              |
+| Static frontend served by a backend                   | Backend, API, or web server | <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" /> |
+| Static frontend served by a gateway or BFF            | Reverse proxy               | <ApiReference name="Aspire.Hosting.YarpResourceExtensions.PublishWithStaticFiles" />    |
+| Static frontend served by its own JavaScript resource | JavaScript app resource     | <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsStaticWebsite" />    |
+| SSR or Node.js app with a built server artifact       | JavaScript app resource     | <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsNodeServer" />       |
+| SSR or Node.js app started by a package script        | JavaScript app resource     | <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsPackageScript" />    |
+| Next.js standalone app                                | Next.js app resource        | <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" />              |
 | Static frontend hosted separately from the backend    | Static host + separate API  | Custom topology             |
 
 This article is deployment-target agnostic. It explains the JavaScript hosting models you can use with Aspire, not the full steps for a specific deployment target.
@@ -109,7 +110,7 @@ await builder.build().run();
 
 ### How it works
 
-1. `AddViteApp` runs the Vite dev server during `aspire run`.
+1. <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> runs the Vite dev server during `aspire run`.
 2. During publish, Aspire builds the frontend and extracts its production output.
 3. `PublishWithContainerFiles` copies those files into the backend or web server container.
 4. The backend or web server becomes the deployed HTTP endpoint and serves the frontend files.
@@ -342,7 +343,7 @@ You can call `PublishAsStaticWebsite` without an API target when the static webs
 
 `PublishAsStaticWebsite` only takes effect at publish time. In run mode, each framework still uses its own dev server, and the browser hits the dev server's origin instead of YARP. To keep the same `/api/*` shape working in development, the dev server itself needs a small proxy config that forwards `/api/*` to the backend resource.
 
-When the frontend references a backend resource, either explicitly through `WithReference` or implicitly when you pass `apiTarget` to `PublishAsStaticWebsite`, Aspire exposes the backend URL through service-discovery environment variables. The variable name follows the pattern `<RESOURCENAME>_<SCHEME>` in upper case. For a backend resource named `api` with an `http` endpoint, that's `API_HTTP`. If you rename the resource, for example `weather`, or use `https`, the variable becomes `WEATHER_HTTP` or `API_HTTPS`. `apiTarget` adds the reference for you, so no extra `WithReference` call is required when you use `PublishAsStaticWebsite(apiPath, apiTarget)`.
+When the frontend references a backend resource, either explicitly through <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> or implicitly when you pass `apiTarget` to `PublishAsStaticWebsite`, Aspire exposes the backend URL through service-discovery environment variables. The variable name follows the pattern `<RESOURCENAME>_<SCHEME>` in upper case. For a backend resource named `api` with an `http` endpoint, that's `API_HTTP`. If you rename the resource, for example `weather`, or use `https`, the variable becomes `WEATHER_HTTP` or `API_HTTPS`. `apiTarget` adds the reference for you, so no extra `WithReference` call is required when you use `PublishAsStaticWebsite(apiPath, apiTarget)`.
 
 Each framework reads that variable from its own dev-server config:
 
@@ -518,7 +519,7 @@ ENTRYPOINT ["sh", "-c", "exec pnpm run start"]
 
 ## Next.js standalone apps
 
-Use `AddNextJsApp` for Next.js apps that use [standalone output](https://nextjs.org/docs/pages/api-reference/next-config-js/output). It is more specific than `AddJavaScriptApp` because it configures the Next.js development server port argument and publish-time standalone container shape, and it validates that the Next.js configuration enables `output: "standalone"`.
+Use `AddNextJsApp` for Next.js apps that use [standalone output](https://nextjs.org/docs/pages/api-reference/next-config-js/output). It is more specific than <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" /> because it configures the Next.js development server port argument and publish-time standalone container shape, and it validates that the Next.js configuration enables `output: "standalone"`.
 
 Choose this method instead of `AddJavaScriptApp(...).PublishAsPackageScript(...)` for Next.js standalone deployments. Use the more general package-script publish method for frameworks where the production server should be started through the package manager and the framework does not have a dedicated Aspire resource.
 
@@ -713,13 +714,13 @@ await builder.build().run();
 
 - **Pit 1 - Runtime environment on the Vite resource**
 
-  Example: `WithEnvironment(...)` / `withEnvironment(...)` on `AddViteApp` / `addViteApp` to set `VITE_API_BASE_URL`.
+  Example: <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> on `AddViteApp` / `addViteApp` to set `VITE_API_BASE_URL`.
 
   Associated failure: Vite usually reads `VITE_*` values at build time, so the deployed browser app does not learn its backend URL from the Vite resource at runtime.
 
 - **Pit 2 - Switching the same value to a build arg**
 
-  Example: `WithBuildArg(...)` / `withBuildArg(...)` to set the backend URL during the frontend image build.
+  Example: <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildArg" /> to set the backend URL during the frontend image build.
 
   Associated failure: the backend URL is usually not known when the frontend image is being built.
 
@@ -1207,7 +1208,7 @@ If a build-only JavaScript resource is not consumed by another resource, publish
 Build-only container resource(s) 'frontend' are not consumed by another resource and won't participate in publish or deploy. Reference them from another resource, for example using 'PublishWithContainerFiles' or 'PublishWithStaticFiles', or suppress this validation for the app by calling 'builder.Pipeline.DisableBuildOnlyContainerValidation()'.
 ```
 
-Prefer fixing the app model by choosing one of the deployment shapes in this article. The app-wide `DisableBuildOnlyContainerValidation()` escape hatch exists for exceptional cases, but it should not be the normal way to deploy JavaScript frontends.
+Prefer fixing the app model by choosing one of the deployment shapes in this article. The app-wide <ApiReference name="Aspire.Hosting.Pipelines.DistributedApplicationPipelineExtensions.DisableBuildOnlyContainerValidation" /> escape hatch exists for exceptional cases, but it should not be the normal way to deploy JavaScript frontends.
 
 To disable the validation for the whole app, call `DisableBuildOnlyContainerValidation` on the pipeline:
 
@@ -1261,7 +1262,7 @@ JavaScript app resource 'js' is configured to run script 'migrate', but publish
 To resolve the conflict, choose one of the following options:
 
 - **Remove or rename the Dockerfile** so Aspire generates a new one that runs your requested script as the container entrypoint.
-- **Override the container entrypoint explicitly** by calling `PublishAsDockerFile(...)` and configuring the entrypoint directly on the container resource. This keeps the existing Dockerfile and gives you full control over what runs:
+- **Override the container entrypoint explicitly** by calling <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.PublishAsDockerFile" /> and configuring the entrypoint directly on the container resource. This keeps the existing Dockerfile and gives you full control over what runs:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/deployment/kubernetes-gateway-aks.mdx b/src/frontend/src/content/docs/deployment/kubernetes-gateway-aks.mdx
index 42630e28be..3bae82442e 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes-gateway-aks.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes-gateway-aks.mdx
@@ -11,8 +11,9 @@ sidebar:
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
-This walkthrough shows how to use `AddGateway` to expose Aspire services on Azure Kubernetes Service (AKS) with **Application Gateway for Containers (AGC)** and automatic TLS certificate provisioning via **cert-manager HTTP-01** challenges.
+This walkthrough shows how to use <ApiReference name="Aspire.Hosting.KubernetesGatewayExtensions.AddGateway" /> to expose Aspire services on Azure Kubernetes Service (AKS) with **Application Gateway for Containers (AGC)** and automatic TLS certificate provisioning via **cert-manager HTTP-01** challenges.
 
 Gateway API with HTTP-01 is the **recommended approach** for TLS on AKS because:
 
@@ -21,7 +22,7 @@ Gateway API with HTTP-01 is the **recommended approach** for TLS on AKS because:
 - **Works with any domain** — including the auto-assigned AGC FQDN (`*.alb.azure.com`), your own custom domain, or even without a pre-existing DNS zone.
 
 <Aside type="tip">
-**Using `AddAzureKubernetesEnvironment`?** The integrated walkthrough at [Deploy to AKS — Expose your app to the internet](/deployment/kubernetes/aks/#expose-your-app-to-the-internet) covers Gateway API + AGC + cert-manager (HTTP-01) end to end with the Aspire-provisioned cluster. Use this page only if you have a pre-existing AKS cluster that wasn't provisioned by Aspire.
+**Using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" />?** The integrated walkthrough at [Deploy to AKS — Expose your app to the internet](/deployment/kubernetes/aks/#expose-your-app-to-the-internet) covers Gateway API + AGC + cert-manager (HTTP-01) end to end with the Aspire-provisioned cluster. Use this page only if you have a pre-existing AKS cluster that wasn't provisioned by Aspire.
 </Aside>
 
 <Aside type="note">
@@ -495,7 +496,7 @@ builder.build().run();
 </TabItem>
 </Tabs>
 
-The `WithTls()` call with no arguments auto-generates the TLS secret name (`ingress-tls`) and adds a cert-manager annotation to the Gateway referencing the `ClusterIssuer` specified via the `clusterIssuer` parameter.
+The <ApiReference name="Aspire.Hosting.KubernetesGatewayExtensions.WithTls" /> call with no arguments auto-generates the TLS secret name (`ingress-tls`) and adds a cert-manager annotation to the Gateway referencing the `ClusterIssuer` specified via the `clusterIssuer` parameter.
 
 ## Deploy
 
@@ -631,7 +632,7 @@ After deployment and DNS propagation, verify that your Gateway is configured cor
 
 ## How it works
 
-When you deploy a Gateway with `WithHostname()` and `WithTls()`, the following sequence occurs:
+When you deploy a Gateway with <ApiReference name="Aspire.Hosting.KubernetesGatewayExtensions.WithHostname" /> and `WithTls()`, the following sequence occurs:
 
 <Steps>
 
diff --git a/src/frontend/src/content/docs/deployment/kubernetes-ingress-aks.mdx b/src/frontend/src/content/docs/deployment/kubernetes-ingress-aks.mdx
index aaa507eac9..d94af4ea29 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes-ingress-aks.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes-ingress-aks.mdx
@@ -11,13 +11,14 @@ sidebar:
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
-This walkthrough shows how to use `AddIngress` to expose Aspire services on
+This walkthrough shows how to use <ApiReference name="Aspire.Hosting.KubernetesIngressExtensions.AddIngress" /> to expose Aspire services on
 Azure Kubernetes Service (AKS) with **Application Gateway for Containers (AGC)**
 and automatic TLS certificate provisioning via **cert-manager** DNS-01 challenges.
 
 <Aside type="tip">
-**Using `AddAzureKubernetesEnvironment`?** The integrated walkthrough at [Deploy to AKS — Expose your app to the internet](/deployment/kubernetes/aks/#expose-your-app-to-the-internet) covers AGC + cert-manager end to end without any of the manual `az aks`, `az network alb`, or `helm install` ceremony below. Use this page only if you have a pre-existing AKS cluster that wasn't provisioned by Aspire, or if you need DNS-01 certificate issuance against an Azure DNS zone.
+**Using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" />?** The integrated walkthrough at [Deploy to AKS — Expose your app to the internet](/deployment/kubernetes/aks/#expose-your-app-to-the-internet) covers AGC + cert-manager end to end without any of the manual `az aks`, `az network alb`, or `helm install` ceremony below. Use this page only if you have a pre-existing AKS cluster that wasn't provisioned by Aspire, or if you need DNS-01 certificate issuance against an Azure DNS zone.
 </Aside>
 
 <Aside type="note">
@@ -726,7 +727,7 @@ After the deployment completes, verify the ingress is working:
 ## How TLS works with Ingress on AGC
 
 When you deploy an ingress with the `cert-manager.io/cluster-issuer` annotation
-and `WithTls`, the following sequence occurs:
+and <ApiReference name="Aspire.Hosting.KubernetesIngressExtensions.WithTls" />, the following sequence occurs:
 
 <Steps>
 
@@ -807,7 +808,7 @@ const ingress = k8s.addIngress("ingress")
 <summary>Deploy without a custom hostname</summary>
 
 <Aside type="caution">
-When you omit `WithHostname`, AGC automatically assigns a generated FQDN to the
+When you omit <ApiReference name="Aspire.Hosting.KubernetesIngressExtensions.WithHostname" />, AGC automatically assigns a generated FQDN to the
 ingress. You won't be able to use cert-manager for TLS because you don't control
 the domain. The AGC-assigned FQDN uses a wildcard certificate managed by Azure.
 </Aside>
diff --git a/src/frontend/src/content/docs/deployment/kubernetes-ingress.mdx b/src/frontend/src/content/docs/deployment/kubernetes-ingress.mdx
index 624015c679..647a860e0b 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes-ingress.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes-ingress.mdx
@@ -7,6 +7,7 @@ sidebar:
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 When you deploy an Aspire application to Kubernetes, your services are accessible only within the cluster by default. To expose services to external traffic — such as a web frontend that users access from the internet — you need to configure an **Ingress** or **Gateway** resource that routes traffic from outside the cluster to your services.
 
@@ -29,7 +30,7 @@ Aspire provides first-class APIs for defining Ingress and Gateway API resources
   new traffic-routing capabilities are landing in Gateway API instead. For new
   Aspire deployments, prefer
   [`AddGateway(...)`](/deployment/kubernetes-gateway-aks/) over
-  `AddIngress(...)` unless your cluster or controller doesn't yet support
+  <ApiReference name="Aspire.Hosting.KubernetesIngressExtensions.AddIngress" /> unless your cluster or controller doesn't yet support
   Gateway API. See [Gateway API
   concepts](https://gateway-api.sigs.k8s.io/concepts/api-overview/) for the
   upstream design rationale.
@@ -47,7 +48,7 @@ Kubernetes offers two approaches for routing external traffic to your services:
 | **Routing features** | Host and path matching | Host, path, header, query, method matching |
 | **Extensibility** | Controller-specific annotations | Standardized filters and policies |
 | **Traffic splitting** | Not standardized | First-class weighted backends |
-| **Aspire API** | `AddIngress()` | `AddGateway()` |
+| **Aspire API** | `AddIngress()` | <ApiReference name="Aspire.Hosting.KubernetesGatewayExtensions.AddGateway" /> |
 
 **Recommendation:** Use **Gateway API** for new deployments. It's the future direction of Kubernetes traffic management and offers richer routing capabilities with better portability across providers. Use **Ingress** when your cluster or ingress controller doesn't support the Gateway API yet.
 
@@ -146,7 +147,7 @@ If you call `WithHostname` more than once, each hostless path or route applies t
 
 A Gateway API `HTTPRoute` supports at most 16 hostnames. If a Gateway has more than 16 hostnames and any hostless routes, publishing fails; define explicit host-scoped routes instead.
 
-An Ingress default backend (`WithDefaultBackend`) doesn't inherit the hostname and remains a catch-all for any traffic that doesn't match a more specific rule. When TLS is also configured, Aspire adds a rule that forwards each TLS hostname without its own rule to the default backend, because some ingress controllers require every TLS host to have a matching rule.
+An Ingress default backend (<ApiReference name="Aspire.Hosting.KubernetesIngressExtensions.WithDefaultBackend" />) doesn't inherit the hostname and remains a catch-all for any traffic that doesn't match a more specific rule. When TLS is also configured, Aspire adds a rule that forwards each TLS hostname without its own rule to the default backend, because some ingress controllers require every TLS host to have a matching rule.
 
 <Aside type="note">
   This inheritance behavior applies from Aspire 13.6 onward. In earlier
diff --git a/src/frontend/src/content/docs/deployment/kubernetes/aks.mdx b/src/frontend/src/content/docs/deployment/kubernetes/aks.mdx
index 6894a47ea7..47b09314ed 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/aks.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/aks.mdx
@@ -7,6 +7,7 @@ description: Deploy your Aspire application to Azure Kubernetes Service with ful
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Deploy your Aspire application to Azure Kubernetes Service (AKS). Aspire provisions the AKS cluster, Azure Container Registry (ACR), and any Azure resources your app depends on — then deploys your application in a single command.
 
@@ -88,7 +89,7 @@ Aspire builds your container images, pushes them to ACR, generates Helm charts,
 
 ### System node pool
 
-Customize the system node pool VM size and scaling using `WithSystemNodePool`:
+Customize the system node pool VM size and scaling using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithSystemNodePool" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -107,7 +108,7 @@ await aks.withSystemNodePool('Standard_D4s_v5', 1, 5);
 
 ### Additional node pools
 
-Add additional node pools for workload isolation or specialized hardware, then use `WithNodePool` to schedule workloads on them:
+Add additional node pools for workload isolation or specialized hardware, then use <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.WithNodePool" /> to schedule workloads on them:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -166,14 +167,14 @@ This walkthrough uses the integrated AGC + cert-manager APIs that ship with [
 
 ### How AGC ingress fits together
 
-When you opt in via `AddLoadBalancer`, Aspire flips the AKS cluster's Bicep to enable the AKS-managed Gateway API and Application Load Balancer ingress profiles. After deploy, the cluster runs the Microsoft-managed AGC controller, which watches for Aspire's generated `Gateway` and `HTTPRoute` resources and programs an Azure-hosted HTTPS frontend automatically.
+When you opt in via <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddLoadBalancer" />, Aspire flips the AKS cluster's Bicep to enable the AKS-managed Gateway API and Application Load Balancer ingress profiles. After deploy, the cluster runs the Microsoft-managed AGC controller, which watches for Aspire's generated `Gateway` and `HTTPRoute` resources and programs an Azure-hosted HTTPS frontend automatically.
 
 The pieces fit together like this:
 
 | Aspire AppHost call | What it produces in Azure / Kubernetes |
 |---|---|
-| `AddAzureKubernetesEnvironment` | AKS cluster (with Gateway API + ALB ingress profile when an LB is added) and ACR |
-| `AddAzureVirtualNetwork` + `AddSubnet` | A VNet and subnets — one for AKS nodes, one (or more) delegated to AGC |
+| <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" /> | AKS cluster (with Gateway API + ALB ingress profile when an LB is added) and ACR |
+| <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddAzureVirtualNetwork" /> + <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddSubnet" /> | A VNet and subnets — one for AKS nodes, one (or more) delegated to AGC |
 | `AddLoadBalancer(name, subnet)` | An AGC `ApplicationLoadBalancer` CR plus role assignments on the subnet |
 | `AddGateway(name).WithLoadBalancer(lb)` | A Gateway API `Gateway` resource attached to the AGC frontend |
 | `WithRoute(path, endpoint)` | An `HTTPRoute` that points the path at your service |
@@ -285,7 +286,7 @@ Each AGC `ApplicationLoadBalancer` caps at five frontends (Gateways or Ingresses
 
 ### Add a Gateway with a route to your service
 
-`AddGateway` declares a Kubernetes Gateway API `Gateway`. `WithLoadBalancer` attaches it to the AGC ALB you just created and defaults the `gatewayClassName` to `azure-alb-external`. `WithRoute` adds an `HTTPRoute` that forwards a path to the named endpoint on one of your services.
+<ApiReference name="Aspire.Hosting.AzureKubernetesIngressExtensions.AddGateway" /> declares a Kubernetes Gateway API `Gateway`. `WithLoadBalancer` attaches it to the AGC ALB you just created and defaults the `gatewayClassName` to `azure-alb-external`. `WithRoute` adds an `HTTPRoute` that forwards a path to the named endpoint on one of your services.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -329,7 +330,7 @@ This first deploy serves plain HTTP only. Continue to the next step before expos
 
 ### Add automatic HTTPS with cert-manager
 
-`AddCertManager` installs the upstream cert-manager Helm chart with the CRDs and Gateway API watcher enabled and the `--force-conflicts` flag set so AKS's Azure Policy add-on doesn't break subsequent upgrades. `AddIssuer` adds a typed `ClusterIssuer` parented to that installation, and `WithTls(issuer)` on a gateway adds an HTTPS listener that cert-manager will populate with a real certificate.
+<ApiReference name="Aspire.Hosting.AzureCertManagerExtensions.AddCertManager" /> installs the upstream cert-manager Helm chart with the CRDs and Gateway API watcher enabled and the `--force-conflicts` flag set so AKS's Azure Policy add-on doesn't break subsequent upgrades. <ApiReference name="Aspire.Hosting.CertManagerExtensions.AddIssuer" /> adds a typed `ClusterIssuer` parented to that installation, and `WithTls(issuer)` on a gateway adds an HTTPS listener that cert-manager will populate with a real certificate.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -394,12 +395,12 @@ await storefront.withTls(letsencrypt, {
 </Tabs>
 
 <Aside type="tip">
-Let's Encrypt's production endpoint enforces strict rate limits. While iterating on your AppHost, swap `WithLetsEncryptProduction` for `WithLetsEncryptStaging` so failed attempts don't cost you your weekly quota. Browsers will warn on staging certificates — flip back to production once everything works end-to-end.
+Let's Encrypt's production endpoint enforces strict rate limits. While iterating on your AppHost, swap <ApiReference name="Aspire.Hosting.CertManagerExtensions.WithLetsEncryptProduction" /> for <ApiReference name="Aspire.Hosting.CertManagerExtensions.WithLetsEncryptStaging" /> so failed attempts don't cost you your weekly quota. Browsers will warn on staging certificates — flip back to production once everything works end-to-end.
 </Aside>
 
 #### How the certificate gets issued
 
-cert-manager validates domain ownership using the **HTTP-01** challenge configured by `WithHttp01Solver` — it asks the gateway to serve a token at `/.well-known/acme-challenge/<token>` and verifies the response. There is no DNS API access required, so this works for the auto-assigned `*.alb.azure.com` FQDN out of the box.
+cert-manager validates domain ownership using the **HTTP-01** challenge configured by <ApiReference name="Aspire.Hosting.CertManagerExtensions.WithHttp01Solver" /> — it asks the gateway to serve a token at `/.well-known/acme-challenge/<token>` and verifies the response. There is no DNS API access required, so this works for the auto-assigned `*.alb.azure.com` FQDN out of the box.
 
 To break the chicken-and-egg problem where AGC won't program a Gateway whose HTTPS listener references a missing secret, Aspire pre-creates a self-signed bootstrap secret on the first deploy. Once AGC publishes the gateway's FQDN, Aspire patches the listener with the real hostname and cert-manager swaps the bootstrap certificate for a Let's Encrypt one. You may briefly see a self-signed certificate during the first deploy — this is expected.
 
@@ -434,7 +435,7 @@ The `*.alb.azure.com` FQDN is fine for testing but real applications need a host
 
 ### Tell the gateway about your hostname
 
-`WithHostname` adds the hostname to the gateway's `HTTPRoute`s and to the HTTPS listener so cert-manager issues the certificate for the right name. Use the parameter overload when the hostname differs across deployment environments.
+<ApiReference name="Aspire.Hosting.KubernetesGatewayExtensions.WithHostname" /> adds the hostname to the gateway's `HTTPRoute`s and to the HTTPS listener so cert-manager issues the certificate for the right name. Use the parameter overload when the hostname differs across deployment environments.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -551,7 +552,7 @@ After authentication, `aspire deploy` needs a target subscription and location.
 
 ### Customizing Azure resources
 
-Use `PublishAsKubernetesService` to customize the Kubernetes resources generated for individual services:
+Use <ApiReference name="Aspire.Hosting.KubernetesServiceExtensions.PublishAsKubernetesService" /> to customize the Kubernetes resources generated for individual services:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -584,7 +585,7 @@ await api.publishAsKubernetesService(async (resource) => {
 
 ## Install external Helm charts
 
-Use `AddHelmChart` on the AKS environment to install pre-existing Helm charts — such as cert-manager or NGINX ingress — as post-deploy pipeline steps alongside your application.
+Use <ApiReference name="Aspire.Hosting.AzureKubernetesIngressExtensions.AddHelmChart" /> on the AKS environment to install pre-existing Helm charts — such as cert-manager or NGINX ingress — as post-deploy pipeline steps alongside your application.
 
 <LearnMore>
 See [Install external Helm charts](/deployment/kubernetes/helm-charts/) for a full walkthrough of adding external charts, configuring Helm values, overriding namespaces and release names, and choosing destroy-time uninstall behavior.
diff --git a/src/frontend/src/content/docs/deployment/kubernetes/clusters.mdx b/src/frontend/src/content/docs/deployment/kubernetes/clusters.mdx
index 950050ef3a..3b56d60403 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/clusters.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/clusters.mdx
@@ -7,6 +7,7 @@ description: Publish and deploy your Aspire application to an existing Kubernete
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import FileTree from 'starlight-plugin-icons/components/FileTree.astro';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Deploy your Aspire application to any existing Kubernetes cluster. Aspire generates a complete Helm chart from your application model, and you can either apply it yourself or let `aspire deploy` install it directly using your current `kubectl` context.
 
@@ -211,7 +212,7 @@ If you prefer to publish first and deploy separately — for example, in a CI/CD
 
 ### Helm settings
 
-Use `WithHelm` to configure Helm chart settings such as namespace, release name, and chart version:
+Use <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.WithHelm" /> to configure Helm chart settings such as namespace, release name, and chart version:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -241,7 +242,7 @@ Helm is the default deployment engine. Call `WithHelm` only when you need to cus
 
 ### Node pools
 
-Use `AddNodePool` to reference an existing node pool in your cluster, then `WithNodePool` to schedule specific workloads on it:
+Use <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.AddNodePool" /> to reference an existing node pool in your cluster, then <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.WithNodePool" /> to schedule specific workloads on it:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -270,7 +271,7 @@ For vanilla Kubernetes, `AddNodePool` creates a named reference to a node pool t
 
 ### Per-resource customization
 
-Use `PublishAsKubernetesService` to modify the generated Kubernetes resources for individual services:
+Use <ApiReference name="Aspire.Hosting.KubernetesServiceExtensions.PublishAsKubernetesService" /> to modify the generated Kubernetes resources for individual services:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -395,7 +396,7 @@ Kubernetes Secrets store values as base64-encoded strings. Verify that your Secr
 
 ## Install external Helm charts
 
-Use `AddHelmChart` on the Kubernetes environment to install pre-existing Helm charts — such as cert-manager, NGINX ingress, or monitoring tools — as post-deploy pipeline steps alongside your application's own chart.
+Use <ApiReference name="Aspire.Hosting.KubernetesHelmChartExtensions.AddHelmChart" /> on the Kubernetes environment to install pre-existing Helm charts — such as cert-manager, NGINX ingress, or monitoring tools — as post-deploy pipeline steps alongside your application's own chart.
 
 <LearnMore>
 See [Install external Helm charts](/deployment/kubernetes/helm-charts/) for a full walkthrough of adding external charts, configuring Helm values, overriding namespaces and release names, and choosing destroy-time uninstall behavior.
diff --git a/src/frontend/src/content/docs/deployment/kubernetes/helm-charts.mdx b/src/frontend/src/content/docs/deployment/kubernetes/helm-charts.mdx
index 6a4b1abd73..756766fc5b 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/helm-charts.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/helm-charts.mdx
@@ -5,6 +5,7 @@ description: Learn how to install external Helm charts alongside your Aspire app
 
 import { Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Install pre-existing Helm charts — such as cert-manager, NGINX ingress controller, or monitoring tools — as part of your Aspire Kubernetes deployment. Aspire runs `helm upgrade --install` for each configured external chart after deploying your application's own generated Helm chart.
 
@@ -16,7 +17,7 @@ Install pre-existing Helm charts — such as cert-manager, NGINX ingress control
 
 ## Deployment order
 
-When you use `aspire deploy`, Aspire deploys your application as a Helm chart and then runs any additional install steps you have defined. `AddHelmChart` registers one of these post-deploy pipeline steps. The install order is:
+When you use `aspire deploy`, Aspire deploys your application as a Helm chart and then runs any additional install steps you have defined. <ApiReference name="Aspire.Hosting.KubernetesHelmChartExtensions.AddHelmChart" /> registers one of these post-deploy pipeline steps. The install order is:
 
 <Steps>
 
diff --git a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
index 32fbba5b34..cb7b93ab2d 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
@@ -6,8 +6,9 @@ description: Model durable storage as first-class persistent volume resources in
 
 import { Tabs, TabItem, Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
-Stateful workloads — databases, message brokers, or any service that writes durable data — need storage that survives pod restarts and rescheduling. Call `AddPersistentVolume` on a Kubernetes environment to describe a durable disk once in your AppHost, configure its storage class, capacity, access modes, and annotations with fluent methods, then bind it to one or more workloads:
+Stateful workloads — databases, message brokers, or any service that writes durable data — need storage that survives pod restarts and rescheduling. Call <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.AddPersistentVolume" /> on a Kubernetes environment to describe a durable disk once in your AppHost, configure its storage class, capacity, access modes, and annotations with fluent methods, then bind it to one or more workloads:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -100,7 +101,7 @@ The available configuration methods are:
 |---|---|---|
 | `WithStorageClass(string)` | `withStorageClass` / `withStorageClassParam` | Sets `spec.storageClassName` on the PVC. In C#, the single method accepts a literal string or an Aspire parameter; in TypeScript, use `withStorageClass` for a literal and `withStorageClassParam` for a parameter. |
 | `WithCapacity(string)` | `withCapacity` / `withCapacityParam` | Sets the requested storage on `spec.resources.requests.storage` (for example, `"20Gi"`). In TypeScript, use `withCapacity` for a literal and `withCapacityParam` for a parameter. |
-| `WithAccessMode(PersistentVolumeAccessMode)` | `withAccessMode` | Adds an entry to `spec.accessModes`. Call multiple times to declare more than one mode. |
+| `WithAccessMode(PersistentVolumeAccessMode)` | <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithAccessMode" /> | Adds an entry to `spec.accessModes`. Call multiple times to declare more than one mode. |
 | `WithVolumeAnnotation(string, string)` | `withVolumeAnnotation` / `withVolumeAnnotationParam` | Adds a key-value pair to the PVC's `metadata.annotations`. Useful for CSI driver hints, dynamic provisioner parameters, or backup tooling tags. In TypeScript, use `withVolumeAnnotation` for a literal value and `withVolumeAnnotationParam` for a parameter. |
 
 The `PersistentVolumeAccessMode` values map directly to the Kubernetes access modes:
@@ -228,7 +229,7 @@ A Kubernetes access mode such as `ReadWriteOnce` controls how a volume can be at
   The automatic security context described in this section requires Aspire 13.6 or later.
 </Aside>
 
-To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, `withKubernetesPersistentVolume` and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
+To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithPersistentVolume" /> and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
 
 ```yaml
 securityContext:
@@ -242,7 +243,7 @@ This default only applies to workloads bound through `WithPersistentVolume(...)`
 
 ### Overriding or removing the default
 
-The default security context is applied before any `PublishAsKubernetesService` callback runs, so a workload or cluster that needs a different group can replace it:
+The default security context is applied before any <ApiReference name="Aspire.Hosting.KubernetesServiceExtensions.PublishAsKubernetesService" /> callback runs, so a workload or cluster that needs a different group can replace it:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/deployment/pipelines.mdx b/src/frontend/src/content/docs/deployment/pipelines.mdx
index 06608baa56..1ef11664f4 100644
--- a/src/frontend/src/content/docs/deployment/pipelines.mdx
+++ b/src/frontend/src/content/docs/deployment/pipelines.mdx
@@ -9,6 +9,7 @@ lastUpdated: true
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 When you compose your distributed app in Aspire's **AppHost**, you're not just defining services for local development and orchestration—you're also setting up the foundation for deployment. The same composition you use to run and debug locally is leveraged when you publish your app, ensuring consistency from development through to production.
 
@@ -149,8 +150,8 @@ Dependencies in Aspire pipelines are explicit and purpose-driven, unlike traditi
 
 Steps declare their relationships using:
 
-- `PipelineStep.DependsOn`: This step must run after another step completes successfully
-- `PipelineStep.RequiredBy`: Another step must run after this step (inverse dependency declaration)
+- <ApiReference name="Aspire.Hosting.Pipelines.PipelineStep.DependsOn" />: This step must run after another step completes successfully
+- <ApiReference name="Aspire.Hosting.Pipelines.PipelineStep.RequiredBy" />: Another step must run after this step (inverse dependency declaration)
 
 **Example dependency relationships:**
 
@@ -520,7 +521,7 @@ aspire do validate
 
 ### Resource-level steps
 
-Resources can contribute their own pipeline steps using `WithPipelineStepFactory`:
+Resources can contribute their own pipeline steps using <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" />:
 
 ```csharp title="Resource-level custom step"
 var api = builder.AddProject<Projects.Api>("api")
@@ -566,7 +567,7 @@ You can choose from two dependency types to fix the step order:
 
 ### Pipeline configuration
 
-Resources can also customize how they participate in the pipeline using `WithPipelineConfiguration`, which provides control over step ordering and resource-specific pipeline behavior.
+Resources can also customize how they participate in the pipeline using <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineConfiguration" />, which provides control over step ordering and resource-specific pipeline behavior.
 
 <Aside type="note">
 The `WithPipelineConfiguration` API is experimental and may change in future releases. Refer to the [aspire do command reference](/reference/cli/commands/aspire-do/) for the latest details on pipeline configuration.
diff --git a/src/frontend/src/content/docs/diagnostics/aspireacadomains001.mdx b/src/frontend/src/content/docs/diagnostics/aspireacadomains001.mdx
index 44d4ed3311..16d1959469 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireacadomains001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireacadomains001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREACADOMAINS001 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 9.0"
@@ -24,7 +25,7 @@ Aspire 9.0 introduces the ability to customize container app resources using any
 When you use one of these methods, the Azure Developer CLI (`azd`) can no longer preserve custom domains. Instead use the `Aspire.Hosting.ContainerAppExtensions.ConfigureCustomDomain` method to configure a custom domain within the Aspire AppHost.
 
 :::note
-`ConfigureCustomDomain` has graduated from experimental and no longer requires suppressing this diagnostic.
+<ApiReference name="Aspire.Hosting.ContainerAppExtensions.ConfigureCustomDomain" /> has graduated from experimental and no longer requires suppressing this diagnostic.
 :::
 
 ## Example
diff --git a/src/frontend/src/content/docs/diagnostics/aspireacanaming001.mdx b/src/frontend/src/content/docs/diagnostics/aspireacanaming001.mdx
index 8d8bb65d2a..bec10d8b5d 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireacanaming001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireacanaming001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREACANAMING001 an
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -15,7 +16,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 > WithCompactResourceNaming is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-This diagnostic warning is reported when using the experimental `WithCompactResourceNaming` extension method on an Azure Container App environment. This API opts the environment into shorter, compact names for the volume-backing Azure Storage resources that Aspire provisions, which avoids storage-account name-length collisions when the environment name is long. It doesn't rename the Container App environment, container registry, Log Analytics workspace, or managed identity.
+This diagnostic warning is reported when using the experimental <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithCompactResourceNaming" /> extension method on an Azure Container App environment. This API opts the environment into shorter, compact names for the volume-backing Azure Storage resources that Aspire provisions, which avoids storage-account name-length collisions when the environment name is long. It doesn't rename the Container App environment, container registry, Log Analytics workspace, or managed identity.
 
 ## Example
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireazure002.mdx b/src/frontend/src/content/docs/diagnostics/aspireazure002.mdx
index b2bf5ccea2..bdf0625352 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireazure002.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireazure002.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREAZURE002 and how
 ---
 
 import { Badge, Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 9.5"
@@ -14,7 +15,7 @@ import { Badge, Aside } from '@astrojs/starlight/components';
 />
 
 <Aside type="note">
-  As of Aspire 13.4, the `PublishAsAzureContainerAppJob` and `PublishAsScheduledAzureContainerAppJob` APIs are no longer experimental and do not trigger `ASPIREAZURE002`. This diagnostic only applies if you are using an earlier version of Aspire.
+  As of Aspire 13.4, the <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsAzureContainerAppJob" /> and <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsScheduledAzureContainerAppJob" /> APIs are no longer experimental and do not trigger `ASPIREAZURE002`. This diagnostic only applies if you are using an earlier version of Aspire.
 </Aside>
 
 > Azure Container App Jobs are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
diff --git a/src/frontend/src/content/docs/diagnostics/aspireazure003.mdx b/src/frontend/src/content/docs/diagnostics/aspireazure003.mdx
index e781e3b80c..79215edffd 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireazure003.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireazure003.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREAZURE003 and how
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -15,7 +16,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 > Azure Virtual Network types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-The Aspire Azure hosting integration now ships with support for Azure Virtual Networks. If you're using any of the `Aspire.Hosting.Azure.Network` APIs such as `AddAzureVirtualNetwork`, you might see a compiler error/warning indicating that the API is experimental. This behavior is expected, as the API is still in preview and the shape of this API is expected to change in the future.
+The Aspire Azure hosting integration now ships with support for Azure Virtual Networks. If you're using any of the `Aspire.Hosting.Azure.Network` APIs such as <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddAzureVirtualNetwork" />, you might see a compiler error/warning indicating that the API is experimental. This behavior is expected, as the API is still in preview and the shape of this API is expected to change in the future.
 
 ## Example
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireblazor001.mdx b/src/frontend/src/content/docs/diagnostics/aspireblazor001.mdx
index 143c40728e..826ed346af 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireblazor001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireblazor001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREBLAZOR001 and h
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.4"
@@ -17,7 +18,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic warning is reported when using experimental Blazor WebAssembly hosting APIs from the `Aspire.Hosting.Blazor` integration, including:
 
-- `BlazorGatewayExtensions` — `AddBlazorGateway`, `AddBlazorWasmApp`, `AddBlazorWasmProject<TProject>`, and `WithBlazorClientApp`
+- `BlazorGatewayExtensions` — <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorGateway" />, <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorWasmApp" />, <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorWasmProject" />, and `WithBlazorClientApp`
 - `BlazorHostedExtensions` — client wiring for a hosted Blazor Web App
 - `BlazorWasmAppResource` — the resource type that represents a Blazor WebAssembly app
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirebrowserlogs001.mdx b/src/frontend/src/content/docs/diagnostics/aspirebrowserlogs001.mdx
index befc10bbdf..f6c06777d3 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirebrowserlogs001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirebrowserlogs001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREBROWSERLOGS001 an
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.3"
@@ -17,7 +18,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic error is reported when using experimental browser logs APIs in Aspire from the `Aspire.Hosting.Browsers` package, including:
 
-- `WithBrowserLogs` extension method
+- <ApiReference name="Aspire.Hosting.BrowserLogsBuilderExtensions.WithBrowserLogs" /> extension method
 - `BrowserUserDataMode` enum
 - Other types and members that configure the tracked browser session
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecertificates001.mdx b/src/frontend/src/content/docs/diagnostics/aspirecertificates001.mdx
index 95afddca14..2c7fcc4ea1 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecertificates001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecertificates001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRECERTIFICATES001
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.0"
@@ -19,8 +20,8 @@ This diagnostic warning is reported when using experimental certificate configur
 
 - `IDeveloperCertificateService` interface
 - `HttpsCertificateAnnotation` class
-- Certificate-related extension methods like `WithHttpsCertificate`, `WithHttpsDeveloperCertificate`, `WithoutHttpsCertificate`
-- Certificate configuration builder extensions like `WithHttpsCertificateConfig` and `WithHttpsCertificateConfiguration`
+- Certificate-related extension methods like `WithHttpsCertificate`, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsDeveloperCertificate" />, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithoutHttpsCertificate" />
+- Certificate configuration builder extensions like <ApiReference name="Aspire.Hosting.ApplicationModel.ExecutionConfigurationBuilderExtensions.WithHttpsCertificateConfig" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsCertificateConfiguration" />
 
 These APIs enable configuring HTTPS/TLS server certificates for resources in your Aspire application, including support for custom certificates and developer certificates for local development scenarios.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecommand001.mdx b/src/frontend/src/content/docs/diagnostics/aspirecommand001.mdx
index 17aa163994..e2a2ebda85 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecommand001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecommand001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRECOMMAND001 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -19,7 +20,7 @@ This diagnostic warning is reported when using the experimental required-command
 
 The following APIs are protected by this diagnostic:
 
-- The `WithRequiredCommand` overload that accepts a validation callback (`Func<RequiredCommandValidationContext, Task<RequiredCommandValidationResult>>`)
+- The <ApiReference name="Aspire.Hosting.RequiredCommandResourceExtensions.WithRequiredCommand" /> overload that accepts a validation callback (`Func<RequiredCommandValidationContext, Task<RequiredCommandValidationResult>>`)
 - `RequiredCommandAnnotation`
 - `IRequiredCommandValidator`
 - `RequiredCommandValidationContext` and `RequiredCommandValidationResult`
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecompute002.mdx b/src/frontend/src/content/docs/diagnostics/aspirecompute002.mdx
index b3ea6cd9c3..2b34602f58 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecompute002.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecompute002.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRECOMPUTE002 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.0"
@@ -13,7 +14,7 @@ import { Badge } from '@astrojs/starlight/components';
   class:list={'mb-1'}
 />
 
-> The `GetHostAddressExpression` method is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
+> The <ApiReference name="Aspire.Hosting.Docker.DockerComposeEnvironmentResource.GetHostAddressExpression" /> method is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
 This diagnostic warning is reported when using the experimental `GetHostAddressExpression` method from the `IComputeEnvironmentResource` interface.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecompute003.mdx b/src/frontend/src/content/docs/diagnostics/aspirecompute003.mdx
index 710cd47424..1f7f461128 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecompute003.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecompute003.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRECOMPUTE003 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.1"
@@ -70,7 +71,7 @@ The `ContainerRegistryResource` represents a general-purpose container registry
 **Resource builder pattern**
 
 - Follows Aspire's resource builder pattern for consistency
-- Can be referenced by other resources using `WithContainerRegistry`
+- Can be referenced by other resources using <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" />
 - Supports chaining with other resource configuration methods
 
 ## To suppress this warning
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecosmosdb001.mdx b/src/frontend/src/content/docs/diagnostics/aspirecosmosdb001.mdx
index ff13b1a1f8..7d00c2759c 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecosmosdb001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecosmosdb001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIRECOSMOSDB001 and h
 ---
 
 import { Badge, Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 9.0"
@@ -14,7 +15,7 @@ import { Badge, Aside } from '@astrojs/starlight/components';
 />
 
 <Aside type="note">
-  As of Aspire 13.6, `RunAsPreviewEmulator` and `WithDataExplorer` are no longer experimental and do not trigger `ASPIRECOSMOSDB001`. `RunAsEmulator` now defaults to the Linux-based (vNext) emulator, and `RunAsPreviewEmulator` is retained only as an obsolete compatibility alias that forwards to `RunAsEmulator`. Use `RunAsClassicEmulator` if you need the classic (Windows-based) emulator instead. This diagnostic only applies if you're using an earlier version of Aspire.
+  As of Aspire 13.6, <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsPreviewEmulator" /> and <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithDataExplorer" /> are no longer experimental and do not trigger `ASPIRECOSMOSDB001`. <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsEmulator" /> now defaults to the Linux-based (vNext) emulator, and `RunAsPreviewEmulator` is retained only as an obsolete compatibility alias that forwards to `RunAsEmulator`. Use <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsClassicEmulator" /> if you need the classic (Windows-based) emulator instead. This diagnostic only applies if you're using an earlier version of Aspire.
 </Aside>
 
 > `RunAsPreviewEmulator` is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
diff --git a/src/frontend/src/content/docs/diagnostics/aspirecsharpapps001.mdx b/src/frontend/src/content/docs/diagnostics/aspirecsharpapps001.mdx
index 2289f091c8..798ba5eeb9 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirecsharpapps001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirecsharpapps001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIRECSHARPAPPS001 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.0"
@@ -13,7 +14,7 @@ import { Badge } from '@astrojs/starlight/components';
   class:list={'mb-1'}
 />
 
-> `AddCSharpApp` is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
+> <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
 Aspire provides a way to add C# app resources to the Aspire AppHost with the `AddCSharpApp` extension. This allows you to reference C# file-based app files (.cs), project files (.csproj), or project directories (directories containing a .csproj file) directly without needing a `ProjectReference` from the AppHost project to the C# application. Since the shape of this API is expected to change in the future, it's experimental.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspiredockerfilebuilder001.mdx b/src/frontend/src/content/docs/diagnostics/aspiredockerfilebuilder001.mdx
index 84f8a6ee1a..909a39f8f0 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiredockerfilebuilder001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiredockerfilebuilder001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREDOCKERFILEBUILD
 ---
 
 import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.0"
@@ -88,7 +89,7 @@ await builder.addDockerfileBuilder("my-service", "./service", configureDockerfil
 </TabItem>
 </Tabs>
 
-The callback can also be applied to an existing container resource with `WithDockerfileBuilder`:
+The callback can also be applied to an existing container resource with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/diagnostics/aspiredotnetproject001.mdx b/src/frontend/src/content/docs/diagnostics/aspiredotnetproject001.mdx
index 49889017cb..362eba7907 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiredotnetproject001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiredotnetproject001.mdx
@@ -5,6 +5,7 @@ description: Learn why Aspire 13.6 removed ASPIREDOTNETPROJECT001 from the prere
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.5"
@@ -16,9 +17,9 @@ import { Badge } from '@astrojs/starlight/components';
 :::note[Removed in Aspire 13.6]
 `Aspire.Hosting.Dotnet` and `Aspire.Hosting.Blazor` are already prerelease packages, so the separate `ASPIREDOTNETPROJECT001` experimental designation was unnecessary. Their APIs remain unstable and may change in future releases.
 
-Starting with Aspire 13.6, `AddDotnetProject`, `DotnetProjectResource`, and the related `WithBuildEnvironment` overloads no longer emit `ASPIREDOTNETPROJECT001`. You can remove suppressions for these APIs after upgrading.
+Starting with Aspire 13.6, <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.AddDotnetProject" />, `DotnetProjectResource`, and the related <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.WithBuildEnvironment" /> overloads no longer emit `ASPIREDOTNETPROJECT001`. You can remove suppressions for these APIs after upgrading.
 
-`AddDotnetProjectBlazorGateway` and the matching `WithBlazorClientApp` overload in `Aspire.Hosting.Blazor` also no longer emit this diagnostic. The separate [`ASPIREBLAZOR001`](/diagnostics/aspireblazor001/) diagnostic still applies to experimental Blazor hosting types.
+<ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddDotnetProjectBlazorGateway" /> and the matching `WithBlazorClientApp` overload in `Aspire.Hosting.Blazor` also no longer emit this diagnostic. The separate [`ASPIREBLAZOR001`](/diagnostics/aspireblazor001/) diagnostic still applies to experimental Blazor hosting types.
 :::
 
 > AddDotnetProject types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
diff --git a/src/frontend/src/content/docs/diagnostics/aspiredotnettool001.mdx b/src/frontend/src/content/docs/diagnostics/aspiredotnettool001.mdx
index fb93ed2fd0..f3791fa3d4 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiredotnettool001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiredotnettool001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREDOTNETTOOL001 a
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -19,7 +20,7 @@ This diagnostic warning is reported when using experimental .NET tool resource A
 
 - `DotnetToolResource`
 - `DotnetToolAnnotation`
-- `AddDotnetTool` extension methods
+- <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.AddDotnetTool" /> extension methods
 
 :::note[Which ID do I suppress?]
 Aspire emits this diagnostic as `ASPIREDOTNETTOOL`, without a numeric suffix. This documentation uses `ASPIREDOTNETTOOL001` as the canonical slug so it stays consistent with every other `ASPIRE*` diagnostic. Suppress the `ASPIREDOTNETTOOL` ID that appears in your build output; the examples below suppress both IDs so they keep working if the emitted ID ever changes.
diff --git a/src/frontend/src/content/docs/diagnostics/aspiredurabletask001.mdx b/src/frontend/src/content/docs/diagnostics/aspiredurabletask001.mdx
index 119a017d5e..60eed059a2 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiredurabletask001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiredurabletask001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREDURABLETASK001
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.3"
@@ -17,11 +18,11 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic warning is reported when using the experimental Durable Task scheduler and task hub APIs in the `Aspire.Hosting.Azure.Functions` package. The following APIs are affected:
 
-- `AddDurableTaskScheduler` extension method on `IDistributedApplicationBuilder`
-- `RunAsExisting` extension methods on `IResourceBuilder<DurableTaskSchedulerResource>`
-- `RunAsEmulator` extension method on `IResourceBuilder<DurableTaskSchedulerResource>`
-- `AddTaskHub` extension method on `IResourceBuilder<DurableTaskSchedulerResource>`
-- `WithTaskHubName` extension methods on `IResourceBuilder<DurableTaskHubResource>`
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.AddDurableTaskScheduler" /> extension method on `IDistributedApplicationBuilder`
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.RunAsExisting" /> extension methods on `IResourceBuilder<DurableTaskSchedulerResource>`
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.RunAsEmulator" /> extension method on `IResourceBuilder<DurableTaskSchedulerResource>`
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.AddTaskHub" /> extension method on `IResourceBuilder<DurableTaskSchedulerResource>`
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.WithTaskHubName" /> extension methods on `IResourceBuilder<DurableTaskHubResource>`
 - `DurableTaskSchedulerResource` class
 - `DurableTaskHubResource` class
 - `DurableTaskSchedulerEmulatorResource` class
diff --git a/src/frontend/src/content/docs/diagnostics/aspireextension001.mdx b/src/frontend/src/content/docs/diagnostics/aspireextension001.mdx
index b34745ecfa..5e6df4170c 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireextension001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireextension001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREEXTENSION001 an
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -25,7 +26,7 @@ This diagnostic warning is reported when using experimental extension debugging
 
 These APIs are primarily used by integration authors to enable F5 debugging for custom resource types in Visual Studio and other IDEs. 
 
-`WithLaunchToolArgs` declares the tool-invocation prefix for the tool that hosts a program (for example `run ./cmd/api` for `go` launcher/CLI, or `-m flask` for `python` CLI), separating it from program-specific arguments a caller adds with `WithArgs`. This allows extensions and IDEs to vary host tool arguments as necessary to reach the desired execution mode of the program (e.g. running under debugger vs not, enabling or disabling profiling etc.) without affecting startup arguments the program sees itself.
+`WithLaunchToolArgs` declares the tool-invocation prefix for the tool that hosts a program (for example `run ./cmd/api` for `go` launcher/CLI, or `-m flask` for `python` CLI), separating it from program-specific arguments a caller adds with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" />. This allows extensions and IDEs to vary host tool arguments as necessary to reach the desired execution mode of the program (e.g. running under debugger vs not, enabling or disabling profiling etc.) without affecting startup arguments the program sees itself.
 
 ## Example
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirehostingpython001.mdx b/src/frontend/src/content/docs/diagnostics/aspirehostingpython001.mdx
index 672db1622b..78fe2b156d 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirehostingpython001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirehostingpython001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREHOSTINGPYTHON001
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 9.0"
@@ -13,7 +14,7 @@ import { Badge } from '@astrojs/starlight/components';
   class:list={'mb-1'}
 />
 
-> `AddPythonApp` is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
+> <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" /> is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
 Aspire provides a way to add Python executables or applications to the Aspire AppHost with the `AddPythonApp` extension. Since the shape of this API is expected to change in the future, it's experimental.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirejavascript001.mdx b/src/frontend/src/content/docs/diagnostics/aspirejavascript001.mdx
index ac3673fd4b..b65cb952f6 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirejavascript001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirejavascript001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREJAVASCRIPT001 a
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.3"
@@ -17,11 +18,11 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic warning is reported when using experimental JavaScript hosting and publishing APIs in Aspire, including:
 
-- `PublishAsStaticWebsite<TResource>`
-- `PublishAsNodeServer<TResource>`
-- `PublishAsPackageScript<TResource>`
-- `AddNextJsApp`
-- `DisableBuildValidation`
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsStaticWebsite" />
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsNodeServer" />
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsPackageScript" />
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" />
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.DisableBuildValidation" />
 
 These APIs enable you to configure how JavaScript applications (Vite, Node.js, Next.js) are published and deployed via Aspire's pipeline infrastructure.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx b/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
index de390167af..77337607e5 100644
--- a/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspiremcp001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREMCP001 and how
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -15,7 +16,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 > <abbr title="Model Context Protocol" data-tooltip-placement="top">MCP</abbr> server types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-This diagnostic warning is reported when using the experimental `WithMcpServer` extension method and related Model Context Protocol (MCP) server APIs. These APIs enable Aspire tooling to discover and proxy MCP servers exposed by resources.
+This diagnostic warning is reported when using the experimental <ApiReference name="Aspire.Hosting.McpServerResourceBuilderExtensions.WithMcpServer" /> extension method and related Model Context Protocol (MCP) server APIs. These APIs enable Aspire tooling to discover and proxy MCP servers exposed by resources.
 
 The following APIs are protected by this diagnostic:
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirepersistence001.mdx b/src/frontend/src/content/docs/diagnostics/aspirepersistence001.mdx
index 5b5044e516..ebb0658a25 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirepersistence001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirepersistence001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREPERSISTENCE001 an
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.4"
@@ -19,10 +20,10 @@ This diagnostic error is reported when a C# AppHost uses the experimental shared
 
 The following APIs and types are protected by this diagnostic:
 
-- `WithSessionLifetime`
-- `WithPersistentLifetime`
-- `WithParentProcessLifetime`
-- `WithLifetimeOf`
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithSessionLifetime" />
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithPersistentLifetime" />
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithParentProcessLifetime" />
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithLifetimeOf" />
 - `PersistenceAnnotation`
 - `PersistenceMode`
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspirepipelines003.mdx b/src/frontend/src/content/docs/diagnostics/aspirepipelines003.mdx
index 32f07ac8bc..22243a18c3 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirepipelines003.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirepipelines003.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler error ASPIREPIPELINES003 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.0"
@@ -29,7 +30,7 @@ This diagnostic applies to the following container image build APIs:
 - `ContainerImageDestination` - Enumeration for selecting a registry or archive destination
 - `ContainerImageFormat` - Enumeration for specifying image format
 - `ContainerTargetPlatform` - Type for specifying target platform
-- `WithContainerBuildOptions` - Extension methods for configuring compute resource builds
+- <ApiReference name="Aspire.Hosting.ApplicationModel.ResourceExtensions.WithContainerBuildOptions" /> - Extension methods for configuring compute resource builds
 - Related annotations, options, and extension methods
 
 ## To correct this error
diff --git a/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx b/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
index 2d9486bd5d..3765e01fbc 100644
--- a/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspirepostgres001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREPOSTGRES001 —
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.2"
@@ -15,12 +16,12 @@ import { Badge } from '@astrojs/starlight/components';
 
 > The PostgreSQL <abbr title="Model Context Protocol" data-tooltip-placement="top">MCP</abbr> integration APIs are experimental and subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-The `WithPostgresMcp` extension method for adding Model Context Protocol (MCP) support to PostgreSQL resources is an experimental feature. This API may change or be removed in future versions.
+The <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithPostgresMcp" /> extension method for adding Model Context Protocol (MCP) support to PostgreSQL resources is an experimental feature. This API may change or be removed in future versions.
 
 The following APIs are protected by this diagnostic:
 
 - `WithPostgresMcp` on `IResourceBuilder<PostgresDatabaseResource>` — adds a Postgres MCP server container to a PostgreSQL database resource.
-- `WithPostgresMcp` on `IResourceBuilder<AzurePostgresFlexibleServerDatabaseResource>` — adds a Postgres MCP server container to an Azure PostgreSQL Flexible Server database resource running as a container.
+- <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.WithPostgresMcp" /> on `IResourceBuilder<AzurePostgresFlexibleServerDatabaseResource>` — adds a Postgres MCP server container to an Azure PostgreSQL Flexible Server database resource running as a container.
 
 ## Example
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireprobes001.mdx b/src/frontend/src/content/docs/diagnostics/aspireprobes001.mdx
index ed8c0fbf2a..3d441c77d4 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireprobes001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireprobes001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREPROBES001 and h
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 9.5"
@@ -20,7 +21,7 @@ This diagnostic warning is reported when using experimental health probe APIs in
 - `IResourceWithProbes` interface
 - `ProbeAnnotation` class and derived types
 - `ProbeType` enumeration
-- `WithHttpProbe` extension methods
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpProbe" /> extension methods
 - `EndpointProbeAnnotation` class
 
 These APIs enable configuring HTTP health probes for resources to monitor startup, readiness, and liveness states, similar to Kubernetes health check concepts.
diff --git a/src/frontend/src/content/docs/diagnostics/aspireprocesscommand001.mdx b/src/frontend/src/content/docs/diagnostics/aspireprocesscommand001.mdx
index ca1b2ac3cf..e9dc7d2878 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireprocesscommand001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireprocesscommand001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREPROCESSCOMMAND0
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.4"
@@ -15,7 +16,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 > Process command types and members are for evaluation purposes only and are subject to change or removal in future updates. Suppress this diagnostic to proceed.
 
-This diagnostic warning is reported when using the experimental `WithProcessCommand` extension method and related process command APIs. These APIs enable AppHost authors to expose custom resource commands backed by local processes (binaries, shell scripts, and other executables on the AppHost machine).
+This diagnostic warning is reported when using the experimental <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithProcessCommand" /> extension method and related process command APIs. These APIs enable AppHost authors to expose custom resource commands backed by local processes (binaries, shell scripts, and other executables on the AppHost machine).
 
 The following APIs are protected by this diagnostic:
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireprojects001.mdx b/src/frontend/src/content/docs/diagnostics/aspireprojects001.mdx
index c0552d53cd..342e5846d5 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireprojects001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireprojects001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREPROJECTS001 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.5"
@@ -21,7 +22,7 @@ This diagnostic warning is reported when using experimental project launch defau
 - `ProjectLaunchDefaultsAnnotation`
 - `ProjectLaunchArgsOverrideAnnotation`
 
-These APIs let a resource opt into the same launch-profile, Kestrel endpoint, and `ASPNETCORE_URLS` wiring that Aspire applies to `AddProject` resources. The resource must carry `IProjectMetadata`. They exist primarily so language integration packages (such as `Aspire.Hosting.Dotnet`) can reuse this behavior for resources that are launched through the .NET SDK.
+These APIs let a resource opt into the same launch-profile, Kestrel endpoint, and `ASPNETCORE_URLS` wiring that Aspire applies to <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> resources. The resource must carry `IProjectMetadata`. They exist primarily so language integration packages (such as `Aspire.Hosting.Dotnet`) can reuse this behavior for resources that are launched through the .NET SDK.
 
 ## Example
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx b/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
index cb0d5e7d5f..b1711491eb 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRERADIUS003 and h
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.5"
@@ -17,7 +18,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic warning is reported when using the experimental Radius cloud-provider APIs from the `Aspire.Hosting.Radius` integration, `WithAzureProvider` and `WithAwsProvider`.
 
-The `[Experimental]` gate is on `WithAzureProvider` and `WithAwsProvider` themselves. The credential callbacks you configure through them—such as `WithServicePrincipal`, `WithWorkloadIdentity`, `WithAccessKey`, and `WithIrsa`—are part of the same experimental surface; they don't each emit `ASPIRERADIUS003` on their own.
+The `[Experimental]` gate is on `WithAzureProvider` and `WithAwsProvider` themselves. The credential callbacks you configure through them—such as `WithServicePrincipal`, <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithWorkloadIdentity" />, `WithAccessKey`, and `WithIrsa`—are part of the same experimental surface; they don't each emit `ASPIRERADIUS003` on their own.
 
 These APIs configure the Azure and AWS cloud providers that the Radius publisher emits and that the deploy pipeline registers credentials for.
 
diff --git a/src/frontend/src/content/docs/diagnostics/aspireterminal001.mdx b/src/frontend/src/content/docs/diagnostics/aspireterminal001.mdx
index 3b6f51c779..acb59cbc0e 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireterminal001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireterminal001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIRETERMINAL001 and
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.5"
@@ -17,7 +18,7 @@ import { Badge } from '@astrojs/starlight/components';
 
 This diagnostic warning is reported when using experimental terminal configuration APIs in Aspire, including:
 
-- `WithTerminal` extension method
+- <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" /> extension method
 - `TerminalOptions`
 
 In Aspire 13.6 preview, the same diagnostic also covers AppHost-owned terminals and terminal interactions, including `TerminalService`, `AspireTerminal`, `TerminalLaunchOptions`, `TerminalPlacement`, `AspireTerminalKey`, `PromptTerminalAsync`, `TerminalInteractionOptions`, and `TerminalContext`.
diff --git a/src/frontend/src/content/docs/diagnostics/aspireusersecrets001.mdx b/src/frontend/src/content/docs/diagnostics/aspireusersecrets001.mdx
index e9cc39d8e1..ff3f072cf7 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireusersecrets001.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireusersecrets001.mdx
@@ -5,6 +5,7 @@ description: Learn what causes the Aspire compiler warning ASPIREUSERSECRETS001
 ---
 
 import { Badge } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge
   text="Version introduced: 13.1"
@@ -45,8 +46,8 @@ bool success = userSecretsManager.TrySetSecret("MySecret", "SecretValue");
 - **`UserSecretsManager`**: Default implementation managing secrets file operations
 - **`UserSecretsManagerFactory`**: Factory for creating and caching manager instances
 - **`FilePath`**: Gets the path to the user secrets JSON file
-- **`TrySetSecret()`**: Attempts to set a secret value in user secrets
-- **`GetOrSetSecret()`**: Gets a secret from configuration or generates and saves a new value
+- **<ApiReference name="Aspire.Hosting.IUserSecretsManager.TrySetSecret" />**: Attempts to set a secret value in user secrets
+- **<ApiReference name="Aspire.Hosting.IUserSecretsManager.GetOrSetSecret" />**: Gets a secret from configuration or generates and saves a new value
 - **`SaveStateAsync()`**: Saves deployment state to user secrets asynchronously
 
 ## To correct this warning
diff --git a/src/frontend/src/content/docs/diagnostics/overview.mdx b/src/frontend/src/content/docs/diagnostics/overview.mdx
index 9e0b41b8ed..948812a0a6 100644
--- a/src/frontend/src/content/docs/diagnostics/overview.mdx
+++ b/src/frontend/src/content/docs/diagnostics/overview.mdx
@@ -4,6 +4,8 @@ seoTitle: 'Aspire diagnostics overview: ASPIRE compiler diagnostics'
 description: Learn about the diagnostics tools and features available in Aspire — analyzers, compiler errors, the dashboard, structured telemetry, and troubleshooting workflows.
 ---
 
+import ApiReference from '@components/ApiReference.astro';
+
 The following table lists the possible MSBuild and analyzer warnings and errors you might encounter with Aspire:
 
 | Diagnostic ID                                                                      | Type                   | Description                                                                                                                                                                                    |
@@ -18,9 +20,9 @@ The following table lists the possible MSBuild and analyzer warnings and errors
 | [ASPIRE009](/diagnostics/aspire009/)                                               | Error                  | 'Project' is configured to use the Aspire CLI bundle, but the bundle could not be resolved.                                                                                                    |
 | [ASPIRE010](/diagnostics/aspire010/)                                               | Warning                | 'Project' is configured with AspireUseCliBundle=false. Some Aspire features require the Aspire CLI bundle.                                                                                     |
 | [ASPIRE011](/diagnostics/aspire011/)                                               | Error                  | 'Project' is configured to invoke the Aspire CLI through DNX, but the dnx command could not be found on PATH.                                                                                  |
-| [ASPIREACADOMAINS001](/diagnostics/aspireacadomains001/)                           | (Experimental) Error   | `ConfigureCustomDomain` is for evaluation purposes only and is subject to change or removal in future updates.                                                                                 |
-| [ASPIREACAEXPRESS001](/diagnostics/aspireacaexpress001/)                           | (Experimental) Error   | `AsExpress` is for evaluation purposes only and is subject to change or removal in future updates.                                                                                             |
-| [ASPIREACANAMING001](/diagnostics/aspireacanaming001/)                             | (Experimental) Warning | `WithCompactResourceNaming` is for evaluation purposes only and is subject to change or removal in future updates.                                                                             |
+| [ASPIREACADOMAINS001](/diagnostics/aspireacadomains001/)                           | (Experimental) Error   | <ApiReference name="Aspire.Hosting.ContainerAppExtensions.ConfigureCustomDomain" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                                 |
+| [ASPIREACAEXPRESS001](/diagnostics/aspireacaexpress001/)                           | (Experimental) Error   | <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AsExpress" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                                             |
+| [ASPIREACANAMING001](/diagnostics/aspireacanaming001/)                             | (Experimental) Warning | <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithCompactResourceNaming" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                             |
 | [ASPIREEXPORT001](/diagnostics/aspireexport001/)                                   | Error                  | `[AspireExport]` method must be static.                                                                                                                                                        |
 | [ASPIREEXPORT002](/diagnostics/aspireexport002/)                                   | Error                  | Invalid export ID format (must match `[a-zA-Z][a-zA-Z0-9.]*`).                                                                                                                                 |
 | [ASPIREEXPORT003](/diagnostics/aspireexport003/)                                   | Error                  | Return type is not ATS-compatible.                                                                                                                                                             |
@@ -45,8 +47,8 @@ The following table lists the possible MSBuild and analyzer warnings and errors
 | [ASPIRECOMPUTE003](/diagnostics/aspirecompute003/)                                 | (Experimental) Warning | The ContainerRegistryResource type is for evaluation purposes only and is subject to change or removal in future updates.                                                                      |
 | [ASPIRECONTAINERRUNTIME001](/diagnostics/aspirecontainerruntime001/)               | (Experimental) Warning | Type is for evaluation purposes only and is subject to change or removal in future updates.                                                                                                    |
 | [ASPIRECONTAINERSHELLEXECUTION001](/diagnostics/aspirecontainershellexecution001/) | (Experimental) Warning | Container shell execution property is for evaluation purposes only and is subject to change or removal in future updates.                                                                      |
-| [ASPIRECOSMOSDB001](/diagnostics/aspirecosmosdb001/)                               | (Experimental) Error   | `RunAsPreviewEmulator` is for evaluation purposes only and is subject to change or removal in future updates.                                                                                  |
-| [ASPIRECSHARPAPPS001](/diagnostics/aspirecsharpapps001/)                           | (Experimental) Error   | `AddCSharpApp` is for evaluation purposes only and is subject to change or removal in future updates.                                                                                          |
+| [ASPIRECOSMOSDB001](/diagnostics/aspirecosmosdb001/)                               | (Experimental) Error   | <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsPreviewEmulator" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                                  |
+| [ASPIRECSHARPAPPS001](/diagnostics/aspirecsharpapps001/)                           | (Experimental) Error   | <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                                          |
 | [ASPIREDOCKERFILEBUILDER001](/diagnostics/aspiredockerfilebuilder001/)             | (Experimental) Warning | Dockerfile builder types and members are for evaluation purposes only and are subject to change or removal in future updates.                                                                  |
 | [ASPIREDOTNETPROJECT001](/diagnostics/aspiredotnetproject001/)                     | (Experimental) Warning | Removed from the prerelease `Aspire.Hosting.Dotnet` and `Aspire.Hosting.Blazor` packages in Aspire 13.6. Their APIs remain unstable and may change.                                              |
 | [ASPIREDOTNETTOOL001](/diagnostics/aspiredotnettool001/)                           | (Experimental) Warning | .NET tool resource types and members are for evaluation purposes only and are subject to change or removal in future updates.                                                                  |
@@ -54,7 +56,7 @@ The following table lists the possible MSBuild and analyzer warnings and errors
 | [ASPIREFILESYSTEM001](/diagnostics/aspirefilesystem001/)                           | (Experimental) Warning | File system service types and members are for evaluation purposes only and are subject to change or removal in future updates.                                                                 |
 | [ASPIREINTERACTION001](/diagnostics/aspireinteraction001/)                         | (Experimental) Warning | Interaction service types and members are for evaluation purposes only and are subject to change or removal in future updates.                                                                 |
 | [ASPIREJAVASCRIPT001](/diagnostics/aspirejavascript001/)                           | (Experimental) Warning | JavaScript hosting and publishing APIs are for evaluation purposes only and are subject to change or removal in future updates.                                                                |
-| [ASPIREHOSTINGPYTHON001](/diagnostics/aspirehostingpython001/)                     | (Experimental) Error   | `AddPythonApp` is for evaluation purposes only and is subject to change or removal in future updates.                                                                                          |
+| [ASPIREHOSTINGPYTHON001](/diagnostics/aspirehostingpython001/)                     | (Experimental) Error   | <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" /> is for evaluation purposes only and is subject to change or removal in future updates.                                                                                          |
 | [ASPIREMCP001](/diagnostics/aspiremcp001/)                                         | (Experimental) Warning | <abbr title="Model Context Protocol" data-tooltip-placement="top">MCP</abbr> server types and members are for evaluation purposes only and are subject to change or removal in future updates. |
 | [ASPIREPERSISTENCE001](/diagnostics/aspirepersistence001/)                         | (Experimental) Error   | Resource lifetime types and members are for evaluation purposes only and are subject to change or removal in future updates.                                                                   |
 | [ASPIREPIPELINES001](/diagnostics/aspirepipelines001/)                             | (Experimental) Error   | Pipeline infrastructure APIs are for evaluation purposes only and are subject to change or removal in future updates.                                                                          |
diff --git a/src/frontend/src/content/docs/extensibility/custom-resources.mdx b/src/frontend/src/content/docs/extensibility/custom-resources.mdx
index c0b7aba83f..a73894aeff 100644
--- a/src/frontend/src/content/docs/extensibility/custom-resources.mdx
+++ b/src/frontend/src/content/docs/extensibility/custom-resources.mdx
@@ -5,6 +5,7 @@ description: "Learn how to create custom resource types for the Aspire AppHost t
 
 import { Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Creating custom resources allows you to extend Aspire to model components that aren't covered by built-in integrations. This guide covers the patterns and APIs for building your own resource types.
 
@@ -32,7 +33,7 @@ Aspire provides several interfaces that give resources specific capabilities:
 | `IResourceWithEndpoints` | Resource has network endpoints |
 | `IResourceWithEnvironment` | Resource can configure environment variables |
 | `IResourceWithArgs` | Resource accepts command-line arguments |
-| `IResourceWithWaitSupport` | Resource supports `WaitFor` orchestration |
+| `IResourceWithWaitSupport` | Resource supports <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> orchestration |
 | `IResourceWithParent` | Resource has a parent resource (lifecycle binding) |
 
 ### Implementing IResourceWithConnectionString
@@ -273,7 +274,7 @@ For more on how the Aspire Dashboard displays resources, see [Dashboard overview
 
 ## Custom icons
 
-Use `WithIconName` to display a custom icon for your resource in the dashboard. Any [Fluent UI system icon](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) can be used:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithIconName" /> to display a custom icon for your resource in the dashboard. Any [Fluent UI system icon](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) can be used:
 
 ```csharp title="Setting custom dashboard icons"
 return builder.AddResource(resource)
diff --git a/src/frontend/src/content/docs/extensibility/interaction-service.mdx b/src/frontend/src/content/docs/extensibility/interaction-service.mdx
index 482dc7eb77..1f94125774 100644
--- a/src/frontend/src/content/docs/extensibility/interaction-service.mdx
+++ b/src/frontend/src/content/docs/extensibility/interaction-service.mdx
@@ -18,6 +18,7 @@ import multipleInputFilled from '@assets/extensibility/interaction-service-multi
 import multipleInputFilledLight from '@assets/extensibility/interaction-service-multiple-input-filled-light.png';
 import multipleInputLogs from '@assets/extensibility/interaction-service-multiple-input-logs.png';
 import multipleInputLogsLight from '@assets/extensibility/interaction-service-multiple-input-logs-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 The interaction service (`Aspire.Hosting.IInteractionService`) allows you to prompt users for input, request confirmation, and display messages. It works in two different contexts:
 
@@ -109,7 +110,7 @@ Any of the available callback-based extension methods of `IResourceBuilder<T>` c
 
 - **Custom resource types**: Gather input from users or confirm actions when you create custom resource types. Resource types are free to define dashboard interactions, such as prompting for user input or displaying messages.
 
-- **Custom resource commands**: Add commands to resources in the Aspire dashboard or CLI. Use the interaction service to prompt users for input or confirmation when these commands run. When you chain a call to `WithCommand` on a target `IResourceBuilder<T>`, your callback can use the interaction service to gather input or confirm actions. For more information, see [Custom resource commands](/fundamentals/custom-resource-commands/).
+- **Custom resource commands**: Add commands to resources in the Aspire dashboard or CLI. Use the interaction service to prompt users for input or confirmation when these commands run. When you chain a call to <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCommand" /> on a target `IResourceBuilder<T>`, your callback can use the interaction service to gather input or confirm actions. For more information, see [Custom resource commands](/fundamentals/custom-resource-commands/).
 
   Commands might not be interactive when triggered from the Aspire CLI. Always check `IInteractionService.IsAvailable` before prompting and provide a fallback path when it returns `false`. [Command arguments](/fundamentals/custom-resource-commands/#command-arguments) are the best way to collect input in commands because they work in both the dashboard and CLI.
 
diff --git a/src/frontend/src/content/docs/extensibility/multi-language-integration-authoring.mdx b/src/frontend/src/content/docs/extensibility/multi-language-integration-authoring.mdx
index 2ea965cdcf..0aeb653d2e 100644
--- a/src/frontend/src/content/docs/extensibility/multi-language-integration-authoring.mdx
+++ b/src/frontend/src/content/docs/extensibility/multi-language-integration-authoring.mdx
@@ -5,6 +5,7 @@ description: Annotate Aspire hosting integrations so they work with TypeScript A
 ---
 
 import { Aside, Steps } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire hosting integrations are C# libraries that extend the AppHost with new resource types. By default, these integrations are only available in C# AppHosts. To make them available in TypeScript AppHosts, you annotate your APIs with ATS (Aspire Type System) attributes.
 
@@ -651,7 +652,7 @@ Prefer getter-only properties (`=> value;` or `{ get; }` without a setter) when
 
 ## Callback context types and the ATS-first editor pattern
 
-When you export a method that accepts a callback (such as `withEnvironmentCallback`, `withArgsCallback`, or `withUrls`), the callback receives a _context_ object. For ATS compatibility, context types should follow the ATS-first design:
+When you export a method that accepts a callback (such as `withEnvironmentCallback`, `withArgsCallback`, or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrls" />), the callback receives a _context_ object. For ATS compatibility, context types should follow the ATS-first design:
 
 1. Use `[AspireExport]` (not `ExposeProperties = true`) on the context class.
 2. Annotate only the properties that generated SDK callers need with individual `[AspireExport]` attributes.
diff --git a/src/frontend/src/content/docs/fundamentals/annotations-overview.mdx b/src/frontend/src/content/docs/fundamentals/annotations-overview.mdx
index a656aeac94..6345d86b46 100644
--- a/src/frontend/src/content/docs/fundamentals/annotations-overview.mdx
+++ b/src/frontend/src/content/docs/fundamentals/annotations-overview.mdx
@@ -6,6 +6,7 @@ description: Learn how Aspire annotations work, how the AppHost composes built-i
 
 import { Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Annotations are a key extensibility mechanism in Aspire that allow you to attach metadata and behavior to resources. They provide a way to customize how resources are configured, deployed, and managed throughout the application lifecycle. This article explains how annotations work and how to use them effectively in your Aspire applications.
 
@@ -39,8 +40,8 @@ builder.Build().Run();
 
 In this example:
 
-- `WithCommand` adds a `ResourceCommandAnnotation` that defines a custom command.
-- `WithUrl` adds a `ResourceUrlAnnotation` that defines a custom URL.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCommand" /> adds a `ResourceCommandAnnotation` that defines a custom command.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrl" /> adds a `ResourceUrlAnnotation` that defines a custom URL.
 
 ## Adding and managing annotations
 
@@ -123,7 +124,7 @@ var postgres = builder.AddPostgres("postgres")
 
 ### `HealthCheckAnnotation`
 
-The `HealthCheckAnnotation` associates health checks with a resource, used by `WaitFor()` to determine when a resource is ready:
+The `HealthCheckAnnotation` associates health checks with a resource, used by <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> to determine when a resource is ready:
 
 ```csharp title="AppHost.cs"
 var api = builder.AddProject<Projects.Api>("api")
@@ -136,7 +137,7 @@ Learn more about how Aspire uses health checks for orchestration in the [Health
 
 ### `WaitAnnotation`
 
-The `WaitAnnotation` declares a dependency on another resource and controls startup order. The `WaitFor`, `WaitForStart`, and `WaitForCompletion` methods add this annotation:
+The `WaitAnnotation` declares a dependency on another resource and controls startup order. The `WaitFor`, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForStart" />, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" /> methods add this annotation:
 
 ```csharp title="AppHost.cs"
 var cache = builder.AddRedis("cache");
diff --git a/src/frontend/src/content/docs/fundamentals/container-networking.mdx b/src/frontend/src/content/docs/fundamentals/container-networking.mdx
index 7c6255b898..8634e9ecea 100644
--- a/src/frontend/src/content/docs/fundamentals/container-networking.mdx
+++ b/src/frontend/src/content/docs/fundamentals/container-networking.mdx
@@ -6,6 +6,7 @@ description: Learn how the Aspire DCP container tunnel enables reliable containe
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 During local development, your Aspire app model often includes a mix of container resources and host-based services (such as C#, Python, or TypeScript projects). Container-to-container communication works naturally over the bridge network, but containers that need to reach services running on the host require a different approach. Aspire solves this with the **container tunnel**, a [Developer Control Plane (DCP)](/architecture/overview/#developer-control-plane) capability that provides reliable, transparent container-to-host connectivity.
 
@@ -23,7 +24,7 @@ These inconsistencies make container-to-host communication fragile and error-pro
 
 ## How the container tunnel works
 
-The container tunnel is managed by DCP and operates transparently—you don't need to configure it directly. When a container resource references an endpoint on a host-based service (via `WithReference`), Aspire detects that the container needs to reach the host and sets up a tunnel automatically.
+The container tunnel is managed by DCP and operates transparently—you don't need to configure it directly. When a container resource references an endpoint on a host-based service (via <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />), Aspire detects that the container needs to reach the host and sets up a tunnel automatically.
 
 At a high level, the tunnel works as follows:
 
diff --git a/src/frontend/src/content/docs/fundamentals/custom-resource-commands.mdx b/src/frontend/src/content/docs/fundamentals/custom-resource-commands.mdx
index 8a31fa12f5..c095714030 100644
--- a/src/frontend/src/content/docs/fundamentals/custom-resource-commands.mdx
+++ b/src/frontend/src/content/docs/fundamentals/custom-resource-commands.mdx
@@ -10,6 +10,7 @@ import customClearCacheCommand from '@assets/fundamentals/custom-clear-cache-com
 import customClearCacheCommandLight from '@assets/fundamentals/custom-clear-cache-command-light.png';
 import customClearCacheCommandSucceeded from '@assets/fundamentals/custom-clear-cache-command-succeeded.png';
 import customClearCacheCommandSucceededLight from '@assets/fundamentals/custom-clear-cache-command-succeeded-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Each resource in the Aspire app model is represented as an `IResource` and when added to the distributed application builder, it's the generic-type parameter of the `IResourceBuilder<T>` interface. You use the _resource builder_ API to chain calls, configuring the underlying resource, and in some situations, you might want to add custom commands to the resource. Some common scenario for creating a custom command might be running database migrations or seeding/resetting a database. In this article, you learn how to add a custom command to a Redis resource that clears the cache.
 
@@ -152,7 +153,7 @@ The preceding code:
 </TabItem>
 </Tabs>
 
-The `WithCommand` API adds the appropriate annotations to the resource, which are consumed in the [Aspire dashboard](/dashboard/overview/). The dashboard uses these annotations to render the command in the UI. Before getting too far into those details, let's ensure that you first understand the parameters of the `WithCommand` method:
+The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCommand" /> API adds the appropriate annotations to the resource, which are consumed in the [Aspire dashboard](/dashboard/overview/). The dashboard uses these annotations to render the command in the UI. Before getting too far into those details, let's ensure that you first understand the parameters of the `WithCommand` method:
 
 - `name`: The name of the command to invoke.
 - `displayName`: The name of the command to display in the dashboard.
@@ -1476,7 +1477,7 @@ For more control over progress behavior, including custom work callbacks and pro
 ## Process-backed resource commands
 
 :::caution[Experimental API]
-`WithProcessCommand` is experimental and requires opting in to the [`ASPIREPROCESSCOMMAND001`](/diagnostics/aspireprocesscommand001/) diagnostic suppression. The API shape may change before it stabilizes.
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithProcessCommand" /> is experimental and requires opting in to the [`ASPIREPROCESSCOMMAND001`](/diagnostics/aspireprocesscommand001/) diagnostic suppression. The API shape may change before it stabilizes.
 :::
 
 The `WithProcessCommand` API provides a reusable helper for the common pattern of exposing a local-tool invocation as a resource command. Instead of managing process start, stdout/stderr capture, and cancellation yourself inside a `WithCommand` callback, `WithProcessCommand` does that for you:
diff --git a/src/frontend/src/content/docs/fundamentals/custom-resource-urls.mdx b/src/frontend/src/content/docs/fundamentals/custom-resource-urls.mdx
index dc96ec1351..304b54aab5 100644
--- a/src/frontend/src/content/docs/fundamentals/custom-resource-urls.mdx
+++ b/src/frontend/src/content/docs/fundamentals/custom-resource-urls.mdx
@@ -5,6 +5,7 @@ description: Create custom resource URLs in Aspire so the dashboard, MCP server,
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 In Aspire, resources that expose endpoints only configure host and port, which aren't known until run time. If you need to access a specific path on one of these endpoints—especially from the [dashboard](/dashboard/overview/)—you can define custom resource URLs. You can also add custom URLs that aren't tied to any endpoint. All custom URLs are only available in "run" mode, since they're meant for dashboard use. This article demonstrates how to define custom URLs.
 
@@ -12,10 +13,10 @@ In Aspire, resources that expose endpoints only configure host and port, which a
 
 By default, Aspire project resources rely on existing configurations such as Kestrel or launch profiles to determine the host and port of a resource for a configured endpoint—and the endpoints are always displayed on the dashboard.
 
-Likewise, you can explicitly expose endpoints using the `WithEndpoint` API. This API allows you to specify the host and port for a resource, which is then used to create the default URL for that resource. The default URL is typically in the format `<scheme>://<host>:<port>`. To omit the host port, use one of the following methods:
+Likewise, you can explicitly expose endpoints using the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> API. This API allows you to specify the host and port for a resource, which is then used to create the default URL for that resource. The default URL is typically in the format `<scheme>://<host>:<port>`. To omit the host port, use one of the following methods:
 
-- `WithHttpEndpoint`
-- `WithHttpsEndpoint`
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" />
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsEndpoint" />
 
 For more information, see [Endpoint extension methods](/fundamentals/networking-overview/#endpoint-extension-methods).
 
@@ -29,7 +30,7 @@ Custom resource URLs are supported for the following resource types:
 
 ## Customize resource URLs
 
-Use the appropriate `WithUrl` overload, `WithUrls`, or `WithUrlForEndpoint` APIs on any supported resource builder to define custom URLs for a resource. The following example demonstrates how to set a custom URL for a project resource:
+Use the appropriate <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrl" /> overload, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrls" />, or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrlForEndpoint" /> APIs on any supported resource builder to define custom URLs for a resource. The following example demonstrates how to set a custom URL for a project resource:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -101,7 +102,7 @@ The preceding code iterates through the URLs defined for the `api` project resou
 <Aside type="tip">
   The `ResourceUrlsCallbackContext` exposes an extension method that enables you
   to easily access the underlying resource named endpoints. Call the
-  `GetEndpoint` API on a context instance to achieve this.
+  <ApiReference name="Aspire.Hosting.ApplicationModel.ResourceUrlsCallbackContext.GetEndpoint" /> API on a context instance to achieve this.
 </Aside>
 
 ## URL customization lifecycle
diff --git a/src/frontend/src/content/docs/fundamentals/environment-variables.mdx b/src/frontend/src/content/docs/fundamentals/environment-variables.mdx
index ce93d7d59c..576cab33e1 100644
--- a/src/frontend/src/content/docs/fundamentals/environment-variables.mdx
+++ b/src/frontend/src/content/docs/fundamentals/environment-variables.mdx
@@ -5,8 +5,9 @@ description: Learn how Aspire generates environment variable names for connectio
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
-When you use `WithReference` to connect resources in the AppHost, Aspire automatically injects environment variables into the consuming resource. This process is called _configuration injection_.
+When you use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> to connect resources in the AppHost, Aspire automatically injects environment variables into the consuming resource. This process is called _configuration injection_.
 
 These environment variable names follow specific conventions based on the referenced resource's name and type. Understanding the conventions is especially useful for applications that read environment variables directly instead of relying on typed Aspire client integrations.
 
@@ -235,7 +236,7 @@ In JavaScript, `process.env` is an object. If you read an original alias contain
 
 ## Custom environment variables
 
-If you need different variable names, use `WithEnvironment` to set custom environment variables:
+If you need different variable names, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> to set custom environment variables:
 
 ```csharp title="C# — AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/fundamentals/external-parameters.mdx b/src/frontend/src/content/docs/fundamentals/external-parameters.mdx
index 303b18c246..5cbb44dadb 100644
--- a/src/frontend/src/content/docs/fundamentals/external-parameters.mdx
+++ b/src/frontend/src/content/docs/fundamentals/external-parameters.mdx
@@ -10,6 +10,7 @@ import dashboardUnresolvedParams from '@assets/fundamentals/dashboard-unresolved
 import dashboardUnresolvedParamsLight from '@assets/fundamentals/dashboard-unresolved-parameters-message-light.png';
 import customizedParameterUi from '@assets/fundamentals/customized-parameter-ui.png';
 import customizedParameterUiLight from '@assets/fundamentals/customized-parameter-ui-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Environments provide context for the application to run in. Parameters express the ability to ask for an external value when running the app. Parameters can be used to provide values to the app when running locally, or to prompt for values when deploying. They can be used to model a wide range of scenarios including secrets, connection strings, and other configuration values that might vary between environments.
 
@@ -203,8 +204,8 @@ When you select **Enter values**, Aspire displays a form that you can use to con
 
 You can also control how the dashboard displays these parameters, by using these methods:
 
-- `WithDescription`: Use this method to provide a text description that helps users understand the purpose of the parameter. To provide a formatted description in [Markdown](https://www.markdownguide.org/basic-syntax/), use the `enableMarkdown: true` parameter.
-- `WithCustomInput`: Use this method to provide a callback method that customizes the parameter dialog. For example, in this callback you can customize the default value, input type, label, and placeholder text. When using `WithCustomInput`, you must copy the `EnableDescriptionMarkdown` property from the parameter to the `InteractionInput` object to preserve markdown rendering.
+- <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.WithDescription" />: Use this method to provide a text description that helps users understand the purpose of the parameter. To provide a formatted description in [Markdown](https://www.markdownguide.org/basic-syntax/), use the `enableMarkdown: true` parameter.
+- <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.WithCustomInput" />: Use this method to provide a callback method that customizes the parameter dialog. For example, in this callback you can customize the default value, input type, label, and placeholder text. When using `WithCustomInput`, you must copy the `EnableDescriptionMarkdown` property from the parameter to the `InteractionInput` object to preserve markdown rendering.
 
 This code shows how to set a description and use the callback:
 
@@ -366,7 +367,7 @@ The manifest representation is as follows:
 
 ## Add parameters from configuration
 
-In some scenarios, you might want to read parameter values directly from a specific configuration key rather than following the standard `Parameters:*` pattern. The `AddParameterFromConfiguration` method allows you to specify a custom configuration key for a parameter.
+In some scenarios, you might want to read parameter values directly from a specific configuration key rather than following the standard `Parameters:*` pattern. The <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameterFromConfiguration" /> method allows you to specify a custom configuration key for a parameter.
 
 <Aside type="note">
 The `addParameterFromConfiguration` API is not yet available in the TypeScript AppHost SDK.
@@ -458,7 +459,7 @@ This method is useful when:
 Parameters can be used to model connection strings. When you publish the app, the value is prompted for and stored in a secure location. When you run the app locally, the value is read from the `ConnectionStrings` section of the AppHost configuration.
 
 <Aside type="danger">
-Always use `AddParameter` to pass secrets to resources. Never include passwords or other sensitive data like connection strings in source code.
+Always use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> to pass secrets to resources. Never include passwords or other sensitive data like connection strings in source code.
 
 If you're connecting to a local database, and want to use Integrated Security or passwordless authentication, you don't need to worry about securing your connection strings. If you're using a password, store the connection string securely using app secrets.
 
@@ -504,7 +505,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="note">
-  Using `WaitFor` with a connection string will implicitly wait for the resource
+  Using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> with a connection string will implicitly wait for the resource
   that the connection string connects to. For connection strings backed only by
   configuration, the dependency is still modeled but there isn't an
   Aspire-managed resource to wait for.
@@ -522,7 +523,7 @@ Now consider the following AppHost configuration file _appsettings.json_:
 
 ### Build connection strings with reference expressions
 
-If you want to construct a connection string from parameters and ensure that it's handled correctly in both development and production, use `AddConnectionString` with a `ReferenceExpression`.
+If you want to construct a connection string from parameters and ensure that it's handled correctly in both development and production, use <ApiReference name="Aspire.Hosting.ConnectionStringBuilderExtensions.AddConnectionString" /> with a `ReferenceExpression`.
 
 For example, if you have a secret parameter that stores a small part of a connection string, use this code to insert it:
 
diff --git a/src/frontend/src/content/docs/fundamentals/health-checks.mdx b/src/frontend/src/content/docs/fundamentals/health-checks.mdx
index 2a71e1d173..73cc2eb453 100644
--- a/src/frontend/src/content/docs/fundamentals/health-checks.mdx
+++ b/src/frontend/src/content/docs/fundamentals/health-checks.mdx
@@ -8,6 +8,7 @@ import ThemeImage from '@components/ThemeImage.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import healthChecksDashboardStatus from '@assets/fundamentals/health-checks-dashboard-status.png';
 import healthChecksDashboardStatusLight from '@assets/fundamentals/health-checks-dashboard-status-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Health checks provide availability and state information about an app. Health checks are often exposed as HTTP endpoints, but can also be used internally by the app to write logs or perform other tasks based on the current health. Health checks are typically used in combination with an external monitoring service or container orchestrator to check the status of an app.
 
@@ -17,7 +18,7 @@ Aspire uses health checks in two distinct contexts. Understanding the difference
 
 | Health check type           | Where it runs    | What it checks            | Used for                           |
 | --------------------------- | ---------------- | ------------------------- | ---------------------------------- |
-| **AppHost resource checks** | AppHost project  | "Is my dependency ready?" | Startup orchestration, `WaitFor()` |
+| **AppHost resource checks** | AppHost project  | "Is my dependency ready?" | Startup orchestration, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> |
 | **Service endpoint checks** | Your application | "Am I healthy?"           | Load balancers, Kubernetes probes  |
 
 <Aside type="tip" title="Key insight">
@@ -468,7 +469,7 @@ await webapp.waitFor(catalogApi); // Waits for /health to return HTTP 200
 </TabItem>
 </Tabs>
 
-The `WithHttpHealthCheck` method can also be applied to project resources:
+The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> method can also be applied to project resources:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -537,7 +538,7 @@ builder.AddProject<Projects.MyApp>("myapp")
   `builder.Services.AddHealthChecks()` is not yet available.
 </Aside>
 
-The `AddCheck` method registers the health check, and `WithHealthCheck` associates it with specific resources. For more details about creating and registering custom health checks, see [Create health checks](https://learn.microsoft.com/aspnet/core/host-and-deploy/health-checks#create-health-checks).
+The `AddCheck` method registers the health check, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHealthCheck" /> associates it with specific resources. For more details about creating and registering custom health checks, see [Create health checks](https://learn.microsoft.com/aspnet/core/host-and-deploy/health-checks#create-health-checks).
 
 ### Dashboard integration
 
diff --git a/src/frontend/src/content/docs/fundamentals/http-commands.mdx b/src/frontend/src/content/docs/fundamentals/http-commands.mdx
index 9d4f7fd01a..3370607af8 100644
--- a/src/frontend/src/content/docs/fundamentals/http-commands.mdx
+++ b/src/frontend/src/content/docs/fundamentals/http-commands.mdx
@@ -15,8 +15,9 @@ import customHttpCommandStarting from '@assets/fundamentals/custom-http-command-
 import customHttpCommandStartingLight from '@assets/fundamentals/custom-http-command-starting-light.png';
 import customHttpCommandSucceeded from '@assets/fundamentals/custom-http-command-succeeded.png';
 import customHttpCommandSucceededLight from '@assets/fundamentals/custom-http-command-succeeded-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
-In Aspire, you can add custom HTTP commands to resources using the `WithHttpCommand` API. This API extends existing functionality, where you provide [custom commands on resources](/fundamentals/custom-resource-commands/). This feature enables a command on a resource that sends an HTTP request to a specified endpoint and path. This is useful for scenarios such as triggering database migrations, clearing caches, or performing custom actions on resources through HTTP requests.
+In Aspire, you can add custom HTTP commands to resources using the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpCommand" /> API. This API extends existing functionality, where you provide [custom commands on resources](/fundamentals/custom-resource-commands/). This feature enables a command on a resource that sends an HTTP request to a specified endpoint and path. This is useful for scenarios such as triggering database migrations, clearing caches, or performing custom actions on resources through HTTP requests.
 
 To implement custom HTTP commands, you define a command on a resource and a corresponding HTTP endpoint that handles the request. This article provides an overview of how to create and configure custom HTTP commands in Aspire.
 
diff --git a/src/frontend/src/content/docs/fundamentals/networking-overview.mdx b/src/frontend/src/content/docs/fundamentals/networking-overview.mdx
index 148806a874..768f210968 100644
--- a/src/frontend/src/content/docs/fundamentals/networking-overview.mdx
+++ b/src/frontend/src/content/docs/fundamentals/networking-overview.mdx
@@ -13,6 +13,7 @@ import proxyWithReplicas from '@assets/fundamentals/networking/proxy-with-replic
 import proxyHostPortAndRandomPort from '@assets/fundamentals/networking/proxy-host-port-and-random-port-1x.png';
 import proxyWithRandomPorts from '@assets/fundamentals/networking/proxy-with-random-ports-1x.png';
 import proxyWithDockerPortMapping from '@assets/fundamentals/networking/proxy-with-docker-port-mapping-1x.png';
+import ApiReference from '@components/ApiReference.astro';
 
 One of the advantages of developing with Aspire is that it enables you to develop, test, and debug cloud-native apps locally. Inner-loop networking is a key aspect of Aspire that allows your apps to communicate with each other in your development environment. In this article, you learn how Aspire handles various networking scenarios with proxies, endpoints, endpoint configurations, and container networking.
 
@@ -53,7 +54,7 @@ flowchart LR
 
 The inner loop is the process of developing and testing your app locally before deploying it to a target environment. Aspire provides several tools and features to simplify and enhance the networking experience in the inner loop, such as:
 
-- **Endpoints/Endpoint configurations**: Endpoints are the connections between your app and the services it depends on, such as databases, message queues, or APIs. Endpoints provide information such as the service name, host port, scheme, and environment variable. Aspire can create endpoints automatically from resource configuration, and you can also add them explicitly by calling `WithEndpoint`.
+- **Endpoints/Endpoint configurations**: Endpoints are the connections between your app and the services it depends on, such as databases, message queues, or APIs. Endpoints provide information such as the service name, host port, scheme, and environment variable. Aspire can create endpoints automatically from resource configuration, and you can also add them explicitly by calling <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" />.
 - **Proxies**: Aspire automatically launches a proxy for each proxied service binding you add to your app, and assigns a port for the proxy to listen on. The proxy then forwards the requests to the port that your app listens on, which might be different from the proxy port. This way, you can avoid port conflicts and access your app and services using consistent and predictable URLs.
 - **Proxyless endpoints**: Endpoints with `IsProxied` set to `false` connect directly to the resource instead of routing through an Aspire-managed proxy. Starting in Aspire 13.4, endpoints on persistent executables and projects are proxyless by default. Persistent containers use proxied endpoints by default, the same as session containers.
 - **Container networks**: Aspire creates and manages dedicated networks for container resources so containers can discover and communicate with each other during local development.
@@ -104,7 +105,7 @@ Containers register themselves on the network using their resource name. Aspire
 
 By default, containers are accessible on the container network using their **resource name** as a DNS alias. For example, a container added with `AddContainer("mydb", ...)` is reachable at `mydb:5432` from other containers.
 
-Sometimes you need additional aliases—for example, when a third-party tool expects a specific hostname, or when migrating from an existing Docker Compose setup. Use `WithContainerNetworkAlias` to add custom DNS names:
+Sometimes you need additional aliases—for example, when a third-party tool expects a specific hostname, or when migrating from an existing Docker Compose setup. Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerNetworkAlias" /> to add custom DNS names:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -156,7 +157,7 @@ Some endpoint behavior depends on the resource type. Keep those details with the
 
 ## Ports and proxies
 
-When defining a proxied service binding, the host port is given to the proxy that sits in front of the service. This allows single or multiple replicas of a service to behave similarly. Additionally, resource dependencies that use the `WithReference` API rely on the proxied endpoint from the environment variable unless the endpoint is configured as proxyless.
+When defining a proxied service binding, the host port is given to the proxy that sits in front of the service. This allows single or multiple replicas of a service to behave similarly. Additionally, resource dependencies that use the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> API rely on the proxied endpoint from the environment variable unless the endpoint is configured as proxyless.
 
 The same proxy pattern applies when a service runs multiple replicas. The browser still connects to one stable host port while the proxy fans out traffic to whichever replica is available:
 
@@ -576,7 +577,7 @@ The following built-in Aspire integrations already apply this pattern to their a
 **Common causes**:
 
 - The container hasn't finished starting
-- Missing `WaitFor()` dependency
+- Missing <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> dependency
 - Container is on the container network but you're connecting from the host
 
 **Solutions**:
diff --git a/src/frontend/src/content/docs/fundamentals/persist-data-volumes.mdx b/src/frontend/src/content/docs/fundamentals/persist-data-volumes.mdx
index caf810d3f4..cf5facb84a 100644
--- a/src/frontend/src/content/docs/fundamentals/persist-data-volumes.mdx
+++ b/src/frontend/src/content/docs/fundamentals/persist-data-volumes.mdx
@@ -4,6 +4,7 @@ description: Configure Aspire resources to persist data across restarts using co
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Every time you start and stop an Aspire project, the app also creates and destroys the app resource containers. Any data or files stored in those containers during a debugging session is lost for subsequent sessions. Many development teams prefer to keep this data across debugging sessions so that, for example, they don't have to repopulate a database with sample data for each run.
 
@@ -35,7 +36,7 @@ Volumes are more secure and portable than bind mounts. They also perform better
 
 ## Use volumes
 
-Volumes are the recommended way to persist data generated by containers and they're supported on both Windows and Linux. Volumes can store data from multiple containers at a time, offer high performance, and are easy to back up or migrate. With Aspire, you configure a volume for each resource container using the `WithVolume` method, which accepts three parameters:
+Volumes are the recommended way to persist data generated by containers and they're supported on both Windows and Linux. Volumes can store data from multiple containers at a time, offer high performance, and are easy to back up or migrate. With Aspire, you configure a volume for each resource container using the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithVolume" /> method, which accepts three parameters:
 
 - **`name`**: An optional name for the volume.
 - **`target`**: The target path in the container of the data you want to persist.
@@ -99,7 +100,7 @@ const sqldb = await sql.addDatabase("sqldb");
 
 In this example `/var/opt/mssql` sets the path to the database files in the container.
 
-All Aspire container resources can utilize volumes, and some provide convenient APIs for adding named volumes derived from resources. Using the `WithDataVolume` method as an example, the following code is functionally equivalent to the previous example but more succinct:
+All Aspire container resources can utilize volumes, and some provide convenient APIs for adding named volumes derived from resources. Using the <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> method as an example, the following code is functionally equivalent to the previous example but more succinct:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -164,7 +165,7 @@ This convention also applies to Kubernetes persistent volumes bound with `WithPe
 
 ## Use bind mounts
 
-Bind mounts enable access to the data from both within the container and from processes on the host machine. For example, once a bind mount is established, you can copy a file into it on your host computer. The file is then available at the bound path within the container for your resource. With Aspire, you configure a bind mount for each resource container using the `WithBindMount` method, which accepts three parameters:
+Bind mounts enable access to the data from both within the container and from processes on the host machine. For example, once a bind mount is established, you can copy a file into it on your host computer. The file is then available at the bound path within the container for your resource. With Aspire, you configure a bind mount for each resource container using the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBindMount" /> method, which accepts three parameters:
 
 - **`source`**: The path to the folder on the host machine to mount in the container.
 - **`target`**: The target path in the container for the folder.
@@ -198,7 +199,7 @@ In this example:
 - `source: @"C:\SqlServer\Data"` sets the folder on the host computer that will be bound.
 - `target: "/var/opt/mssql"` sets the path to the database files in the container.
 
-As for volumes, some Aspire container resources provide convenient APIs for adding bind mounts. Using the `WithDataBindMount` method as an example, the following code is functionally equivalent to the previous example but more succinct:
+As for volumes, some Aspire container resources provide convenient APIs for adding bind mounts. Using the <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataBindMount" /> method as an example, the following code is functionally equivalent to the previous example but more succinct:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -246,7 +247,7 @@ const sqldb = await sql.addDatabase("sqldb");
 </TabItem>
 </Tabs>
 
-Since the `password` parameter isn't provided when calling `AddSqlServer`, Aspire automatically generates a password for the SQL Server resource.
+Since the `password` parameter isn't provided when calling <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.AddSqlServer" />, Aspire automatically generates a password for the SQL Server resource.
 
 <Aside type="caution">
   This isn't a persistent password! Instead, it changes every time the AppHost
@@ -273,7 +274,7 @@ The same pattern applies to the other server-based resource types, such as those
 | RabbitMQ      | [📦 Aspire.Hosting.RabbitMq](https://www.nuget.org/packages/Aspire.Hosting.RabbitMq)     | `rabbitmq`            | `Parameters:rabbitmq-password`   |
 | SQL Server    | [📦 Aspire.Hosting.SqlServer](https://www.nuget.org/packages/Aspire.Hosting.SqlServer)   | `sql`                 | `Parameters:sql-password`        |
 
-By overriding the generated password, you can ensure that the password remains consistent between app launches. An alternative approach is to use the `AddParameter` method to create a parameter that can be used as a password. The following code demonstrates how to create a persistent password for a SQL Server resource:
+By overriding the generated password, you can ensure that the password remains consistent between app launches. An alternative approach is to use the <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> method to create a parameter that can be used as a password. The following code demonstrates how to create a persistent password for a SQL Server resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/fundamentals/service-discovery.mdx b/src/frontend/src/content/docs/fundamentals/service-discovery.mdx
index f44376910a..79603f78e6 100644
--- a/src/frontend/src/content/docs/fundamentals/service-discovery.mdx
+++ b/src/frontend/src/content/docs/fundamentals/service-discovery.mdx
@@ -5,12 +5,13 @@ description: Understand essential Aspire service discovery concepts — endpoint
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Service discovery is how your services find each other. Instead of hardcoding URLs like `http://localhost:5001`, your frontend can simply reference the `catalog` service by name—and Aspire handles resolving the actual address.
 
 ## How service discovery works
 
-When you connect services using `WithReference()`, Aspire sets up automatic service discovery:
+When you connect services using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, Aspire sets up automatic service discovery:
 
 1. **AppHost declares resources** and allocates endpoints
 2. **Configuration is injected** into each service via environment variables
@@ -365,7 +366,7 @@ const response = await fetch(`${dashboardUrl}/api/stats`);
 **Common causes**:
 
 1. **Missing `WithReference()`** - The calling service wasn't connected to the target service in AppHost
-2. **Wrong service name** - The name in your URI doesn't match the name in `AddProject()` or `AddContainer()`
+2. **Wrong service name** - The name in your URI doesn't match the name in <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> or <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" />
 3. **Service not started** - The target service failed to start or is still starting
 
 **Solution**: Verify your AppHost connects the services:
diff --git a/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx b/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
index b7820b0fd2..0f48ebf52d 100644
--- a/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
+++ b/src/frontend/src/content/docs/get-started/add-aspire-existing-app.mdx
@@ -179,7 +179,7 @@ After setup, a typical repo layout looks like this:
 </FileTree>
 
 :::caution[AddCSharpApp is experimental]
-`AddCSharpApp` is currently experimental. If you want details on limitations or diagnostic suppression, see [C# file-based apps](/integrations/dotnet/csharp-file-based-apps/).
+<ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> is currently experimental. If you want details on limitations or diagnostic suppression, see [C# file-based apps](/integrations/dotnet/csharp-file-based-apps/).
 :::
 
 #### Project-based AppHost (with a .sln)
diff --git a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
index 440b16f948..c674a558b0 100644
--- a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
+++ b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
@@ -7,6 +7,7 @@ import { Aside, Steps, TabItem, Tabs } from '@astrojs/starlight/components';
 import AsciinemaPlayer from '@components/AsciinemaPlayer.astro';
 import LearnMore from '@components/LearnMore.astro';
 import LoopingVideo from '@components/LoopingVideo.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Give your AI coding agent access to application observability, not just source code. Run `aspire agent init` in your project to install skills that teach your assistant to use the Aspire CLI, inspect local services, and work with TypeScript or C# AppHosts. A runtime MCP server is optional.
 
@@ -67,7 +68,7 @@ The optional MCP server gives your AI agent direct runtime access to your runnin
 
 ## Start and stop AppHosts through VS Code
 
-With the [Aspire VS Code extension](/get-started/aspire-vscode-extension/#let-coding-agents-start-and-stop-apphosts), agents can use `#aspireStartAppHost` and `#aspireStopAppHost` to control a discovered AppHost through the editor. Start supports `run` and `debug` modes, and both tools require a trusted workspace and user confirmation.
+With the [Aspire VS Code extension](/get-started/aspire-vscode-extension/#let-coding-agents-start-and-stop-apphosts), agents can use `#aspireStartAppHost` and `#aspireStopAppHost` to control a discovered AppHost through the editor. Start supports <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> and `debug` modes, and both tools require a trusted workspace and user confirmation.
 
 > Use #aspireStartAppHost to start my AppHost in debug mode, then inspect the resource status.
 
diff --git a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
index 063e0ed3cb..6016fdcff9 100644
--- a/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-sdk.mdx
@@ -5,6 +5,7 @@ description: Learn how the Aspire SDK simplifies orchestrating Aspire applicatio
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 The Aspire SDK is intended for [AppHost projects](/get-started/app-host/), which serve as the orchestrator for Aspire applications. These projects are designated by their usage of the `Aspire.AppHost.Sdk` in the project file. The SDK provides features that simplify the development of Aspire apps.
 
@@ -54,7 +55,7 @@ The Aspire SDK provides several key features.
 
 ### Project references
 
-Each `ProjectReference` in the AppHost project isn't treated as standard project references. Instead, they enable the AppHost to execute these projects as part of its orchestration. Each project reference triggers a generator to create a `class` that represents the project as an `IProjectMetadata`. This metadata is used to populate the named projects in the generated `Projects` namespace. When you call the `AddProject` API, the `Projects` namespace is used to reference the project—passing the generated class as a generic-type parameter.
+Each `ProjectReference` in the AppHost project isn't treated as standard project references. Instead, they enable the AppHost to execute these projects as part of its orchestration. Each project reference triggers a generator to create a `class` that represents the project as an `IProjectMetadata`. This metadata is used to populate the named projects in the generated `Projects` namespace. When you call the <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> API, the `Projects` namespace is used to reference the project—passing the generated class as a generic-type parameter.
 
 :::tip
 To prevent a project from being treated as an Aspire resource in the AppHost, set the `IsAspireProjectResource` attribute on the `ProjectReference` element to `false`, as shown in the following example:
diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 1cbd7e1404..592b5ef2bd 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -13,6 +13,7 @@ import sidebarTreeLight from '@assets/get-started/code-extension-sidebar-light.p
 import debugSessions from '@assets/get-started/code-extension-debug.png';
 import debugSessionsLight from '@assets/get-started/code-extension-debug-light.png';
 import { Kbd } from 'starlight-kbd/components';
+import ApiReference from '@components/ApiReference.astro';
 
 The official Aspire extension for [Visual Studio Code](https://code.visualstudio.com/) turns VS Code into a first-class environment for building, debugging, and shipping [polyglot](/get-started/glossary/#polyglot) Aspire apps.
 Press <Kbd windows='F5' /> to build your AppHost, start your resources, and debug supported resource types — including C#, TypeScript, Java, Python, browser apps, and Azure Functions — alongside the Aspire dashboard.
@@ -86,7 +87,7 @@ In Aspire 13.6, the extension exposes two VS Code language model tools so a codi
 
 | Tool                   | Chat reference        | Action                                               |
 | ---------------------- | --------------------- | ---------------------------------------------------- |
-| `aspire_apphost_start` | `#aspireStartAppHost` | Start a discovered AppHost in `run` or `debug` mode. |
+| `aspire_apphost_start` | `#aspireStartAppHost` | Start a discovered AppHost in <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> or `debug` mode. |
 | `aspire_apphost_stop`  | `#aspireStopAppHost`  | Stop the selected discovered AppHost.                |
 
 Open a trusted workspace with the Aspire extension installed and an AppHost visible in the Aspire view. In an agent chat that supports VS Code tools, try:
diff --git a/src/frontend/src/content/docs/integrations/ai/github-models/github-models-host.mdx b/src/frontend/src/content/docs/integrations/ai/github-models/github-models-host.mdx
index 5a5fc6273e..286975d56a 100644
--- a/src/frontend/src/content/docs/integrations/ai/github-models/github-models-host.mdx
+++ b/src/frontend/src/content/docs/integrations/ai/github-models/github-models-host.mdx
@@ -6,6 +6,7 @@ description: Learn how to use the Aspire GitHub Models hosting integration to or
 import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import githubIcon from '@assets/icons/github-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={githubIcon}
@@ -88,7 +89,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 <Steps>
 
-1. Calling `AddGitHubModel` (or `addGitHubModel`) creates a `GitHubModelResource`. It registers a secret parameter for the API key that defaults to the `GITHUB_TOKEN` environment variable.
+1. Calling <ApiReference name="Aspire.Hosting.GitHubModelsExtensions.AddGitHubModel" /> creates a `GitHubModelResource`. It registers a secret parameter for the API key that defaults to the `GITHUB_TOKEN` environment variable.
 
 1. The model identifier selects which GitHub-hosted model to target. In C#, use the strongly-typed `GitHubModel` constants grouped by publisher; in TypeScript, use the `GitHubModelName` enum.
 
@@ -156,7 +157,7 @@ aspire secret set Parameters:chat-gh-apikey github_pat_YOUR_TOKEN_HERE
 
 ## Use a custom API key parameter
 
-Replace the default parameter by creating your own secret parameter and passing it to `WithApiKey` (or `withApiKey`):
+Replace the default parameter by creating your own secret parameter and passing it to <ApiReference name="Aspire.Hosting.GitHubModelsExtensions.WithApiKey" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/ai/ollama/ollama-connect.mdx b/src/frontend/src/content/docs/integrations/ai/ollama/ollama-connect.mdx
index 4b34f4d0fd..a0c08086ad 100644
--- a/src/frontend/src/content/docs/integrations/ai/ollama/ollama-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/ai/ollama/ollama-connect.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import ollamaIcon from '@assets/icons/ollama-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -343,5 +344,5 @@ for await (const chunk of stream) {
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the Aspire AppHost documentation for details on custom environment variable injection.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the Aspire AppHost documentation for details on custom environment variable injection.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/ai/ollama/ollama-host.mdx b/src/frontend/src/content/docs/integrations/ai/ollama/ollama-host.mdx
index 09690b2a5e..b458ba2d04 100644
--- a/src/frontend/src/content/docs/integrations/ai/ollama/ollama-host.mdx
+++ b/src/frontend/src/content/docs/integrations/ai/ollama/ollama-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import ollamaIcon from '@assets/icons/ollama-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -117,7 +118,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 1. When Aspire adds a container image to the AppHost, as shown in the preceding example with the `docker.io/ollama/ollama` image, it creates a new Ollama instance on your local machine.
 
-1. The resource name passed to `AddOllama` is used as the connection string name when referenced in a dependency. Model sub-resources are named by sanitizing the model name (for example, `"llama3"` produces the resource name `"ollama-llama3"`).
+1. The resource name passed to <ApiReference name="Aspire.Hosting.OllamaResourceBuilderExtensions.AddOllama" /> is used as the connection string name when referenced in a dependency. Model sub-resources are named by sanitizing the model name (for example, `"llama3"` produces the resource name `"ollama-llama3"`).
 
 1. The AppHost reference call configures a connection in the consuming project named after the referenced model resource.
 
@@ -129,7 +130,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add Ollama model resource
 
-Models are sub-resources of an Ollama server resource. You add them with the `AddModel` (or `addModel`) method. Each model is downloaded when the Ollama container first starts.
+Models are sub-resources of an Ollama server resource. You add them with the <ApiReference name="Aspire.Hosting.OllamaResourceBuilderExtensions.AddModel" /> method. Each model is downloaded when the Ollama container first starts.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -226,7 +227,7 @@ The data volume is mounted at `/root/.ollama` in the Ollama container. When a `n
 
 ## Use GPUs when available
 
-By default, the Ollama container runs on CPU. To enable GPU acceleration, use the `WithGPUSupport` (or `withGPUSupport`) extension method:
+By default, the Ollama container runs on CPU. To enable GPU acceleration, use the <ApiReference name="Aspire.Hosting.OllamaResourceBuilderExtensions.WithGPUSupport" /> extension method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -301,7 +302,7 @@ For more information, see [GPU support in Docker Desktop](https://docs.docker.co
 
 ## Add a model from Hugging Face
 
-To use a model in GGUF format from [Hugging Face](https://huggingface.co/), use the `AddHuggingFaceModel` (or `addHuggingFaceModel`) extension method:
+To use a model in GGUF format from [Hugging Face](https://huggingface.co/), use the <ApiReference name="Aspire.Hosting.OllamaResourceBuilderExtensions.AddHuggingFaceModel" /> extension method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/ai/openai/openai-host.mdx b/src/frontend/src/content/docs/integrations/ai/openai/openai-host.mdx
index 6fcfdab97f..aeecdb7ba5 100644
--- a/src/frontend/src/content/docs/integrations/ai/openai/openai-host.mdx
+++ b/src/frontend/src/content/docs/integrations/ai/openai/openai-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import openaiIcon from '@assets/icons/openai-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={openaiIcon}
@@ -110,9 +111,9 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 <Steps>
 
-1. Calling `AddOpenAI` (or `addOpenAI`) creates an `OpenAIResource` that models the OpenAI account. It registers a secret parameter for the API key that defaults to the `OPENAI_API_KEY` environment variable.
+1. Calling <ApiReference name="Aspire.Hosting.OpenAIExtensions.AddOpenAI" /> creates an `OpenAIResource` that models the OpenAI account. It registers a secret parameter for the API key that defaults to the `OPENAI_API_KEY` environment variable.
 
-1. Calling `AddModel` (or `addModel`) creates an `OpenAIModelResource` child whose connection string is composed from the parent endpoint, API key, and the model name you supply.
+1. Calling <ApiReference name="Aspire.Hosting.OpenAIExtensions.AddModel" /> creates an `OpenAIModelResource` child whose connection string is composed from the parent endpoint, API key, and the model name you supply.
 
 1. The AppHost reference call configures a connection in the consuming project named after the referenced model resource, such as `chat` in the preceding example. Multiple models can share the single API key and endpoint from the parent resource.
 
@@ -180,7 +181,7 @@ aspire secret set Parameters:openai-openai-apikey sk-your-api-key
 
 ## Use custom API key parameter
 
-Replace the default parameter by creating your own secret parameter and passing it to `WithApiKey` (or `withApiKey`) on the parent:
+Replace the default parameter by creating your own secret parameter and passing it to <ApiReference name="Aspire.Hosting.OpenAIExtensions.WithApiKey" /> on the parent:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -225,7 +226,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add a custom endpoint
 
-Override the default `https://api.openai.com/v1` endpoint to use a proxy, an Azure OpenAI endpoint, or any OpenAI-compatible gateway. Call `WithEndpoint` (or `withEndpoint`) on the parent resource:
+Override the default `https://api.openai.com/v1` endpoint to use a proxy, an Azure OpenAI endpoint, or any OpenAI-compatible gateway. Call <ApiReference name="Aspire.Hosting.OpenAIExtensions.WithEndpoint" /> on the parent resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/caching/garnet/garnet-connect.mdx b/src/frontend/src/content/docs/integrations/caching/garnet/garnet-connect.mdx
index 359539b485..815cc226f2 100644
--- a/src/frontend/src/content/docs/integrations/caching/garnet/garnet-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/garnet/garnet-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import garnetIcon from '@assets/icons/garnet-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={garnetIcon}
@@ -62,7 +63,7 @@ This is the **recommended approach** because Aspire manages the resource lifecyc
 
 When your AppHost uses `builder.AddConnectionString("cache")` to reference an existing, pre-configured Garnet instance outside Aspire's control, only a **single connection string** environment variable is injected:
 
-- `ConnectionStrings__cache` = the full connection string provided to `AddConnectionString`
+- `ConnectionStrings__cache` = the full connection string provided to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />
 
 With this approach, there are **no individual property variables** (`CACHE_HOST`, `CACHE_PORT`, etc.). Consuming apps must parse the connection string themselves or use client libraries that accept a connection string directly.
 
diff --git a/src/frontend/src/content/docs/integrations/caching/garnet/garnet-host.mdx b/src/frontend/src/content/docs/integrations/caching/garnet/garnet-host.mdx
index f4656b6fe3..1dfe7d66d3 100644
--- a/src/frontend/src/content/docs/integrations/caching/garnet/garnet-host.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/garnet/garnet-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import garnetIcon from '@assets/icons/garnet-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={garnetIcon}
@@ -156,7 +157,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The data volume is used to persist Garnet data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Garnet container, and when a `name` parameter isn't provided, the name is generated at random. Calling `WithDataVolume` (or `withDataVolume`) also enables Garnet persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-garnet-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
+The data volume is used to persist Garnet data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Garnet container, and when a `name` parameter isn't provided, the name is generated at random. Calling <ApiReference name="Aspire.Hosting.GarnetBuilderExtensions.WithDataVolume" /> also enables Garnet persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-garnet-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
 
 ## Add Garnet resource with data bind mount
 
@@ -203,7 +204,7 @@ Data bind mounts rely on the host machine's filesystem to persist Garnet data ac
 
 ## Add Garnet resource with persistence
 
-To configure Garnet snapshot persistence explicitly, call `WithPersistence` (or `withPersistence`) alongside a data volume or bind mount:
+To configure Garnet snapshot persistence explicitly, call <ApiReference name="Aspire.Hosting.GarnetBuilderExtensions.WithPersistence" /> alongside a data volume or bind mount:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -334,7 +335,7 @@ await builder.build().run();
 
 ## Connect to an existing Garnet instance
 
-To reference an externally managed Garnet instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed Garnet instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-get-started.mdx b/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-get-started.mdx
index ab82c03537..bff4d76507 100644
--- a/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand why you use the Aspire Redis distributed caching integra
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import redisIcon from '@assets/icons/redis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={redisIcon}
@@ -57,7 +58,7 @@ Getting there is a two-step process: model the Redis resource in your AppHost, t
 
 1. ### Model Redis in your AppHost
 
-    Add the Redis hosting integration to your AppHost, declare a Redis resource, and reference it from the apps that need distributed caching. The [Redis distributed caching AppHost](/integrations/caching/redis-distributed/redis-distributed-host/) article covers the installation and the basic `AddRedis` call. For the full AppHost API surface — data volumes, persistence, Redis Insight, Redis Commander, parameters, and more — see the [Redis Hosting integration](/integrations/caching/redis/redis-host/) reference.
+    Add the Redis hosting integration to your AppHost, declare a Redis resource, and reference it from the apps that need distributed caching. The [Redis distributed caching AppHost](/integrations/caching/redis-distributed/redis-distributed-host/) article covers the installation and the basic <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> call. For the full AppHost API surface — data volumes, persistence, Redis Insight, Redis Commander, parameters, and more — see the [Redis Hosting integration](/integrations/caching/redis/redis-host/) reference.
 
     <LinkButton
         variant='secondary'
diff --git a/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-host.mdx b/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-host.mdx
index 8f24a4a4db..5455ff1357 100644
--- a/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-host.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/redis-distributed/redis-distributed-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import redisIcon from '@assets/icons/redis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={redisIcon}
@@ -121,11 +122,11 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 The Redis distributed caching integration shares the Redis hosting integration with the rest of the Redis ecosystem. For all available AppHost APIs, see the [Redis Hosting integration](/integrations/caching/redis/redis-host/) reference, which covers:
 
-- `WithDataVolume` — persist Redis data outside the container lifecycle.
-- `WithDataBindMount` — bind-mount a host directory into the container.
-- `WithPersistence` — configure snapshotting interval and key-change threshold.
-- `WithRedisInsight` / `WithRedisCommander` — attach management UIs.
-- `AddParameter` for explicit port and password — override auto-generated values.
+- <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithDataVolume" parameterTypes={['Aspire.Hosting.ApplicationModel.IResourceBuilder<Aspire.Hosting.ApplicationModel.RedisResource>', 'string?', 'bool']} /> — persist Redis data outside the container lifecycle.
+- <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithDataBindMount" parameterTypes={['Aspire.Hosting.ApplicationModel.IResourceBuilder<Aspire.Hosting.ApplicationModel.RedisResource>', 'string', 'bool']} /> — bind-mount a host directory into the container.
+- <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithPersistence" /> — configure snapshotting interval and key-change threshold.
+- <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithRedisInsight" /> / <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithRedisCommander" /> — attach management UIs.
+- <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> for explicit port and password — override auto-generated values.
 - Custom environment variables — map connection properties to app-specific variable names.
 - `AsExisting` — connect to an externally managed Redis instance instead of starting a container.
 - Hosting health checks — automatically verify the Redis container is reachable.
diff --git a/src/frontend/src/content/docs/integrations/caching/redis-extensions.mdx b/src/frontend/src/content/docs/integrations/caching/redis-extensions.mdx
index 63ab629f7a..0e3de4ddb2 100644
--- a/src/frontend/src/content/docs/integrations/caching/redis-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/redis-extensions.mdx
@@ -8,6 +8,7 @@ import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import redisIcon from '@assets/icons/redis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -61,7 +62,7 @@ This updates your `aspire.config.json` with the Redis extensions package:
 
 ### DbGate management UI
 
-To add the DbGate management UI, decorate the official Redis resource with `WithDbGate` / `withDbGate`:
+To add the DbGate management UI, decorate the official Redis resource with <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithDbGate" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -105,7 +106,7 @@ This adds a new DbGate resource to the app host which is available from the Aspi
 
 ### dbx management UI
 
-[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Decorate the Redis resource with `WithDbx` / `withDbx` to add it:
+[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Decorate the Redis resource with <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithDbx" /> to add it:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/caching/redis/redis-connect.mdx b/src/frontend/src/content/docs/integrations/caching/redis/redis-connect.mdx
index df72e44146..df4d39dab8 100644
--- a/src/frontend/src/content/docs/integrations/caching/redis/redis-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/redis/redis-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import redisIcon from '@assets/icons/redis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={redisIcon}
@@ -62,7 +63,7 @@ This is the **recommended approach** because Aspire manages the resource lifecyc
 
 When your AppHost uses `builder.AddConnectionString("cache")` to reference an existing, pre-configured Redis instance outside Aspire's control, only a **single connection string** environment variable is injected:
 
-- `ConnectionStrings__cache` = the full connection string provided to `AddConnectionString`
+- `ConnectionStrings__cache` = the full connection string provided to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />
 
 With this approach, there are **no individual property variables** (`CACHE_HOST`, `CACHE_PORT`, etc.). Consuming apps must parse the connection string themselves or use client libraries that accept a connection string directly.
 
diff --git a/src/frontend/src/content/docs/integrations/caching/redis/redis-host.mdx b/src/frontend/src/content/docs/integrations/caching/redis/redis-host.mdx
index 4b18bffd63..5968e3d978 100644
--- a/src/frontend/src/content/docs/integrations/caching/redis/redis-host.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/redis/redis-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import redisIcon from '@assets/icons/redis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={redisIcon}
@@ -156,7 +157,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The data volume is used to persist Redis data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Redis container, and when a `name` parameter isn't provided, the name is generated at random. Calling `WithDataVolume` (or `withDataVolume`) also enables Redis persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-redis-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
+The data volume is used to persist Redis data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Redis container, and when a `name` parameter isn't provided, the name is generated at random. Calling <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithDataVolume" parameterTypes={['Aspire.Hosting.ApplicationModel.IResourceBuilder<Aspire.Hosting.ApplicationModel.RedisResource>', 'string?', 'bool']} /> also enables Redis persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-redis-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
 
 ## Add Redis resource with data bind mount
 
@@ -203,7 +204,7 @@ Data bind mounts rely on the host machine's filesystem to persist Redis data acr
 
 ## Add Redis resource with persistence
 
-To configure Redis snapshot persistence explicitly, call `WithPersistence` (or `withPersistence`) alongside a data volume or bind mount:
+To configure Redis snapshot persistence explicitly, call <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithPersistence" /> alongside a data volume or bind mount:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -511,7 +512,7 @@ await builder.build().run();
 
 ## Connect to an existing Redis instance
 
-To reference an externally managed Redis instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed Redis instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -549,7 +550,7 @@ With `AddConnectionString` and `addConnectionString`, Aspire resolves `cache` fr
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the Redis resource to enable a **REPL** command that opens `redis-cli` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithRepl" /> to the Redis resource to enable a **REPL** command that opens `redis-cli` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/caching/valkey/valkey-connect.mdx b/src/frontend/src/content/docs/integrations/caching/valkey/valkey-connect.mdx
index d729010bdb..7b2d2657a4 100644
--- a/src/frontend/src/content/docs/integrations/caching/valkey/valkey-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/valkey/valkey-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import valkeyIcon from '@assets/icons/valkey-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={valkeyIcon}
@@ -62,7 +63,7 @@ This is the **recommended approach** because Aspire manages the resource lifecyc
 
 When your AppHost uses `builder.AddConnectionString("cache")` to reference an existing, pre-configured Valkey instance outside Aspire's control, only a **single connection string** environment variable is injected:
 
-- `ConnectionStrings__cache` = the full connection string provided to `AddConnectionString`
+- `ConnectionStrings__cache` = the full connection string provided to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />
 
 With this approach, there are **no individual property variables** (`CACHE_HOST`, `CACHE_PORT`, etc.). Consuming apps must parse the connection string themselves or use client libraries that accept a connection string directly.
 
diff --git a/src/frontend/src/content/docs/integrations/caching/valkey/valkey-host.mdx b/src/frontend/src/content/docs/integrations/caching/valkey/valkey-host.mdx
index f3ee6ce8b2..e53cab6cd6 100644
--- a/src/frontend/src/content/docs/integrations/caching/valkey/valkey-host.mdx
+++ b/src/frontend/src/content/docs/integrations/caching/valkey/valkey-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import valkeyIcon from '@assets/icons/valkey-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={valkeyIcon}
@@ -156,7 +157,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The data volume is used to persist Valkey data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Valkey container, and when a `name` parameter isn't provided, the name is generated at random. Calling `WithDataVolume` (or `withDataVolume`) also enables Valkey persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-valkey-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
+The data volume is used to persist Valkey data outside the lifecycle of its container. The data volume is mounted at the `/data` path in the Valkey container, and when a `name` parameter isn't provided, the name is generated at random. Calling <ApiReference name="Aspire.Hosting.ValkeyBuilderExtensions.WithDataVolume" /> also enables Valkey persistence so the in-memory state survives container restarts. For more information on data volumes and details on why they're preferred over [bind mounts](#add-valkey-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
 
 ## Add Valkey resource with data bind mount
 
@@ -203,7 +204,7 @@ Data bind mounts rely on the host machine's filesystem to persist Valkey data ac
 
 ## Add Valkey resource with persistence
 
-To configure Valkey snapshot persistence explicitly, call `WithPersistence` (or `withPersistence`) alongside a data volume or bind mount:
+To configure Valkey snapshot persistence explicitly, call <ApiReference name="Aspire.Hosting.ValkeyBuilderExtensions.WithPersistence" /> alongside a data volume or bind mount:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -331,7 +332,7 @@ await builder.build().run();
 
 ## Connect to an existing Valkey instance
 
-To reference an externally managed Valkey instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed Valkey instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -369,7 +370,7 @@ With `AddConnectionString` and `addConnectionString`, Aspire resolves `cache` fr
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the Valkey resource to enable a **REPL** command that opens `valkey-cli` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.ValkeyBuilderExtensions.WithRepl" /> to the Valkey resource to enable a **REPL** command that opens `valkey-cli` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx
index 91d997c1eb..09e2c05caa 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/aks/index.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import LearnMore from '@components/LearnMore.astro';
 import kubernetesIcon from '@assets/icons/kubernetes.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={kubernetesIcon}
@@ -30,7 +31,7 @@ To get started with the Aspire AKS hosting integration, install the [📦 Aspire
 
 ## Add AKS environment
 
-After installing the package, add an AKS environment to your AppHost using `AddAzureKubernetesEnvironment`:
+After installing the package, add an AKS environment to your AppHost using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -66,7 +67,7 @@ When an AKS environment is present, all compute resources are automatically depl
 
 ## Configure the system node pool
 
-Customize the system node pool VM size and scaling using `WithSystemNodePool`:
+Customize the system node pool VM size and scaling using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithSystemNodePool" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -85,7 +86,7 @@ await aks.withSystemNodePool('Standard_D4s_v5', 1, 5);
 
 ## Add node pools
 
-Add additional node pools for workload isolation, GPU workloads, or specialized hardware requirements using `AddNodePool`:
+Add additional node pools for workload isolation, GPU workloads, or specialized hardware requirements using <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddNodePool" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -114,7 +115,7 @@ await worker.withNodePool(gpuPool);
   Persistent volume APIs are experimental. In C#, suppress the `ASPIRECOMPUTE002` diagnostic to use them.
 </Aside>
 
-Call `AddPersistentVolume` directly on the AKS environment to model durable storage without reaching through to the underlying Kubernetes integration. The call forwards to the AKS environment's Kubernetes publisher, so the same configuration methods and workload-binding APIs described in [Persistent volumes on Kubernetes](/deployment/kubernetes/persistent-volumes/) apply:
+Call <ApiReference name="Aspire.Hosting.AzureKubernetesPersistentVolumeExtensions.AddPersistentVolume" /> directly on the AKS environment to model durable storage without reaching through to the underlying Kubernetes integration. The call forwards to the AKS environment's Kubernetes publisher, so the same configuration methods and workload-binding APIs described in [Persistent volumes on Kubernetes](/deployment/kubernetes/persistent-volumes/) apply:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-connect.mdx
index c6d56e54c2..ef97e7cfe8 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-connect.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import aiFoundryIcon from '@assets/icons/azure-ai-foundry-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={aiFoundryIcon}
@@ -49,7 +50,7 @@ CHAT_AIINFERENCEURI=https://my-foundry.services.ai.azure.com/models
 ```
 
 <Aside type="note">
-  By default, `AddFoundry(...)` provisions the Foundry account with `disableLocalAuth: true` and creates the role assignments consuming apps need, so apps authenticate via managed identity. Because Aspire only ever surfaces `Key` for Foundry Local, the examples below default to token-based authentication (`DefaultAzureCredential`) for every scenario except Foundry Local.
+  By default, <ApiReference name="Aspire.Hosting.FoundryExtensions.AddFoundry" /> provisions the Foundry account with `disableLocalAuth: true` and creates the role assignments consuming apps need, so apps authenticate via managed identity. Because Aspire only ever surfaces `Key` for Foundry Local, the examples below default to token-based authentication (`DefaultAzureCredential`) for every scenario except Foundry Local.
 </Aside>
 
 ### Foundry deployment resource
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
index e6c5045914..0b6397a0a5 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
@@ -7,6 +7,7 @@ prev: false
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import aiFoundryIcon from '@assets/icons/azure-ai-foundry-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={aiFoundryIcon}
@@ -25,9 +26,9 @@ Adding Azure AI Foundry through Aspire — rather than hard-coding endpoints and
 
 - **Centralized credential management.** Endpoint and API key are stored once in the AppHost and injected into each consuming app automatically.
 - **Model deployments as first-class resources.** Each deployment composes a connection string from the parent Foundry endpoint, API key, and model name, giving consuming apps a single named connection.
-- **Foundry Projects for agents.** Model Foundry projects with `AddProject`, attach model deployments, web-search tools, and hosted or prompt agents, and reference them from consuming services.
+- **Foundry Projects for agents.** Model Foundry projects with <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />, attach model deployments, web-search tools, and hosted or prompt agents, and reference them from consuming services.
 - **Consistent connection info across languages.** Once you reference a deployment from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
-- **Foundry Local for offline development.** Use `RunAsFoundryLocal()` to run models locally without an Azure subscription.
+- **Foundry Local for offline development.** Use <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> to run models locally without an Azure subscription.
 - **An upgrade path to the cloud.** The same AppHost model provisions Azure Cognitive Services accounts and deployments when you publish.
 
 ## How the pieces fit together
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
index 73218eb655..e7a3836dac 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host.mdx
@@ -12,6 +12,7 @@ import agentSendMessage from '@assets/integrations/cloud/azure/azure-ai-foundry/
 import agentSendMessageLight from '@assets/integrations/cloud/azure/azure-ai-foundry/agent-send-message-light.png';
 import agentResponsesResult from '@assets/integrations/cloud/azure/azure-ai-foundry/agent-responses-result.png';
 import agentResponsesResultLight from '@assets/integrations/cloud/azure/azure-ai-foundry/agent-responses-result-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={aiFoundryIcon}
@@ -56,7 +57,7 @@ Or, choose a manual installation approach:
   This integration was previously shipped as `Aspire.Hosting.Azure.AIFoundry`.
   When upgrading from Aspire 13.1 or earlier, replace that package with
   `Aspire.Hosting.Foundry` and rename `AddAzureAIFoundry(...)` to
-  `AddFoundry(...)`. Resource and model types moved from
+  <ApiReference name="Aspire.Hosting.FoundryExtensions.AddFoundry" />. Resource and model types moved from
   `Aspire.Hosting.Azure` to `Aspire.Hosting.Foundry`; add
   `using Aspire.Hosting.Foundry;` for direct type references and remove
   `using Aspire.Hosting.Azure;` only if your code no longer uses other types
@@ -129,10 +130,10 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The preceding code adds an Azure AI Foundry resource named `foundry` to the AppHost project. The `WithReference` method passes the connection information to the `ExampleProject` project.
+The preceding code adds an Azure AI Foundry resource named `foundry` to the AppHost project. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method passes the connection information to the `ExampleProject` project.
 
 <Aside type="caution">
-  When you call `AddFoundry`, it implicitly calls `AddAzureProvisioning`—which
+  When you call `AddFoundry`, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which
   adds support for generating Azure resources dynamically during app startup.
   The app must configure the appropriate subscription and location. For more
   information, see [Local provisioning:
@@ -141,7 +142,7 @@ The preceding code adds an Azure AI Foundry resource named `foundry` to the AppH
 
 ## Add a Foundry deployment resource
 
-To add a Foundry deployment resource, call the `AddDeployment` method with one of the generated `FoundryModel` entries:
+To add a Foundry deployment resource, call the <ApiReference name="Aspire.Hosting.FoundryExtensions.AddDeployment" /> method with one of the generated `FoundryModel` entries:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -240,7 +241,7 @@ await builder.build().run();
 
 ## Configure deployment properties
 
-You can customize deployment properties using the `WithProperties` method:
+You can customize deployment properties using the <ApiReference name="Aspire.Hosting.FoundryExtensions.WithProperties" /> method:
 
 ```csharp
 var chat = foundry.AddDeployment("chat", FoundryModel.OpenAI.Gpt5Mini)
@@ -255,7 +256,7 @@ The preceding code sets the SKU name to `Standard` and capacity to `10` for the
 
 ## Add a Foundry project
 
-Use the `AddProject` method to create an Azure AI Foundry project for agents, project-scoped connections, and related Azure resources:
+Use the <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddProject" /> method to create an Azure AI Foundry project for agents, project-scoped connections, and related Azure resources:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -305,7 +306,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The preceding code creates a Foundry project and adds a deployment through `AddModelDeployment`. When you call `WithReference(project)`, Aspire injects the standard connection string and project-specific connection properties such as the project endpoint and Application Insights connection string into the consuming resource.
+The preceding code creates a Foundry project and adds a deployment through <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddModelDeployment" />. When you call `WithReference(project)`, Aspire injects the standard connection string and project-specific connection properties such as the project endpoint and Application Insights connection string into the consuming resource.
 
 ### Configure a Foundry project
 
@@ -351,11 +352,11 @@ await foundry
 </TabItem>
 </Tabs>
 
-`AddProject` creates a default Azure Container Registry for hosted agents only in publish mode (when deploying to Azure). In local run mode, no default registry is created. Use `WithContainerRegistry` when you want to point the project at a specific registry.
+`AddProject` creates a default Azure Container Registry for hosted agents only in publish mode (when deploying to Azure). In local run mode, no default registry is created. Use <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" /> when you want to point the project at a specific registry.
 
 ## Add a Toolbox
 
-A [Toolbox](https://learn.microsoft.com/azure/foundry/agents/how-to/tools/toolbox) is a Foundry data-plane resource that bundles reusable tools behind a single MCP endpoint. Toolboxes don't have an ARM or Bicep representation — Aspire manages them directly through the Foundry data-plane API. Use `AddToolbox` on a Foundry project to declare one:
+A [Toolbox](https://learn.microsoft.com/azure/foundry/agents/how-to/tools/toolbox) is a Foundry data-plane resource that bundles reusable tools behind a single MCP endpoint. Toolboxes don't have an ARM or Bicep representation — Aspire manages them directly through the Foundry data-plane API. Use <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.AddToolbox" /> on a Foundry project to declare one:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
@@ -432,14 +433,14 @@ builder.Build().Run();
 
 Parameter details:
 
-The identity running `aspire run` or `aspire deploy` needs the **Foundry User** role on the project to manage Toolbox versions. Deployed compute resources that reference the Toolbox receive this role on the project automatically. The Search index named `docs` must already exist and contain data: neither `AddAzureSearch` nor `WithAISearchTool` creates or populates it. Toolbox availability depends on the Foundry service preview and its supported regions.
+The identity running `aspire run` or `aspire deploy` needs the **Foundry User** role on the project to manage Toolbox versions. Deployed compute resources that reference the Toolbox receive this role on the project automatically. The Search index named `docs` must already exist and contain data: neither <ApiReference name="Aspire.Hosting.AzureSearchExtensions.AddAzureSearch" /> nor <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.WithAISearchTool" /> creates or populates it. Toolbox availability depends on the Foundry service preview and its supported regions.
 
 | API | Parameter | Description |
 | --- | --- | --- |
 | `AddToolbox(...)` | `name` | The Aspire resource name and the Toolbox name. |
-| `WithDescription(...)` | `description` | A description persisted with each Toolbox version. |
-| `WithWebSearchTool(...)` | `name`, `description` | Adds a web search tool definition to the Toolbox. |
-| `WithMcpTool(...)` | `name`, `endpoint`, `options` | Adds an MCP tool definition. `endpoint` accepts a string URI, an `EndpointReference`, or a `ReferenceExpression` for composed URLs. `options` configures the MCP server label, description, and approval policy. |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.WithDescription" /> | `description` | A description persisted with each Toolbox version. |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.WithWebSearchTool" /> | `name`, `description` | Adds a web search tool definition to the Toolbox. |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.WithMcpTool" /> | `name`, `endpoint`, `options` | Adds an MCP tool definition. `endpoint` accepts a string URI, an `EndpointReference`, or a `ReferenceExpression` for composed URLs. `options` configures the MCP server label, description, and approval policy. |
 | `WithAISearchTool(...)` | `name`, `search`, `indexName`, `description` | Adds an Azure AI Search tool backed by an `AddAzureSearch` resource and an existing search index. |
 
 <Aside type="caution">
@@ -460,15 +461,15 @@ Use the existing-resource methods to validate a remote Toolbox without resolving
 
 | Method | `aspire run` | `aspire deploy` |
 | --- | --- | --- |
-| `RunAsExisting()` | Validate existing | Reconcile managed |
-| `PublishAsExisting()` | Reconcile managed | Validate existing |
-| `AsExisting()` | Validate existing | Validate existing |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.RunAsExisting" /> | Validate existing | Reconcile managed |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.PublishAsExisting" /> | Reconcile managed | Validate existing |
+| <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.AsExisting" /> | Validate existing | Validate existing |
 
 These methods apply to the Toolbox resource itself. Existing mode validates the remote Toolbox, and a pinned version if supplied, without resolving local tools or promoting a version. See [Toolbox connection properties](../azure-ai-foundry-connect/#foundry-toolbox-resource) for the consumer's endpoint, authentication scope, and required request header.
 
 ## Add a hosted agent to Azure AI Foundry
 
-Use `AsHostedAgent` in C# or `asHostedAgent` in TypeScript to configure an executable or containerized app as a hosted agent in a Foundry project:
+Use <ApiReference name="Aspire.Hosting.HostedAgentResourceBuilderExtensions.AsHostedAgent" /> to configure an executable or containerized app as a hosted agent in a Foundry project:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -613,7 +614,7 @@ The defaulted `asHostedAgent` entry point and the explicit `asHostedAgentWithPro
 
 ### Add and publish a prompt agent
 
-For prompt-only scenarios, use `AddPromptAgent` on a Foundry project:
+For prompt-only scenarios, use <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddPromptAgent" /> on a Foundry project:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -680,7 +681,7 @@ Parameter details:
 | `AddPromptAgent(...)` | `model`        | The Foundry model deployment resource the prompt agent uses, such as `chat` from `project.AddModelDeployment(...)`.                                               |
 | `AddPromptAgent(...)` | `name`         | The Aspire resource name and Foundry agent name. This also drives generated environment variable prefixes, for example `web-researcher` becomes `WEB_RESEARCHER`. |
 | `AddPromptAgent(...)` | `instructions` | Optional system instructions for the prompt agent. Use this to define behavior, tool-use guidance, and response style.                                            |
-| `WithTool(...)`       | `tool`         | A Foundry tool resource created on the same Foundry project, such as `AddWebSearchTool(...)`, `AddCodeInterpreterTool(...)`, or `AddAISearchTool(...)`.           |
+| <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.WithTool" />       | `tool`         | A Foundry tool resource created on the same Foundry project, such as <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddWebSearchTool" />, <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddCodeInterpreterTool" />, or <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddAISearchTool" />.           |
 
 Prompt agents are deployed to Azure AI Foundry even during local development. Local apps call the cloud-provisioned agent through the injected project endpoint and agent name.
 
@@ -816,7 +817,7 @@ When the AppHost starts, Aspire automatically starts the Foundry Local service u
 
 This requires the `foundry` CLI to be installed and available on `PATH`. For installation instructions, see [Foundry Local get started](https://learn.microsoft.com/azure/ai-foundry/foundry-local/get-started).
 
-The `RunAsFoundryLocal` method configures the resource to use the local service. It downloads and loads the specified models locally, provides health checks for the local service, and fully manages the Foundry Local lifecycle — including start and stop — through the `foundry` CLI.
+The <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> method configures the resource to use the local service. It downloads and loads the specified models locally, provides health checks for the local service, and fully manages the Foundry Local lifecycle — including start and stop — through the `foundry` CLI.
 
 <Aside type="caution">
   Foundry Projects aren't supported when the parent Foundry resource uses
@@ -1006,7 +1007,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This enables customization of the generated Bicep by providing a fluent API to configure the Azure resources—using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This enables customization of the generated Bicep by providing a fluent API to configure the Azure resources—using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 ```csharp title="AppHost.cs"
 builder.AddFoundry("foundry")
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-inference/azure-ai-inference-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-inference/azure-ai-inference-host.mdx
index 394711b517..9f5338ce25 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-inference/azure-ai-inference-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-inference/azure-ai-inference-host.mdx
@@ -6,6 +6,7 @@ description: Register an existing Azure AI Inference endpoint in your AppHost as
 import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import aiFoundryIcon from '@assets/icons/azure-ai-foundry-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={aiFoundryIcon}
@@ -24,7 +25,7 @@ If you're new to Azure AI Inference, start with [Get started with the Azure AI I
 
 ## Add an Azure AI Inference connection
 
-Use `AddConnectionString` to register an existing Azure AI Inference endpoint with your AppHost, then reference it from any consuming app:
+Use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> to register an existing Azure AI Inference endpoint with your AppHost, then reference it from any consuming app:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-search/azure-ai-search-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-search/azure-ai-search-host.mdx
index 7c3d742cee..088b5cffae 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-search/azure-ai-search-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-search/azure-ai-search-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import searchIcon from '@assets/icons/azure-search-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={searchIcon}
@@ -107,11 +108,11 @@ await builder.build().run();
 
 <Steps>
 
-1. When Aspire adds an Azure AI Search resource, it implicitly calls `AddAzureProvisioning`, which adds support for generating Azure resources dynamically during app startup.
+1. When Aspire adds an Azure AI Search resource, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which adds support for generating Azure resources dynamically during app startup.
 
 1. The app must configure the appropriate Azure subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 
-1. The `withReference` call configures a connection in the consuming project named after the referenced search resource, such as `search` in the preceding example.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the referenced search resource, such as `search` in the preceding example.
 
 </Steps>
 
@@ -234,7 +235,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -293,7 +294,7 @@ By default, the Azure AI Search hosting integration generates role assignments f
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
 
-Role assignments are generated automatically in the provisioned Bicep. To clear the default role assignments and assign custom ones, use `ClearDefaultRoleAssignments` and then configure via `ConfigureInfrastructure`:
+Role assignments are generated automatically in the provisioned Bicep. To clear the default role assignments and assign custom ones, use <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> and then configure via `ConfigureInfrastructure`:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-configuration/azure-app-configuration-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-configuration/azure-app-configuration-host.mdx
index 1d4058dd94..70a48ee337 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-configuration/azure-app-configuration-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-configuration/azure-app-configuration-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import appConfigIcon from '@assets/icons/azure-appconfig-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={appConfigIcon}
@@ -113,8 +114,8 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureAppConfiguration` (or `addAzureAppConfiguration`), it implicitly calls
-  `AddAzureProvisioning`—which adds support for generating Azure resources
+  When you call <ApiReference name="Aspire.Hosting.AzureAppConfigurationExtensions.AddAzureAppConfiguration" />, it implicitly calls
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -182,7 +183,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources — using the `ConfigureInfrastructure` API (or `configureInfrastructure` in TypeScript). For example, you can configure the SKU, enable purge protection, add tags, and more:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources — using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API (or `configureInfrastructure` in TypeScript). For example, you can configure the SKU, enable purge protection, add tags, and more:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -239,7 +240,7 @@ There are many more configuration options available to customize the Azure App C
 
 ## Add Azure App Configuration emulator resource
 
-Microsoft provides the Azure App Configuration emulator for developers who want a local, lightweight implementation of the Azure App Configuration service to code and test against. In Aspire, you can use this emulator by calling the `RunAsEmulator` method (or `runAsEmulator`) when you add your resource:
+Microsoft provides the Azure App Configuration emulator for developers who want a local, lightweight implementation of the Azure App Configuration service to code and test against. In Aspire, you can use this emulator by calling the <ApiReference name="Aspire.Hosting.AzureAppConfigurationExtensions.RunAsEmulator" /> method (or `runAsEmulator`) when you add your resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -326,7 +327,7 @@ The preceding code configures the emulator container's endpoint to listen on por
 
 #### Configure Azure App Configuration emulator with persistent lifetime
 
-To configure the emulator container with a persistent lifetime, call the `WithLifetime` method (or `withLifetime`) on the emulator container resource and pass `ContainerLifetime.Persistent`:
+To configure the emulator container with a persistent lifetime, call the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> method (or `withLifetime`) on the emulator container resource and pass `ContainerLifetime.Persistent`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -366,7 +367,7 @@ const appConfig = await builder.addAzureAppConfiguration("config")
 
 #### Configure Azure App Configuration emulator with data volume
 
-By default, the Azure App Configuration emulator doesn't persist data between container restarts. To enable persistent storage using a Docker volume, call the `WithDataVolume` method (or `withDataVolume`) on the emulator resource:
+By default, the Azure App Configuration emulator doesn't persist data between container restarts. To enable persistent storage using a Docker volume, call the <ApiReference name="Aspire.Hosting.AzureAppConfigurationExtensions.WithDataVolume" /> method (or `withDataVolume`) on the emulator resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -408,7 +409,7 @@ The data volume is used to persist the emulator data outside the lifecycle of it
 
 #### Configure Azure App Configuration emulator with data bind mount
 
-To persist emulator data to a specific directory on your host machine, call the `WithDataBindMount` method (or `withDataBindMount`). This is useful when you want direct access to the data files on your host system:
+To persist emulator data to a specific directory on your host machine, call the <ApiReference name="Aspire.Hosting.AzureAppConfigurationExtensions.WithDataBindMount" /> method (or `withDataBindMount`). This is useful when you want direct access to the data files on your host system:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -454,7 +455,7 @@ Data bind mounts rely on the host machine's filesystem to persist the emulator d
 
 ## Use existing Azure App Configuration resource
 
-You might have an existing Azure App Configuration store that you want to connect to. Call the `AsExisting` method (or `asExisting`) with the config store name and resource group parameters to connect to an existing store:
+You might have an existing Azure App Configuration store that you want to connect to. Call the <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> method (or `asExisting`) with the config store name and resource group parameters to connect to an existing store:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -499,7 +500,7 @@ For more information, see [Use existing Azure resources](/integrations/cloud/azu
 
 ## Connect to existing Azure App Configuration store
 
-An alternative approach to using the `AsExisting` API enables the addition of a connection string instead, where the AppHost uses configuration to resolve the connection information. To add a connection to an existing Azure App Configuration store, call the `AddConnectionString` method:
+An alternative approach to using the `AsExisting` API enables the addition of a connection string instead, where the AppHost uses configuration to resolve the connection information. To add a connection to an existing Azure App Configuration store, call the <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-get-started.mdx
index ca59ca23c9..1b78e19476 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-get-started.mdx
@@ -7,6 +7,7 @@ prev: false
 import { Image } from 'astro:assets';
 import { Badge, LinkButton, Steps } from '@astrojs/starlight/components';
 import appServiceIcon from '@assets/icons/azure-app-services.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={appServiceIcon}
@@ -27,7 +28,7 @@ Adding an Azure App Service environment through Aspire — rather than configuri
 
 - **Zero extra local setup.** During development your projects run locally as usual. The App Service environment is only provisioned when you publish.
 - **Automatic deployment targeting.** Once an App Service environment is in your AppHost, all supported compute resources (project resources and Dockerfile-backed containers) are deployed to it automatically — no extra wiring required.
-- **Optional customization.** Use `PublishAsAzureAppServiceWebsite` (C#) or `publishAsAzureAppServiceWebsite` (TypeScript) only when you need to customize the generated website — for example to add application settings, tags, or deployment slots.
+- **Optional customization.** Use <ApiReference name="Aspire.Hosting.AzureAppServiceComputeResourceExtensions.PublishAsAzureAppServiceWebsite" /> only when you need to customize the generated website — for example to add application settings, tags, or deployment slots.
 - **Deployment slots.** Stage changes safely by configuring a named deployment slot for the environment so that new deployments land in staging before you swap them to production.
 - **Bicep-backed provisioning.** The hosting integration generates all required Azure resources — App Service Plan, Azure Container Registry, and managed identity — from the same C# or TypeScript AppHost code. No hand-authored Bicep required.
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-host.mdx
index 4d36e9ea71..c79c2f70da 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-app-service/azure-app-service-host.mdx
@@ -11,6 +11,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import LearnMore from '@components/LearnMore.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import appServiceIcon from '@assets/icons/azure-app-services.svg';
@@ -120,7 +121,7 @@ await builder.build().run();
 
 <Steps>
 
-1. When you call `addAzureAppServiceEnvironment` (or `AddAzureAppServiceEnvironment` in C#), Aspire implicitly enables Azure provisioning for the application.
+1. When you call <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.AddAzureAppServiceEnvironment" />, Aspire implicitly enables Azure provisioning for the application.
 
 2. All project resources and Dockerfile-backed containers in the AppHost are **automatically targeted** to the App Service environment when it's present — no explicit wiring is required.
 
@@ -130,7 +131,7 @@ await builder.build().run();
 
 <Aside type="caution">
   Calling `AddAzureAppServiceEnvironment` (or `addAzureAppServiceEnvironment` in
-  TypeScript) implicitly calls `AddAzureProvisioning`, which adds support for
+  TypeScript) implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which adds support for
   generating Azure resources dynamically during app startup. The app must
   configure an Azure subscription and location. For more information, see [Local
   provisioning:
@@ -207,7 +208,7 @@ For more information on treating Azure resources as existing resources, see [Use
 
 ## Customize App Service websites
 
-By default, Aspire generates an App Service website for each eligible resource without additional configuration. Use `PublishAsAzureAppServiceWebsite` (C#) or `publishAsAzureAppServiceWebsite` (TypeScript) when you need to customize the generated website — for example to add application settings or tags:
+By default, Aspire generates an App Service website for each eligible resource without additional configuration. Use <ApiReference name="Aspire.Hosting.AzureAppServiceComputeResourceExtensions.PublishAsAzureAppServiceWebsite" /> when you need to customize the generated website — for example to add application settings or tags:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -275,7 +276,7 @@ The preceding code:
 
 ## Deployment slots
 
-[Deployment slots](https://learn.microsoft.com/azure/app-service/deploy-staging-slots) let you deploy your app to a staging environment for testing before swapping it into production. The `WithDeploymentSlot` extension method (or `withDeploymentSlot` in TypeScript) configures a deployment slot for the App Service environment:
+[Deployment slots](https://learn.microsoft.com/azure/app-service/deploy-staging-slots) let you deploy your app to a staging environment for testing before swapping it into production. The <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.WithDeploymentSlot" /> extension method (or `withDeploymentSlot` in TypeScript) configures a deployment slot for the App Service environment:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -388,7 +389,7 @@ With this configuration, provide a value for the `deploymentSlot` parameter when
   slot when needed.
 </Aside>
 
-When you customize App Service resources using `PublishAsAzureAppServiceWebsite` (or `publishAsAzureAppServiceWebsite`) or `ConfigureInfrastructure`, those customizations apply to the production slot by default. Apply them separately to each slot when needed using the `configureSlot` option:
+When you customize App Service resources using `PublishAsAzureAppServiceWebsite` (or `publishAsAzureAppServiceWebsite`) or <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />, those customizations apply to the production slot by default. Apply them separately to each slot when needed using the `configureSlot` option:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -421,7 +422,7 @@ await api.publishAsAzureAppServiceWebsite({
 
 ## Regional virtual network integration
 
-To configure [regional virtual network integration](https://learn.microsoft.com/azure/app-service/overview-vnet-integration) for the websites in an App Service environment, add the [📦 Aspire.Hosting.Azure.Network](https://www.nuget.org/packages/Aspire.Hosting.Azure.Network) integration and delegate a subnet to the environment with `WithDelegatedSubnet` (or `withDelegatedSubnet` in TypeScript):
+To configure [regional virtual network integration](https://learn.microsoft.com/azure/app-service/overview-vnet-integration) for the websites in an App Service environment, add the [📦 Aspire.Hosting.Azure.Network](https://www.nuget.org/packages/Aspire.Hosting.Azure.Network) integration and delegate a subnet to the environment with <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithDelegatedSubnet" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-application-insights.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-application-insights.mdx
index 841b988c6a..6b589b4942 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-application-insights.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-application-insights.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import appInsightsIcon from '@assets/icons/azure-appinsights-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={appInsightsIcon}
@@ -78,7 +79,7 @@ This updates your `aspire.config.json` with the Azure Application Insights hosti
 
 ### Add Azure Application Insights resource
 
-Once you've installed the hosting integration in your AppHost project, call `AddAzureApplicationInsights` (or `addAzureApplicationInsights`) to add and return an Azure Application Insights resource builder:
+Once you've installed the hosting integration in your AppHost project, call <ApiReference name="Aspire.Hosting.AzureApplicationInsightsExtensions.AddAzureApplicationInsights" /> to add and return an Azure Application Insights resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -117,13 +118,13 @@ await builder.build().run();
 
 1. A Log Analytics workspace is automatically created to store the telemetry data.
 
-1. The `WithReference` (or `withReference`) call configures a connection in the consuming project, making the Application Insights connection string available as the `APPLICATIONINSIGHTS_CONNECTION_STRING` environment variable.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project, making the Application Insights connection string available as the `APPLICATIONINSIGHTS_CONNECTION_STRING` environment variable.
 
 </Steps>
 
 <Aside type="caution">
   When you call `AddAzureApplicationInsights` (or `addAzureApplicationInsights`), it implicitly calls
-  `AddAzureProvisioning` — which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -257,7 +258,7 @@ The generated Bicep is a starting point that reflects the provisioning infrastru
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-connect.mdx
index c985bbbbc3..50d7ae89d3 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import cacheRedisIcon from '@assets/icons/azure-cacheredis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={cacheRedisIcon}
@@ -30,8 +31,8 @@ The Azure Managed Redis resource exposes the following connection properties:
 | Property Name | Description |
 | ------------- | ----------- |
 | `Host`        | The hostname of the Azure Cache for Redis endpoint |
-| `Port`        | The port number. Uses the default Azure Cache for Redis TLS port when connecting to Azure; uses the configured container port when running locally via `RunAsContainer` |
-| `Password`    | The access key. Empty when using Entra ID authentication; populated when using `WithAccessKeyAuthentication` or running as a local container |
+| `Port`        | The port number. Uses the default Azure Cache for Redis TLS port when connecting to Azure; uses the configured container port when running locally via <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.RunAsContainer" /> |
+| `Password`    | The access key. Empty when using Entra ID authentication; populated when using <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.WithAccessKeyAuthentication" /> or running as a local container |
 | `Uri`         | The connection URI. In Azure mode: `redis://{Host}`; when running as a local container: `redis://[:{Password}@]{Host}:{Port}` |
 
 **Example connection strings:**
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-host.mdx
index 7cb1237b98..81582acbe3 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cache-redis/azure-cache-redis-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import cacheRedisIcon from '@assets/icons/azure-cacheredis-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={cacheRedisIcon}
@@ -111,12 +112,12 @@ await builder.build().run();
 
 1. By default, Aspire configures the resource to use Microsoft Entra ID (role-based access) authentication. No password is stored in the connection string. For more information, see [Configure access key authentication](#configure-access-key-authentication).
 
-1. The `WithReference` (or `withReference`) call configures a connection in the consuming project named after the resource, such as `cache` in the preceding example.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the resource, such as `cache` in the preceding example.
 
 </Steps>
 
 <Aside type="caution">
-  When you call `AddAzureManagedRedis` (or `addAzureManagedRedis`), it implicitly calls `AddAzureProvisioning` — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+  When you call <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.AddAzureManagedRedis" />, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 <Aside type="note">
@@ -127,7 +128,7 @@ await builder.build().run();
 
 The Azure Cache for Redis hosting integration supports running a local Redis container during development. This lets you develop and test your app locally without provisioning an Azure resource or connecting to an existing Azure Cache for Redis instance.
 
-To run the resource as a container, chain a call to `RunAsContainer` (or `runAsContainer`):
+To run the resource as a container, chain a call to <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.RunAsContainer" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -170,7 +171,7 @@ The `RunAsContainer` method accepts an optional delegate that lets you customize
 
 ## Connect to an existing Azure Cache for Redis instance
 
-If you already have an Azure Cache for Redis instance you want to use, call `AsExisting` (or `asExisting`) to annotate that the resource already exists rather than being provisioned:
+If you already have an Azure Cache for Redis instance you want to use, call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that the resource already exists rather than being provisioned:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -215,7 +216,7 @@ For more information on treating Azure resources as existing resources, see [Use
 
 ## Configure access key authentication
 
-By default, the Azure Managed Redis resource uses Microsoft Entra ID authentication. To switch to access key authentication (not recommended for production), call `WithAccessKeyAuthentication` (or `withAccessKeyAuthentication`):
+By default, the Azure Managed Redis resource uses Microsoft Entra ID authentication. To switch to access key authentication (not recommended for production), call <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.WithAccessKeyAuthentication" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -325,7 +326,7 @@ The generated Bicep provisions the Azure Cache for Redis instance and creates an
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables Bicep customization through the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables Bicep customization through the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-connector-namespace.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-connector-namespace.mdx
index 822e77a354..f29360701c 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-connector-namespace.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-connector-namespace.mdx
@@ -5,6 +5,7 @@ description: Model Azure Connector Namespace connections, managed MCP servers, o
 
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Azure Connector Namespace connects applications to external services such as Office 365 and SharePoint. Aspire models the namespace, authenticated connections, managed MCP server configurations, and access policies together.
 
@@ -118,7 +119,7 @@ After provisioning, open `https://connectors.azure.com/<subscription-id>/<resour
 
 Keep the two authorization surfaces separate:
 
-- **Connection policies** grant a specified Entra principal access to the connection. Use `WithIdentityAccessPolicy` / `withIdentityAccessPolicy` for a user-assigned managed identity without hard-coding its principal ID.
+- **Connection policies** grant a specified Entra principal access to the connection. Use <ApiReference name="Aspire.Hosting.AzureConnectorNamespaceExtensions.WithIdentityAccessPolicy" /> for a user-assigned managed identity without hard-coding its principal ID.
 - **MCP server policies** grant an Entra user or group access to the managed MCP endpoint. This preview doesn't support service principals or managed identities for MCP access policies.
 - **Operation allow-lists** restrict the connector operations exposed as MCP tools. Expose only what your application needs; don't put credentials or tokens in descriptions or operation metadata.
 
@@ -128,7 +129,7 @@ Incremental ARM deployments don't delete child resources omitted from the next d
 
 ## Reference existing resources
 
-Use the standard Azure `PublishAsExisting` / `publishAsExisting` and `AsExisting` / `asExisting` workflows for a namespace. Existing connection and MCP configuration children support `AsExisting` / `asExisting` and are emitted as read-only Bicep references.
+Use the standard Azure <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> and <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> workflows for a namespace. Existing connection and MCP configuration children support `AsExisting` / `asExisting` and are emitted as read-only Bicep references.
 
 When adding a new access policy beneath an existing namespace, set the Azure deployment location to the namespace's location. Bicep can't read the existing location early enough to assign the child resource location automatically.
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-connect.mdx
index d3e6776f07..93ca1f2238 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-connect.mdx
@@ -6,6 +6,7 @@ description: Learn how Azure Container Registry is consumed as a publish target
 import { Image } from 'astro:assets';
 import { Aside } from '@astrojs/starlight/components';
 import containerRegistryIcon from '@assets/icons/azure-container-registry-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={containerRegistryIcon}
@@ -37,11 +38,11 @@ When Aspire provisions an Azure Container Registry resource, the generated Bicep
 | `name`        | The provisioned name of the registry (used to reference the registry from other Bicep modules). |
 | `loginServer` | The registry login server hostname, for example `myacr1234abcd.azurecr.io`. This is the endpoint used to tag and push images during CI/CD and to pull images in compute environments. |
 
-These outputs are automatically wired into the compute environment's Bicep when you call `WithAzureContainerRegistry` (or `withAzureContainerRegistry`) from your AppHost.
+These outputs are automatically wired into the compute environment's Bicep when you call <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.WithAzureContainerRegistry" /> from your AppHost.
 
 ## Reference loginServer in your AppHost
 
-If you need to pass the registry's `loginServer` value to another resource in your AppHost — for example, to tag images before pushing — use `GetOutput` (or `getOutput`) to retrieve it as a Bicep output reference:
+If you need to pass the registry's `loginServer` value to another resource in your AppHost — for example, to tag images before pushing — use <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.GetOutput" /> to retrieve it as a Bicep output reference:
 
 ```csharp title="AppHost.cs"
 var acr = builder.AddAzureContainerRegistry("my-acr");
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-get-started.mdx
index 6f34a985c8..085a20d2b8 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-get-started.mdx
@@ -13,6 +13,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import containerRegistryIcon from '@assets/icons/azure-container-registry-icon.svg';
 
@@ -35,7 +36,7 @@ Modeling an Azure Container Registry through Aspire — rather than manually con
 - **Declarative infrastructure.** The hosting integration generates the Azure Bicep that provisions the registry alongside the rest of your app's infrastructure, keeping everything version-controlled.
 - **Fine-grained access control.** Use role assignments — such as `AcrPush` — to grant individual project resources permission to push images to the registry.
 - **Automated image cleanup.** Schedule ACR purge tasks to remove old images and control storage costs without manual intervention.
-- **Reference existing registries.** Use a registry your team already manages by referencing it with `publishAsExisting` or `asExisting` rather than provisioning a new one.
+- **Reference existing registries.** Use a registry your team already manages by referencing it with <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> or <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> rather than provisioning a new one.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-host.mdx
index 30d00fe392..f9f6d3680c 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-container-registry/azure-container-registry-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import containerRegistryIcon from '@assets/icons/azure-container-registry-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={containerRegistryIcon}
@@ -71,8 +72,8 @@ This updates your `aspire.config.json` with the Azure Container Registry hosting
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureContainerRegistry` (or `addAzureContainerRegistry`), it implicitly calls
-  `AddAzureProvisioning` — which adds support for generating Azure resources dynamically during app
+  When you call <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.AddAzureContainerRegistry" />, it implicitly calls
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app
   startup. The app must configure the appropriate subscription and location. For more information,
   see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
@@ -118,7 +119,7 @@ await builder.build().run();
 
 1. The registry resource is modeled as an `AzureContainerRegistryResource` in the Aspire resource graph.
 
-1. Calling `WithAzureContainerRegistry` (or `withAzureContainerRegistry`) on the compute environment attaches the registry and provisions the necessary role assignments and managed-identity bindings so the environment can pull images securely.
+1. Calling <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.WithAzureContainerRegistry" /> on the compute environment attaches the registry and provisions the necessary role assignments and managed-identity bindings so the environment can pull images securely.
 
 1. At deployment time, the generated Bicep provisions the registry and outputs its `name` and `loginServer` for use by the deployment pipeline.
 
@@ -130,7 +131,7 @@ await builder.build().run();
 
 ## Get the registry from a compute environment
 
-To retrieve the registry that is associated with a compute environment — for example, to add purge tasks to the auto-provisioned default registry — use `GetAzureContainerRegistry` (or `getAzureContainerRegistry`):
+To retrieve the registry that is associated with a compute environment — for example, to add purge tasks to the auto-provisioned default registry — use <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.GetAzureContainerRegistry" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -169,7 +170,7 @@ This returns an `AzureContainerRegistryResource` builder that you can use for fu
 
 ## Reference an existing container registry
 
-To reference a registry your team already manages rather than provisioning a new one, use `publishAsExisting`, `runAsExisting`, or `asExisting`:
+To reference a registry your team already manages rather than provisioning a new one, use <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, or <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -274,7 +275,7 @@ Available roles include: `AcrPull`, `AcrPush`, `AcrDelete`, `AcrImageSigner`, `A
 
 ## Schedule image cleanup with purge tasks
 
-Over time, container registries accumulate old images that consume storage. Use `WithPurgeTask` (or `withPurgeTask`) to add a scheduled [ACR purge task](https://learn.microsoft.com/azure/container-registry/container-registry-auto-purge) that automatically removes old or unused images:
+Over time, container registries accumulate old images that consume storage. Use <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.WithPurgeTask" /> to add a scheduled [ACR purge task](https://learn.microsoft.com/azure/container-registry/container-registry-auto-purge) that automatically removes old or unused images:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -343,7 +344,7 @@ Each purge task is given a unique name automatically. Use the `taskName` option
 
 ## Customize the provisioning infrastructure
 
-To make changes that go beyond what the built-in APIs expose, configure the underlying Bicep infrastructure directly via `ConfigureInfrastructure` (or `configureInfrastructure`):
+To make changes that go beyond what the built-in APIs expose, configure the underlying Bicep infrastructure directly via <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-connect.mdx
index 752ed3bf93..b7c0aeb0ff 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import cosmosDbIcon from '@assets/icons/azure-cosmosdb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={cosmosDbIcon}
@@ -33,7 +34,7 @@ The Cosmos DB account resource exposes the following connection properties:
 | Property Name      | Description |
 | ------------------ | ----------- |
 | `ConnectionString` | The account endpoint URI, with the format `AccountEndpoint=https://{account}.documents.azure.com:443/`. When access key authentication is enabled, also includes `AccountKey={key};`. |
-| `AccountKey`       | The account key (only available when running the emulator or when access key authentication is enabled via `WithAccessKeyAuthentication`). |
+| `AccountKey`       | The account key (only available when running the emulator or when access key authentication is enabled via <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithAccessKeyAuthentication" />). |
 
 **Example (Entra ID / role-based access):**
 
@@ -355,5 +356,5 @@ const database = client.database(databaseName!);
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [Customize resources](/integrations/cloud/azure/customize-resources/) in the Azure integration reference.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Customize resources](/integrations/cloud/azure/customize-resources/) in the Azure integration reference.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host.mdx
index ea7610a0e4..f4eb08f3e4 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host.mdx
@@ -11,6 +11,7 @@ import ThemeImage from '@components/ThemeImage.astro';
 import cosmosDbIcon from '@assets/icons/azure-cosmosdb-icon.png';
 import cosmosResourceRelationships from '@assets/integrations/cloud/azure/cosmos-db/cosmos-resource-relationships.svg';
 import cosmosResourceRelationshipsLight from '@assets/integrations/cloud/azure/cosmos-db/cosmos-resource-relationships-light.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={cosmosDbIcon}
@@ -108,7 +109,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureCosmosDB` (or `addAzureCosmosDB`), it implicitly calls `AddAzureProvisioning` — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+  When you call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.AddAzureCosmosDB" />, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 <Aside type="note">
@@ -117,7 +118,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Run as emulator
 
-For local development, use the Azure Cosmos DB Emulator instead of a live Azure account. Chain `RunAsEmulator` (or `runAsEmulator`) on the resource builder:
+For local development, use the Azure Cosmos DB Emulator instead of a live Azure account. Chain <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsEmulator" /> on the resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -162,7 +163,7 @@ By default, the Cosmos DB emulator container exposes the following endpoint:
 | -------- | -------------- | --------- |
 | `https`  | 8081           | dynamic   |
 
-To configure a fixed host port, call `WithGatewayPort` (or `withGatewayPort`) inside the emulator callback:
+To configure a fixed host port, call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithGatewayPort" /> inside the emulator callback:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -204,7 +205,7 @@ The Cosmos DB emulator container's port is mapped to the host port as shown in t
 
 ### Configure classic emulator partition count
 
-To configure the partition count for the classic Cosmos DB emulator container, call `WithPartitionCount` (or `withPartitionCount`) inside the classic emulator callback. The default Linux-based (vNext) emulator doesn't support partition counts and throws a <code>NotSupportedException</code> if you call this API with `RunAsEmulator` (or `runAsEmulator`).
+To configure the partition count for the classic Cosmos DB emulator container, call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithPartitionCount" /> inside the classic emulator callback. The default Linux-based (vNext) emulator doesn't support partition counts and throws a <code>NotSupportedException</code> if you call this API with `RunAsEmulator` (or `runAsEmulator`).
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -280,7 +281,7 @@ The data volume is mounted at `/tmp/cosmos/appdata` in the emulator container. W
 
 ### Configure emulator with persistent lifetime
 
-To configure the Cosmos DB emulator container with a persistent lifetime, call the `WithLifetime` method with `ContainerLifetime.Persistent`:
+To configure the Cosmos DB emulator container with a persistent lifetime, call the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> method with `ContainerLifetime.Persistent`:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -300,7 +301,7 @@ var cosmos = builder.AddAzureCosmosDB("cosmos-db")
 
 ## Run as classic emulator
 
-Use the classic (Windows-based) Azure Cosmos DB emulator instead of the default Linux-based (vNext) emulator by calling `RunAsClassicEmulator` (or `runAsClassicEmulator`):
+Use the classic (Windows-based) Azure Cosmos DB emulator instead of the default Linux-based (vNext) emulator by calling <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsClassicEmulator" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -330,12 +331,12 @@ await cosmos.runAsClassicEmulator();
 `RunAsClassicEmulator` configures the Cosmos DB resource to use the `stable` tag of the [Azure Cosmos DB Emulator](https://learn.microsoft.com/azure/cosmos-db/emulator#authentication) container image. Unlike the default vNext emulator, the classic emulator requires a TLS/SSL certificate. For more information, see [Export the emulator's TLS/SSL certificate](https://learn.microsoft.com/azure/cosmos-db/how-to-develop-emulator?tabs=docker-linux#export-the-emulators-tlsssl-certificate).
 
 <Aside type="note">
-  `RunAsPreviewEmulator` (or `runAsPreviewEmulator`) is still available but is now obsolete. It forwards to `RunAsEmulator` (the vNext emulator) so existing code keeps working, but new code should call `RunAsEmulator` directly.
+  <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsPreviewEmulator" /> is still available but is now obsolete. It forwards to `RunAsEmulator` (the vNext emulator) so existing code keeps working, but new code should call `RunAsEmulator` directly.
 </Aside>
 
 ## Configure the Data Explorer
 
-The Linux-based (vNext) emulator used by `RunAsEmulator` includes a built-in **Data Explorer** web UI. Call `WithDataExplorer` (or `withDataExplorer`) inside the emulator callback to expose it:
+The Linux-based (vNext) emulator used by `RunAsEmulator` includes a built-in **Data Explorer** web UI. Call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithDataExplorer" /> inside the emulator callback to expose it:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -377,7 +378,7 @@ await cosmos.runAsEmulator({
 
 ## Connect to an existing Azure Cosmos DB account
 
-You might have an existing Azure Cosmos DB account you want to connect to. Chain a call to `AsExisting` (or `asExisting`) on the resource builder:
+You might have an existing Azure Cosmos DB account you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> on the resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -428,7 +429,7 @@ Aspire models parent-child relationships between Azure Cosmos DB resources. An A
 
 ### Add a database
 
-To add an Azure Cosmos DB database resource, call `AddCosmosDatabase` (or `addCosmosDatabase`) on the Cosmos DB account resource builder:
+To add an Azure Cosmos DB database resource, call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.AddCosmosDatabase" /> on the Cosmos DB account resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -459,7 +460,7 @@ The `AddCosmosDatabase` call adds a logical database named `db` to your Cosmos D
 
 ### Add a container
 
-An Azure Cosmos DB container is where data is stored. When you create a container, you must supply a partition key path. To add an Azure Cosmos DB container resource, call `AddContainer` (or `addContainer`) on the database resource builder:
+An Azure Cosmos DB container is where data is stored. When you create a container, you must supply a partition key path. To add an Azure Cosmos DB container resource, call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.AddContainer" /> on the database resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -556,7 +557,7 @@ When your AppHost code expresses parent-child relationships, consuming apps can
 
 ## Enable access key authentication
 
-By default, the Azure Cosmos DB hosting integration uses Microsoft Entra ID (role-based access). To enable access key authentication instead, call `WithAccessKeyAuthentication` (or `withAccessKeyAuthentication`):
+By default, the Azure Cosmos DB hosting integration uses Microsoft Entra ID (role-based access). To enable access key authentication instead, call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithAccessKeyAuthentication" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -659,7 +660,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables fluent customization of the generated Bicep using the `ConfigureInfrastructure` (or `configureInfrastructure`) API. For example, you can configure the `kind`, `consistencyPolicy`, `locations`, and more:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables fluent customization of the generated Bicep using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API. For example, you can configure the `kind`, `consistencyPolicy`, `locations`, and more:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-data-explorer.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-data-explorer.mdx
index c32cab2373..0cdbb13e3e 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-data-explorer.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-data-explorer.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import kustoIcon from '@assets/icons/azure-dataexplorer-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={kustoIcon}
@@ -77,7 +78,7 @@ This updates your `aspire.config.json` with the Azure Data Explorer hosting inte
 
 ## Add an Azure Data Explorer cluster resource
 
-Once you've installed the hosting integration, call `AddAzureKustoCluster` (or `addAzureKustoCluster`) to declare a cluster, then call `AddReadWriteDatabase` (or `addReadWriteDatabase`) to declare one or more databases inside it:
+Once you've installed the hosting integration, call <ApiReference name="Aspire.Hosting.AzureKustoBuilderExtensions.AddAzureKustoCluster" /> to declare a cluster, then call <ApiReference name="Aspire.Hosting.AzureKustoBuilderExtensions.AddReadWriteDatabase" /> to declare one or more databases inside it:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -112,10 +113,10 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The preceding code adds an Azure Data Explorer cluster named `kusto` with a read-write database named `analytics`. The `WithReference` (or `withReference`) method injects the connection information into the consuming project.
+The preceding code adds an Azure Data Explorer cluster named `kusto` with a read-write database named `analytics`. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method injects the connection information into the consuming project.
 
 <Aside type="caution">
-  When you call `AddAzureKustoCluster`, it implicitly calls `AddAzureProvisioning` —
+  When you call `AddAzureKustoCluster`, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> —
   which adds support for generating Azure resources dynamically during app startup.
   The app must configure the appropriate subscription and location. For more
   information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -168,7 +169,7 @@ When running as an emulator, databases are automatically created when the contai
 
 ### Configure the emulator host port
 
-By default, the emulator uses a dynamic host port. To fix the host port, pass a `configureContainer` callback and call `WithHostPort` (or `withHostPort`):
+By default, the emulator uses a dynamic host port. To fix the host port, pass a `configureContainer` callback and call <ApiReference name="Aspire.Hosting.AzureKustoBuilderExtensions.WithHostPort" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -316,7 +317,7 @@ The generated Bicep is a starting point — customise it through the C# provisio
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources subclass `AzureProvisioningResource`. The `ConfigureInfrastructure` (or `configureInfrastructure`) API lets you customise the generated Bicep with a fluent callback:
+All Aspire Azure resources subclass `AzureProvisioningResource`. The <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API lets you customise the generated Bicep with a fluent callback:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-default-credential.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-default-credential.mdx
index bdadcb9375..e1c4bdd985 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-default-credential.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-default-credential.mdx
@@ -6,6 +6,7 @@ description: Learn about the default credential behavior in Aspire Azure client
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -76,7 +77,7 @@ TokenCredential credential = provider.TokenCredential;
 var armClient = new ArmClient(credential);
 ```
 
-`ITokenCredentialProvider` is registered as a singleton by `AddAzureProvisioning`. Azure resource extension methods invoke `AddAzureProvisioning`, so using those methods registers the provider indirectly. The credential it exposes is configured by the same Azure provisioning options (tenant ID, credential source, and so on) and matched to the current run or publish execution context, as described in [Default credential behavior](#default-credential-behavior).
+`ITokenCredentialProvider` is registered as a singleton by <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />. Azure resource extension methods invoke `AddAzureProvisioning`, so using those methods registers the provider indirectly. The credential it exposes is configured by the same Azure provisioning options (tenant ID, credential source, and so on) and matched to the current run or publish execution context, as described in [Default credential behavior](#default-credential-behavior).
 
 Treat the returned `TokenCredential` as opaque because its concrete type is an implementation detail that may change between releases; do not rely on casts or type checks.
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
index ac7d9619ef..7df6c19380 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import eventHubsIcon from '@assets/icons/azure-eventhubs-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={eventHubsIcon}
@@ -80,7 +81,7 @@ This updates your `aspire.config.json` with the Azure Event Hubs hosting integra
 
 ## Add an Azure Event Hubs resource
 
-Once you've installed the hosting integration, call `AddAzureEventHubs` to declare a namespace, then call `AddHub` to declare one or more hubs inside it:
+Once you've installed the hosting integration, call <ApiReference name="Aspire.Hosting.AzureEventHubsExtensions.AddAzureEventHubs" /> to declare a namespace, then call <ApiReference name="Aspire.Hosting.AzureEventHubsExtensions.AddHub" /> to declare one or more hubs inside it:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -113,10 +114,10 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The preceding code adds an Azure Event Hubs namespace named `event-hubs` with an Event Hub named `messages`. The `WithReference` (or `withReference`) method injects the connection information into the consuming project.
+The preceding code adds an Azure Event Hubs namespace named `event-hubs` with an Event Hub named `messages`. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method injects the connection information into the consuming project.
 
 <Aside type="caution">
-  When you call `AddAzureEventHubs`, it implicitly calls `AddAzureProvisioning` —
+  When you call `AddAzureEventHubs`, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> —
   which adds support for generating Azure resources dynamically during app startup.
   The app must configure the appropriate subscription and location. For more
   information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -131,7 +132,7 @@ The preceding code adds an Azure Event Hubs namespace named `event-hubs` with an
 
 ## Add an Event Hub consumer group
 
-To add a consumer group to a hub, call `AddConsumerGroup` (or `addConsumerGroup`) on the hub resource builder:
+To add a consumer group to a hub, call <ApiReference name="Aspire.Hosting.AzureEventHubsExtensions.AddConsumerGroup" /> on the hub resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -219,7 +220,7 @@ By default, the emulator container exposes port `5672` mapped to a random host p
 | ---------- | -------------------------------------------------------------- | -------------- | --------- |
 | `emulator` | `mcr.microsoft.com/azure-messaging/eventhubs-emulator`         | 5672           | dynamic   |
 
-To fix the host port, pass a `configureContainer` callback and call `WithHostPort` (or `withHostPort`):
+To fix the host port, pass a `configureContainer` callback and call <ApiReference name="Aspire.Hosting.AzureEventHubsExtensions.WithHostPort" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -319,7 +320,7 @@ builder.AddProject<Projects.ExampleService>()
 ```
 </TabItem>
 <TabItem id="typescript" label="TypeScript">
-The TypeScript AppHost doesn't currently expose `withDataBindMount` on the Event Hubs emulator resource. Use a data volume via the C# AppHost or pre-configure hubs with `withConfigurationFile` instead.
+The TypeScript AppHost doesn't currently expose `withDataBindMount` on the Event Hubs emulator resource. Use a data volume via the C# AppHost or pre-configure hubs with <ApiReference name="Aspire.Hosting.AzureEventHubsExtensions.WithConfigurationFile" /> instead.
 </TabItem>
 </Tabs>
 
@@ -403,12 +404,12 @@ builder.AddProject<Projects.ExampleService>()
 ```
 
 <Aside type="note">
-  `WithConfiguration` is not available in the TypeScript AppHost. Use `withConfigurationFile` to supply a fully customized configuration file instead.
+  <ApiReference name="Aspire.Hosting.YarpResourceExtensions.WithConfiguration" /> is not available in the TypeScript AppHost. Use `withConfigurationFile` to supply a fully customized configuration file instead.
 </Aside>
 
 ## Connect to an existing Azure Event Hubs namespace
 
-If you already have an Azure Event Hubs namespace, call `AsExisting` (or `asExisting`) instead of provisioning a new one:
+If you already have an Azure Event Hubs namespace, call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> instead of provisioning a new one:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -567,7 +568,7 @@ The generated Bicep is a starting point — customise it through the C# provisio
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources subclass `AzureProvisioningResource`. The `ConfigureInfrastructure` (or `configureInfrastructure`) API lets you customise the generated Bicep with a fluent callback:
+All Aspire Azure resources subclass `AzureProvisioningResource`. The <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API lets you customise the generated Bicep with a fluent callback:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx
index 29584742ad..1c6725108b 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-front-door.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import azureIcon from '@assets/icons/azure-front-door-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -32,7 +33,7 @@ To access this type and APIs, add the [📦 Aspire.Hosting.Azure.FrontDoor](http
 
 ### Add an Azure Front Door resource
 
-In your AppHost, call `addAzureFrontDoor` to add a Front Door profile, then call `withOrigin` to attach a backend resource as an origin:
+In your AppHost, call <ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.AddAzureFrontDoor" /> to add a Front Door profile, then call <ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.WithOrigin" /> to attach a backend resource as an origin:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -78,14 +79,14 @@ await builder.build().run();
 The preceding code:
 
 - Adds an Azure App Service environment (a compute environment is required so Front Door can resolve the origin's hostname).
-- Adds an `api` project and exposes it externally with `withExternalHttpEndpoints`. Front Door requires an origin to expose an external HTTP or HTTPS endpoint.
+- Adds an `api` project and exposes it externally with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" />. Front Door requires an origin to expose an external HTTP or HTTPS endpoint.
 - Adds a Front Door profile named `frontdoor` and configures the `api` project as an origin.
 
 Each call to `withOrigin` creates a separate Front Door endpoint, origin group, origin, and route, so each backend is independently routable through its own `*.azurefd.net` hostname.
 
 <Aside type="caution">
   When you call `addAzureFrontDoor`, it implicitly calls
-  `addAzureProvisioning`—which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -146,14 +147,14 @@ Each origin must be added at most once per Front Door resource — adding the sa
 
 ### Health probes
 
-Front Door uses health probes to determine which origins are healthy. By default, the Aspire integration probes the origin's external endpoint at path `/` over HTTPS. If you have configured an HTTP probe on the origin (for example with `WithHttpProbe`), Front Door uses the path and protocol from the resource's liveness probe instead.
+Front Door uses health probes to determine which origins are healthy. By default, the Aspire integration probes the origin's external endpoint at path `/` over HTTPS. If you have configured an HTTP probe on the origin (for example with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpProbe" />), Front Door uses the path and protocol from the resource's liveness probe instead.
 
 ### Provisioning-generated Bicep
 
 When you publish your app, Aspire generates Bicep alongside the manifest. A Front Door resource with a single origin generates Bicep similar to the following:
 
 <Aside type="caution">
-  **Upgrading from Aspire 13.3.0-preview:** The resource names generated for Front Door profiles, endpoints, origin groups, origins, and routes changed in Aspire 13.4. This can result in duplicate Azure resources (profiles, endpoints, origin groups, routes, and origins) during an upgrade. To avoid duplicates, either remove the existing Azure resources before redeploying, or set resource names explicitly using `ConfigureInfrastructure`.
+  **Upgrading from Aspire 13.3.0-preview:** The resource names generated for Front Door profiles, endpoints, origin groups, origins, and routes changed in Aspire 13.4. This can result in duplicate Azure resources (profiles, endpoints, origin groups, routes, and origins) during an upgrade. To avoid duplicates, either remove the existing Azure resources before redeploying, or set resource names explicitly using <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />.
 </Aside>
 
 <Aside type="caution">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-connect.mdx
index b354da35e7..dbdb76a104 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-connect.mdx
@@ -6,6 +6,7 @@ description: Learn how Azure Functions code reads Aspire-injected environment va
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import functionsIcon from '@assets/icons/azure-functionapps-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={functionsIcon}
@@ -24,7 +25,7 @@ Most Aspire integrations follow a pattern where the AppHost provisions a backing
 
 ## How Aspire injects values
 
-When the AppHost calls `WithReference` on the Functions project resource, Aspire writes the referenced resource connection properties as environment variables into the Functions host process. The variable names follow the standard Aspire pattern: `[RESOURCE]_[PROPERTY]` (uppercased).
+When the AppHost calls <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> on the Functions project resource, Aspire writes the referenced resource connection properties as environment variables into the Functions host process. The variable names follow the standard Aspire pattern: `[RESOURCE]_[PROPERTY]` (uppercased).
 
 For example, if the AppHost references a blob storage container named `blobs`, Aspire injects:
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-get-started.mdx
index beb786fec3..26806c26a5 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-get-started.mdx
@@ -7,6 +7,7 @@ prev: false
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import functionsIcon from '@assets/icons/azure-functionapps-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={functionsIcon}
@@ -27,7 +28,7 @@ Adding Azure Functions through Aspire — rather than configuring host JSON and
 - **Consistent resource references.** Trigger and binding configuration for Service Bus, Storage, Cosmos DB, and Event Hubs is automatically injected into the Functions host at run time.
 - **Dashboard observability.** The Functions project shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
 - **KEDA-based deployment.** When deployed to Azure Container Apps, the integration configures KEDA auto-scaling rules for your functions automatically.
-- **Durable Task Scheduler support.** Attach a local or existing Durable Task Scheduler with `AddDurableTaskScheduler` and a named task hub.
+- **Durable Task Scheduler support.** Attach a local or existing Durable Task Scheduler with <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.AddDurableTaskScheduler" /> and a named task hub.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-host.mdx
index 13e4fb5656..170ab7b5bf 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-functions/azure-functions-host.mdx
@@ -9,6 +9,7 @@ import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import functionsIcon from '@assets/icons/azure-functionapps-icon.png';
 import vsAzureFunctionsOptions from '@assets/integrations/cloud/azure/functions/visual-studio-azure-functions-options.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={functionsIcon}
@@ -94,7 +95,7 @@ This updates your `aspire.config.json` with the Azure Functions hosting integrat
 
 ## Add Azure Functions resource
 
-The Azure Functions hosting integration models Azure Functions projects as the `AzureFunctionsProjectResource` type. Call `addAzureFunctionsProject` on the `builder` instance to add an Azure Functions project resource to the app model.
+The Azure Functions hosting integration models Azure Functions projects as the `AzureFunctionsProjectResource` type. Call <ApiReference name="Aspire.Hosting.AzureFunctionsProjectResourceExtensions.AddAzureFunctionsProject" /> on the `builder` instance to add an Azure Functions project resource to the app model.
 
 There are two ways to add an Azure Functions project in C#, depending on whether the Functions project is referenced by the AppHost project. The TypeScript AppHost always uses the file path approach.
 
@@ -165,9 +166,9 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 1. The path to the Functions project file is relative to the AppHost project directory. If the path is not absolute, it is resolved relative to the AppHost directory.
 
-1. The `functions` resource can be referenced by other project resources. The `WithReference` (or `withReference`) method configures a connection named `"functions"` in the consuming project.
+1. The `functions` resource can be referenced by other project resources. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method configures a connection named `"functions"` in the consuming project.
 
-1. If the Functions project exposes an HTTP trigger and you call `WithExternalHttpEndpoints` (or `withExternalHttpEndpoints`), the trigger endpoint is publicly accessible when deployed.
+1. If the Functions project exposes an HTTP trigger and you call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" />, the trigger endpoint is publicly accessible when deployed.
 
 </Steps>
 
@@ -177,7 +178,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add Azure Functions resource with host storage
 
-Azure Functions requires an Azure Storage account as host storage for checkpoints, leases, and other internal state. By default, Aspire creates an implicit host storage resource automatically. To use a specific storage account, call `WithHostStorage` (or `withHostStorage`) on the Azure Functions resource:
+Azure Functions requires an Azure Storage account as host storage for checkpoints, leases, and other internal state. By default, Aspire creates an implicit host storage resource automatically. To use a specific storage account, call <ApiReference name="Aspire.Hosting.AzureFunctionsProjectResourceExtensions.WithHostStorage" /> on the Azure Functions resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -341,7 +342,7 @@ The Durable Task scheduler and task hub APIs are experimental in this release. T
 To use these APIs without compiler warnings, suppress the `ASPIREDURABLETASK001` diagnostic. For suppression options, see [ASPIREDURABLETASK001](/diagnostics/aspiredurabletask001/).
 :::
 
-The `Aspire.Hosting.Azure.Functions` package includes support for [Azure Durable Task Scheduler](https://learn.microsoft.com/azure/azure-functions/durable/durable-task-scheduler/durable-task-scheduler), which provides a managed backend for Durable Functions orchestrations. Use `AddDurableTaskScheduler` to add a scheduler resource and `AddTaskHub` to associate a task hub with it.
+The `Aspire.Hosting.Azure.Functions` package includes support for [Azure Durable Task Scheduler](https://learn.microsoft.com/azure/azure-functions/durable/durable-task-scheduler/durable-task-scheduler), which provides a managed backend for Durable Functions orchestrations. Use <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.AddDurableTaskScheduler" /> to add a scheduler resource and <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.AddTaskHub" /> to associate a task hub with it.
 
 ### Add a Durable Task scheduler and task hub
 
@@ -404,7 +405,7 @@ await functions.withReference(taskHub);
 In the preceding example:
 
 - `AddDurableTaskScheduler` (or `addDurableTaskScheduler`) adds a `DurableTaskSchedulerResource` to the app model.
-- `RunAsEmulator` (or `runAsEmulator`) configures the scheduler to use the local Durable Task emulator for development and testing.
+- <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.RunAsEmulator" /> configures the scheduler to use the local Durable Task emulator for development and testing.
 - `AddTaskHub` (or `addTaskHub`) creates a `DurableTaskHubResource` associated with the scheduler.
 - `WithReference(taskHub)` (or `withReference(taskHub)`) injects the task hub connection information into the Azure Functions project.
 
@@ -418,7 +419,7 @@ When using `RunAsEmulator()`, Aspire starts a local container running the DTS em
 
 ### Use an existing scheduler
 
-To connect to an already-deployed Durable Task Scheduler instance instead of provisioning a new one, use `RunAsExisting`. The overload accepts either a plain `string` connection string or an `IResourceBuilder<ParameterResource>` for securely supplying the value at runtime:
+To connect to an already-deployed Durable Task Scheduler instance instead of provisioning a new one, use <ApiReference name="Aspire.Hosting.DurableTaskResourceExtensions.RunAsExisting" />. The overload accepts either a plain `string` connection string or an `IResourceBuilder<ParameterResource>` for securely supplying the value at runtime:
 
 ```csharp title="AppHost.cs"
 #pragma warning disable ASPIREDURABLETASK001
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-key-vault/azure-key-vault-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-key-vault/azure-key-vault-host.mdx
index 8cb405db49..a912ce35ff 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-key-vault/azure-key-vault-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-key-vault/azure-key-vault-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import keyVaultIcon from '@assets/icons/azure-keyvault-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={keyVaultIcon}
@@ -108,11 +109,11 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The `WithReference` (or `withReference`) method configures a connection in the consuming project named after the referenced Key Vault resource.
+The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method configures a connection in the consuming project named after the referenced Key Vault resource.
 
 <Aside type="caution">
-  When you call `AddAzureKeyVault` (or `addAzureKeyVault`), it implicitly calls
-  `AddAzureProvisioning`, which adds support for generating Azure resources
+  When you call <ApiReference name="Aspire.Hosting.AzureKeyVaultResourceExtensions.AddAzureKeyVault" />, it implicitly calls
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -127,7 +128,7 @@ The `WithReference` (or `withReference`) method configures a connection in the c
 
 ## Connect to an existing Azure Key Vault instance
 
-You might have an existing Azure Key Vault instance that you want to connect to. Chain a call to `AsExisting` (or `asExisting`) to annotate that your resource already exists in Azure:
+You might have an existing Azure Key Vault instance that you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your resource already exists in Azure:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -218,7 +219,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-To clear the default role assignments and configure only specific roles, call `ClearDefaultRoleAssignments` (or `clearDefaultRoleAssignments`) before adding the roles you need.
+To clear the default role assignments and configure only specific roles, call <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> before adding the roles you need.
 
 ## Secret references
 
@@ -226,7 +227,7 @@ You can reference secrets stored in an Azure Key Vault directly from your AppHos
 
 ### Add a secret to Key Vault
 
-To add a secret to the Key Vault resource from the AppHost, call `AddSecret` (or `addSecret`) providing a name and a parameter:
+To add a secret to the Key Vault resource from the AppHost, call <ApiReference name="Aspire.Hosting.AzureKeyVaultResourceExtensions.AddSecret" /> providing a name and a parameter:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -264,7 +265,7 @@ await builder.build().run();
 
 ### Reference an existing secret
 
-To reference an existing secret in the vault and pass it to a consuming resource, use `GetSecret` (or `getSecret`):
+To reference an existing secret in the vault and pass it to a consuming resource, use <ApiReference name="Aspire.Hosting.AzureKeyVaultResourceExtensions.GetSecret" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -371,7 +372,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` (or `configureInfrastructure`) API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
index f906a7c128..9672c47cec 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import logAnalyticsIcon from '@assets/icons/azure-loganalytics-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={logAnalyticsIcon}
@@ -75,7 +76,7 @@ This updates your `aspire.config.json` with the Azure Log Analytics hosting inte
 
 ## Add Azure Log Analytics workspace resource
 
-The Aspire Azure Log Analytics hosting integration models the Log Analytics workspace as the `AzureLogAnalyticsWorkspaceResource` type. To add a Log Analytics workspace resource to your app host, call `AddAzureLogAnalyticsWorkspace` (or `addAzureLogAnalyticsWorkspace`):
+The Aspire Azure Log Analytics hosting integration models the Log Analytics workspace as the `AzureLogAnalyticsWorkspaceResource` type. To add a Log Analytics workspace resource to your app host, call <ApiReference name="Aspire.Hosting.AzureLogAnalyticsWorkspaceExtensions.AddAzureLogAnalyticsWorkspace" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -112,7 +113,7 @@ The preceding code adds an Azure Log Analytics workspace resource named `log-ana
 <Aside type="caution">
   When you call `AddAzureLogAnalyticsWorkspace` (or
   `addAzureLogAnalyticsWorkspace`), it implicitly calls
-  `AddAzureProvisioning`—which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -207,7 +208,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API. For example, you can configure the SKU, retention period, and more. The following example demonstrates how to customize the Azure Log Analytics workspace:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API. For example, you can configure the SKU, retention period, and more. The following example demonstrates how to customize the Azure Log Analytics workspace:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-openai/azure-openai-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-openai/azure-openai-host.mdx
index f235259aff..510ae0d578 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-openai/azure-openai-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-openai/azure-openai-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import openaiIcon from '@assets/icons/azure-openai-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={openaiIcon}
@@ -114,9 +115,9 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 <Steps>
 
-1. Calling `AddAzureOpenAI` (or `addAzureOpenAI`) creates an `AzureOpenAIResource` that models the Azure Cognitive Services account. It implicitly calls `AddAzureProvisioning`, which adds support for generating Azure resources dynamically during app startup.
+1. Calling <ApiReference name="Aspire.Hosting.AzureOpenAIExtensions.AddAzureOpenAI" /> creates an `AzureOpenAIResource` that models the Azure Cognitive Services account. It implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which adds support for generating Azure resources dynamically during app startup.
 
-1. Calling `AddDeployment` (or `addDeployment`) creates an `AzureOpenAIDeploymentResource` child that represents a model deployment on the account. Specify the deployment name, model name, and model version. See [Azure OpenAI model versions](https://learn.microsoft.com/azure/ai-services/openai/concepts/models) for available models and versions.
+1. Calling <ApiReference name="Aspire.Hosting.AzureOpenAIExtensions.AddDeployment" /> creates an `AzureOpenAIDeploymentResource` child that represents a model deployment on the account. Specify the deployment name, model name, and model version. See [Azure OpenAI model versions](https://learn.microsoft.com/azure/ai-services/openai/concepts/models) for available models and versions.
 
 1. The AppHost reference call configures a connection in the consuming project named after the referenced deployment resource, such as `chat` in the preceding example.
 
@@ -230,11 +231,11 @@ The available `AzureOpenAIRole` values are:
 
 | Role | Description |
 | ---- | ----------- |
-| `CognitiveServicesOpenAIUser` | Read access to models, deployments, and completions. Default when using `WithReference`. |
+| `CognitiveServicesOpenAIUser` | Read access to models, deployments, and completions. Default when using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />. |
 | `CognitiveServicesOpenAIContributor` | Create and delete deployments in addition to user permissions. |
 | `CognitiveServicesUser` | Broader Cognitive Services access. |
 
-To remove the default automatic role assignments and manage them entirely yourself, call `ClearDefaultRoleAssignments` (or `clearDefaultRoleAssignments`) on the Azure OpenAI resource:
+To remove the default automatic role assignments and manage them entirely yourself, call <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> on the Azure OpenAI resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -257,7 +258,7 @@ await openai.clearDefaultRoleAssignments();
 
 ## Connect to an existing Azure OpenAI service
 
-You might have an already-deployed Azure OpenAI account in your Azure subscription that you want to connect to. Use `AsExisting` (or `asExisting`) to point the resource at an existing account instead of provisioning a new one:
+You might have an already-deployed Azure OpenAI account in your Azure subscription that you want to connect to. Use <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to point the resource at an existing account instead of provisioning a new one:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -385,7 +386,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of `AzureProvisioningResource`. This enables customization of the generated Bicep by providing a fluent API to configure Azure resources using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of `AzureProvisioningResource`. This enables customization of the generated Bicep by providing a fluent API to configure Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-connect.mdx
index f75a57eca6..e0c94a636e 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import postgresqlIcon from '@assets/icons/azure-postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={postgresqlIcon}
@@ -367,5 +368,5 @@ await client.connect();
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost. See the [AppHost reference](/get-started/app-host/) for details on `WithEnvironment` and related APIs.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost. See the [AppHost reference](/get-started/app-host/) for details on <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> and related APIs.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
index 307561b7c1..e6575e01b5 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
@@ -6,6 +6,7 @@ description: "Use the Aspire Azure Database for PostgreSQL hosting and client in
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import postgresqlIcon from '@assets/icons/azure-postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={postgresqlIcon}
@@ -23,7 +24,7 @@ import postgresqlIcon from '@assets/icons/azure-postgresql-icon.png';
 Adding Azure PostgreSQL through Aspire — rather than managing connection strings and credentials by hand — gives you:
 
 - **Managed identity by default.** Aspire configures [Microsoft Entra ID](https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-azure-ad-authentication) authentication so no passwords are stored in your app configuration.
-- **Easy local development.** Call `runAsContainer` (TypeScript) or `RunAsContainer` (C#) to run a local PostgreSQL container with auto-generated credentials instead of provisioning an Azure resource during development.
+- **Easy local development.** Call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.RunAsContainer" /> (TypeScript) or `RunAsContainer` (C#) to run a local PostgreSQL container with auto-generated credentials instead of provisioning an Azure resource during development.
 - **Consistent connection info across languages.** Once you reference the database from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the server is ready.
 - **Dashboard observability.** The database resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-host.mdx
index 81a2a9f685..21b52b343b 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import postgresqlIcon from '@assets/icons/azure-postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={postgresqlIcon}
@@ -113,12 +114,12 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The preceding code adds an Azure PostgreSQL flexible server resource named `postgres` with a database named `postgresdb`. The `withReference` / `WithReference` call injects the connection information into the consuming project.
+The preceding code adds an Azure PostgreSQL flexible server resource named `postgres` with a database named `postgresdb`. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call injects the connection information into the consuming project.
 
 <Aside type="caution">
-  When you call `AddAzurePostgresFlexibleServer` /
+  When you call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.AddAzurePostgresFlexibleServer" /> /
   `addAzurePostgresFlexibleServer`, it implicitly calls
-  `AddAzureProvisioning`—which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -241,7 +242,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-When `RunAsContainer` / `runAsContainer` is called, Aspire uses the [`docker.io/library/postgres`](https://hub.docker.com/_/postgres) container image and generates credentials automatically. The same consuming app code and environment variable names work in both local-container and Azure modes.
+When <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.RunAsContainer" /> is called, Aspire uses the [`docker.io/library/postgres`](https://hub.docker.com/_/postgres) container image and generates credentials automatically. The same consuming app code and environment variable names work in both local-container and Azure modes.
 
 <Aside type="tip">
   The `RunAsContainer` / `runAsContainer` API exposes an optional delegate
@@ -254,13 +255,13 @@ When `RunAsContainer` / `runAsContainer` is called, Aspire uses the [`docker.io/
 
 ### Cross-reference: local-container vs Azure PostgreSQL
 
-If you are developing against a local container and want to switch to Azure PostgreSQL for staging or production, change `AddPostgres` to `AddAzurePostgresFlexibleServer` in the AppHost. The connection information injected into consuming apps uses the same environment variable names, so no application code changes are required.
+If you are developing against a local container and want to switch to Azure PostgreSQL for staging or production, change <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" /> to `AddAzurePostgresFlexibleServer` in the AppHost. The connection information injected into consuming apps uses the same environment variable names, so no application code changes are required.
 
 For a comparison of the two hosting integrations, see [PostgreSQL Hosting integration](/integrations/databases/postgres/postgres-host/).
 
 ## Connect to an existing Azure PostgreSQL flexible server
 
-If you have an existing Azure Database for PostgreSQL Flexible Server that you want to connect to rather than provisioning a new one, use `AsExisting` / `asExisting`:
+If you have an existing Azure Database for PostgreSQL Flexible Server that you want to connect to rather than provisioning a new one, use <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -307,7 +308,7 @@ For more information on treating Azure resources as existing, see [Use existing
 
 ## Configure password authentication
 
-By default, the Azure PostgreSQL flexible server is configured to use [Microsoft Entra ID](https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-azure-ad-authentication) authentication — no username or password is stored in your app configuration. If you need password authentication (for example, to connect with a legacy client that doesn't support Entra tokens), call `WithPasswordAuthentication` / `withPasswordAuthentication`:
+By default, the Azure PostgreSQL flexible server is configured to use [Microsoft Entra ID](https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-azure-ad-authentication) authentication — no username or password is stored in your app configuration. If you need password authentication (for example, to connect with a legacy client that doesn't support Entra tokens), call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.WithPasswordAuthentication" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -450,7 +451,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -500,7 +501,7 @@ There are many more configuration options available to customize the PostgreSQL
 
 ## Database creation after initial deployment
 
-When you call `AddDatabase` / `addDatabase` on an Azure PostgreSQL resource, Aspire provisions the database during the **first** deployment. On subsequent deployments with `azd up`, only the server-level Bicep is redeployed — databases that already exist are not recreated or deleted.
+When you call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.AddDatabase" /> on an Azure PostgreSQL resource, Aspire provisions the database during the **first** deployment. On subsequent deployments with `azd up`, only the server-level Bicep is redeployed — databases that already exist are not recreated or deleted.
 
 <Aside type="note">
   If a database does not appear after redeployment, verify that the
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-service-bus/azure-service-bus-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-service-bus/azure-service-bus-host.mdx
index 81b0a17724..27560a583b 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-service-bus/azure-service-bus-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-service-bus/azure-service-bus-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import serviceBusIcon from '@assets/icons/azure-servicebus-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={serviceBusIcon}
@@ -112,8 +113,8 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureServiceBus` (C#) or `addAzureServiceBus` (TypeScript),
-  it implicitly calls `AddAzureProvisioning`—which adds support for generating
+  When you call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.AddAzureServiceBus" />,
+  it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating
   Azure resources dynamically during app startup. The app must configure the
   appropriate subscription and location. For more information, see [Local
   provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -129,7 +130,7 @@ await builder.build().run();
 
 ## Connect to an existing Azure Service Bus namespace
 
-If you have an existing Azure Service Bus namespace, chain a call to `AsExisting` (C#) or `asExisting` (TypeScript) to connect to it instead of provisioning a new one:
+If you have an existing Azure Service Bus namespace, chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to connect to it instead of provisioning a new one:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -185,7 +186,7 @@ For more information on treating Azure resources as existing resources, see [Use
 
 ## Add Azure Service Bus queue
 
-To add a queue to an Azure Service Bus namespace, call `AddServiceBusQueue` (C#) or `addServiceBusQueue` (TypeScript) on the Service Bus resource builder:
+To add a queue to an Azure Service Bus namespace, call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.AddServiceBusQueue" /> on the Service Bus resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -227,7 +228,7 @@ This expresses an explicit parent-child relationship between the `messaging` Ser
 
 ## Add Azure Service Bus topic
 
-To add a topic, call `AddServiceBusTopic` (C#) or `addServiceBusTopic` (TypeScript) on the Service Bus resource builder:
+To add a topic, call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.AddServiceBusTopic" /> on the Service Bus resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -263,7 +264,7 @@ The topic is created in the namespace that the `AzureServiceBusResource` represe
 
 ## Add Azure Service Bus subscription
 
-To add a subscription for a topic, call `AddServiceBusSubscription` (C#) or `addServiceBusSubscription` (TypeScript) on the topic resource builder:
+To add a subscription for a topic, call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.AddServiceBusSubscription" /> on the topic resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -343,7 +344,7 @@ builder.Build().Run();
 
 ## Add Azure Service Bus emulator resource
 
-For local development, Aspire can run the [Azure Service Bus Emulator](https://learn.microsoft.com/azure/service-bus-messaging/overview-emulator) as a container. Chain a call to `RunAsEmulator` (C#) or `runAsEmulator` (TypeScript) on the Service Bus resource builder:
+For local development, Aspire can run the [Azure Service Bus Emulator](https://learn.microsoft.com/azure/service-bus-messaging/overview-emulator) as a container. Chain a call to <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.RunAsEmulator" /> on the Service Bus resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -388,7 +389,7 @@ By default, the Service Bus emulator container exposes the following endpoints:
 
 ### Configure the emulator host port
 
-By default, the host port is assigned dynamically. To pin it to a specific port, pass the `configureContainer` callback and call `withHostPort`:
+By default, the host port is assigned dynamically. To pin it to a specific port, pass the `configureContainer` callback and call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.WithHostPort" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -435,7 +436,7 @@ The preceding code maps the `emulator` endpoint to host port `7777`:
 
 ### Configure the emulator with a custom JSON file
 
-The Service Bus emulator generates its configuration automatically from the resources you've added. To provide a fully custom configuration file instead, call `WithConfigurationFile` (C#) or `withConfigurationFile` (TypeScript):
+The Service Bus emulator generates its configuration automatically from the resources you've added. To provide a fully custom configuration file instead, call <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.WithConfigurationFile" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -569,7 +570,7 @@ For more information on the assigned role, see [Azure Service Bus Data Owner](ht
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables customization of the generated Bicep using the fluent `ConfigureInfrastructure` API. For example, you can configure the SKU, location, tags, and more:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables customization of the generated Bicep using the fluent <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API. For example, you can configure the SKU, location, tags, and more:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-connect.mdx
index 808171ee57..e71eb0698f 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import signalrIcon from '@assets/icons/azure-signalr-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={signalrIcon}
@@ -22,7 +23,7 @@ This page describes how consuming apps connect to an Azure SignalR Service resou
 Azure SignalR Service acts as a proxy between **hub servers** (where `Hub` or `Hub<T>` types are hosted) and **clients** (browser or mobile apps using the SignalR client). The architecture differs from a direct database connection: the server never receives connections from clients directly — Azure SignalR Service routes all traffic.
 
 :::note
-Aspire integrates at the **hub server** level, not the end-client level. The `WithReference` call injects the service endpoint into the server-side project so it can connect to Azure SignalR Service. End clients (browser apps, mobile apps) connect to hubs through normal SignalR client negotiation, not through Aspire.
+Aspire integrates at the **hub server** level, not the end-client level. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call injects the service endpoint into the server-side project so it can connect to Azure SignalR Service. End clients (browser apps, mobile apps) connect to hubs through normal SignalR client negotiation, not through Aspire.
 :::
 
 ## Connection properties
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-host.mdx
index d43b3c2aa0..845a2be401 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-signalr/azure-signalr-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import signalrIcon from '@assets/icons/azure-signalr-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={signalrIcon}
@@ -109,8 +110,8 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureSignalR` (or `addAzureSignalR`), it implicitly calls
-  `AddAzureProvisioning` — which adds support for generating Azure resources
+  When you call <ApiReference name="Aspire.Hosting.AzureSignalRExtensions.AddAzureSignalR" />, it implicitly calls
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -183,7 +184,7 @@ await builder.build().run();
 <Aside type="note">
   `AzureSignalRServiceMode` is not available as a TypeScript parameter. Full
   service mode configuration requires modifying the Bicep object model through
-  `configureInfrastructure`. See [Customize provisioning
+  <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />. See [Customize provisioning
   infrastructure](#customize-provisioning-infrastructure) for an example.
 </Aside>
 
@@ -198,7 +199,7 @@ The Azure SignalR Service emulator only works in _Serverless_ mode. The `AddName
 
 The Azure SignalR Service emulator allows local development and testing without requiring an Azure subscription. The emulator only supports [_Serverless_ mode](https://learn.microsoft.com/azure/azure-signalr/concept-service-mode#serverless-mode).
 
-To use the emulator, chain a call to `RunAsEmulator` (or `runAsEmulator`):
+To use the emulator, chain a call to <ApiReference name="Aspire.Hosting.AzureSignalRExtensions.RunAsEmulator" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -243,7 +244,7 @@ The `RunAsEmulator` call configures the Azure SignalR Service resource to use th
 
 ## Connect to an existing Azure SignalR instance
 
-You might have an existing Azure SignalR Service that you want to connect to. Use `AsExisting` (or `asExisting`) to annotate that your `AzureSignalRResource` is an existing resource:
+You might have an existing Azure SignalR Service that you want to connect to. Use <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your `AzureSignalRResource` is an existing resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -413,7 +414,7 @@ For more information, see [Azure.Provisioning customization](/integrations/cloud
 
 ## Connection properties
 
-When you reference an Azure SignalR Service resource using `WithReference` (or `withReference`), the following connection property is made available to the consuming project:
+When you reference an Azure SignalR Service resource using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, the following connection property is made available to the consuming project:
 
 | Property Name | Description |
 | ------------- | ----------- |
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-connect.mdx
index e867220022..2673310ef7 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlServerIcon}
@@ -64,7 +65,7 @@ JdbcConnectionString: jdbc:sqlserver://myserver.database.windows.net:1433;databa
 <Aside type="note">
   Azure SQL Database uses Azure Active Directory authentication (managed identity)
   when deployed to Azure — no username or password is injected. When you use
-  `RunAsContainer` for local development, the connection string includes SQL
+  <ApiReference name="Aspire.Hosting.AzureSqlExtensions.RunAsContainer" /> for local development, the connection string includes SQL
   authentication credentials instead. For JDBC connections, add the appropriate
   authentication property such as `authentication=ActiveDirectoryDefault` or
   `authentication=ActiveDirectoryManagedIdentity`.
@@ -370,5 +371,5 @@ const pool = await sql.connect(process.env.DATABASE_URI!);
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment` (C#) or `withEnvironment` (TypeScript).
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-get-started.mdx
index 93af903c12..7948472d6f 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand why you use the Aspire Azure SQL Database integrations a
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlServerIcon}
@@ -22,13 +23,13 @@ import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
 
 Adding Azure SQL Database through Aspire — rather than wiring up connection strings and provisioning infrastructure by hand — gives you:
 
-- **Local development without Azure.** Call `runAsContainer()` to run SQL Server in a local container during development and testing, with the same connection story as the deployed Azure SQL Database.
+- **Local development without Azure.** Call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.RunAsContainer" /> to run SQL Server in a local container during development and testing, with the same connection story as the deployed Azure SQL Database.
 - **Consistent connection info across languages.** Once you reference the database from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
 - **Managed identity and role-based access.** When deployed, Aspire automatically runs a deployment script that grants your app's managed identity access to the database — no passwords to rotate.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the server is ready.
 - **Dashboard observability.** The database resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
 - **A first-class C# client integration.** C# apps can use the `Aspire.Microsoft.Data.SqlClient` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name.
-- **Infrastructure as code through Bicep.** Aspire generates Bicep for the Azure SQL Server resource automatically, and you can customize it through the `ConfigureInfrastructure` API.
+- **Infrastructure as code through Bicep.** Aspire generates Bicep for the Azure SQL Server resource automatically, and you can customize it through the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-host.mdx
index 43dffaed50..417a9f6a0d 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-sql-database/azure-sql-database-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlServerIcon}
@@ -113,11 +114,11 @@ await builder.build().run();
 
 <Steps>
 
-1. The `AddAzureSqlServer` (or `addAzureSqlServer`) call models an Azure SQL Server that is provisioned in Azure when you publish your app.
+1. The <ApiReference name="Aspire.Hosting.AzureSqlExtensions.AddAzureSqlServer" /> call models an Azure SQL Server that is provisioned in Azure when you publish your app.
 
-1. Calling `AddDatabase` (or `addDatabase`) on the returned resource builder models a named database within that server. The `WithReference` (or `withReference`) call configures a named connection in the consuming project that matches the database resource name.
+1. Calling <ApiReference name="Aspire.Hosting.AzureSqlExtensions.AddDatabase" /> on the returned resource builder models a named database within that server. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a named connection in the consuming project that matches the database resource name.
 
-1. When you call `AddAzureSqlServer`, it implicitly calls `AddAzureProvisioning` — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location.
+1. When you call `AddAzureSqlServer`, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location.
 
 </Steps>
 
@@ -139,7 +140,7 @@ await builder.build().run();
 
 ## Run Azure SQL server resource as a container
 
-During local development and testing, you can run an Azure SQL server as a local SQL Server container instead of provisioning an actual Azure resource. Call `RunAsContainer` (or `runAsContainer`) to switch to a local container:
+During local development and testing, you can run an Azure SQL server as a local SQL Server container instead of provisioning an actual Azure resource. Call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.RunAsContainer" /> to switch to a local container:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -192,7 +193,7 @@ When `RunAsContainer` is active, Aspire pulls a SQL Server container image and r
 
 ## Connect to an existing Azure SQL server
 
-You might have an existing Azure SQL Database service that you want to connect to. Chain a call to `AsExisting` (or `asExisting`) to annotate that your resource already exists in Azure:
+You might have an existing Azure SQL Database service that you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your resource already exists in Azure:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -311,7 +312,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API. For example, you can configure the `sku`, `version`, and more. The following example demonstrates how to customize the Azure SQL Database resource:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API. For example, you can configure the `sku`, `version`, and more. The following example demonstrates how to customize the Azure SQL Database resource:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -371,7 +372,7 @@ You can modify the default behavior in the following ways:
 
 #### Disable the deployment script
 
-Call `ClearDefaultRoleAssignments` (or `clearDefaultRoleAssignments`) to disable the deployment script entirely:
+Call <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> to disable the deployment script entirely:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -408,7 +409,7 @@ await builder.build().run();
 
 #### Specify a custom subnet
 
-Call `WithAdminDeploymentScriptSubnet` (or `withAdminDeploymentScriptSubnet`) to provide your own subnet for the deployment script container:
+Call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.WithAdminDeploymentScriptSubnet" /> to provide your own subnet for the deployment script container:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -453,7 +454,7 @@ await builder.build().run();
 
 #### Specify a custom storage account
 
-Call `WithAdminDeploymentScriptStorage` (or `withAdminDeploymentScriptStorage`) to provide your own storage account for the deployment script:
+Call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.WithAdminDeploymentScriptStorage" /> to provide your own storage account for the deployment script:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-connect.mdx
index 008742ae04..a2c298b960 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import storageIcon from '@assets/icons/azure-storagecontainer-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={storageIcon}
@@ -28,7 +29,7 @@ Aspire exposes each property as an environment variable named `[RESOURCE]_[PROPE
 
 ### Blob storage resource
 
-The blob storage resource (`AddBlobs` / `addBlobs`) exposes the following connection properties:
+The blob storage resource (<ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddBlobs" />) exposes the following connection properties:
 
 | Property Name      | Description |
 | ------------------ | ----------- |
@@ -43,7 +44,7 @@ Uri: https://mystorageaccount.blob.core.windows.net/
 
 ### Blob container resource
 
-The blob container resource (`AddBlobContainer` / `addBlobContainer`) inherits all properties from its parent blob storage resource and adds:
+The blob container resource (<ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddBlobContainer" />) inherits all properties from its parent blob storage resource and adds:
 
 | Property Name       | Description |
 | ------------------- | ----------- |
@@ -363,5 +364,5 @@ const client = BlobServiceClient.fromConnectionString(connStr);
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [Customize Azure resources](/integrations/cloud/azure/customize-resources/) for more information.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Customize Azure resources](/integrations/cloud/azure/customize-resources/) for more information.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-host.mdx
index fce6b33fdd..b306992356 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-blobs/azure-storage-blobs-host.mdx
@@ -10,6 +10,7 @@ import LearnMore from '@components/LearnMore.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import storageIcon from '@assets/icons/azure-storagecontainer-icon.png';
 import storageExplorerImage from '@assets/integrations/cloud/azure/storage/azure-storage-explorer.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={storageIcon}
@@ -103,7 +104,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="caution">
-When you call `AddAzureStorage` (or `addAzureStorage`), it implicitly calls `AddAzureProvisioning`—which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+When you call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddAzureStorage" />, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 <Aside type="note">
@@ -112,7 +113,7 @@ When you call `AddAzureStorage` (or `addAzureStorage`), it implicitly calls `Add
 
 ## Add blob resource
 
-After creating an Azure Storage resource, you can add a blob service resource to it using `AddBlobs` (or `addBlobs`):
+After creating an Azure Storage resource, you can add a blob service resource to it using <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddBlobs" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -157,7 +158,7 @@ The preceding code:
 
 ## Add blob container resource
 
-You can add a specific named blob container resource directly using `AddBlobContainer` (or `addBlobContainer`). This is useful when your app needs access to a specific container by name:
+You can add a specific named blob container resource directly using <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddBlobContainer" />. This is useful when your app needs access to a specific container by name:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -198,7 +199,7 @@ The `blobContainerName` option (or `options.blobContainerName` in TypeScript) se
 
 ## Configure Azurite emulator
 
-During local development, you can configure the Azure Storage resource to use [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) — the open-source Azure Storage emulator — instead of a real Azure subscription. Call `RunAsEmulator` (or `runAsEmulator`) on the storage resource:
+During local development, you can configure the Azure Storage resource to use [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) — the open-source Azure Storage emulator — instead of a real Azure subscription. Call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" /> on the storage resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -291,7 +292,7 @@ await builder.build().run();
 
 ### Configure Azurite container with persistent lifetime
 
-To configure the Azurite container with a persistent lifetime, call `WithLifetime` (or `withLifetime`) with `ContainerLifetime.Persistent`:
+To configure the Azurite container with a persistent lifetime, call <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> with `ContainerLifetime.Persistent`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -329,7 +330,7 @@ await builder.build().run();
 
 ### Configure Azurite container with data volume
 
-To add a data volume to the Azurite container, call `WithDataVolume` (or `withDataVolume`) on the emulator resource:
+To add a data volume to the Azurite container, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.WithDataVolume" /> on the emulator resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -369,7 +370,7 @@ The data volume is used to persist Azurite data outside the lifecycle of its con
 
 ### Configure Azurite container with data bind mount
 
-To add a data bind mount to the Azurite container, call `WithDataBindMount` (or `withDataBindMount`) on the emulator resource:
+To add a data bind mount to the Azurite container, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.WithDataBindMount" /> on the emulator resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -413,7 +414,7 @@ Data bind mounts rely on the host machine's filesystem to persist the Azurite da
 
 ## Connect to an existing Azure Storage account
 
-You might have an existing Azure Storage account that you want to connect to instead of provisioning a new one. Chain a call to `AsExisting` (or `asExisting`) on the storage resource:
+You might have an existing Azure Storage account that you want to connect to instead of provisioning a new one. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> on the storage resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -457,7 +458,7 @@ await builder.build().run();
 </Tabs>
 
 :::caution
-When you call `RunAsExisting`, `PublishAsExisting`, or `AsExisting` to work with resources already present in your Azure subscription, you must add certain configuration values to your AppHost so that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
+When you call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" />, or `AsExisting` to work with resources already present in your Azure subscription, you must add certain configuration values to your AppHost so that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
 :::
 
 ## Connect to storage resources
@@ -596,7 +597,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ### Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` (or `configureInfrastructure`) API. For example, you can configure the `sku`, `accessTier`, and more:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API. For example, you can configure the `sku`, `accessTier`, and more:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-datalake.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-datalake.mdx
index e82b72e0fa..b734ee45d4 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-datalake.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-datalake.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import dataLakeIcon from '@assets/icons/azure-datalake-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dataLakeIcon}
@@ -71,7 +72,7 @@ This updates your `aspire.config.json` with the Azure Storage hosting integratio
 
 ### Add Azure Data Lake resource
 
-In your AppHost project, call `AddDataLake` (or `addDataLake`) on an Azure Storage resource builder to add a Data Lake resource:
+In your AppHost project, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddDataLake" /> on an Azure Storage resource builder to add a Data Lake resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -120,7 +121,7 @@ Azure Data Lake Storage does **not** support the Azure Storage emulator. You mus
 
 ### Add Azure Data Lake file system resource
 
-You can also add a Data Lake file system resource directly from the storage resource using `AddDataLakeFileSystem` (or `addDataLakeFileSystem`):
+You can also add a Data Lake file system resource directly from the storage resource using <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddDataLakeFileSystem" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -171,7 +172,7 @@ Both `AddDataLake` and `AddDataLakeFileSystem` are called on the storage resourc
 
 ### Customize provisioning infrastructure
 
-The Data Lake resource is part of the Azure Storage resource, which is a subclass of `AzureProvisioningResource`. You can customize the generated Bicep using the `ConfigureInfrastructure` (or `configureInfrastructure`) API on the storage resource. For example, you can configure the storage SKU, access tier, and other properties:
+The Data Lake resource is part of the Azure Storage resource, which is a subclass of `AzureProvisioningResource`. You can customize the generated Bicep using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API on the storage resource. For example, you can configure the storage SKU, access tier, and other properties:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-connect.mdx
index 208008a606..6155417f6c 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import queueIcon from '@assets/icons/azure-storagequeue-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={queueIcon}
@@ -337,5 +338,5 @@ if (connectionString) {
 </Tabs>
 
 <Aside type="tip">
-If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [Set up Azure Queue Storage in the AppHost](../azure-storage-queues-host/) for details.
+If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Set up Azure Queue Storage in the AppHost](../azure-storage-queues-host/) for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-get-started.mdx
index f8dc5c04fa..a4224007aa 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand why you use the Aspire Azure Queue Storage integrations
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import queueIcon from '@assets/icons/azure-storagequeue-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={queueIcon}
@@ -27,7 +28,7 @@ Adding Azure Queue Storage through Aspire — rather than wiring up endpoints an
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the queue service is ready.
 - **Dashboard observability.** The queue resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
 - **A first-class C# client integration.** C# apps can use the `Aspire.Azure.Storage.Queues` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name.
-- **An upgrade path to Azure.** Swap from the local Azurite emulator to a real Azure Storage account by removing `RunAsEmulator` (C#) or `runAsEmulator` (TypeScript) in your AppHost.
+- **An upgrade path to Azure.** Swap from the local Azurite emulator to a real Azure Storage account by removing <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" /> in your AppHost.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-host.mdx
index 0c01b6e94d..57c3468b0e 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-queues/azure-storage-queues-host.mdx
@@ -10,6 +10,7 @@ import LearnMore from '@components/LearnMore.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import queueIcon from '@assets/icons/azure-storagequeue-icon.png';
 import storageExplorerImage from '@assets/integrations/cloud/azure/storage/azure-storage-explorer.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={queueIcon}
@@ -119,7 +120,7 @@ await builder.build().run();
 The preceding code adds an Azure Storage resource named `storage`, attaches a queue storage resource named `queues` to it, and passes the queue's connection information to the consuming project.
 
 <Aside type="caution">
-When you call `AddAzureStorage` (or `addAzureStorage`), it implicitly calls `AddAzureProvisioning`—which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+When you call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddAzureStorage" />, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 <Aside type="note">
@@ -128,7 +129,7 @@ When you reference the queue resource from the AppHost, Aspire makes several con
 
 ## Run as Azurite emulator
 
-For local development, Aspire can run the [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) emulator in a container to avoid requiring an Azure subscription. Call `RunAsEmulator` (C#) or `runAsEmulator` (TypeScript) on the storage resource:
+For local development, Aspire can run the [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) emulator in a container to avoid requiring an Azure subscription. Call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" /> on the storage resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -239,7 +240,7 @@ The resulting port mappings (`container:host`) are:
 
 ## Configure Azurite container with persistent lifetime
 
-To keep the Azurite container alive across AppHost restarts, call `WithLifetime` with `ContainerLifetime.Persistent`:
+To keep the Azurite container alive across AppHost restarts, call <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> with `ContainerLifetime.Persistent`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -325,7 +326,7 @@ The data volume is mounted at the `/data` path in the Azurite container. When a
 
 ## Configure Azurite container with data bind mount
 
-To use a bind mount instead of a volume, call `WithDataBindMount`:
+To use a bind mount instead of a volume, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.WithDataBindMount" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -373,7 +374,7 @@ Data bind mounts rely on the host machine's filesystem to persist Azurite data a
 
 ## Connect to an existing Azure Storage account
 
-You might have an existing Azure Storage account that you want to connect to. Call `AsExisting` (or `asExisting`) to annotate the resource as already provisioned:
+You might have an existing Azure Storage account that you want to connect to. Call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate the resource as already provisioned:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -420,7 +421,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="caution">
-When you call `RunAsExisting`, `PublishAsExisting`, or `AsExisting` to work with resources that are already present in your Azure subscription, you must add certain configuration values to your AppHost so that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information about how to set them, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
+When you call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" />, or `AsExisting` to work with resources that are already present in your Azure subscription, you must add certain configuration values to your AppHost so that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information about how to set them, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
 </Aside>
 
 ## Connect to storage resources from Azure Storage Explorer
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-connect.mdx
index 75ef9023fc..d8672a7c9f 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import tableIcon from '@assets/icons/azure-table-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={tableIcon}
@@ -326,5 +327,5 @@ for await (const table of client.listTables()) {
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the [AppHost reference](/get-started/app-host/) for details.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the [AppHost reference](/get-started/app-host/) for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-get-started.mdx
index 1e10b5bd61..fb0a2c3dab 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand why you use the Aspire Azure Table Storage integrations
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import tableIcon from '@assets/icons/azure-table-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={tableIcon}
@@ -24,7 +25,7 @@ Adding Azure Table Storage through Aspire — rather than wiring up connection s
 
 - **Zero-config local development.** Aspire runs the [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) emulator automatically so you can develop and test without an Azure subscription.
 - **Consistent connection info across languages.** Once you reference the table storage resource from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
-- **Built-in Azure provisioning.** Calling `AddAzureStorage` implicitly enables `AddAzureProvisioning`, which generates Azure resources dynamically during app startup when you target a real Azure subscription.
+- **Built-in Azure provisioning.** Calling <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddAzureStorage" /> implicitly enables <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which generates Azure resources dynamically during app startup when you target a real Azure subscription.
 - **Dashboard observability.** The storage resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
 - **A first-class C# client integration.** C# apps can use the `Aspire.Azure.Data.Tables` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name.
 - **An emulator-to-cloud upgrade path.** The same AppHost model works in local emulator mode and against a real Azure Storage account — switch modes without changing consuming app code.
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-host.mdx
index f2ad3541fe..7ec6e897c8 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-storage-tables/azure-storage-tables-host.mdx
@@ -9,6 +9,7 @@ import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import tableIcon from '@assets/icons/azure-table-icon.png';
 import storageExplorerImage from '@assets/integrations/cloud/azure/storage/azure-storage-explorer.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={tableIcon}
@@ -115,16 +116,16 @@ await builder.build().run();
 
 1. An Azure Storage resource named `storage` is added to the AppHost.
 
-1. A table storage resource named `tables` is added to the storage resource by chaining a call to `AddTables` (or `addTables`).
+1. A table storage resource named `tables` is added to the storage resource by chaining a call to <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddTables" />.
 
-1. The table storage resource is referenced from the consuming project with `WithReference` (or `withReference`), which injects connection properties as environment variables.
+1. The table storage resource is referenced from the consuming project with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, which injects connection properties as environment variables.
 
-1. `WaitFor` (or `waitFor`) ensures the consuming project waits until the table storage resource is ready before starting.
+1. <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> ensures the consuming project waits until the table storage resource is ready before starting.
 
 </Steps>
 
 <Aside type="caution">
-When you call `AddAzureStorage` (or `addAzureStorage`), it implicitly calls `AddAzureProvisioning` (or `addAzureProvisioning`) — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+When you call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddAzureStorage" />, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 <Aside type="note">
@@ -133,7 +134,7 @@ When you reference an Azure Table Storage resource from the AppHost, Aspire inje
 
 ## Run as emulator (Azurite)
 
-For local development, configure the storage resource to use the [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) emulator instead of a real Azure Storage account. Call `RunAsEmulator` (or `runAsEmulator`) on the storage resource:
+For local development, configure the storage resource to use the [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) emulator instead of a real Azure Storage account. Call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" /> on the storage resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -239,7 +240,7 @@ The preceding code configures the Azurite container ports as follows:
 
 ## Configure Azurite container with persistent lifetime
 
-To configure the Azurite container with a persistent lifetime so it survives app restarts, call `WithLifetime` (or `withLifetime`) with `ContainerLifetime.Persistent`:
+To configure the Azurite container with a persistent lifetime so it survives app restarts, call <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> with `ContainerLifetime.Persistent`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -277,7 +278,7 @@ await builder.build().run();
 
 ## Configure Azurite container with data volume
 
-To persist Azurite data across container restarts with a data volume, call `WithDataVolume` (or `withDataVolume`) on the emulator resource:
+To persist Azurite data across container restarts with a data volume, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.WithDataVolume" /> on the emulator resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -317,7 +318,7 @@ The data volume is mounted at the `/data` path in the Azurite container and when
 
 ## Configure Azurite container with data bind mount
 
-To add a data bind mount to the Azurite container instead of a named volume, call `WithDataBindMount` (or `withDataBindMount`):
+To add a data bind mount to the Azurite container instead of a named volume, call <ApiReference name="Aspire.Hosting.AzureStorageExtensions.WithDataBindMount" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -389,7 +390,7 @@ For more information on using the Azure Storage Explorer, see [Get started with
 
 ## Connect to an existing Azure Storage account
 
-If you have an existing Azure Storage account, you can connect to it using the `AsExisting` (or `asExisting`) method instead of provisioning a new one:
+If you have an existing Azure Storage account, you can connect to it using the <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> method instead of provisioning a new one:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -435,7 +436,7 @@ await builder.build().run();
 </Tabs>
 
 :::important
-When you call `RunAsExisting`, `PublishAsExisting`, or `AsExisting` methods to work with resources that are already present in your Azure subscription, you must add certain configuration values to your AppHost to ensure that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
+When you call <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" />, or `AsExisting` methods to work with resources that are already present in your Azure subscription, you must add certain configuration values to your AppHost to ensure that Aspire can locate them. The necessary configuration values include **SubscriptionId**, **AllowResourceGroupCreation**, **ResourceGroup**, and **Location**. If you don't set them, "Missing configuration" errors appear in the Aspire dashboard. For more information, see [Use existing Azure resources](/integrations/cloud/azure/overview/#use-existing-azure-resources).
 :::
 
 ## Connection properties
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-virtual-network.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-virtual-network.mdx
index 8a080624a1..19e6fe0779 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-virtual-network.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-virtual-network.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -92,7 +93,7 @@ This updates your `aspire.config.json` with the Azure Network hosting integratio
 
 <Aside type="tip">
   When you call any of the Azure Virtual Network APIs, it implicitly calls
-  `AddAzureProvisioning`—which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -100,7 +101,7 @@ This updates your `aspire.config.json` with the Azure Network hosting integratio
 
 ### Add a virtual network
 
-To add a virtual network, call `AddAzureVirtualNetwork` (or `addAzureVirtualNetwork`) on the `builder` instance:
+To add a virtual network, call <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddAzureVirtualNetwork" /> on the `builder` instance:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -150,7 +151,7 @@ const vnet = await builder.addAzureVirtualNetwork('vnet', '10.1.0.0/16');
 
 ### Add subnets
 
-Call `AddSubnet` (or `addSubnet`) on the virtual network builder to add a subnet with a name and address prefix:
+Call <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddSubnet" /> on the virtual network builder to add a subnet with a name and address prefix:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -175,7 +176,7 @@ You can add multiple subnets with different address ranges to a single virtual n
 
 ### Add NAT gateways
 
-A [NAT gateway](https://learn.microsoft.com/azure/nat-gateway/) provides deterministic outbound public IP addresses for subnet resources. Call `AddNatGateway` (or `addNatGateway`) to create a NAT gateway, then associate it with a subnet using `WithNatGateway` (or `withNatGateway`):
+A [NAT gateway](https://learn.microsoft.com/azure/nat-gateway/) provides deterministic outbound public IP addresses for subnet resources. Call <ApiReference name="Aspire.Hosting.AzureNatGatewayExtensions.AddNatGateway" /> to create a NAT gateway, then associate it with a subnet using <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithNatGateway" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -200,7 +201,7 @@ const subnet = vnet.addSubnet("aca-subnet", "10.0.0.0/23")
 </TabItem>
 </Tabs>
 
-By default, a public IP address is automatically created for the NAT gateway. To provide an explicit public IP address for full control, call `AddPublicIPAddress` (or `addPublicIPAddress`) and associate it with `WithPublicIPAddress` (or `withPublicIPAddress`):
+By default, a public IP address is automatically created for the NAT gateway. To provide an explicit public IP address for full control, call <ApiReference name="Aspire.Hosting.AzurePublicIPAddressExtensions.AddPublicIPAddress" /> and associate it with <ApiReference name="Aspire.Hosting.AzureNatGatewayExtensions.WithPublicIPAddress" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -260,10 +261,10 @@ const subnet = vnet.addSubnet("web", "10.0.1.0/24")
 
 The available shorthand methods are:
 
-- `AllowInbound` (or `allowInbound`) — Allow inbound traffic.
-- `DenyInbound` (or `denyInbound`) — Deny inbound traffic.
-- `AllowOutbound` (or `allowOutbound`) — Allow outbound traffic.
-- `DenyOutbound` (or `denyOutbound`) — Deny outbound traffic.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowInbound" /> — Allow inbound traffic.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyInbound" /> — Deny inbound traffic.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowOutbound" /> — Allow outbound traffic.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyOutbound" /> — Deny outbound traffic.
 
 Priority auto-increments by 100 (100, 200, 300...) and rule names are auto-generated from the access, direction, port, and source (for example, `allow-inbound-443-AzureLoadBalancer`).
 
@@ -276,7 +277,7 @@ Priority auto-increments by 100 (100, 200, 300...) and rule names are auto-gener
 
 #### Explicit API
 
-For full control over security rules, create a standalone NSG with `AddNetworkSecurityGroup` (or `addNetworkSecurityGroup`) on the `builder` and attach it to a subnet with `WithNetworkSecurityGroup` (or `withNetworkSecurityGroup`):
+For full control over security rules, create a standalone NSG with <ApiReference name="Aspire.Hosting.AzureNetworkSecurityGroupExtensions.AddNetworkSecurityGroup" /> on the `builder` and attach it to a subnet with <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithNetworkSecurityGroup" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -338,7 +339,7 @@ A single NSG can be shared across multiple subnets.
 
 ### Delegate subnets to compute environments
 
-Compute environment integrations that support regional virtual network integration expose a `WithDelegatedSubnet` (or `withDelegatedSubnet` in TypeScript) extension method that assigns a subnet to the environment, enabling subnet delegation so the environment can inject its infrastructure. For example, [Azure Container Apps](/integrations/cloud/azure/configure-container-apps/) and [Azure App Service](/integrations/cloud/azure/azure-app-service/azure-app-service-host/#regional-virtual-network-integration) both support `WithDelegatedSubnet`:
+Compute environment integrations that support regional virtual network integration expose a <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithDelegatedSubnet" /> extension method that assigns a subnet to the environment, enabling subnet delegation so the environment can inject its infrastructure. For example, [Azure Container Apps](/integrations/cloud/azure/configure-container-apps/) and [Azure App Service](/integrations/cloud/azure/azure-app-service/azure-app-service-host/#regional-virtual-network-integration) both support `WithDelegatedSubnet`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -380,7 +381,7 @@ Each compute environment delegates the subnet to its own Azure service (for exam
 
 ### Delegate a subnet to an Azure service
 
-For scenarios that aren't covered by a compute environment's `WithDelegatedSubnet` helper, call `WithServiceDelegation` (or `withServiceDelegation` in TypeScript) directly on the subnet builder to delegate it to a supported Azure service. The delegation `name` defaults to `serviceName` so you don't have to repeat the value:
+For scenarios that aren't covered by a compute environment's `WithDelegatedSubnet` helper, call <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithServiceDelegation" /> directly on the subnet builder to delegate it to a supported Azure service. The delegation `name` defaults to `serviceName` so you don't have to repeat the value:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -426,7 +427,7 @@ You can also pass another supported Azure resource provider path as `serviceName
 
 ### Add private endpoints
 
-[Private endpoints](https://learn.microsoft.com/azure/private-link/) enable secure connectivity to Azure services over a private network. Call `AddPrivateEndpoint` (or `addPrivateEndpoint`) on a subnet builder and pass the Azure resource to connect to:
+[Private endpoints](https://learn.microsoft.com/azure/private-link/) enable secure connectivity to Azure services over a private network. Call <ApiReference name="Aspire.Hosting.AzurePrivateEndpointExtensions.AddPrivateEndpoint" /> on a subnet builder and pass the Azure resource to connect to:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -462,7 +463,7 @@ When you add a private endpoint, the following resources are automatically creat
 3. A **DNS Zone Group** on the private endpoint for automatic DNS registration.
 4. The target resource is automatically configured to **deny public network access**.
 
-The private DNS zone ensures that services within the virtual network automatically resolve the target resource's hostname to its private IP address. Resources that reference the target (for example, via `WithReference`) use the same connection information—DNS resolution handles routing traffic over the private network.
+The private DNS zone ensures that services within the virtual network automatically resolve the target resource's hostname to its private IP address. Resources that reference the target (for example, via <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />) use the same connection information—DNS resolution handles routing traffic over the private network.
 
 <Aside type="caution">
   Adding a private endpoint automatically disables public network access on the
@@ -474,7 +475,7 @@ The private DNS zone ensures that services within the virtual network automatica
 
 #### Override public network access
 
-To keep public access enabled on a resource that has a private endpoint, use `ConfigureInfrastructure` to override the automatic lockdown:
+To keep public access enabled on a resource that has a private endpoint, use <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> to override the automatic lockdown:
 
 ```csharp title="AppHost.cs"
 storage.ConfigureInfrastructure(infra =>
@@ -532,7 +533,7 @@ NSPs complement private endpoints with a higher-level grouping model. Instead of
 
 #### Create a perimeter
 
-Call `AddNetworkSecurityPerimeter` (or `addNetworkSecurityPerimeter`) on the `builder` instance to create an NSP with a default profile:
+Call <ApiReference name="Aspire.Hosting.AzureNetworkSecurityPerimeterExtensions.AddNetworkSecurityPerimeter" /> on the `builder` instance to create an NSP with a default profile:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -563,7 +564,7 @@ await builder.build().run();
 
 #### Add access rules
 
-Access rules control traffic flowing into and out of the perimeter. Call `WithAccessRule` (or `withAccessRule`) and pass an `AzureNspAccessRule` to define a rule:
+Access rules control traffic flowing into and out of the perimeter. Call <ApiReference name="Aspire.Hosting.AzureNetworkSecurityPerimeterExtensions.WithAccessRule" /> and pass an `AzureNspAccessRule` to define a rule:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -618,7 +619,7 @@ Each property also has a corresponding `*References` variant (for example, `Addr
 
 #### Associate resources with a perimeter
 
-Call `WithNetworkSecurityPerimeter` (or `withNetworkSecurityPerimeter`) on a PaaS resource builder to associate it with an NSP:
+Call <ApiReference name="Aspire.Hosting.AzureNetworkSecurityPerimeterExtensions.WithNetworkSecurityPerimeter" /> on a PaaS resource builder to associate it with an NSP:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-connect.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-connect.mdx
index 2a3a03638d..80bd02d4b8 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import webPubSubIcon from '@assets/icons/azure-webpubsub-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={webPubSubIcon}
@@ -332,5 +333,5 @@ const client = new WebPubSubServiceClient(connectionString, "messages");
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [Customize provisioning infrastructure](../azure-web-pubsub-host/#customize-provisioning-infrastructure) in the Hosting integration reference.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Customize provisioning infrastructure](../azure-web-pubsub-host/#customize-provisioning-infrastructure) in the Hosting integration reference.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-host.mdx
index a86f054092..b2b9cd4c6d 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-web-pubsub/azure-web-pubsub-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import webPubSubIcon from '@assets/icons/azure-webpubsub-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={webPubSubIcon}
@@ -105,7 +106,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 <Steps>
 
-1. The `AddAzureWebPubSub` (or `addAzureWebPubSub`) call declares an Azure Web PubSub resource named `web-pubsub` in the AppHost.
+1. The <ApiReference name="Aspire.Hosting.AzureWebPubSubExtensions.AddAzureWebPubSub" /> call declares an Azure Web PubSub resource named `web-pubsub` in the AppHost.
 
 1. The AppHost reference call configures a connection in the consuming project named after the referenced resource, such as `web-pubsub` in the preceding example.
 
@@ -113,7 +114,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 <Aside type="caution">
   When you call `AddAzureWebPubSub`, it implicitly calls
-  `AddAzureProvisioning`—which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />—which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -125,7 +126,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add Azure Web PubSub hub resource
 
-A hub is a logical grouping of connections and event handlers in Azure Web PubSub. To add a hub to a Web PubSub resource, chain a call to `AddHub` (or `addHub`):
+A hub is a logical grouping of connections and event handlers in Azure Web PubSub. To add a hub to a Web PubSub resource, chain a call to <ApiReference name="Aspire.Hosting.AzureWebPubSubExtensions.AddHub" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -156,7 +157,7 @@ The preceding code adds a hub resource named `messages` with a hub name of `mess
 
 ## Add event handler to a hub
 
-Event handlers allow your backend services to receive events from Azure Web PubSub. To add an event handler to a hub, chain a call to `AddEventHandler` (or `addEventHandler`):
+Event handlers allow your backend services to receive events from Azure Web PubSub. To add an event handler to a hub, chain a call to <ApiReference name="Aspire.Hosting.AzureWebPubSubExtensions.AddEventHandler" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -251,7 +252,7 @@ The available roles for Azure Web PubSub are:
 
 ## Connect to an existing Azure Web PubSub instance
 
-You might have an existing Azure Web PubSub service that you want to connect to. Chain a call to `AsExisting` (or `asExisting`) to annotate that your resource is externally managed:
+You might have an existing Azure Web PubSub service that you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your resource is externally managed:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -379,7 +380,7 @@ The generated Bicep is a starting point and is influenced by changes to the prov
 
 ## Customize provisioning infrastructure
 
-All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the `ConfigureInfrastructure` API:
+All Aspire Azure resources are subclasses of the `AzureProvisioningResource` type. This type enables the customization of the generated Bicep by providing a fluent API to configure the Azure resources using the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/configure-container-apps.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/configure-container-apps.mdx
index b6ae6a2eea..327a832d8c 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/configure-container-apps.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/configure-container-apps.mdx
@@ -6,6 +6,7 @@ description: Learn how to configure Azure Container Apps environment settings, s
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import containerAppsIcon from '@assets/icons/azure-container-apps-environments.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={containerAppsIcon}
@@ -18,7 +19,7 @@ import containerAppsIcon from '@assets/icons/azure-container-apps-environments.s
 
 The [Aspire AppHost](/get-started/app-host/) simplifies infrastructure provisioning by generating code to create Azure resources for your applications. This approach lets you model and configure deployment-related aspects directly in your AppHost, reducing the need to rely on tools like Bicep. These aspects include configuring ACA environments, which provide a serverless platform for running containerized applications.
 
-Using the `Aspire.Hosting.Azure.AppContainers` integration, you can deploy compute resources to Azure Container Apps by adding an ACA environment with `AddAzureContainerAppEnvironment`. Use `PublishAsAzureContainerApp` only when you want to customize the generated Container App resource for a project, container, or executable — it does not create the ACA environment. Add an ACA environment first, then use the callback to customize the generated Container App resource.
+Using the `Aspire.Hosting.Azure.AppContainers` integration, you can deploy compute resources to Azure Container Apps by adding an ACA environment with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />. Use `PublishAsAzureContainerApp` only when you want to customize the generated Container App resource for a project, container, or executable — it does not create the ACA environment. Add an ACA environment first, then use the callback to customize the generated Container App resource.
 
 By using the `Azure.Provisioning` APIs (explained in [Customize Azure resources](/integrations/cloud/azure/customize-resources/)), you can configure and customize ACA environments along with related resources, such as container registries and file share volumes. Any available deployment setting can be configured. For more information on the available settings, see [Microsoft.App managedEnvironments](https://learn.microsoft.com/azure/templates/microsoft.app/managedenvironments).
 
@@ -188,11 +189,11 @@ This module configures:
 - A role assignment for the user principal ID to the ACA environment.
 - Various outputs for the ACA environment.
 
-Using the `acaEnv` variable, you can chain a call to the `ConfigureInfrastructure` API to customize the ACA environment to your liking. For more information, see [Configure infrastructure](/integrations/cloud/azure/customize-resources/).
+Using the `acaEnv` variable, you can chain a call to the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> API to customize the ACA environment to your liking. For more information, see [Configure infrastructure](/integrations/cloud/azure/customize-resources/).
 
 ## Use an existing ACA environment
 
-If you've already provisioned an Azure Container Apps environment, chain `AsExisting` (or `asExisting`) on `AddAzureContainerAppEnvironment` to deploy your container apps into it instead of creating a new one:
+If you've already provisioned an Azure Container Apps environment, chain <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> on `AddAzureContainerAppEnvironment` to deploy your container apps into it instead of creating a new one:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -233,13 +234,13 @@ When the environment is marked as existing, Aspire generates a thin Bicep module
 
 Some configurations are incompatible with an existing environment and are rejected at publish time:
 
-- `WithDelegatedSubnet` — VNet integration is a property of the managed environment and can't be reconfigured on an existing one.
-- `WithAzureLogAnalyticsWorkspace` — the existing environment already owns its workspace.
+- <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithDelegatedSubnet" /> — VNet integration is a property of the managed environment and can't be reconfigured on an existing one.
+- <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithAzureLogAnalyticsWorkspace" /> — the existing environment already owns its workspace.
 - Volume mounts on container apps targeting the environment — Azure Files storage attaches to the managed environment, which Aspire can't change on an existing environment.
 
 ### Bring your own ACR pull identity
 
-By default, even when the environment is existing, Aspire still emits a new user-assigned managed identity and an `AcrPull` role assignment on the container registry so that newly deployed container apps can pull their images. If your deployment principal can't create identities or role assignments, or if you have an existing identity that you want to reuse, supply a pre-existing identity with `WithAcrPullIdentity` (or `withAcrPullIdentity`):
+By default, even when the environment is existing, Aspire still emits a new user-assigned managed identity and an `AcrPull` role assignment on the container registry so that newly deployed container apps can pull their images. If your deployment principal can't create identities or role assignments, or if you have an existing identity that you want to reuse, supply a pre-existing identity with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithAcrPullIdentity" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -362,7 +363,7 @@ builder.Build().Run();
 
 ## Handle naming conventions
 
-By default, `AddAzureContainerAppEnvironment` uses a different Azure resource naming scheme than the [Azure Developer CLI (`azd`)](https://learn.microsoft.com/azure/developer/azure-developer-cli/). If you're upgrading an existing deployment that previously used `azd`, you might see duplicate Azure resources. To avoid this issue, call the `WithAzdResourceNaming` method to revert to the naming convention used by `azd`:
+By default, `AddAzureContainerAppEnvironment` uses a different Azure resource naming scheme than the [Azure Developer CLI (`azd`)](https://learn.microsoft.com/azure/developer/azure-developer-cli/). If you're upgrading an existing deployment that previously used `azd`, you might see duplicate Azure resources. To avoid this issue, call the <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithAzdResourceNaming" /> method to revert to the naming convention used by `azd`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -397,7 +398,7 @@ Calling this API ensures your existing Azure resources remain consistent and pre
 
 By default, the generated managed environment `name` keeps only lowercase letters from the resource name, so `AddAzureContainerAppEnvironment("cae1")` and `AddAzureContainerAppEnvironment("cae2")` both produce the same Bicep expression once digits are stripped. If you deploy both environments to the *same resource group*, they collapse onto a single physical Azure Container Apps environment and concurrent deployments can fail with `ManagedEnvironmentOperationInProgress`.
 
-Publish and deploy detect this collision up front and fail with guidance to call `WithUniqueResourceNaming` on the colliding environments:
+Publish and deploy detect this collision up front and fail with guidance to call <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithUniqueResourceNaming" /> on the colliding environments:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/container-app-jobs.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/container-app-jobs.mdx
index 4e2ea62861..f9970eee94 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/container-app-jobs.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/container-app-jobs.mdx
@@ -6,6 +6,7 @@ description: Learn how to use the Aspire Azure Container App Jobs hosting integr
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import containerAppsIcon from '@assets/icons/azure-container-apps-environments.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={containerAppsIcon}
@@ -16,7 +17,7 @@ import containerAppsIcon from '@assets/icons/azure-container-apps-environments.s
   data-zoom-off
 />
 
-[Azure Container Apps jobs](https://learn.microsoft.com/azure/container-apps/jobs) let you run containerized tasks that execute for a finite duration and exit. Unlike continuously-running Container Apps, jobs are purpose-built for batch processing, scheduled tasks, and event-driven workloads. The Aspire Azure Container App Jobs hosting integration exposes `PublishAsAzureContainerAppJob` and `PublishAsScheduledAzureContainerAppJob` extension methods so you can declare any `ProjectResource`, `ContainerResource`, or `ExecutableResource` as an Azure Container App Job directly from your [`AppHost`](/get-started/app-host/).
+[Azure Container Apps jobs](https://learn.microsoft.com/azure/container-apps/jobs) let you run containerized tasks that execute for a finite duration and exit. Unlike continuously-running Container Apps, jobs are purpose-built for batch processing, scheduled tasks, and event-driven workloads. The Aspire Azure Container App Jobs hosting integration exposes <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsAzureContainerAppJob" /> and <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsScheduledAzureContainerAppJob" /> extension methods so you can declare any `ProjectResource`, `ContainerResource`, or `ExecutableResource` as an Azure Container App Job directly from your [`AppHost`](/get-started/app-host/).
 
 ## Supported resource types
 
@@ -24,9 +25,9 @@ The following resource types can be published as Azure Container App Jobs:
 
 | Resource type | Description |
 |---|---|
-| `ProjectResource` | A .NET project added via `AddProject<T>`. |
-| `ContainerResource` | A container image added via `AddContainer`. |
-| `ExecutableResource` | An executable process added via `AddExecutable`. |
+| `ProjectResource` | A .NET project added via <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />. |
+| `ContainerResource` | A container image added via <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" />. |
+| `ExecutableResource` | An executable process added via <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.AddExecutable" />. |
 
 ## Publish a project as a Container App Job
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
index 7161150a21..157b0da1cb 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -29,7 +30,7 @@ When working with Azure integrations in Aspire, you often need to customize the
 
 ### Use existing Azure resources
 
-Use `AsExisting`, `RunAsExisting`, and `PublishAsExisting` when you want Aspire to reference an Azure resource that already exists instead of provisioning a new one.
+Use <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, and <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> when you want Aspire to reference an Azure resource that already exists instead of provisioning a new one.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="typescript" label="TypeScript">
@@ -74,7 +75,7 @@ Use `RunAsExisting` when only local run mode should use the existing resource, `
 
 ### Manage default role assignments
 
-Aspire automatically assigns Azure RBAC roles based on how resources reference one another. When you need to opt out of those defaults before applying different permissions, use `ClearDefaultRoleAssignments`.
+Aspire automatically assigns Azure RBAC roles based on how resources reference one another. When you need to opt out of those defaults before applying different permissions, use <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" />.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="typescript" label="TypeScript">
@@ -146,7 +147,7 @@ builder.Build().Run();
 </TabItem>
 </Tabs>
 
-Use `GetBicepIdentifier()` inside `ConfigureInfrastructure` or infrastructure resolvers when you need a stable identifier for a provisioned Azure construct. Use output references such as `ClientId`, `NameOutputReference`, or `getOutput("...")` when you need Azure-assigned values like a client ID, endpoint, or resource name.
+Use <ApiReference name="Aspire.Hosting.AzureResourceExtensions.GetBicepIdentifier" /> inside <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> or infrastructure resolvers when you need a stable identifier for a provisioned Azure construct. Use output references such as `ClientId`, `NameOutputReference`, or `getOutput("...")` when you need Azure-assigned values like a client ID, endpoint, or resource name.
 
 ## Azure.Provisioning customization
 
@@ -625,7 +626,7 @@ The callback above applies the queue setting to every queue modeled under that n
 
 ### Add Azure resources to the infrastructure
 
-For common scenarios, prefer Aspire's higher-level resource builders. For example, to add a private endpoint to a storage account, use `AddPrivateEndpoint` from the `Aspire.Hosting.Azure.Network` package, which automatically wires up the Private DNS Zone, VNet link, and DNS Zone Group:
+For common scenarios, prefer Aspire's higher-level resource builders. For example, to add a private endpoint to a storage account, use <ApiReference name="Aspire.Hosting.AzurePrivateEndpointExtensions.AddPrivateEndpoint" /> from the `Aspire.Hosting.Azure.Network` package, which automatically wires up the Private DNS Zone, VNet link, and DNS Zone Group:
 
 Install `Aspire.Hosting.Azure.Network` for this example. These networking APIs are experimental under `ASPIREAZURE003`; the C# example explicitly acknowledges that diagnostic. This hosting API is separate from the opt-in SDK proxies.
 
@@ -765,7 +766,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
 output storageAccountName string = storageAccount.name
 ```
 
-Reference the file from the AppHost using `AddBicepTemplate` (C#) or `addBicepTemplate` (TypeScript). Use `WithParameter` / `withParameter` to supply input parameters, and `GetOutput` / `getOutput` to consume a named output by passing the resulting reference to another resource:
+Reference the file from the AppHost using <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.AddBicepTemplate" />. Use <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.WithParameter" /> to supply input parameters, and <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.GetOutput" /> to consume a named output by passing the resulting reference to another resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="typescript" label="TypeScript">
@@ -812,7 +813,7 @@ builder.Build().Run();
 
 <Aside type="tip">
   For inline Bicep snippets, use `AddBicepTemplateString` (C#) or
-  `addBicepTemplateString` (TypeScript) instead of `AddBicepTemplate`. Both APIs
+  <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.AddBicepTemplateString" /> (TypeScript) instead of `AddBicepTemplate`. Both APIs
   return the same `AzureBicepResource` and support the same `WithParameter` and
   `GetOutput` patterns.
 </Aside>
@@ -821,7 +822,7 @@ builder.Build().Run();
 
 `WithParameter` accepts several kinds of values beyond plain strings, so a custom Bicep template can take values that are computed at deployment time. Common sources include:
 
-- A `ParameterResource` declared with `AddParameter` (including secret parameters).
+- A `ParameterResource` declared with <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> (including secret parameters).
 - A `BicepOutputReference` from another Bicep resource — useful when one template's output feeds another template's input.
 - A `ReferenceExpression` that composes values from multiple resources.
 - A connection-string-bearing resource via `IResourceBuilder<IResourceWithConnectionString>`.
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/local-provisioning.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/local-provisioning.mdx
index 46c2a8aae5..82f5e30d58 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/local-provisioning.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/local-provisioning.mdx
@@ -6,6 +6,7 @@ description: Learn how to automatically provision Azure resources during local d
 import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -20,7 +21,7 @@ This article describes how to enable local Azure provisioning in your Aspire [`A
 
 ## How it works
 
-When you add an Azure resource using methods like `AddAzureStorage()` or `AddAzureServiceBus()`, Aspire:
+When you add an Azure resource using methods like <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddAzureStorage" /> or <ApiReference name="Aspire.Hosting.AzureServiceBusExtensions.AddAzureServiceBus" />, Aspire:
 
 <Steps>
 
@@ -256,7 +257,7 @@ When you use local provisioning, Aspire generates Bicep files in the `./infra` d
 
 - Define all Azure resources
 - Include configurations and connections
-- Can be customized using `ConfigureInfrastructure()`
+- Can be customized using <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />
 - Are used for both local provisioning and production deployment
 
 Example generated structure:
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/overview.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/overview.mdx
index f58e43bfaf..5a2df6e62d 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/overview.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/overview.mdx
@@ -7,6 +7,7 @@ import { Kbd } from 'starlight-kbd/components'
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -74,7 +75,7 @@ The resource reference supplies connection information to your API, and the star
 - **Frictionless local development**: Aspire provisions real Azure resources (or emulators/containers) automatically when you run your app locally.
 - **Observability built in**: Azure client integrations wire up health checks, distributed tracing, and metrics out of the box.
 - **Bicep-first deployment**: Aspire generates Bicep templates from your app model, giving you full control over what's deployed to Azure.
-- **Consistent API patterns**: All Azure integrations share common `AddAzure*`, `RunAs*`, `PublishAs*`, and `AsExisting` conventions.
+- **Consistent API patterns**: All Azure integrations share common `AddAzure*`, `RunAs*`, `PublishAs*`, and <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> conventions.
 
 ## What are Azure integrations?
 
@@ -105,7 +106,7 @@ Some Azure services can be emulated to run locally. Currently, Aspire supports t
 |--|--|
 | [Azure App Configuration](/integrations/cloud/azure/azure-app-configuration/azure-app-configuration-get-started/) | Call `RunAsEmulator` on the `IResourceBuilder<AzureAppConfigurationResource>` to configure the Azure App Configuration resource to be [emulated with the Azure App Configuration Emulator](https://learn.microsoft.com/azure/azure-app-configuration/emulator-overview). |
 | [Azure Cosmos DB](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-get-started/) | Call `RunAsEmulator` on the `IResourceBuilder<AzureCosmosDBResource>` to configure the Cosmos DB resource to be [emulated with the NoSQL API](https://learn.microsoft.com/azure/cosmos-db/how-to-develop-emulator). |
-| [Microsoft Foundry](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started/) | Call `RunAsFoundryLocal` on the `IResourceBuilder<FoundryResource>` to configure the resource to be [emulated with Foundry Local](https://learn.microsoft.com/azure/ai-foundry/foundry-local/get-started). |
+| [Microsoft Foundry](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started/) | Call <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> on the `IResourceBuilder<FoundryResource>` to configure the resource to be [emulated with Foundry Local](https://learn.microsoft.com/azure/ai-foundry/foundry-local/get-started). |
 | [Azure Event Hubs](/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-get-started/) | Call `RunAsEmulator` on the `IResourceBuilder<AzureEventHubsResource>` to configure the Event Hubs resource to be [emulated](https://learn.microsoft.com/azure/event-hubs/overview-emulator). |
 | [Azure Service Bus](/integrations/cloud/azure/azure-service-bus/azure-service-bus-get-started/) | Call `RunAsEmulator` on the `IResourceBuilder<AzureServiceBusResource>` to configure the Service Bus resource to be [emulated with Service Bus emulator](https://learn.microsoft.com/azure/service-bus-messaging/overview-emulator). |
 | [Azure SignalR Service](/integrations/cloud/azure/azure-signalr/azure-signalr-get-started/) | Call `RunAsEmulator` on the `IResourceBuilder<AzureSignalRResource>` to configure the SignalR resource to be [emulated with Azure SignalR emulator](https://learn.microsoft.com/azure/azure-signalr/signalr-howto-emulator). |
@@ -169,11 +170,11 @@ The following table summarizes the naming conventions used to express Azure reso
 
 | Operation | API | Description |
 |--|--|--|
-| Publish | `PublishAsConnectionString` _(obsolete)_ | Changes the resource to be published as a connection string reference in the manifest. Use `AddConnectionString` with the [execution context](/get-started/app-host/) instead. |
-| Publish | `PublishAsExisting` | Uses an existing Azure resource when the application is deployed instead of creating a new one. |
+| Publish | <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.PublishAsConnectionString" /> _(obsolete)_ | Changes the resource to be published as a connection string reference in the manifest. Use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> with the [execution context](/get-started/app-host/) instead. |
+| Publish | <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> | Uses an existing Azure resource when the application is deployed instead of creating a new one. |
 | Run | `RunAsContainer` | Configures an equivalent container to run locally. For more information, see [Local containers](#local-containers). |
 | Run | `RunAsEmulator` | Configures the Azure resource to be emulated. For more information, see [Local emulators](#local-emulators). |
-| Run | `RunAsExisting` | Uses an existing resource when the application is running instead of creating a new one. |
+| Run | <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" /> | Uses an existing resource when the application is running instead of creating a new one. |
 | Publish and Run | `AsExisting` | Uses an existing resource regardless of the operation. |
 
 :::caution[PublishAsConnectionString is obsolete]
@@ -450,7 +451,7 @@ Aspire deploys compute resources to [Azure Container Apps](https://learn.microso
 - `ExecutableResource`: Represents a specified executable process.
 - `ProjectResource`: Represents a specified .NET project.
 
-Add an ACA environment with `AddAzureContainerAppEnvironment` to target these resources to Azure Container Apps.
+Add an ACA environment with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" /> to target these resources to Azure Container Apps.
 
 Use the following APIs when you want to customize the generated Container App resource for a specific resource:
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/user-assigned-identity.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/user-assigned-identity.mdx
index fe008476cd..c54f9e8ce6 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/user-assigned-identity.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/user-assigned-identity.mdx
@@ -6,6 +6,7 @@ description: Learn how to configure user-assigned managed identities for Aspire
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import azureIcon from '@assets/icons/azure-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={azureIcon}
@@ -22,7 +23,7 @@ A user-assigned managed identity is a standalone Azure resource that you assign
 
 ## Add a user-assigned managed identity
 
-To create a new user-assigned managed identity, use the `AddAzureUserAssignedIdentity` (or `addAzureUserAssignedIdentity`) API:
+To create a new user-assigned managed identity, use the <ApiReference name="Aspire.Hosting.Azure.AzureUserAssignedIdentityExtensions.AddAzureUserAssignedIdentity" /> API:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -57,7 +58,7 @@ The preceding code creates a new managed identity named `"custom-umi"` that you
 
 <Aside type="caution">
   Calling `AddAzureUserAssignedIdentity` (or `addAzureUserAssignedIdentity`)
-  implicitly calls `AddAzureProvisioning`, which adds support for generating
+  implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" />, which adds support for generating
   Azure resources dynamically during app startup. The app must configure the
   appropriate subscription and location. For more information, see [Local
   provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -65,7 +66,7 @@ The preceding code creates a new managed identity named `"custom-umi"` that you
 
 ## Reference an existing managed identity
 
-If you already have a managed identity, reference it using the `PublishAsExisting` (or `publishAsExisting`) method. This is useful when you want to use an identity created outside of your Aspire project:
+If you already have a managed identity, reference it using the <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> method. This is useful when you want to use an identity created outside of your Aspire project:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/compute/docker.mdx b/src/frontend/src/content/docs/integrations/compute/docker.mdx
index 0a4e99d443..efd58c347a 100644
--- a/src/frontend/src/content/docs/integrations/compute/docker.mdx
+++ b/src/frontend/src/content/docs/integrations/compute/docker.mdx
@@ -7,6 +7,7 @@ description: Learn how to use the Aspire Docker hosting integration to deploy yo
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import dockerIcon from '@assets/icons/docker.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dockerIcon}
@@ -146,7 +147,7 @@ When a Docker Compose environment is present, all resources are automatically pu
   With the `compose` variable assigned, you can pass it to the compute environment API to
   disambiguate compute resources for solutions that define more than one. Otherwise, the `compose`
   variable isn't required. This API is named `WithComputeEnvironment` in C# AppHosts and
-  `withComputeEnvironment` in TypeScript AppHosts.
+  <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" /> in TypeScript AppHosts.
 
   <Tabs syncKey='aspire-lang'>
   <TabItem id='csharp' label='C#'>
@@ -170,7 +171,7 @@ When a Docker Compose environment is present, all resources are automatically pu
 
 ### Add Docker Compose environment resource with properties
 
-You can configure various properties of the Docker Compose environment using the `WithProperties` method:
+You can configure various properties of the Docker Compose environment using the <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.WithProperties" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -202,7 +203,7 @@ The `DashboardEnabled` property determines whether to include an Aspire dashboar
 
 ### Add Docker Compose environment resource with compose file
 
-You can customize the generated Docker Compose file using the `ConfigureComposeFile` method:
+You can customize the generated Docker Compose file using the <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureComposeFile" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -240,7 +241,7 @@ The `ConfigureComposeFile` callback runs after Aspire generates the Docker Compo
 
 ### Add Aspire dashboard resource to environment
 
-The Docker hosting integration includes an Aspire dashboard for telemetry visualization. You can configure or disable it using the `WithDashboard` method:
+The Docker hosting integration includes an Aspire dashboard for telemetry visualization. You can configure or disable it using the <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.WithDashboard" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -277,11 +278,11 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The `WithHostPort` method configures the port used to access the Aspire dashboard from a browser. The `WithForwardedHeaders` method enables forwarded headers processing when the dashboard is accessed through a reverse proxy or load balancer.
+The <ApiReference name="Aspire.Hosting.DockerComposeAspireDashboardResourceBuilderExtensions.WithHostPort" /> method configures the port used to access the Aspire dashboard from a browser. The <ApiReference name="Aspire.Hosting.DockerComposeAspireDashboardResourceBuilderExtensions.WithForwardedHeaders" /> method enables forwarded headers processing when the dashboard is accessed through a reverse proxy or load balancer.
 
 ### Resolve Docker Compose service host names
 
-Use `GetHostAddressExpression` to get the Docker Compose host name that another service should use for an endpoint. In Docker Compose deployments, this expression resolves to the generated service name on the Compose network.
+Use <ApiReference name="Aspire.Hosting.Docker.DockerComposeEnvironmentResource.GetHostAddressExpression" /> to get the Docker Compose host name that another service should use for an endpoint. In Docker Compose deployments, this expression resolves to the generated service name on the Compose network.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -324,7 +325,7 @@ The Docker hosting integration captures environment variables from your app mode
 
 #### Customize environment file
 
-For advanced scenarios, use `ConfigureEnvFile` to customize the generated `.env` file:
+For advanced scenarios, use <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureEnvFile" /> to customize the generated `.env` file:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -367,7 +368,7 @@ This is useful when you need to add custom environment variables to the generate
 
 ### Customize a Docker Compose service
 
-To customize the generated Docker Compose service for a specific resource, use the `PublishAsDockerComposeService` method. This is optional — all resources are automatically included in the Docker Compose output. Use this method only when you need to modify the generated service definition:
+To customize the generated Docker Compose service for a specific resource, use the <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.PublishAsDockerComposeService" /> method. This is optional — all resources are automatically included in the Docker Compose output. Use this method only when you need to modify the generated service definition:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -414,11 +415,11 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The `configure` callback receives the `DockerComposeServiceResource` and the generated `Service` object, allowing you to modify properties like labels, restart policy, container name, or other Docker Compose service settings. Use `AsEnvironmentPlaceholder` for values that should be written as Compose environment variable placeholders in the generated YAML and `.env` files.
+The `configure` callback receives the `DockerComposeServiceResource` and the generated `Service` object, allowing you to modify properties like labels, restart policy, container name, or other Docker Compose service settings. Use <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.AsEnvironmentPlaceholder" /> for values that should be written as Compose environment variable placeholders in the generated YAML and `.env` files.
 
 ### Generate Dockerfiles programmatically
 
-Use `AddDockerfileBuilder` to create a container resource from a Dockerfile generated by AppHost code. Use `WithDockerfileBuilder` when you want to apply the generated Dockerfile to an existing container resource.
+Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> to create a container resource from a Dockerfile generated by AppHost code. Use <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" /> when you want to apply the generated Dockerfile to an existing container resource.
 
 <Aside type="caution">
   The Dockerfile builder APIs are experimental and may change in future
@@ -498,7 +499,7 @@ Container resources support an `ImagePullPolicy` that controls when the containe
 | `Missing` | Pulls the image only if it doesn't already exist locally. |
 | `Never` | Never pulls the image from a registry. The image must already exist locally. |
 
-Use the `WithImagePullPolicy` extension method to set the policy on a container resource:
+Use the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImagePullPolicy" /> extension method to set the policy on a container resource:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -575,7 +576,7 @@ When deploying containers, you can customize how container images are named and
 
 ### Set remote image name and tag
 
-Use `WithRemoteImageName` and `WithRemoteImageTag` to customize the image reference:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithRemoteImageName" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithRemoteImageTag" /> to customize the image reference:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -610,7 +611,7 @@ await api.withRemoteImageTag("v1.0.0");
 
 ### Advanced customization with callbacks
 
-For more complex scenarios, use `WithImagePushOptions` to register a callback that can dynamically configure push options:
+For more complex scenarios, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithImagePushOptions" /> to register a callback that can dynamically configure push options:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -709,7 +710,7 @@ Multiple callbacks can be registered on the same resource, and they will be invo
 
 ## Push images to container registries
 
-You can configure your Aspire application to push container images to registries like GitHub Container Registry (GHCR), Docker Hub, or private registries using the `AddContainerRegistry` method.
+You can configure your Aspire application to push container images to registries like GitHub Container Registry (GHCR), Docker Hub, or private registries using the <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.AddContainerRegistry" /> method.
 
 <Aside type="caution">
   The `AddContainerRegistry` API is experimental and may change in future releases. Use diagnostic code `ASPIRECOMPUTE003` to suppress the experimental warning. For more information, see [ASPIRECOMPUTE003](/diagnostics/aspirecompute003/).
@@ -717,7 +718,7 @@ You can configure your Aspire application to push container images to registries
 
 ### Configure a container registry
 
-Use the `AddContainerRegistry` method to define a container registry and the `WithContainerRegistry` method to associate resources with that registry:
+Use the `AddContainerRegistry` method to define a container registry and the <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" /> method to associate resources with that registry:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/compute/floci.mdx b/src/frontend/src/content/docs/integrations/compute/floci.mdx
index f9801f8c36..16f70f51b0 100644
--- a/src/frontend/src/content/docs/integrations/compute/floci.mdx
+++ b/src/frontend/src/content/docs/integrations/compute/floci.mdx
@@ -8,6 +8,7 @@ import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import ThemeImage from '@components/ThemeImage.astro';
 import flociIcon from '@assets/icons/floci-icon.svg';
 import flociLightIcon from '@assets/icons/floci-icon-light.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -82,7 +83,7 @@ This updates your `aspire.config.json` with the Floci hosting integration packag
 
 ### Add a Floci resource
 
-Each cloud has its own dedicated method — `AddFlociAws`/`addFlociAws`, `AddFlociAzure`/`addFlociAzure`, and `AddFlociGcp`/`addFlociGcp` — and each returns its own resource type. Add whichever clouds your app depends on; they can coexist in the same AppHost.
+Each cloud has its own dedicated method — <ApiReference name="Aspire.Hosting.FlociHostingExtension.AddFlociAws" />/`addFlociAws`, <ApiReference name="Aspire.Hosting.FlociHostingExtension.AddFlociAzure" />/`addFlociAzure`, and <ApiReference name="Aspire.Hosting.FlociHostingExtension.AddFlociGcp" />/`addFlociGcp` — and each returns its own resource type. Add whichever clouds your app depends on; they can coexist in the same AppHost.
 
 #### Add a Floci resource for AWS
 
@@ -377,7 +378,7 @@ Either approach persists resource state across container restarts and allows loc
 
 ### Use the cloud SDKs to interact with Floci
 
-Once a Floci resource is running and referenced by your service, use the matching cloud SDK as you normally would. `WithReference` in C# or the cloud-specific `withFloci*Reference` method in TypeScript injects provider-specific settings into the dependent resource.
+Once a Floci resource is running and referenced by your service, use the matching cloud SDK as you normally would. <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> in C# or the cloud-specific `withFloci*Reference` method in TypeScript injects provider-specific settings into the dependent resource.
 
 AWS and GCP SDKs read their emulator endpoint and region or project settings from the injected environment variables. Azure Storage clients don't automatically read `AZURE_STORAGE_CONNECTION_STRING`; construct the client from the injected value:
 
@@ -570,7 +571,7 @@ quarkus:
     level: DEBUG
 ```
 
-All Floci settings can also be set via `FLOCI_`-prefixed environment variables — `WithConfigFile`/`withConfigFile` is only needed for settings that don't have a dedicated extension method.
+All Floci settings can also be set via `FLOCI_`-prefixed environment variables — <ApiReference name="Aspire.Hosting.FlociHostingExtension.WithConfigFile" /> is only needed for settings that don't have a dedicated extension method.
 
 ### Configure TLS for AWS and Azure
 
diff --git a/src/frontend/src/content/docs/integrations/compute/k3s.mdx b/src/frontend/src/content/docs/integrations/compute/k3s.mdx
index 6a390be83e..e6f99e4ad9 100644
--- a/src/frontend/src/content/docs/integrations/compute/k3s.mdx
+++ b/src/frontend/src/content/docs/integrations/compute/k3s.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, FileTree, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import k3sIcon from '@assets/icons/k3s-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -110,7 +111,7 @@ The examples below show how to use the k3s integration APIs. They assume you alr
     - AppHost.cs Add the k3s cluster here
   - MyOperator/ Existing project
     - MyOperator.csproj
-  - k8s/ Manifests used with `AddK8sManifest`
+  - k8s/ Manifests used with <ApiReference name="Aspire.Hosting.K3sManifestBuilderExtensions.AddK8sManifest" />
     - app-config.yaml Kubernetes manifests
 </FileTree>
 
@@ -203,14 +204,14 @@ The available options are:
 
 | Method | Parameter / Effect |
 |---|---|
-| `AddK3sCluster(agentCount:)` | Number of worker nodes (`0` = single-node). Equivalent to `WithAgentCount`. |
+| `AddK3sCluster(agentCount:)` | Number of worker nodes (`0` = single-node). Equivalent to <ApiReference name="Aspire.Hosting.K3sBuilderExtensions.WithAgentCount" />. |
 | `WithAgentCount(n)` | Same as above, fluent alternative. The health check waits for all `1 + n` nodes to be `Ready`. |
 | `WithK3sVersion(tag)` | Overrides the k3s image tag, for example `v1.32.3-k3s1`. Synced to agents automatically. |
 | `WithPodSubnet(cidr)` | Sets `--cluster-cidr`. Defaults to the k3s built-in `10.42.0.0/16`. |
 | `WithServiceSubnet(cidr)` | Sets `--service-cidr`. Defaults to the k3s built-in `10.43.0.0/16`. |
 | `WithDisabledComponent(c)` | Passes `--disable=<c>`. Call multiple times for multiple components. |
 | `WithExtraArg(arg)` | Appends a raw argument to `k3s server`. |
-| `WithHelmImage(tag?, image?, registry?)` | Overrides the `alpine/helm` image used by `AddHelmRelease`. |
+| `WithHelmImage(tag?, image?, registry?)` | Overrides the `alpine/helm` image used by <ApiReference name="Aspire.Hosting.K3sHelmBuilderExtensions.AddHelmRelease" />. |
 | `WithKubectlImage(tag?, image?, registry?)` | Overrides the `alpine/kubectl` image used by `AddK8sManifest`. |
 | `WithDataVolume(name?)` | Mounts a named Docker volume at `/var/lib/rancher/k3s`. |
 | `WithLifetime(lifetime)` | Sets `ContainerLifetime.Persistent` or `Session` for the cluster and its agents. |
@@ -238,7 +239,7 @@ const cluster = await builder.addK3sCluster('k8s')
 </TabItem>
 </Tabs>
 
-`WithDataVolume` persists the k3s database, certificates, and node tokens across AppHost restarts. `WithLifetime(Persistent)` tells DCP to keep the Docker container alive between runs, making subsequent starts much faster.
+<ApiReference name="Aspire.Hosting.K3sBuilderExtensions.WithDataVolume" /> persists the k3s database, certificates, and node tokens across AppHost restarts. `WithLifetime(Persistent)` tells DCP to keep the Docker container alive between runs, making subsequent starts much faster.
 
 <Aside type="caution">
 With persistent containers, `agentCount` must stay constant across runs. Decreasing it leaves orphaned agent containers that fail to rejoin the cluster; delete them manually with `docker rm -f`.
@@ -288,8 +289,8 @@ await operator.withReference(cluster);
 
 Values are applied in this order, with the last one winning:
 
-1. `WithHelmValuesFile` — in declaration order
-2. `WithHelmValue` (`--set` flags) — always override files
+1. <ApiReference name="Aspire.Hosting.K3sHelmBuilderExtensions.WithHelmValuesFile" /> — in declaration order
+2. <ApiReference name="Aspire.Hosting.K3sHelmBuilderExtensions.WithHelmValue" /> (`--set` flags) — always override files
 
 Use `WithHelmValuesFile` for structured overrides (values with commas, braces, or backslashes). `WithHelmValue` is convenient for individual scalar overrides.
 
@@ -336,7 +337,7 @@ await monitoring.waitForCompletion(appConfig);
 
 ## Expose Kubernetes services
 
-`AddServiceEndpoint` starts an in-process WebSocket port-forward bound to `0.0.0.0:{allocatedPort}` — no `NodePort` or `LoadBalancer` configuration is required. The endpoint transitions to `Running` only after the target service has a ready pod.
+<ApiReference name="Aspire.Hosting.K3sServiceEndpointExtensions.AddServiceEndpoint" /> starts an in-process WebSocket port-forward bound to `0.0.0.0:{allocatedPort}` — no `NodePort` or `LoadBalancer` configuration is required. The endpoint transitions to `Running` only after the target service has a ready pod.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -387,7 +388,7 @@ Scheme is inferred from the port: `443` and `8443` resolve to `https`, all other
 
 ## Kubeconfig injection
 
-Both `K3sClusterResource` and `K3sServiceEndpointResource` implement `IResourceWithConnectionString`, so the standard `WithReference` overload handles credential injection automatically:
+Both `K3sClusterResource` and `K3sServiceEndpointResource` implement `IResourceWithConnectionString`, so the standard <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> overload handles credential injection automatically:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/compute/kubernetes.mdx b/src/frontend/src/content/docs/integrations/compute/kubernetes.mdx
index f72838b635..7736de1cf5 100644
--- a/src/frontend/src/content/docs/integrations/compute/kubernetes.mdx
+++ b/src/frontend/src/content/docs/integrations/compute/kubernetes.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Tabs, TabItem, Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import kubernetesIcon from '@assets/icons/kubernetes.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={kubernetesIcon}
@@ -115,7 +116,7 @@ await builder.build().run();
   With the `k8s` variable assigned, you can pass it to the compute environment API to
   disambiguate compute resources for solutions that define more than one. Otherwise, the `k8s`
   variable isn't required. This API is named `WithComputeEnvironment` in C# AppHosts and
-  `withComputeEnvironment` in TypeScript AppHosts.
+  <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" /> in TypeScript AppHosts.
 
   <Tabs syncKey="aspire-lang">
   <TabItem id="csharp" label="C#">
@@ -139,7 +140,7 @@ await builder.build().run();
 
 ## Configure Helm chart options
 
-You can configure the generated Helm chart using the `WithHelm` method, which provides a fluent `HelmChartOptions` builder:
+You can configure the generated Helm chart using the <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.WithHelm" /> method, which provides a fluent `HelmChartOptions` builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -187,7 +188,7 @@ The `WithHelm` method is the single configuration entry point for Helm chart set
 
 ## Configure a container registry
 
-A vanilla Kubernetes cluster doesn't know which container registry to use for your application images. Use `AddContainerRegistry` and `WithContainerRegistry` to specify a registry that is accessible from both your local machine and from the cluster:
+A vanilla Kubernetes cluster doesn't know which container registry to use for your application images. Use <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.AddContainerRegistry" /> and <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" /> to specify a registry that is accessible from both your local machine and from the cluster:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -215,7 +216,7 @@ await k8s.withContainerRegistry(registry);
 
 ## Persistent volumes
 
-To create durable storage in a Kubernetes cluster, model it as a first-class `KubernetesPersistentVolumeResource` with `AddPersistentVolume`. Then configure its storage class, capacity, and access modes, and bind it to workloads. At publish time, the volume renders as a `v1.PersistentVolumeClaim`, and any workload bound to it is promoted to a `StatefulSet`.
+To create durable storage in a Kubernetes cluster, model it as a first-class `KubernetesPersistentVolumeResource` with <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.AddPersistentVolume" />. Then configure its storage class, capacity, and access modes, and bind it to workloads. At publish time, the volume renders as a `v1.PersistentVolumeClaim`, and any workload bound to it is promoted to a `StatefulSet`.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -302,7 +303,7 @@ This C# resource-model type isn't exported as a typed TypeScript AppHost API. Fo
 
 ## Customize individual resources
 
-Use `PublishAsKubernetesService` to modify the generated Kubernetes resources for individual services:
+Use <ApiReference name="Aspire.Hosting.KubernetesServiceExtensions.PublishAsKubernetesService" /> to modify the generated Kubernetes resources for individual services:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -419,7 +420,7 @@ await service.publishAsKubernetesService(async (resource) => {
 </TabItem>
 </Tabs>
 
-The manifest handle returned by `addManifest` supports the following configuration methods:
+The manifest handle returned by <ApiReference name="Aspire.Hosting.KindManifestResourceBuilderExtensions.AddManifest" /> supports the following configuration methods:
 
 | Method | Description |
 |---|---|
diff --git a/src/frontend/src/content/docs/integrations/custom-integrations/hosting-integrations.mdx b/src/frontend/src/content/docs/integrations/custom-integrations/hosting-integrations.mdx
index 93d5a30e21..1e5fcad91c 100644
--- a/src/frontend/src/content/docs/integrations/custom-integrations/hosting-integrations.mdx
+++ b/src/frontend/src/content/docs/integrations/custom-integrations/hosting-integrations.mdx
@@ -20,6 +20,7 @@ import maildevEnvvar from '@assets/integrations/custom-integrations/maildev-envv
 import maildevEnvvarLight from '@assets/integrations/custom-integrations/maildev-envvar-light.png';
 import maildevEmails from '@assets/integrations/custom-integrations/maildev-emails.png';
 import maildevEmailsLight from '@assets/integrations/custom-integrations/maildev-emails-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire improves the development experience by providing reusable building blocks that can be used to quickly arrange application dependencies and expose them to your own code. One of the key building blocks of an Aspire-based application is the _resource_.
 
@@ -192,7 +193,7 @@ builder.AddProject<Projects.NewsletterService>("newsletterservice")
     .WithReference(maildev);
 ```
 
-To achieve this, you need a custom resource named `MailDevResource` which implements `IResourceWithConnectionString` so that consumers can use it with the `WithReference` extension to inject the connection details for the MailDev server as a connection string.
+To achieve this, you need a custom resource named `MailDevResource` which implements `IResourceWithConnectionString` so that consumers can use it with the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> extension to inject the connection details for the MailDev server as a connection string.
 
 MailDev is available as a container resource, so you'll also want to derive from `ContainerResource` so that we can make use of various pre-existing container-focused extensions in Aspire.
 
@@ -593,7 +594,7 @@ Here's how the flow of execution works:
 3. The `WithReference` wraps the resource in a `ConnectionStringReference` instance and the object is captured in an `EnvironmentCallbackAnnotation` which is evaluated after the Aspire project is built and starts running.
 4. As the process that references the connection string starts Aspire starts evaluating the expression. It first gets the `ConnectionStringReference` and calls its `GetValueAsync` method.
 5. The `GetValueAsync` method gets the value of the `IResourceWithConnectionString.ConnectionStringExpression` property to get the `ReferenceExpression` instance.
-6. The `ConnectionStringReference.GetValueAsync` method then calls `ReferenceExpression.GetValueAsync` to process the previously captured interpolated string.
+6. The `ConnectionStringReference.GetValueAsync` method then calls <ApiReference name="Aspire.Hosting.ApplicationModel.ReferenceExpression.GetValueAsync" /> to process the previously captured interpolated string.
 7. Because the interpolated string contains references to other reference types such as `EndpointReference` they're also evaluated and real value substituted (which at this time is now available).
 </Steps>
 
@@ -693,7 +694,7 @@ Because the `MailDevResource` implements `IResourceWithConnectionString` the man
 
 Aspire knows how to form this string because it looks at `IResourceWithConnectionString.ConnectionStringExpression` and builds up the final string via the `IManifestExpressionProvider` interface (in much the same way as the `IValueProvider` interface is used).
 
-The `MailDevResource` automatically gets included in the manifest because it's derived from `ContainerResource`. Resource authors can choose to suppress outputting content to the manifest by using the `ExcludeFromManifest` extension method on the resource builder.
+The `MailDevResource` automatically gets included in the manifest because it's derived from `ContainerResource`. Resource authors can choose to suppress outputting content to the manifest by using the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" /> extension method on the resource builder.
 
 ```diff lang="csharp" title="MailDevResourceBuilderExtensions.cs"
 public static IResourceBuilder<MailDevResource> AddMailDev(
diff --git a/src/frontend/src/content/docs/integrations/custom-integrations/secure-communication.mdx b/src/frontend/src/content/docs/integrations/custom-integrations/secure-communication.mdx
index 84f4dce5f2..1364fcb1e7 100644
--- a/src/frontend/src/content/docs/integrations/custom-integrations/secure-communication.mdx
+++ b/src/frontend/src/content/docs/integrations/custom-integrations/secure-communication.mdx
@@ -11,6 +11,7 @@ import maildevDetails from '@assets/integrations/custom-integrations/maildev-det
 import maildevDetailsLight from '@assets/integrations/custom-integrations/maildev-details-light.png';
 import newsletterDetails from '@assets/integrations/custom-integrations/newsletter-details.png';
 import newsletterDetailsLight from '@assets/integrations/custom-integrations/newsletter-details-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 This article is a continuation of two previous articles demonstrating the creation of [custom hosting integrations](/integrations/custom-integrations/hosting-integrations/) and [custom client integrations](/integrations/custom-integrations/client-integrations/).
 
@@ -179,7 +180,7 @@ internal static class MailDevContainerImageTags
 }
 ```
 
-The preceding code updates the `AddMailDev` extension method to include the `username` and `password` parameters. The `WithEnvironment` method is updated to include the `UserEnvVarName` and `PasswordEnvVarName` environment variables. These environment variables are used to set the MailDev username and password.
+The preceding code updates the `AddMailDev` extension method to include the `username` and `password` parameters. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> method is updated to include the `UserEnvVarName` and `PasswordEnvVarName` environment variables. These environment variables are used to set the MailDev username and password.
 
 ## Update the AppHost
 
diff --git a/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-connect.mdx b/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-connect.mdx
index c2c9f0b249..045f2fd86a 100644
--- a/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import clickhouseIcon from '@assets/icons/clickhouse-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={clickhouseIcon}
@@ -321,5 +322,5 @@ console.log('ClickHouse connection status:', result.success);
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. For more information, see [External parameters](/get-started/resources/).
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. For more information, see [External parameters](/get-started/resources/).
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-host.mdx b/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-host.mdx
index 72757ec18a..5deb99038b 100644
--- a/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/clickhouse/clickhouse-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import clickhouseIcon from '@assets/icons/clickhouse-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={clickhouseIcon}
@@ -81,7 +82,7 @@ var exampleProject = builder.AddProject<Projects.ExampleProject>("apiservice")
     }
     ```
 
-1. The `WithReference` call configures a connection in the consuming project named after the referenced database resource, such as `clickhousedb` in the preceding example.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the referenced database resource, such as `clickhousedb` in the preceding example.
 
 </Steps>
 
@@ -90,7 +91,7 @@ var exampleProject = builder.AddProject<Projects.ExampleProject>("apiservice")
 </Aside>
 
 <Aside type="tip">
-    If you'd rather connect to an existing ClickHouse server, call `AddConnectionString` instead. For more information, see [Reference existing resources](/get-started/resources/).
+    If you'd rather connect to an existing ClickHouse server, call <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> instead. For more information, see [Reference existing resources](/get-started/resources/).
 </Aside>
 
 ## Add ClickHouse resource with data volume
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/azure-cosmos-db/azure-cosmos-db-host.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/azure-cosmos-db/azure-cosmos-db-host.mdx
index 4ed3da1ee1..a7b5be7751 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/azure-cosmos-db/azure-cosmos-db-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/azure-cosmos-db/azure-cosmos-db-host.mdx
@@ -11,6 +11,7 @@ import ThemeImage from '@components/ThemeImage.astro';
 import cosmosDbIcon from '@assets/icons/azure-cosmosdb-icon.png';
 import cosmosResourceRelationships from '@assets/integrations/cloud/azure/cosmos-db/cosmos-resource-relationships.svg';
 import cosmosResourceRelationshipsLight from '@assets/integrations/cloud/azure/cosmos-db/cosmos-resource-relationships-light.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={cosmosDbIcon}
@@ -26,7 +27,7 @@ This article is the AppHost reference for the Azure Cosmos DB hosting integratio
 If you're new to the EF Core Azure Cosmos DB integration, start with the [Get started with the EF Core Azure Cosmos DB integrations](/integrations/databases/efcore/azure-cosmos-db/azure-cosmos-db-get-started/) guide. For how C# consuming apps register a `DbContext` from the resources this page exposes, see [Connect to Azure Cosmos DB with EF Core](../azure-cosmos-db-connect/).
 
 <Aside type="note">
-  The AppHost hosting integration is **shared** between the direct `CosmosClient` integration and this EF Core integration — both use the same `Aspire.Hosting.Azure.CosmosDB` package and the same `AddAzureCosmosDB` API. The difference is in the client-side package: EF Core apps install `Aspire.Microsoft.EntityFrameworkCore.Cosmos` and call `AddCosmosDbContext`, while direct SDK apps install `Aspire.Microsoft.Azure.Cosmos` and call `AddAzureCosmosClient`. For the full AppHost reference including TypeScript examples, see [Azure Cosmos DB Hosting integration](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/).
+  The AppHost hosting integration is **shared** between the direct `CosmosClient` integration and this EF Core integration — both use the same `Aspire.Hosting.Azure.CosmosDB` package and the same <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.AddAzureCosmosDB" /> API. The difference is in the client-side package: EF Core apps install `Aspire.Microsoft.EntityFrameworkCore.Cosmos` and call `AddCosmosDbContext`, while direct SDK apps install `Aspire.Microsoft.Azure.Cosmos` and call `AddAzureCosmosClient`. For the full AppHost reference including TypeScript examples, see [Azure Cosmos DB Hosting integration](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/).
 </Aside>
 
 ## Installation
@@ -106,7 +107,7 @@ const cosmos = await builder.addAzureCosmosDb("cosmos-db");
 </Tabs>
 
 <Aside type="caution">
-  When you call `AddAzureCosmosDB`, it implicitly calls `AddAzureProvisioning` — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
+  When you call `AddAzureCosmosDB`, it implicitly calls <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources dynamically during app startup. The app must configure the appropriate subscription and location. For more information, see [Local provisioning: Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
 </Aside>
 
 ## Add Azure Cosmos DB database and container resources
@@ -161,7 +162,7 @@ For more information, see [Databases, containers, and items in Azure Cosmos DB](
 
 ## Add Azure Cosmos DB emulator resource
 
-To run locally without an Azure subscription, chain a call to `RunAsEmulator` on the Cosmos DB resource builder:
+To run locally without an Azure subscription, chain a call to <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsEmulator" /> on the Cosmos DB resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -194,7 +195,7 @@ For the full emulator configuration reference — gateway port, data volumes, pa
 
 ## Connect to an existing Azure Cosmos DB account
 
-You might have an existing Azure Cosmos DB account that you want to connect to. Chain a call to `AsExisting` to annotate that your resource is an existing resource:
+You might have an existing Azure Cosmos DB account that you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your resource is an existing resource:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -215,7 +216,7 @@ For more information on treating Azure Cosmos DB resources as existing resources
 
 ## Provisioning-generated Bicep
 
-When you publish your app, Aspire generates Bicep for the Cosmos DB account alongside the manifest file. For the full generated Bicep and infrastructure customization reference (including `ConfigureInfrastructure`), see [Azure Cosmos DB Hosting integration](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/#provisioning-generated-bicep).
+When you publish your app, Aspire generates Bicep for the Cosmos DB account alongside the manifest file. For the full generated Bicep and infrastructure customization reference (including <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />), see [Azure Cosmos DB Hosting integration](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/#provisioning-generated-bicep).
 
 ## Hosting integration health checks
 
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-get-started.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-get-started.mdx
index 75fba62fb7..f8cf592a2c 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand why you use the Aspire Azure SQL EF Core integrations an
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlServerIcon}
@@ -22,7 +23,7 @@ import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
 
 Adding Azure SQL through Aspire — rather than managing connection strings and Azure resources by hand — gives you:
 
-- **Zero-config local development.** Aspire can run Azure SQL locally using the SQL Server container image via `RunAsContainer`, with credentials generated automatically.
+- **Zero-config local development.** Aspire can run Azure SQL locally using the SQL Server container image via <ApiReference name="Aspire.Hosting.AzureSqlExtensions.RunAsContainer" />, with credentials generated automatically.
 - **Seamless cloud deployment.** When you're ready to deploy, the same AppHost model provisions a real Azure SQL Database with managed identity access — no code changes needed.
 - **Consistent connection info.** Once you reference the database from a consuming app, Aspire injects connection properties as environment variables in a predictable format.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the Aspire dashboard and your orchestrator can tell when the server is ready.
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-host.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-host.mdx
index fe9082cb6c..7cadec5557 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/azure-sql/azure-sql-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import sqlServerIcon from '@assets/icons/azure-sqlserver-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlServerIcon}
@@ -73,7 +74,7 @@ This updates your `aspire.config.json` with the Azure SQL Database hosting integ
 
 ## Add Azure SQL server resource and database resource
 
-In your AppHost project, call `AddAzureSqlServer` to add and return an Azure SQL server resource builder. Chain a call to `AddDatabase` to add an Azure SQL database resource:
+In your AppHost project, call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.AddAzureSqlServer" /> to add and return an Azure SQL server resource builder. Chain a call to <ApiReference name="Aspire.Hosting.AzureSqlExtensions.AddDatabase" /> to add an Azure SQL database resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -114,13 +115,13 @@ await builder.build().run();
 
 1. Calling `AddDatabase` (or `addDatabase`) on the returned resource builder models a named database within that server.
 
-1. The `WithReference` (or `withReference`) call configures a named connection in the consuming project that matches the database resource name.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a named connection in the consuming project that matches the database resource name.
 
 </Steps>
 
 <Aside type="caution">
   When you call `AddAzureSqlServer`, it implicitly calls
-  `AddAzureProvisioning` — which adds support for generating Azure resources
+  <ApiReference name="Aspire.Hosting.AzureProvisionerExtensions.AddAzureProvisioning" /> — which adds support for generating Azure resources
   dynamically during app startup. The app must configure the appropriate
   subscription and location. For more information, see [Local provisioning:
   Configuration](/integrations/cloud/azure/local-provisioning/#configuration).
@@ -132,7 +133,7 @@ await builder.build().run();
 
 ## Connect to an existing Azure SQL server
 
-You might have an existing Azure SQL Database service that you want to connect to. Chain a call to `AsExisting` (or `asExisting`) to annotate that your resource already exists in Azure:
+You might have an existing Azure SQL Database service that you want to connect to. Chain a call to <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" /> to annotate that your resource already exists in Azure:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -179,7 +180,7 @@ For more information on treating Azure SQL resources as existing resources, see
 
 ## Run Azure SQL server resource as a container
 
-During local development and testing, you can run an Azure SQL server as a local SQL Server container instead of provisioning an actual Azure resource. Call `RunAsContainer` (or `runAsContainer`) to switch to a local container:
+During local development and testing, you can run an Azure SQL server as a local SQL Server container instead of provisioning an actual Azure resource. Call <ApiReference name="Aspire.Hosting.AzureSqlExtensions.RunAsContainer" /> to switch to a local container:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/migrations.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/migrations.mdx
index 2b5a74be26..4035eefc77 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/migrations.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/migrations.mdx
@@ -11,6 +11,7 @@ import { Image } from 'astro:assets';
 import dotnetIcon from '@assets/icons/dotnet.svg';
 import dashboardPostMigrationDark from '@assets/integrations/efcore/dashboard-post-migration-dark.png';
 import dashboardPostMigrationLight from '@assets/integrations/efcore/dashboard-post-migration-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -394,7 +395,7 @@ The migration service is created, but it needs to be added to the Aspire AppHost
     This code enlists the *`SupportTicketApi.MigrationService`* project as a service in the Aspire AppHost. It also ensures that the API resource doesn't run until the migrations are complete.
 
     :::note
-    In the preceding code, the call to `AddDatabase` adds a representation of a SQL Server database to the Aspire application model with a connection string. It *doesn't* create a database in the SQL Server container. To ensure that the database is created, the sample project calls the EF Core `IDatabaseCreator.EnsureCreated` method from the support ticket API's `Program.cs` file.
+    In the preceding code, the call to <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.AddDatabase" /> adds a representation of a SQL Server database to the Aspire application model with a connection string. It *doesn't* create a database in the SQL Server container. To ensure that the database is created, the sample project calls the EF Core `IDatabaseCreator.EnsureCreated` method from the support ticket API's `Program.cs` file.
     :::
 
     :::tip
@@ -546,7 +547,7 @@ The [Aspire Shop](https://learn.microsoft.com/samples/microsoft/aspire-samples/a
 
 ## Automated EF migrations with `AddEFMigrations`
 
-In addition to creating a dedicated worker service as described above, Aspire provides a first-class AppHost API for managing EF Core migrations: `AddEFMigrations`. This API integrates migration execution directly into the AppHost orchestration and the Aspire publishing pipeline, without requiring a separate migration service project.
+In addition to creating a dedicated worker service as described above, Aspire provides a first-class AppHost API for managing EF Core migrations: <ApiReference name="Aspire.Hosting.EFResourceBuilderExtensions.AddEFMigrations" />. This API integrates migration execution directly into the AppHost orchestration and the Aspire publishing pipeline, without requiring a separate migration service project.
 
 ### Add the package
 
@@ -580,7 +581,7 @@ var apiMigrations = api.AddEFMigrations("api-migrations")
 
 ### Run migrations on startup
 
-To apply migrations automatically when running locally with [`aspire run`](/reference/cli/commands/aspire-run/), chain `RunDatabaseUpdateOnStart()`:
+To apply migrations automatically when running locally with [`aspire run`](/reference/cli/commands/aspire-run/), chain <ApiReference name="Aspire.Hosting.EFMigrationResourceBuilderExtensions.RunDatabaseUpdateOnStart" />:
 
 ```csharp title="AppHost.cs"
 var apiMigrations = api.AddEFMigrations("api-migrations")
@@ -605,7 +606,7 @@ When `RunDatabaseUpdateOnStart()` is called, a health check is registered for th
 
 ### Publish migration artifacts
 
-To generate migration artifacts during [`aspire publish`](/reference/cli/commands/aspire-publish/), use `PublishAsMigrationScript` or `PublishAsMigrationBundle`:
+To generate migration artifacts during [`aspire publish`](/reference/cli/commands/aspire-publish/), use <ApiReference name="Aspire.Hosting.EFMigrationResourceBuilderExtensions.PublishAsMigrationScript" /> or <ApiReference name="Aspire.Hosting.EFMigrationResourceBuilderExtensions.PublishAsMigrationBundle" />:
 
 ```csharp title="AppHost.cs"
 // Generate both a SQL script and a self-contained bundle during publish
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/mongodb/mongodb-efcore-connect.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/mongodb/mongodb-efcore-connect.mdx
index 3d225a1d35..5b1f97821c 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/mongodb/mongodb-efcore-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/mongodb/mongodb-efcore-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import mongodbIcon from '@assets/icons/mongodb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mongodbIcon}
@@ -67,7 +68,7 @@ builder.AddMongoDbContext<MyDbContext>("mongodb", "mydb");
 ```
 
 <Aside type="note">
-  When using `AddDatabase` in the AppHost, the database name is included in the generated connection string, so you typically don't need to specify it separately.
+  When using <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.AddDatabase" /> in the AppHost, the database name is included in the generated connection string, so you typically don't need to specify it separately.
 </Aside>
 
 ### Enrich a MongoDB database context
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/mysql/mysql-connect.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/mysql/mysql-connect.mdx
index 0c44f52ef1..f86cf6aace 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/mysql/mysql-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/mysql/mysql-connect.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import { Image } from 'astro:assets';
 import mysqlIcon from '@assets/icons/mysqlconnector-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mysqlIcon}
@@ -95,7 +96,7 @@ The `settings` parameter is an instance of the `MySqlEntityFrameworkCoreSettings
 
 ### Connection properties
 
-When you use the `WithReference` method to pass a MySQL server or database resource from the AppHost project to a consuming project, Aspire exposes each property as an environment variable named `[RESOURCE]_[PROPERTY]`. For instance, the `ConnectionString` property of a resource called `mysqldb` becomes `MYSQLDB_CONNECTIONSTRING`.
+When you use the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> method to pass a MySQL server or database resource from the AppHost project to a consuming project, Aspire exposes each property as an environment variable named `[RESOURCE]_[PROPERTY]`. For instance, the `ConnectionString` property of a resource called `mysqldb` becomes `MYSQLDB_CONNECTIONSTRING`.
 
 #### MySQL server
 
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/oracle/oracle-host.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/oracle/oracle-host.mdx
index 328e07dbcc..c0b1632062 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/oracle/oracle-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/oracle/oracle-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import oracleIcon from '@assets/icons/oracle-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={oracleIcon}
@@ -52,7 +53,7 @@ Or, choose a manual installation approach:
 
 ## Add Oracle server and database resources
 
-In the AppHost project, call `AddOracle` to add and return an Oracle server resource builder. Chain a call to `AddDatabase` on the returned resource builder to add an Oracle database to the server resource:
+In the AppHost project, call <ApiReference name="Aspire.Hosting.OracleDatabaseBuilderExtensions.AddOracle" /> to add and return an Oracle server resource builder. Chain a call to <ApiReference name="Aspire.Hosting.OracleDatabaseBuilderExtensions.AddDatabase" /> on the returned resource builder to add an Oracle database to the server resource:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -77,7 +78,7 @@ builder.AddProject<Projects.ExampleProject>()
 
 1. The Oracle server resource includes default credentials with a randomly generated `password` using the `CreateDefaultPasswordParameter` method.
 
-1. The `WithReference` call configures a connection in the consuming project named after the referenced database resource — `"oracledb"` in the preceding example.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the referenced database resource — `"oracledb"` in the preceding example.
 
 </Steps>
 
@@ -120,7 +121,7 @@ For more information, see [External parameters](/get-started/resources/).
 
 ## Add Oracle resource with data volume
 
-To add a data volume to the Oracle resource, call the `WithDataVolume` method:
+To add a data volume to the Oracle resource, call the <ApiReference name="Aspire.Hosting.OracleDatabaseBuilderExtensions.WithDataVolume" /> method:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -146,7 +147,7 @@ The password is stored in the data volume. When using a data volume and if the p
 
 ## Add Oracle resource with data bind mount
 
-To add a data bind mount to the Oracle resource, call the `WithDataBindMount` method:
+To add a data bind mount to the Oracle resource, call the <ApiReference name="Aspire.Hosting.OracleDatabaseBuilderExtensions.WithDataBindMount" /> method:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/postgres/postgresql-connect.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/postgres/postgresql-connect.mdx
index 36f6d1ac3e..977607be1a 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/postgres/postgresql-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/postgres/postgresql-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import postgresIcon from '@assets/icons/postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={postgresIcon}
@@ -23,7 +24,7 @@ EF Core is a .NET-only technology. If your consuming app is written in Go, Pytho
 
 ## Connection properties
 
-When you reference a PostgreSQL resource from your AppHost using `WithReference`, Aspire injects the connection information into the consuming app as environment variables. Aspire exposes each property as an environment variable named `[RESOURCE]_[PROPERTY]`. For instance, the `ConnectionString` property of a resource called `postgresdb` becomes `POSTGRESDB_CONNECTIONSTRING`.
+When you reference a PostgreSQL resource from your AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, Aspire injects the connection information into the consuming app as environment variables. Aspire exposes each property as an environment variable named `[RESOURCE]_[PROPERTY]`. For instance, the `ConnectionString` property of a resource called `postgresdb` becomes `POSTGRESDB_CONNECTIONSTRING`.
 
 ### PostgreSQL server
 
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
index f0515f5ec5..f863db8014 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
@@ -6,6 +6,7 @@ description: Learn how to seed database data in Aspire projects using SQL script
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import dotnetIcon from '@assets/icons/dotnet.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -52,7 +53,7 @@ The recommended method for executing database seeding scripts depends on the dat
 <Tabs syncKey="efcore-db-provider">
 <TabItem label="SQL Server">
 
-With Aspire, you can use the `WithCreationScript` method to ensure a T-SQL script is run when the database is created. Add SQL code to this script that creates and populates the database, the necessary tables, and other database objects.
+With Aspire, you can use the <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithCreationScript" /> method to ensure a T-SQL script is run when the database is created. Add SQL code to this script that creates and populates the database, the necessary tables, and other database objects.
 
 The following code is an example T-SQL script that creates and populates an address book database:
 
@@ -157,7 +158,7 @@ var addressBookDb = sqlserver.AddDatabase("AddressBook")
 The preceding code:
 
 - Create a SQL Server container by calling `builder.AddSqlServer()`.
-- Ensures that data is persisted across debugging sessions by calling `WithDataVolume()` and `WithLifetime(ContainerLifetime.Persistent)`.
+- Ensures that data is persisted across debugging sessions by calling <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> and `WithLifetime(ContainerLifetime.Persistent)`.
 - Obtains the path to the T-SQL script in the output folder.
 - Calls `WithCreationScript()` to create and seed the database.
 
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/sql-server/sql-server-connect.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/sql-server/sql-server-connect.mdx
index 5a850e2a54..69abf84be2 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/sql-server/sql-server-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/sql-server/sql-server-connect.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import sqlIcon from '@assets/icons/sql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlIcon}
@@ -76,7 +77,7 @@ builder.AddSqlServerDbContext<ExampleDbContext>(connectionName: "database");
 ```
 
 <Aside type="tip">
-The `connectionName` parameter must match the name used when adding the SQL Server database resource in the AppHost project. In other words, when you call `AddDatabase` and provide a name of `database` that same name should be used when calling `AddSqlServerDbContext`. For more information, see [Add SQL Server resource and database resource](/integrations/databases/sql-server/sql-server-host/#add-sql-server-resource).
+The `connectionName` parameter must match the name used when adding the SQL Server database resource in the AppHost project. In other words, when you call <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.AddDatabase" /> and provide a name of `database` that same name should be used when calling `AddSqlServerDbContext`. For more information, see [Add SQL Server resource and database resource](/integrations/databases/sql-server/sql-server-host/#add-sql-server-resource).
 </Aside>
 
 To retrieve `ExampleDbContext` object from a service:
diff --git a/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-connect.mdx b/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-connect.mdx
index 65af33f090..821920476b 100644
--- a/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import elasticIcon from '@assets/icons/elastic-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={elasticIcon}
@@ -56,7 +57,7 @@ This is the **recommended approach** because Aspire manages the resource lifecyc
 
 When your AppHost uses `builder.AddConnectionString("elasticsearch")` to reference an existing, pre-configured Elasticsearch instance outside Aspire's control, only a **single connection string** environment variable is injected:
 
-- `ConnectionStrings__elasticsearch` = the full connection string provided to `AddConnectionString`
+- `ConnectionStrings__elasticsearch` = the full connection string provided to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />
 
 With this approach, there are **no individual property variables** (`ELASTICSEARCH_URI`). Consuming apps must use the connection string directly or parse it themselves to extract the necessary connection details.
 
@@ -314,5 +315,5 @@ console.log('Elasticsearch connection status:', response);
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [External parameters](/get-started/resources/) for more information.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [External parameters](/get-started/resources/) for more information.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-host.mdx b/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-host.mdx
index 558d299da6..ebb11c9f9a 100644
--- a/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/elasticsearch/elasticsearch-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import elasticIcon from '@assets/icons/elastic-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={elasticIcon}
@@ -194,7 +195,7 @@ When no `password` parameter is provided, Aspire generates a strong password aut
 
 ## Connect to an existing Elasticsearch instance
 
-To reference an externally managed Elasticsearch instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed Elasticsearch instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/kurrentdb/kurrentdb-connect.mdx b/src/frontend/src/content/docs/integrations/databases/kurrentdb/kurrentdb-connect.mdx
index a7cae39b98..03dcb7a7c0 100644
--- a/src/frontend/src/content/docs/integrations/databases/kurrentdb/kurrentdb-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/kurrentdb/kurrentdb-connect.mdx
@@ -9,6 +9,7 @@ import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import kurrentIcon from '@assets/icons/kurrent-icon.png';
 import kurrentLightIcon from '@assets/icons/kurrent-light-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -288,5 +289,5 @@ const client = KurrentDBClient.connectionString(
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the Aspire AppHost documentation for details.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the Aspire AppHost documentation for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-connect.mdx b/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-connect.mdx
index 82d14ec8fc..7e5d8c63f1 100644
--- a/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-connect.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, TabItem, Tabs } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import meilisearchIcon from '@assets/icons/meilisearch-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -239,5 +240,5 @@ const client = new MeiliSearch({
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the [AppHost reference](/get-started/app-host/) for details.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the [AppHost reference](/get-started/app-host/) for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-host.mdx b/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-host.mdx
index b3c72d8cf0..1a4e5352b0 100644
--- a/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/meilisearch/meilisearch-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Steps, TabItem, Tabs } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import meilisearchIcon from '@assets/icons/meilisearch-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -117,7 +118,7 @@ await builder.build().run();
 
 1. The Meilisearch resource is configured with a randomly generated master key by default. To set an explicit master key, see [Add Meilisearch resource with master key parameter](#add-meilisearch-resource-with-master-key-parameter).
 
-1. The `WithReference` call configures a connection in the consuming project named after the referenced Meilisearch resource, such as `meilisearch` in the preceding example.
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the referenced Meilisearch resource, such as `meilisearch` in the preceding example.
 
 </Steps>
 
@@ -127,7 +128,7 @@ await builder.build().run();
 
 ## Add Meilisearch resource with data volume
 
-To add a data volume to the Meilisearch resource, call the `WithDataVolume` method:
+To add a data volume to the Meilisearch resource, call the <ApiReference name="Aspire.Hosting.MeilisearchBuilderExtensions.WithDataVolume" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -168,7 +169,7 @@ The data volume is used to persist Meilisearch data outside the lifecycle of its
 
 ## Add Meilisearch resource with data bind mount
 
-To add a data bind mount to the Meilisearch resource, call the `WithDataBindMount` method:
+To add a data bind mount to the Meilisearch resource, call the <ApiReference name="Aspire.Hosting.MeilisearchBuilderExtensions.WithDataBindMount" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/milvus/milvus-host.mdx b/src/frontend/src/content/docs/integrations/databases/milvus/milvus-host.mdx
index 2a84f01119..e3dad16943 100644
--- a/src/frontend/src/content/docs/integrations/databases/milvus/milvus-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/milvus/milvus-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import milvusIcon from '@assets/icons/milvus-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={milvusIcon}
@@ -132,7 +133,7 @@ The Milvus container can be slow to start, so it's best to use a persistent life
 </Aside>
 
 <Aside type="tip">
-If you'd rather connect to an existing Milvus server, call `AddConnectionString` instead. For more information, see [Reference existing resources](/get-started/resources/).
+If you'd rather connect to an existing Milvus server, call <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> instead. For more information, see [Reference existing resources](/get-started/resources/).
 </Aside>
 
 <ContainerImages package="Aspire.Hosting.Milvus" only="Milvus" />
@@ -290,7 +291,7 @@ Data bind mounts rely on the host machine's filesystem to persist the Milvus dat
 
 ## Add Attu resource
 
-[Attu](https://zilliz.com/attu) is a graphical user interface (GUI) and management tool for Milvus. To add an Attu container alongside your Milvus server, call `WithAttu` (or `withAttu`):
+[Attu](https://zilliz.com/attu) is a graphical user interface (GUI) and management tool for Milvus. To add an Attu container alongside your Milvus server, call <ApiReference name="Aspire.Hosting.MilvusBuilderExtensions.WithAttu" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-extensions.mdx b/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-extensions.mdx
index f7dec1a9d9..055114c810 100644
--- a/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-extensions.mdx
@@ -7,6 +7,7 @@ import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import mongodbIcon from '@assets/icons/mongodb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -47,7 +48,7 @@ For TypeScript AppHosts, add the Community Toolkit MongoDB extensions package to
 
 ### DbGate management UI
 
-To add the [DbGate](https://dbgate.org/) management UI, decorate the official `MongoDBServerResource` builder with `WithDbGate` / `withDbGate`:
+To add the [DbGate](https://dbgate.org/) management UI, decorate the official `MongoDBServerResource` builder with <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithDbGate" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -88,7 +89,7 @@ This adds a new DbGate resource to the AppHost which is available from the Aspir
 
 ### dbx management UI
 
-[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use `WithDbx` / `withDbx` to add a dbx child resource configured for the MongoDB server:
+[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithDbx" /> to add a dbx child resource configured for the MongoDB server:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-host.mdx b/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-host.mdx
index 5795a0062d..6e18816728 100644
--- a/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/mongodb/mongodb-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import mongodbIcon from '@assets/icons/mongodb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mongodbIcon}
@@ -125,7 +126,7 @@ The MongoDB container can be slow to start, so it's best to use a persistent lif
 </Aside>
 
 <Aside type="tip">
-If you'd rather connect to an existing MongoDB server, call `AddConnectionString` instead. For more information, see [Reference existing resources](/get-started/resources/).
+If you'd rather connect to an existing MongoDB server, call <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> instead. For more information, see [Reference existing resources](/get-started/resources/).
 </Aside>
 
 <Aside type="note">
@@ -136,7 +137,7 @@ If you'd rather connect to an existing MongoDB server, call `AddConnectionString
 
 ## Automatic TLS and migration from earlier versions
 
-Starting in **Aspire 13.6**, MongoDB participates in Aspire's shared certificate configuration during local runs. This applies to ordinary `AddMongoDB` / `addMongoDB` resources, **not just replica sets**. When a certificate is configured and available, normally the ASP.NET Core developer certificate under the default settings, Aspire starts MongoDB with `--tlsMode requireTLS` and adds `tls=true` to its generated connection string. Without an available configured certificate, the standalone server uses plaintext.
+Starting in **Aspire 13.6**, MongoDB participates in Aspire's shared certificate configuration during local runs. This applies to ordinary <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.AddMongoDB" /> resources, **not just replica sets**. When a certificate is configured and available, normally the ASP.NET Core developer certificate under the default settings, Aspire starts MongoDB with `--tlsMode requireTLS` and adds `tls=true` to its generated connection string. Without an available configured certificate, the standalone server uses plaintext.
 
 Existing clients that connected without TLS can stop working after upgrading. Use the **complete Aspire-generated connection string**, such as the `MONGODB_URI` environment variable for a database resource named `mongodb`, rather than rebuilding a URI from `Host` and `Port`. The generated URI preserves TLS and other connection options, but clients still need to validate the server certificate.
 
@@ -191,7 +192,7 @@ builder.Build().Run();
 </TabItem>
 </Tabs>
 
-The certificate API is experimental and reports [ASPIRECERTIFICATES001](/diagnostics/aspirecertificates001/) in C#. This opt-out also works when the server uses the [simple single-member replica-set configuration](#enable-transactions-and-change-streams-with-a-single-member-replica-set): configure `WithReplicaSet()` / `withReplicaSet()` on the same server. That path doesn't require TLS.
+The certificate API is experimental and reports [ASPIRECERTIFICATES001](/diagnostics/aspirecertificates001/) in C#. This opt-out also works when the server uses the [simple single-member replica-set configuration](#enable-transactions-and-change-streams-with-a-single-member-replica-set): configure <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithReplicaSet" /> on the same server. That path doesn't require TLS.
 
 :::caution
 This opt-out disables transport encryption. Use it only as an explicit local-development choice, not as a production security configuration. Don't apply it to members of an advanced `AddMongoDBReplicaSet(...).WithMember(...)` configuration, which requires TLS.
@@ -248,7 +249,7 @@ The advanced path is for local multi-member experiments. Disabling ambient defau
 
 ### Run versus publish
 
-Automatic developer-certificate configuration applies to **local run mode**. Published MongoDB containers don't automatically receive the same certificate configuration; configure production transport security for your deployment separately. Both replica-set paths, keyfile configuration, and explicit MongoDB TLS configuration APIs such as `WithTlsMode` reject publish mode because their deployment support hasn't been implemented.
+Automatic developer-certificate configuration applies to **local run mode**. Published MongoDB containers don't automatically receive the same certificate configuration; configure production transport security for your deployment separately. Both replica-set paths, keyfile configuration, and explicit MongoDB TLS configuration APIs such as <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithTlsMode" /> reject publish mode because their deployment support hasn't been implemented.
 
 ## Add MongoDB server resource with parameters
 
@@ -323,7 +324,7 @@ For more information, see [External parameters](/get-started/resources/).
 
 ## Add MongoDB server resource with data volume
 
-To add a data volume to the MongoDB server resource, call the `WithDataVolume` method:
+To add a data volume to the MongoDB server resource, call the <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithDataVolume" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -378,7 +379,7 @@ You can resolve the problem by deploying to a Kubernetes cluster, such as Azure
 
 ## Add MongoDB server resource with data bind mount
 
-To add a data bind mount to the MongoDB server resource, call the `WithDataBindMount` method:
+To add a data bind mount to the MongoDB server resource, call the <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithDataBindMount" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -467,7 +468,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 ```
 
 :::note
-The TypeScript AppHost exposes `withInitFiles(source)` instead of `withInitBindMount(source)`. The `withInitFiles` method copies the specified files into the container's init folder, whereas the C# `WithInitBindMount` performs a host bind mount. The functional outcome — running initialization scripts at container startup — is the same.
+The TypeScript AppHost exposes `withInitFiles(source)` instead of `withInitBindMount(source)`. The <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithInitFiles" /> method copies the specified files into the container's init folder, whereas the C# `WithInitBindMount` performs a host bind mount. The functional outcome — running initialization scripts at container startup — is the same.
 :::
 </TabItem>
 </Tabs>
@@ -476,7 +477,7 @@ MongoDB executes any JavaScript or shell scripts found in the init folder when t
 
 ## Enable transactions and change streams with a single-member replica set
 
-MongoDB transactions and change streams require replica-set mode, even for a single server. Call `WithReplicaSet` (C#) or `withReplicaSet` (TypeScript) directly on the `MongoDBServerResource` to configure **and initialize** a single-member replica set, without creating a separate logical replica-set resource or configuring split-horizon TLS. Continue using `AddDatabase`, `WithReference`, and `WaitFor` as usual — initialization runs during the resource lifecycle, and readiness waits for both initialization and primary election, so consumers can use transactions and change streams as soon as `WaitFor` completes.
+MongoDB transactions and change streams require replica-set mode, even for a single server. Call `WithReplicaSet` (C#) or `withReplicaSet` (TypeScript) directly on the `MongoDBServerResource` to configure **and initialize** a single-member replica set, without creating a separate logical replica-set resource or configuring split-horizon TLS. Continue using <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.AddDatabase" />, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> as usual — initialization runs during the resource lifecycle, and readiness waits for both initialization and primary election, so consumers can use transactions and change streams as soon as `WaitFor` completes.
 
 <Aside type="caution">
 `WithReplicaSet` and the other replica-set APIs are experimental and marked `ASPIREMONGODB001`. C# AppHosts must explicitly suppress this diagnostic where these APIs are used, and the APIs may change in a future release.
@@ -541,7 +542,7 @@ const mongo = await builder.addMongoDB("mongo").withReplicaSet({ name: "app-rs"
 
 Repeated calls with the same configuration are a no-op, but a conflicting name throws. Consumers use the server's normal endpoint with `directConnection=true` and the driver's default primary read preference — no topology discovery, split-horizon addresses, or fixed host ports are required.
 
-MongoDB requires a keyfile when authentication and replication are both enabled, even with a single member. `WithReplicaSet` generates a secret keyfile automatically when none is configured. To supply your own keyfile content, configure `WithKeyFile` with a secret parameter **before** calling `WithReplicaSet`:
+MongoDB requires a keyfile when authentication and replication are both enabled, even with a single member. `WithReplicaSet` generates a secret keyfile automatically when none is configured. To supply your own keyfile content, configure <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithKeyFile" /> with a secret parameter **before** calling `WithReplicaSet`:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -571,12 +572,12 @@ The parameter supplies the keyfile's **contents**, not a host file path. The con
 When using `WithDataVolume` or `WithDataBindMount` to persist data, keep the configured credentials and replica set identity unchanged when reusing existing data — MongoDB only applies initial credentials to an empty data directory. With the default set name, renaming the Aspire resource also changes the set identity. Existing compatible single-member data is reused without forced reconfiguration, but mismatched set names, member addresses, or multi-member data are rejected.
 
 <Aside type="note">
-For local multi-member replication experiments, `AddMongoDBReplicaSet(...).WithMember(...)` remains available as a separate experimental API. Both replica-set paths are supported only for local runs and reject publish mode. The advanced API is intended for exploring replication or elections across multiple containers, not for simply enabling transactions or change streams. Don't call `WithReplicaSet` on servers that will be added as members to an `AddMongoDBReplicaSet` resource.
+For local multi-member replication experiments, `AddMongoDBReplicaSet(...).WithMember(...)` remains available as a separate experimental API. Both replica-set paths are supported only for local runs and reject publish mode. The advanced API is intended for exploring replication or elections across multiple containers, not for simply enabling transactions or change streams. Don't call `WithReplicaSet` on servers that will be added as members to an <ApiReference name="Aspire.Hosting.MongoDBReplicaSetBuilderExtensions.AddMongoDBReplicaSet" /> resource.
 </Aside>
 
 ## Add MongoDB Express resource
 
-[MongoDB Express](https://github.com/mongo-express/mongo-express) is a web-based MongoDB admin user interface. To add a MongoDB Express resource that corresponds to the `docker.io/library/mongo-express` container image, call the `WithMongoExpress` method on the MongoDB server resource:
+[MongoDB Express](https://github.com/mongo-express/mongo-express) is a web-based MongoDB admin user interface. To add a MongoDB Express resource that corresponds to the `docker.io/library/mongo-express` container image, call the <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithMongoExpress" /> method on the MongoDB server resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -723,7 +724,7 @@ await builder.build().run();
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the MongoDB server resource to enable a **REPL** command that opens `mongosh` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithRepl" /> to the MongoDB server resource to enable a **REPL** command that opens `mongosh` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-extensions.mdx b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-extensions.mdx
index 6e82fc84ca..63d1302b79 100644
--- a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-extensions.mdx
@@ -7,6 +7,7 @@ import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import mysqlIcon from '@assets/icons/mysqlconnector-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -48,7 +49,7 @@ For TypeScript AppHosts, add the Community Toolkit MySQL extensions package to `
 
 ### DbGate management UI
 
-To add the [DbGate](https://dbgate.org/) management UI, decorate the official `MySqlServerResource` builder with `WithDbGate` / `withDbGate`:
+To add the [DbGate](https://dbgate.org/) management UI, decorate the official `MySqlServerResource` builder with <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithDbGate" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -89,7 +90,7 @@ This adds a new DbGate resource to the AppHost which is available from the Aspir
 
 ### Adminer management UI
 
-To add the [Adminer](https://adminer.org/) management UI, decorate the official `MySqlServerResource` builder with `WithAdminer` / `withAdminer`:
+To add the [Adminer](https://adminer.org/) management UI, decorate the official `MySqlServerResource` builder with <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithAdminer" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -171,7 +172,7 @@ await builder.build().run();
 
 ### dbx management UI
 
-[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use `WithDbx` / `withDbx` to add a dbx child resource configured for the MySQL server:
+[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithDbx" /> to add a dbx child resource configured for the MySQL server:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-get-started.mdx b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-get-started.mdx
index 20e384868e..a50ba3439b 100644
--- a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-get-started.mdx
@@ -7,6 +7,7 @@ description: "Use the Aspire MySQL hosting and client integrations to spin up My
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import mysqlIcon from '@assets/icons/mysqlconnector-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mysqlIcon}
@@ -28,7 +29,7 @@ Adding MySQL through Aspire — rather than wiring up containers and connection
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the server is ready.
 - **Dashboard observability.** The database resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
 - **A first-class C# client integration.** C# apps can use the `Aspire.MySqlConnector` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name. Entity Framework Core (EF Core) users can use the [Pomelo EF Core MySQL integration](/integrations/databases/efcore/mysql/mysql-get-started/) instead.
-- **phpMyAdmin on demand.** Call `WithPhpMyAdmin` (or `withPhpMyAdmin`) to spin up a phpMyAdmin instance alongside your database for web-based database management.
+- **phpMyAdmin on demand.** Call <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithPhpMyAdmin" /> to spin up a phpMyAdmin instance alongside your database for web-based database management.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-host.mdx b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-host.mdx
index 969203afb9..0f1f53f194 100644
--- a/src/frontend/src/content/docs/integrations/databases/mysql/mysql-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/mysql/mysql-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import mysqlIcon from '@assets/icons/mysqlconnector-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mysqlIcon}
@@ -135,7 +136,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add MySQL resource with database scripts
 
-You can use the `WithCreationScript` method to execute SQL scripts when the database is created. This is useful for initializing database schema or seeding data:
+You can use the <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithCreationScript" /> method to execute SQL scripts when the database is created. This is useful for initializing database schema or seeding data:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -197,7 +198,7 @@ The script is executed only when the database is first created. If you need to r
 
 ## Add MySQL resource with phpMyAdmin
 
-[**phpMyAdmin**](https://www.phpmyadmin.net/) is a popular web-based administration tool for MySQL. Call the `WithPhpMyAdmin` (or `withPhpMyAdmin`) method to add a phpMyAdmin container resource that connects to the MySQL container:
+[**phpMyAdmin**](https://www.phpmyadmin.net/) is a popular web-based administration tool for MySQL. Call the <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithPhpMyAdmin" /> method to add a phpMyAdmin container resource that connects to the MySQL container:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -427,7 +428,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 // After adding all resources, run the app...
 ```
 
-The TypeScript AppHost doesn't currently expose a `withInitBindMount(...)` API for MySQL. Use `withInitFiles(...)` to copy initialization files into the container instead.
+The TypeScript AppHost doesn't currently expose a `withInitBindMount(...)` API for MySQL. Use <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithInitFiles" /> to copy initialization files into the container instead.
 </TabItem>
 </Tabs>
 
@@ -531,7 +532,7 @@ await builder.build().run();
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the MySQL server resource to enable a **REPL** command that opens `mysql` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.MySqlBuilderExtensions.WithRepl" /> to the MySQL server resource to enable a **REPL** command that opens `mysql` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/databases/postgres/postgres-host.mdx b/src/frontend/src/content/docs/integrations/databases/postgres/postgres-host.mdx
index ddbc6de759..73750d1a88 100644
--- a/src/frontend/src/content/docs/integrations/databases/postgres/postgres-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/postgres/postgres-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import postgresIcon from '@assets/icons/postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={postgresIcon}
@@ -408,7 +409,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 </TabItem>
 </Tabs>
 
-The data volume is used to persist the PostgreSQL server data outside the lifecycle of its container. The container data directory depends on the PostgreSQL image version: PostgreSQL 17 and earlier use `/var/lib/postgresql/data`, while PostgreSQL 18 and later use `/var/lib/postgresql`. `WithDataVolume(...)` selects the correct path automatically based on the configured image tag. When a `name` parameter isn't provided, the name is generated at random. For more information on data volumes and details on why they're preferred over [bind mounts](#add-postgresql-server-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
+The data volume is used to persist the PostgreSQL server data outside the lifecycle of its container. The container data directory depends on the PostgreSQL image version: PostgreSQL 17 and earlier use `/var/lib/postgresql/data`, while PostgreSQL 18 and later use `/var/lib/postgresql`. <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> selects the correct path automatically based on the configured image tag. When a `name` parameter isn't provided, the name is generated at random. For more information on data volumes and details on why they're preferred over [bind mounts](#add-postgresql-server-resource-with-data-bind-mount), see [Docker docs: Volumes](https://docs.docker.com/engine/storage/volumes).
 
 <Aside type="caution">
   Aspire 13.4 bumped the default PostgreSQL image to 18, which uses a different on-disk data layout than PostgreSQL 17. A data volume or data bind mount created on PostgreSQL 17 (Aspire 13.3 or earlier) is incompatible after upgrading. See [PostgreSQL 18 data directory change](#postgresql-18-data-directory-change) for recovery options.
@@ -504,7 +505,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 // After adding all resources, run the app...
 ```
 
-The TypeScript AppHost doesn't currently expose a `withInitBindMount(...)` API for PostgreSQL. Use `withInitFiles(...)` when you want to copy initialization files into the container instead.
+The TypeScript AppHost doesn't currently expose a `withInitBindMount(...)` API for PostgreSQL. Use <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithInitFiles" /> when you want to copy initialization files into the container instead.
 </TabItem>
 </Tabs>
 
@@ -604,9 +605,9 @@ await builder.build().run();
 
 ## PostgreSQL 18 data directory change
 
-Starting with Aspire 13.4, the default PostgreSQL container image used by `AddPostgres` is **18.3** (previously 17.6). PostgreSQL 18 changed the on-disk data layout: the official `postgres` image now stores cluster files under a major-version-specific subdirectory of `/var/lib/postgresql` (for example, `/var/lib/postgresql/18/docker`), whereas PostgreSQL 17 and earlier stored data directly in `/var/lib/postgresql/data`. For upstream details, see [docker-library/postgres#1259](https://github.com/docker-library/postgres/issues/1259) and [docker-library/postgres#37](https://github.com/docker-library/postgres/issues/37).
+Starting with Aspire 13.4, the default PostgreSQL container image used by <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" /> is **18.3** (previously 17.6). PostgreSQL 18 changed the on-disk data layout: the official `postgres` image now stores cluster files under a major-version-specific subdirectory of `/var/lib/postgresql` (for example, `/var/lib/postgresql/18/docker`), whereas PostgreSQL 17 and earlier stored data directly in `/var/lib/postgresql/data`. For upstream details, see [docker-library/postgres#1259](https://github.com/docker-library/postgres/issues/1259) and [docker-library/postgres#37](https://github.com/docker-library/postgres/issues/37).
 
-`WithDataVolume(...)` and `WithDataBindMount(...)` are version-aware: Aspire chooses the container data directory from the configured image tag at the time the method is called. PostgreSQL 17 and earlier map to `/var/lib/postgresql/data`; PostgreSQL 18 and later map to `/var/lib/postgresql`.
+`WithDataVolume(...)` and <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataBindMount" /> are version-aware: Aspire chooses the container data directory from the configured image tag at the time the method is called. PostgreSQL 17 and earlier map to `/var/lib/postgresql/data`; PostgreSQL 18 and later map to `/var/lib/postgresql`.
 
 Because of this layout change, PostgreSQL 17 data persisted with `WithDataVolume(...)` or `WithDataBindMount(...)` (Aspire 13.3 or earlier) is incompatible with PostgreSQL 18 after upgrading to Aspire 13.4. The container fails to start with an error similar to:
 
@@ -618,7 +619,7 @@ You have two ways to recover.
 
 ### Option 1: Stay on PostgreSQL 17 (recommended, no migration)
 
-Pin the image back to a PostgreSQL 17 tag with `WithImageTag(...)` **before** calling `WithDataVolume(...)`. Aspire then selects the legacy `/var/lib/postgresql/data` path and your existing volume keeps working with no migration:
+Pin the image back to a PostgreSQL 17 tag with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImageTag" /> **before** calling `WithDataVolume(...)`. Aspire then selects the legacy `/var/lib/postgresql/data` path and your existing volume keeps working with no migration:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -668,7 +669,7 @@ docker volume rm <old-volume-name>
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the PostgreSQL server resource to enable a **REPL** command that opens `psql` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithRepl" /> to the PostgreSQL server resource to enable a **REPL** command that opens `psql` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/databases/postgres/postgresql-extensions.mdx b/src/frontend/src/content/docs/integrations/databases/postgres/postgresql-extensions.mdx
index bd2d7e42a1..c98921187a 100644
--- a/src/frontend/src/content/docs/integrations/databases/postgres/postgresql-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/postgres/postgresql-extensions.mdx
@@ -7,6 +7,7 @@ import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import postgresqlIcon from '@assets/icons/postgresql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -49,7 +50,7 @@ For TypeScript AppHosts, add the Community Toolkit PostgreSQL extensions package
 
 ### DbGate management UI
 
-To add the DbGate management UI, decorate the official `PostgresServerResource` builder with `WithDbGate` / `withDbGate`:
+To add the DbGate management UI, decorate the official `PostgresServerResource` builder with <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDbGate" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -93,7 +94,7 @@ This adds a new DbGate resource to the app host which is available from the Aspi
 
 ### Adminer management UI
 
-To add the Adminer management UI, decorate the official `PostgresServerResource` builder with `WithAdminer` / `withAdminer`:
+To add the Adminer management UI, decorate the official `PostgresServerResource` builder with <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithAdminer" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -181,7 +182,7 @@ await exampleProject.withReference(postgres);
 
 ### dbx management UI
 
-[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use `WithDbx` / `withDbx` to add a dbx child resource configured for the PostgreSQL server:
+[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDbx" /> to add a dbx child resource configured for the PostgreSQL server:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -266,7 +267,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithFlywayMigration` configures the Flyway connection arguments and `migrate` command; it doesn't add resource ordering. In the C# example, `migrations.WaitFor(database)` ensures Flyway starts only after PostgreSQL is ready, and `api.WaitForCompletion(migrations)` gates the API on the migration resource's completion.
+<ApiReference name="Aspire.Hosting.PostgresDatabaseResourceBuilderExtensions.WithFlywayMigration" /> configures the Flyway connection arguments and `migrate` command; it doesn't add resource ordering. In the C# example, `migrations.WaitFor(database)` ensures Flyway starts only after PostgreSQL is ready, and `api.WaitForCompletion(migrations)` gates the API on the migration resource's completion.
 
 The TypeScript overload creates and configures the Flyway resource internally, but it doesn't add a `waitFor` relationship or return the Flyway resource builder. The TypeScript binding therefore can't express the C# example's startup and completion dependencies for that internally created resource.
 
diff --git a/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-connect.mdx b/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-connect.mdx
index 5d69941529..d831c17f1a 100644
--- a/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import ravendbIcon from '@assets/icons/ravendb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -298,5 +299,5 @@ store.initialize();
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the [AppHost reference](/get-started/app-host/) for details.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the [AppHost reference](/get-started/app-host/) for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-host.mdx b/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-host.mdx
index 3fffd12de7..ea1375f8a7 100644
--- a/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/ravendb/ravendb-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import ravendbIcon from '@assets/icons/ravendb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -119,7 +120,7 @@ await builder.build().run();
 
 1. When Aspire adds a container image to the app host, as shown in the preceding example with the `docker.io/ravendb/ravendb` image, it creates a new RavenDB instance on your local machine.
 
-1. The `AddDatabase` call registers a database sub-resource named `ravendb` on the server. By default, the database name matches the resource name. You can pass a different database name as the second argument: `ravenServer.AddDatabase("ravendb", databaseName: "mydb")`.
+1. The <ApiReference name="Aspire.Hosting.RavenDBBuilderExtensions.AddDatabase" /> call registers a database sub-resource named `ravendb` on the server. By default, the database name matches the resource name. You can pass a different database name as the second argument: `ravenServer.AddDatabase("ravendb", databaseName: "mydb")`.
 
 1. The AppHost reference call configures a connection in the consuming project named after the referenced database resource, such as `ravendb` in the preceding example.
 
diff --git a/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-extensions.mdx b/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-extensions.mdx
index 3d7e32cd7c..779a7e02c1 100644
--- a/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-extensions.mdx
@@ -7,6 +7,7 @@ import { Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import sqlIcon from '@assets/icons/sql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -48,7 +49,7 @@ For TypeScript AppHosts, add the Community Toolkit SQL Server extensions package
 
 ### DbGate management UI
 
-To add the [DbGate](https://dbgate.org/) management UI, decorate the official `SqlServerServerResource` builder with `WithDbGate` / `withDbGate`:
+To add the [DbGate](https://dbgate.org/) management UI, decorate the official `SqlServerServerResource` builder with <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithDbGate" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -89,7 +90,7 @@ This adds a new DbGate resource to the AppHost which is available from the Aspir
 
 ### Adminer management UI
 
-To add the [Adminer](https://adminer.org/) management UI, decorate the official `SqlServerServerResource` builder with `WithAdminer` / `withAdminer`:
+To add the [Adminer](https://adminer.org/) management UI, decorate the official `SqlServerServerResource` builder with <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithAdminer" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -171,7 +172,7 @@ await builder.build().run();
 
 ### dbx management UI
 
-[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use `WithDbx` / `withDbx` to add a dbx child resource configured for the SQL Server resource:
+[dbx](https://github.com/t8y2/dbx) is a lightweight, web-based database client and an alternative management UI to DbGate and Adminer. Use <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithDbx" /> to add a dbx child resource configured for the SQL Server resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-host.mdx b/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-host.mdx
index f58d4d4ae4..394e99bdb1 100644
--- a/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/sql-server/sql-server-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import sqlIcon from '@assets/icons/sql-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={sqlIcon}
@@ -146,7 +147,7 @@ IF (NOT EXISTS (SELECT 1 FROM sys.databases WHERE name = @DatabaseName))
     CREATE DATABASE [<QUOTED_DATABASE_NAME>];
 ```
 
-To supply a custom creation script, call `WithCreationScript` (or `withCreationScript`) on the database resource builder:
+To supply a custom creation script, call <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithCreationScript" /> on the database resource builder:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -373,7 +374,7 @@ When no `password` parameter is provided, Aspire generates a strong password aut
 
 ## Use a specific SQL Server container image tag
 
-To pin the SQL Server container to a specific release, call `WithImageTag` (or `withImageTag`):
+To pin the SQL Server container to a specific release, call <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImageTag" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -464,7 +465,7 @@ await builder.build().run();
 
 ## Connect to an existing SQL Server instance
 
-To reference an externally managed SQL Server instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed SQL Server instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -560,7 +561,7 @@ When the AppHost runs, the server's database resources can be accessed from exte
 
 ## Open an interactive REPL
 
-In Aspire 13.6 or later, add `WithRepl()` to the SQL Server resource to enable a **REPL** command that opens `sqlcmd` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
+In Aspire 13.6 or later, add <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithRepl" /> to the SQL Server resource to enable a **REPL** command that opens `sqlcmd` in the [terminal dock](/dashboard/terminals/#use-the-terminal-dock).
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
diff --git a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-connect.mdx b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-connect.mdx
index d8384a082c..7c61cb8b66 100644
--- a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import sqliteIcon from '@assets/icons/sqlite-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -275,5 +276,5 @@ db.close();
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See [Pass connection information to app resources](../sqlite-host/#connection-properties) in the Hosting integration reference.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Pass connection information to app resources](../sqlite-host/#connection-properties) in the Hosting integration reference.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-get-started.mdx b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-get-started.mdx
index 6168545deb..82c17a900e 100644
--- a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-get-started.mdx
@@ -7,6 +7,7 @@ description: Learn how the Aspire SQLite integrations register a file-backed SQL
 import { Image } from 'astro:assets';
 import { Badge, LinkButton, Steps } from '@astrojs/starlight/components';
 import sqliteIcon from '@assets/icons/sqlite-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -28,7 +29,7 @@ Adding SQLite through Aspire — rather than hardcoding file paths and connectio
 
 - **Ideal for local development, unit tests, and desktop apps.** No container to spin up, no server to configure — SQLite runs in-process directly from a single file on disk.
 - **Consistent connection info across languages.** Once you reference the SQLite resource from a consuming app, Aspire injects the database file path as an environment variable in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
-- **Optional browser-based UI.** The `WithSqliteWeb` method adds a lightweight [`sqlite-web`](https://github.com/coleifer/sqlite-web) container alongside your database so you can inspect and query it during development.
+- **Optional browser-based UI.** The <ApiReference name="Aspire.Hosting.SqliteResourceBuilderExtensions.WithSqliteWeb" /> method adds a lightweight [`sqlite-web`](https://github.com/coleifer/sqlite-web) container alongside your database so you can inspect and query it during development.
 - **A first-class C# client integration.** C# apps can use the `CommunityToolkit.Aspire.Microsoft.Data.Sqlite` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name.
 
 ## How the pieces fit together
diff --git a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-host.mdx b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-host.mdx
index 72920cd119..4a3f2f1208 100644
--- a/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/sqlite/sqlite-host.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import sqliteIcon from '@assets/icons/sqlite-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -129,7 +130,7 @@ await builder.build().run();
 
 ## Add SQLite resource with custom database file path
 
-By default, Aspire creates the SQLite database file in the user's temporary directory. To specify a custom location, provide the directory path and file name as arguments to `AddSqlite`:
+By default, Aspire creates the SQLite database file in the user's temporary directory. To specify a custom location, provide the directory path and file name as arguments to <ApiReference name="Aspire.Hosting.SqliteResourceBuilderExtensions.AddSqlite" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -171,7 +172,7 @@ The preceding code creates the SQLite database file at `C:\Database\Location\my-
 
 ## Add SQLiteWeb resource
 
-To add a browser-based management UI alongside your SQLite database, use the `WithSqliteWeb` extension method:
+To add a browser-based management UI alongside your SQLite database, use the <ApiReference name="Aspire.Hosting.SqliteResourceBuilderExtensions.WithSqliteWeb" /> extension method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-connect.mdx b/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-connect.mdx
index 3ce9d602b8..c062b4840f 100644
--- a/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import surrealdbIcon from '@assets/icons/surrealdb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -287,5 +288,5 @@ await db.close();
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment`. See the Aspire AppHost documentation for details.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the Aspire AppHost documentation for details.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-host.mdx b/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-host.mdx
index 5811d0e583..7482280a67 100644
--- a/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-host.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/surrealdb/surrealdb-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Badge, Steps, Tabs, TabItem } from '@astrojs/starlight/component
 import InstallPackage from '@components/InstallPackage.astro';
 import LearnMore from '@components/LearnMore.astro';
 import surrealdbIcon from '@assets/icons/surrealdb-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -130,7 +131,7 @@ await builder.build().run();
 
 ## Add Surrealist
 
-To add [Surrealist](https://hub.docker.com/r/surrealdb/surrealist) to the SurrealDB server resource, call the `WithSurrealist` method:
+To add [Surrealist](https://hub.docker.com/r/surrealdb/surrealist) to the SurrealDB server resource, call the <ApiReference name="Aspire.Hosting.SurrealDbBuilderExtensions.WithSurrealist" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -180,7 +181,7 @@ Surrealist is a web-based user interface for interacting with your SurrealDB dat
 
 ## Add SurrealDB resource with data bind mount
 
-To add a data bind mount to the SurrealDB resource, call the `WithDataBindMount` method:
+To add a data bind mount to the SurrealDB resource, call the <ApiReference name="Aspire.Hosting.SurrealDbBuilderExtensions.WithDataBindMount" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -277,7 +278,7 @@ For more information on providing parameters, see [External parameters](/get-sta
 
 ## Configure logging
 
-To configure the log level for the SurrealDB container, call the `WithLogLevel` method:
+To configure the log level for the SurrealDB container, call the <ApiReference name="Aspire.Hosting.SurrealDbBuilderExtensions.WithLogLevel" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/devtools/browser-logs.mdx b/src/frontend/src/content/docs/integrations/devtools/browser-logs.mdx
index 9ec01a7e5d..a33b0c3d80 100644
--- a/src/frontend/src/content/docs/integrations/devtools/browser-logs.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/browser-logs.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import aspireIcon from '@assets/icons/aspire-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={aspireIcon}
@@ -80,7 +81,7 @@ This updates your `aspire.config.json` with the browser logs hosting integration
 
 ## Add browser logs to a resource
 
-Browser logs work with **any resource that exposes an HTTP or HTTPS endpoint that can be rendered in a browser** — projects, containers, executables, or custom resources. The examples below use [Vite](https://vite.dev/) (from the [JavaScript integration](/integrations/frameworks/javascript/)) for illustration, but the same `WithBrowserLogs()` call applies to any browseable resource:
+Browser logs work with **any resource that exposes an HTTP or HTTPS endpoint that can be rendered in a browser** — projects, containers, executables, or custom resources. The examples below use [Vite](https://vite.dev/) (from the [JavaScript integration](/integrations/frameworks/javascript/)) for illustration, but the same <ApiReference name="Aspire.Hosting.BrowserLogsBuilderExtensions.WithBrowserLogs" /> call applies to any browseable resource:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/devtools/dab/dab-host.mdx b/src/frontend/src/content/docs/integrations/devtools/dab/dab-host.mdx
index fab8ff8982..3ef83f86a5 100644
--- a/src/frontend/src/content/docs/integrations/devtools/dab/dab-host.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/dab/dab-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import dabIcon from '@assets/icons/data-api-builder-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -48,7 +49,7 @@ Or add the package manually:
 aspire add CommunityToolkit.Aspire.Hosting.Azure.DataApiBuilder
 ```
 
-This adds the package to `aspire.config.json`. After `aspire restore`, `.aspire/modules/aspire.mjs` includes `addDataAPIBuilder` and the exported resource properties.
+This adds the package to `aspire.config.json`. After `aspire restore`, `.aspire/modules/aspire.mjs` includes <ApiReference name="Aspire.Hosting.DataApiBuilderHostingExtension.AddDataAPIBuilder" /> and the exported resource properties.
 
 </TabItem>
 </Tabs>
diff --git a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
index c6c8f7fcc1..e1f7e6ecc6 100644
--- a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Tabs, TabItem, Aside } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import devTunnelsIcon from '@assets/icons/dev-tunnels-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={devTunnelsIcon}
@@ -109,7 +110,7 @@ When you run the AppHost, the dev tunnel is created to expose the web applicatio
 
 ### Allow anonymous access
 
-To allow anonymous, public access to the entire tunnel, chain a call to the `WithAnonymousAccess` method:
+To allow anonymous, public access to the entire tunnel, chain a call to the <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.WithAnonymousAccess" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -140,7 +141,7 @@ const tunnel = await builder.addDevTunnel("public-api")
 
 ### Configure dev tunnel options
 
-To configure other options for the dev tunnel, provide the `DevTunnelOptions` to the `AddDevTunnel` method:
+To configure other options for the dev tunnel, provide the `DevTunnelOptions` to the <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.AddDevTunnel" /> method:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -176,7 +177,7 @@ const tunnel = await builder.addDevTunnel("qa", "my-tunnel-id", false, "QA envir
 
 ### Configure for mixed access
 
-To allow anonymous access to specific endpoints, use the appropriate `WithReference` overload:
+To allow anonymous access to specific endpoints, use the appropriate <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> overload:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/devtools/flagd/flagd-host.mdx b/src/frontend/src/content/docs/integrations/devtools/flagd/flagd-host.mdx
index 6e492974b3..bf857e5749 100644
--- a/src/frontend/src/content/docs/integrations/devtools/flagd/flagd-host.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/flagd/flagd-host.mdx
@@ -11,6 +11,7 @@ import {
   TabItem,
   Tabs,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import LearnMore from '@components/LearnMore.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import flagdIcon from '@assets/icons/flagd-icon.svg';
@@ -57,7 +58,7 @@ Or, choose a manual installation approach:
 
 ## Add flagd resource
 
-Once you've installed the hosting integration in your AppHost project, you can add a flagd resource. The flagd container requires a sync source. Use `WithBindFileSync` to mount a directory of flag-definition files into the container:
+Once you've installed the hosting integration in your AppHost project, you can add a flagd resource. The flagd container requires a sync source. Use <ApiReference name="Aspire.Hosting.FlagdBuilderExtensions.WithBindFileSync" /> to mount a directory of flag-definition files into the container:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -217,7 +218,7 @@ The flagd hosting source explicitly marks `WithLogLevel` with `[AspireExportIgno
 
 ## Customize ports
 
-To use fixed host ports instead of randomly assigned ones, pass the `port` and `ofrepPort` parameters to `AddFlagd`:
+To use fixed host ports instead of randomly assigned ones, pass the `port` and `ofrepPort` parameters to <ApiReference name="Aspire.Hosting.FlagdBuilderExtensions.AddFlagd" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/devtools/goff/goff-connect.mdx b/src/frontend/src/content/docs/integrations/devtools/goff/goff-connect.mdx
index da4b9aee0b..8305351f29 100644
--- a/src/frontend/src/content/docs/integrations/devtools/goff/goff-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/goff/goff-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import goffIcon from '@assets/icons/go-feature-flag.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -309,6 +310,6 @@ const client = OpenFeature.getClient();
 <Aside type="tip">
   If your app expects a specific environment variable name other than the Aspire
   defaults, you can pass individual connection properties from the AppHost using
-  `WithEnvironment`. See the Aspire AppHost documentation for more information
+  <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See the Aspire AppHost documentation for more information
   on [passing environment variables](/get-started/app-host/).
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/devtools/goff/goff-host.mdx b/src/frontend/src/content/docs/integrations/devtools/goff/goff-host.mdx
index aaf73556b4..fdd6f0f5fd 100644
--- a/src/frontend/src/content/docs/integrations/devtools/goff/goff-host.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/goff/goff-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Badge, Steps, TabItem, Tabs } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import goffIcon from '@assets/icons/go-feature-flag.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -94,9 +95,9 @@ await builder.build().run();
 
 1. When Aspire adds a container image to the AppHost, as shown in the preceding example with the `docker.io/gofeatureflag/go-feature-flag` image, it creates a new GO Feature Flag relay proxy instance on your local machine.
 
-1. The `WithGoffBindMount` call mounts a local folder into the `/goff` path inside the container, where the relay proxy reads its flag and proxy configuration files.
+1. The <ApiReference name="Aspire.Hosting.GoFeatureFlagBuilderExtensions.WithGoffBindMount" /> call mounts a local folder into the `/goff` path inside the container, where the relay proxy reads its flag and proxy configuration files.
 
-1. The `WithReference` call configures a connection in the consuming project named after the referenced resource (`goff` in the preceding example).
+1. The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> call configures a connection in the consuming project named after the referenced resource (`goff` in the preceding example).
 
 </Steps>
 
@@ -106,7 +107,7 @@ When you reference a GO Feature Flag resource from the AppHost, Aspire makes sev
 
 ## Add goff resource with configuration path
 
-To point the relay proxy to a specific configuration file inside the container, pass the `pathToConfigFile` parameter to `AddGoFeatureFlag`:
+To point the relay proxy to a specific configuration file inside the container, pass the `pathToConfigFile` parameter to <ApiReference name="Aspire.Hosting.GoFeatureFlagBuilderExtensions.AddGoFeatureFlag" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -227,7 +228,7 @@ This instructs the relay proxy to load flags from the `flags.yaml` file inside t
 
 ## Configure logging
 
-To configure the log level for the GO Feature Flag container resource, call `WithLogLevel`:
+To configure the log level for the GO Feature Flag container resource, call <ApiReference name="Aspire.Hosting.GoFeatureFlagBuilderExtensions.WithLogLevel" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/devtools/k6/k6-host.mdx b/src/frontend/src/content/docs/integrations/devtools/k6/k6-host.mdx
index 2e5d64912b..5aad769ddd 100644
--- a/src/frontend/src/content/docs/integrations/devtools/k6/k6-host.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/k6/k6-host.mdx
@@ -8,6 +8,7 @@ import { Badge, TabItem, Tabs } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import LearnMore from '@components/LearnMore.astro';
 import k6Icon from '@assets/icons/k6-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -67,7 +68,7 @@ The command adds the package to `aspire.config.json`:
 
 ## Add a k6 resource
 
-Use `AddK6` / `addK6` to add a Grafana k6 container resource. The resource uses the `docker.io/grafana/k6` image, exposes its HTTP API as the `http` endpoint, and is visible in the dashboard.
+Use <ApiReference name="Aspire.Hosting.K6BuilderExtensions.AddK6" /> to add a Grafana k6 container resource. The resource uses the `docker.io/grafana/k6` image, exposes its HTTP API as the `http` endpoint, and is visible in the dashboard.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -105,7 +106,7 @@ await builder.build().run();
 - An internal `http` endpoint targets port `6565`. Specify `port` to bind a fixed host port; otherwise Aspire allocates one.
 - Aspire checks `GET /health` on that endpoint.
 - The resource is a container resource, so its logs, lifecycle actions, endpoint link, and health state appear in the dashboard.
-- The integration configures an OTLP exporter for the container. Use `WithK6OtlpEnvironment` / `withK6OtlpEnvironment` when k6 should consume the corresponding k6 environment variables.
+- The integration configures an OTLP exporter for the container. Use <ApiReference name="Aspire.Hosting.K6BuilderExtensions.WithK6OtlpEnvironment" /> when k6 should consume the corresponding k6 environment variables.
 
 The examples read `PrimaryEndpoint` / `primaryEndpoint()` when an AppHost API needs the k6 HTTP endpoint directly.
 
@@ -141,9 +142,9 @@ The default image does not include browser support. Enable it only for tests tha
 
 ## Run a script
 
-`WithScript` / `withScript` configures the container command as `k6 run`, binds it to `0.0.0.0:6565`, and sets the virtual-user and duration arguments. `virtualUsers` defaults to `10` and `duration` defaults to `30s`.
+<ApiReference name="Aspire.Hosting.K6BuilderExtensions.WithScript" /> configures the container command as `k6 run`, binds it to `0.0.0.0:6565`, and sets the virtual-user and duration arguments. `virtualUsers` defaults to `10` and `duration` defaults to `30s`.
 
-Mount the script directory with the standard container `WithBindMount` / `withBindMount` API before selecting a path in the container:
+Mount the script directory with the standard container <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBindMount" /> API before selecting a path in the container:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -193,7 +194,7 @@ await k6.withK6OtlpEnvironment();
 
 ## References and publishing
 
-Use the standard `WithReference` / `withReference` and `WaitFor` / `waitFor` APIs to model the relationship between the test and the resources it exercises. Referenced resources provide their connection information through Aspire's normal resource configuration.
+Use the standard <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> APIs to model the relationship between the test and the resources it exercises. Referenced resources provide their connection information through Aspire's normal resource configuration.
 
 The integration doesn't add k6-specific publish or export callbacks. It remains a normal Aspire container resource with its configured image, endpoint, and container settings available to publishers.
 
diff --git a/src/frontend/src/content/docs/integrations/devtools/mailpit/mailpit-connect.mdx b/src/frontend/src/content/docs/integrations/devtools/mailpit/mailpit-connect.mdx
index 4c98a7de7f..2e3a5509d6 100644
--- a/src/frontend/src/content/docs/integrations/devtools/mailpit/mailpit-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/mailpit/mailpit-connect.mdx
@@ -8,6 +8,7 @@ import { Aside, Badge, TabItem, Tabs } from '@astrojs/starlight/components';
 import ThemeImage from '@components/ThemeImage.astro';
 import mailpitIcon from '@assets/icons/mailpit-icon.svg';
 import mailpitLightIcon from '@assets/icons/mailpit-light-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -205,6 +206,6 @@ await transporter.sendMail({
 <Aside type="tip">
   If your app expects specific environment variable names different from the
   Aspire defaults, you can pass individual connection properties from the
-  AppHost using `WithEnvironment`. See [Pass custom environment
+  AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Pass custom environment
   variables](/get-started/app-host/) in the AppHost reference.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/devtools/sql-projects/sql-projects-host.mdx b/src/frontend/src/content/docs/integrations/devtools/sql-projects/sql-projects-host.mdx
index 3b1a064e3c..57329c8c14 100644
--- a/src/frontend/src/content/docs/integrations/devtools/sql-projects/sql-projects-host.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/sql-projects/sql-projects-host.mdx
@@ -10,6 +10,7 @@ import InstallPackage from '@components/InstallPackage.astro';
 import LearnMore from '@components/LearnMore.astro';
 
 import sqlIcon from '@assets/icons/sql-database-projects-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -58,7 +59,7 @@ Run `aspire restore` after changing a TypeScript AppHost package configuration t
 
 ## Add a project or DACPAC resource
 
-`AddSqlProject` creates a `SqlProject` dashboard resource in the waiting state. It is a deployment resource, so it has no endpoint, environment variables, connection string, or health check. It implements standard wait support, which lets other resources use `WaitForCompletion`.
+<ApiReference name="Aspire.Hosting.SqlProjectBuilderExtensions.AddSqlProject" /> creates a `SqlProject` dashboard resource in the waiting state. It is a deployment resource, so it has no endpoint, environment variables, connection string, or health check. It implements standard wait support, which lets other resources use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" />.
 
 In a C# AppHost, use `AddSqlProject<TProject>` when the AppHost references an MSBuild SQL project. The generic project metadata overload resolves the project's `SqlTargetPath` or `TargetPath` output. Use the non-generic overload with `WithDacpac` when you already have a DACPAC.
 
@@ -112,7 +113,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithDacpac` accepts a path to a `.dacpac` file. At deployment time, a relative DACPAC path is resolved against the AppHost content root. The integration does not set a working directory.
+<ApiReference name="Aspire.Hosting.SqlProjectBuilderExtensions.WithDacpac" /> accepts a path to a `.dacpac` file. At deployment time, a relative DACPAC path is resolved against the AppHost content root. The integration does not set a working directory.
 
 :::note
 The generic `AddSqlProject<TProject>` overload is C# only. It requires `IProjectMetadata`, so TypeScript uses `addSqlProject(name)` and `withDacpac(path)` instead.
@@ -138,7 +139,7 @@ The package resource uses `tools/<package-id>.dacpac` by default; `WithDacpac` s
 
 ## Configure deployment
 
-Use a DACFx publish profile with `WithDacDeployOptions`, or configure `DacDeployOptions` directly in a C# AppHost. A publish-profile path is loaded as supplied, so use a path that is valid for the AppHost process.
+Use a DACFx publish profile with <ApiReference name="Aspire.Hosting.SqlProjectBuilderExtensions.WithDacDeployOptions" />, or configure `DacDeployOptions` directly in a C# AppHost. A publish-profile path is loaded as supplied, so use a path that is valid for the AppHost process.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -177,7 +178,7 @@ await databaseProject.withReference(database);
 
 ## Avoid unchanged deployments
 
-`WithSkipWhenDeployed` records a DACPAC checksum in the target database. On later deployments, the integration skips the DACPAC if the checksum is unchanged. It sets `DropExtendedPropertiesNotInSource` to `false` while this option is active.
+<ApiReference name="Aspire.Hosting.SqlProjectBuilderExtensions.WithSkipWhenDeployed" /> records a DACPAC checksum in the target database. On later deployments, the integration skips the DACPAC if the checksum is unchanged. It sets `DropExtendedPropertiesNotInSource` to `false` while this option is active.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -215,7 +216,7 @@ Use this with a persistent database when avoiding an unchanged schema deployment
 
 ## Target a database
 
-`WithReference` establishes a parent relationship to the target, waits for that target to be ready, and then deploys the DACPAC. A SQL Server database target supplies the database name automatically. You can instead target any connection-string resource; its connection string must contain `Database` or `Initial Catalog` so DACFx can infer the target database.
+<ApiReference name="Aspire.Hosting.SqlProjectBuilderExtensions.WithReference" /> establishes a parent relationship to the target, waits for that target to be ready, and then deploys the DACPAC. A SQL Server database target supplies the database name automatically. You can instead target any connection-string resource; its connection string must contain `Database` or `Initial Catalog` so DACFx can infer the target database.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -246,7 +247,7 @@ The SQL Server database overload is `withReference` in TypeScript. The connectio
 
 ## Dashboard behavior and resource properties
 
-When a referenced target becomes ready, the integration publishes the DACPAC and reports the deployment resource as `Running`, then `Finished` with exit code `0`; failures are reported in the resource logs and state. Use standard `WithExplicitStart` on a project or package resource to prevent that automatic deployment, then invoke its highlighted **Deploy** dashboard command. The command also deploys a schema again manually and is disabled while the resource is starting or running.
+When a referenced target becomes ready, the integration publishes the DACPAC and reports the deployment resource as `Running`, then `Finished` with exit code `0`; failures are reported in the resource logs and state. Use standard <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> on a project or package resource to prevent that automatic deployment, then invoke its highlighted **Deploy** dashboard command. The command also deploys a schema again manually and is disabled while the resource is starting or running.
 
 The preceding synchronized examples also show the `SqlProjectResource` properties exported to TypeScript AppHosts:
 
diff --git a/src/frontend/src/content/docs/integrations/dotnet/blazor-connect.mdx b/src/frontend/src/content/docs/integrations/dotnet/blazor-connect.mdx
index eee6802bff..4b23f597d5 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/blazor-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/blazor-connect.mdx
@@ -6,6 +6,7 @@ description: Learn which service discovery connection properties Aspire exposes
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import blazorIcon from '@assets/icons/blazor-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={blazorIcon}
@@ -20,7 +21,7 @@ This page describes how to connect Blazor app resources and APIs after you've al
 
 ## Connection properties
 
-When you use `WithReference` / `withReference`, Aspire publishes service discovery endpoint values as environment variables. The key format is:
+When you use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, Aspire publishes service discovery endpoint values as environment variables. The key format is:
 
 - `services__{resource-name}__{endpoint-name}__{index}`
 
diff --git a/src/frontend/src/content/docs/integrations/dotnet/blazor-get-started.mdx b/src/frontend/src/content/docs/integrations/dotnet/blazor-get-started.mdx
index c818a19c5c..c99b49cde9 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/blazor-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/blazor-get-started.mdx
@@ -6,6 +6,7 @@ description: Learn what the Aspire Blazor hosting integration is, why to use it,
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import blazorIcon from '@assets/icons/blazor-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={blazorIcon}
@@ -22,8 +23,8 @@ The Aspire Blazor hosting integration helps you model a Blazor WebAssembly proje
 
 The integration adds AppHost APIs that let you:
 
-- Add a Blazor WebAssembly project resource with `AddBlazorWasmProject` / `addBlazorWasmProject`.
-- Add a Blazor Gateway resource with `AddBlazorGateway` / `addBlazorGateway`.
+- Add a Blazor WebAssembly project resource with <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorWasmProject" />.
+- Add a Blazor Gateway resource with <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorGateway" />.
 - Associate the client app with the gateway by using `WithBlazorClientApp` / `withBlazorClientApp`.
 
 ## Why use Blazor hosting with Aspire
diff --git a/src/frontend/src/content/docs/integrations/dotnet/blazor-hosting.mdx b/src/frontend/src/content/docs/integrations/dotnet/blazor-hosting.mdx
index e2680e7fca..a8eeff7fb8 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/blazor-hosting.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/blazor-hosting.mdx
@@ -255,7 +255,7 @@ builder.Build().Run();
 :::note
 `Aspire.Hosting.Blazor` is a prerelease package. Its APIs remain unstable and may change in future releases.
 
-Starting with Aspire 13.6, `AddDotnetProjectBlazorGateway` and its `WithBlazorClientApp` overload no longer emit [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for this diagnostic after upgrading.
+Starting with Aspire 13.6, <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddDotnetProjectBlazorGateway" /> and its `WithBlazorClientApp` overload no longer emit [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for this diagnostic after upgrading.
 
 The separate [`ASPIREBLAZOR001`](/diagnostics/aspireblazor001/) diagnostic still applies to experimental Blazor hosting types, such as `BlazorWasmAppResource`. Keep the `ASPIREBLAZOR001` suppression in the example.
 :::
diff --git a/src/frontend/src/content/docs/integrations/dotnet/csharp-file-based-apps.mdx b/src/frontend/src/content/docs/integrations/dotnet/csharp-file-based-apps.mdx
index 92daaef1d2..ff74c3cf3e 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/csharp-file-based-apps.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/csharp-file-based-apps.mdx
@@ -8,9 +8,10 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import csharpIcon from '@assets/icons/csharp.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Aside type="danger" title="Experimental">
-  The `AddCSharpApp` API is experimental and may change or be removed in future
+  The <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> API is experimental and may change or be removed in future
   releases. You must suppress the
   [ASPIRECSHARPAPPS001](/diagnostics/aspirecsharpapps001/) diagnostic to use it.
 </Aside>
@@ -37,7 +38,7 @@ Use file-based apps when you need to:
 - Create lightweight APIs with minimal ceremony.
 - Experiment with Aspire integrations in a single file.
 
-For production workloads or apps with multiple source files, use `AddProject<T>` (C#) or `addProject` (TypeScript) with a standard `.csproj` project instead.
+For production workloads or apps with multiple source files, use <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> with a standard `.csproj` project instead.
 
 ## Add C# app resource
 
diff --git a/src/frontend/src/content/docs/integrations/dotnet/dotnet-tool-resources.mdx b/src/frontend/src/content/docs/integrations/dotnet/dotnet-tool-resources.mdx
index cd67e343be..841614aa0e 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/dotnet-tool-resources.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/dotnet-tool-resources.mdx
@@ -7,6 +7,7 @@ description: Learn how to use the AddDotnetTool AppHost API to run .NET CLI tool
 import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import dotnetIcon from '@assets/icons/dotnet.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -43,7 +44,7 @@ Before using .NET tool resources, ensure you have:
 
 ## Add a .NET tool resource
 
-The `addDotnetTool` API requires a resource name and the NuGet package ID of the tool:
+The <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.AddDotnetTool" /> API requires a resource name and the NuGet package ID of the tool:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -81,7 +82,7 @@ When the AppHost runs, Aspire executes `dotnet tool exec dotnet-ef` to run the t
 
 ## Pass arguments to a tool
 
-Use `withArgs` to pass command-line arguments to the tool:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" /> to pass command-line arguments to the tool:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -124,7 +125,7 @@ By default, the latest stable version of the tool is used. You can specify a par
 
 ### Specify a version
 
-Use `withToolVersion` to pin to a specific version:
+Use <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.WithToolVersion" /> to pin to a specific version:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -168,7 +169,7 @@ await efTool.withToolVersion("10.0.*");
 
 ### Allow prerelease versions
 
-Use `withToolPrerelease` to allow prerelease versions of the tool:
+Use <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.WithToolPrerelease" /> to allow prerelease versions of the tool:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -195,7 +196,7 @@ By default, tools are acquired from configured NuGet feeds. You can add addition
 
 ### Add a package source
 
-Use `withToolSource` to add a NuGet package source:
+Use <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.WithToolSource" /> to add a NuGet package source:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -218,7 +219,7 @@ await tool.withToolSource("https://my-private-feed.example.com/nuget/v3/index.js
 
 ### Use only specified sources
 
-Use `withToolIgnoreExistingFeeds` to ignore the existing NuGet configuration and use only the sources you specify:
+Use <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.WithToolIgnoreExistingFeeds" /> to ignore the existing NuGet configuration and use only the sources you specify:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -243,7 +244,7 @@ await tool.withToolIgnoreExistingFeeds();
 
 ### Ignore failed sources
 
-Use `withToolIgnoreFailedSources` to treat package source failures as warnings rather than errors:
+Use <ApiReference name="Aspire.Hosting.DotnetToolResourceExtensions.WithToolIgnoreFailedSources" /> to treat package source failures as warnings rather than errors:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/dotnet/launch-profiles.mdx b/src/frontend/src/content/docs/integrations/dotnet/launch-profiles.mdx
index 6e49894e80..7390cf0dee 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/launch-profiles.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/launch-profiles.mdx
@@ -7,6 +7,7 @@ description: Learn how Aspire integrates with .NET launch profiles for C# AppHos
 import { Image } from 'astro:assets';
 import { Aside, Steps } from '@astrojs/starlight/components';
 import dotnetIcon from '@assets/icons/dotnet.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -107,13 +108,13 @@ The Aspire templates define a similar set of launch profiles to a regular ASP.NE
 
 The C# AppHost is responsible for coordinating the launch of multiple service projects. When you run the AppHost — from the command line, Visual Studio, or another development environment — a launch profile is selected for the AppHost. In turn, the AppHost attempts to find a matching launch profile in the service projects it launches, and uses those options to control the environment and default networking configuration for the service project.
 
-When the AppHost launches a service project, it doesn't use the `--launch-profile` option directly. Instead, Aspire resolves an effective launch profile, sets `DOTNET_LAUNCH_PROFILE` for consistency with `dotnet run` and `dotnet watch`, and adjusts the `ASPNETCORE_URLS` environment variable (derived from the `applicationUrl` field in the launch profile) to use a different port. By default, Aspire inserts a reverse proxy in front of the ASP.NET Core application to support multiple instances via `WithReplicas`.
+When the AppHost launches a service project, it doesn't use the `--launch-profile` option directly. Instead, Aspire resolves an effective launch profile, sets `DOTNET_LAUNCH_PROFILE` for consistency with `dotnet run` and `dotnet watch`, and adjusts the `ASPNETCORE_URLS` environment variable (derived from the `applicationUrl` field in the launch profile) to use a different port. By default, Aspire inserts a reverse proxy in front of the ASP.NET Core application to support multiple instances via <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithReplicas" />.
 
 Other settings, such as `environmentVariables`, are passed to the application without modification.
 
 ## Control launch profile selection
 
-Ideally, you can align the launch profile names between the AppHost and its service projects so that switching profiles in the AppHost switches them across all coordinated projects at once. However, you can also specify which profile a particular project uses by passing `launchProfileName` to `AddProject`:
+Ideally, you can align the launch profile names between the AppHost and its service projects so that switching profiles in the AppHost switches them across all coordinated projects at once. However, you can also specify which profile a particular project uses by passing `launchProfileName` to <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -140,7 +141,7 @@ To force a service project to launch without a launch profile, set the `launchPr
 
 ## Launch profiles and endpoints for ASP.NET Core projects
 
-When adding an ASP.NET Core project to the AppHost, Aspire parses the _launchSettings.json_ file, selects the appropriate launch profile, and automatically generates endpoints in the application model based on the URLs in the `applicationUrl` field. To modify the automatically injected endpoints, use `WithEndpoint`:
+When adding an ASP.NET Core project to the AppHost, Aspire parses the _launchSettings.json_ file, selects the appropriate launch profile, and automatically generates endpoints in the application model based on the URLs in the `applicationUrl` field. To modify the automatically injected endpoints, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" />:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/integrations/dotnet/maui.mdx b/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
index a03239a9c9..ae40c6fb37 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/maui.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import mauiIcon from '@assets/icons/maui-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={mauiIcon}
@@ -64,7 +65,7 @@ TypeScript AppHost support for this integration is not yet available.
 
 ### Add .NET MAUI project
 
-To orchestrate a .NET MAUI application in your AppHost, call `AddMauiProject` with the name and path to the `.csproj` file:
+To orchestrate a .NET MAUI application in your AppHost, call <ApiReference name="Aspire.Hosting.MauiProjectExtensions.AddMauiProject" /> with the name and path to the `.csproj` file:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -135,7 +136,7 @@ mauiapp.AddAndroidEmulator()
 </TabItem>
 </Tabs>
 
-On Windows and Mac Catalyst, local service connectivity works directly through localhost without requiring Dev Tunnels. iOS Simulator and Android Emulator require Dev Tunnels; the `WithOtlpDevTunnel()` method creates a Dev Tunnel specifically for OpenTelemetry Protocol (OTLP) traffic so telemetry from mobile targets reaches the Aspire dashboard.
+On Windows and Mac Catalyst, local service connectivity works directly through localhost without requiring Dev Tunnels. iOS Simulator and Android Emulator require Dev Tunnels; the <ApiReference name="Aspire.Hosting.MauiOtlpExtensions.WithOtlpDevTunnel" /> method creates a Dev Tunnel specifically for OpenTelemetry Protocol (OTLP) traffic so telemetry from mobile targets reaches the Aspire dashboard.
 
 <Aside type="tip">
 You can add multiple device configurations for the same MAUI project. Each device configuration can target a different platform, allowing you to deploy and test your app on multiple targets simultaneously from the same AppHost.
diff --git a/src/frontend/src/content/docs/integrations/dotnet/project-resources.mdx b/src/frontend/src/content/docs/integrations/dotnet/project-resources.mdx
index ded0a04538..d672c906ff 100644
--- a/src/frontend/src/content/docs/integrations/dotnet/project-resources.mdx
+++ b/src/frontend/src/content/docs/integrations/dotnet/project-resources.mdx
@@ -11,6 +11,7 @@ import dotnetIcon from '@assets/icons/dotnet.svg';
 import proxyWithReplicas from '@assets/fundamentals/networking/proxy-with-replicas-1x.png';
 import proxyHostPortAndRandomPort from '@assets/fundamentals/networking/proxy-host-port-and-random-port-1x.png';
 import proxyWithRandomPorts from '@assets/fundamentals/networking/proxy-with-random-ports-1x.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -28,7 +29,7 @@ This article is the reference for modeling .NET projects as first-class Aspire r
 Use project resources when you need to:
 
 - Orchestrate an ASP.NET Core, worker, or console project from an AppHost.
-- Connect the project to other Aspire resources with `withReference`, service discovery, and generated connection strings.
+- Connect the project to other Aspire resources with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, service discovery, and generated connection strings.
 - Reuse launch profile settings and ASP.NET Core endpoint discovery from `launchSettings.json`.
 
 In a **C# AppHost**, `AddProject<T>` references the target project through a generated `Projects.*` type, created from a `ProjectReference` in the AppHost `.csproj`. In a **TypeScript AppHost**, `addProject(name, path)` takes the path to the `.csproj` file directly — no generated type or project file reference is needed.
@@ -48,7 +49,7 @@ Start by adding a `ProjectReference` from the AppHost to the target project:
 </ItemGroup>
 ```
 
-When the AppHost builds, Aspire generates a metadata type in the `Projects` namespace for that reference. Use the generated type with `AddProject`:
+When the AppHost builds, Aspire generates a metadata type in the `Projects` namespace for that reference. Use the generated type with <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -58,7 +59,7 @@ var api = builder.AddProject<Projects.ApiService>("api");
 builder.Build().Run();
 ```
 
-The path to the project comes from the `ProjectReference`, so `AddProject` doesn't need a `.csproj` path. This is the main difference from `AddCSharpApp`, which points directly to a file, project, or directory.
+The path to the project comes from the `ProjectReference`, so `AddProject` doesn't need a `.csproj` path. This is the main difference from <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" />, which points directly to a file, project, or directory.
 
 </TabItem>
 <TabItem id="typescript" label="TypeScript">
@@ -277,7 +278,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-For ASP.NET Core projects, Aspire reads the selected launch profile and can create endpoints from the `applicationUrl` field in _launchSettings.json_. You can then customize those endpoints with methods like `WithEndpoint`:
+For ASP.NET Core projects, Aspire reads the selected launch profile and can create endpoints from the `applicationUrl` field in _launchSettings.json_. You can then customize those endpoints with methods like <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -343,7 +344,7 @@ With that configuration:
 - The project receives its internal binding through `ASPNETCORE_URLS`.
 - Browsers and dependent resources talk to the proxy endpoint, not directly to a replica.
 
-Without `WithReplicas`, the proxy still fronts the project resource. The host port stays stable, while the project itself listens on a random internal port.
+Without <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithReplicas" />, the proxy still fronts the project resource. The host port stays stable, while the project itself listens on a random internal port.
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -397,7 +398,7 @@ In this configuration, Aspire assigns a random proxy port for the host-facing en
 
 ## Filter endpoints in environment variables
 
-Project resource endpoints follow default heuristics. Some endpoints are included in `ASPNETCORE_URLS`, some are published as `HTTP/HTTPS_PORTS`, and some are resolved from Kestrel configuration. Use `WithEndpointsInEnvironment` when you need to filter which endpoints are exposed through environment variables:
+Project resource endpoints follow default heuristics. Some endpoints are included in `ASPNETCORE_URLS`, some are published as `HTTP/HTTPS_PORTS`, and some are resolved from Kestrel configuration. Use <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithEndpointsInEnvironment" /> when you need to filter which endpoints are exposed through environment variables:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -554,7 +555,7 @@ In a **C# AppHost**, use `AddProject<T>` when you have a standard `.csproj`, can
 
 In a **TypeScript AppHost**, `addProject(name, path)` always takes a path, so the distinction between `AddProject<T>` and `AddCSharpApp` doesn't apply in the same way.
 
-Some .NET app types use specialized integrations instead of `AddProject`. For example, [.NET MAUI integration](/integrations/dotnet/maui/) uses `AddMauiProject` because MAUI apps aren't added to the AppHost through `ProjectReference` metadata.
+Some .NET app types use specialized integrations instead of `AddProject`. For example, [.NET MAUI integration](/integrations/dotnet/maui/) uses <ApiReference name="Aspire.Hosting.MauiProjectExtensions.AddMauiProject" /> because MAUI apps aren't added to the AppHost through `ProjectReference` metadata.
 
 ## Migrate from legacy project resources
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/bun-apps.mdx b/src/frontend/src/content/docs/integrations/frameworks/bun-apps.mdx
index e5cccbc742..dbceb3d2f1 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/bun-apps.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/bun-apps.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import bunIcon from '@assets/icons/bun-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={bunIcon}
@@ -80,7 +81,7 @@ The official package requires both paths. In TypeScript, replace the Toolkit opt
 
 ### Add Bun app
 
-Add a Bun application to your AppHost using `AddBunApp` / `addBunApp`:
+Add a Bun application to your AppHost using <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddBunApp" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -165,7 +166,7 @@ When your Bun app includes a `package.json` file, Aspire uses Bun as the package
 
 ### Configure HTTP endpoints
 
-Bun applications typically read the port from an environment variable. Use `WithHttpEndpoint` to declare the HTTP endpoint and bind it to a named environment variable:
+Bun applications typically read the port from an environment variable. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" /> to declare the HTTP endpoint and bind it to a named environment variable:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/frameworks/deno/deno-get-started.mdx b/src/frontend/src/content/docs/integrations/frameworks/deno/deno-get-started.mdx
index fbb17cb27c..a64672a214 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/deno/deno-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/deno/deno-get-started.mdx
@@ -10,6 +10,7 @@ import {
   TabItem,
   Tabs,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import denoIcon from '@assets/icons/deno-icon.png';
 import denoLightIcon from '@assets/icons/deno-light-icon.png';
@@ -30,7 +31,7 @@ The [Aspire Community Toolkit](https://github.com/CommunityToolkit/Aspire) Deno
 
 ## How the integration works
 
-The integration is a hosting integration: install it in the AppHost, then model each application with an `AddDenoApp` / `addDenoApp` resource or an `AddDenoTask` / `addDenoTask` resource. The resource runs the local `deno` command. You configure its working directory, permissions, arguments, endpoints, environment variables, and health checks in the AppHost.
+The integration is a hosting integration: install it in the AppHost, then model each application with an <ApiReference name="Aspire.Hosting.DenoAppHostingExtensions.AddDenoApp" /> resource or an <ApiReference name="Aspire.Hosting.DenoAppHostingExtensions.AddDenoTask" /> resource. The resource runs the local `deno` command. You configure its working directory, permissions, arguments, endpoints, environment variables, and health checks in the AppHost.
 
 `AddDenoApp` runs a script with `deno run`; `AddDenoTask` runs a task from `deno.json` or `deno.jsonc` with `deno task`. Both resource types participate in service discovery and can be referenced by other resources.
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/deno/deno-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/deno/deno-host.mdx
index f95a8687e4..8c71b1cef0 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/deno/deno-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/deno/deno-host.mdx
@@ -9,6 +9,7 @@ import LearnMore from '@components/LearnMore.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import denoIcon from '@assets/icons/deno-icon.png';
 import denoLightIcon from '@assets/icons/deno-light-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -34,7 +35,7 @@ The Deno executable must be available on `PATH` when Aspire runs the resource.
 
 ## Add a Deno script
 
-`AddDenoApp` / `addDenoApp` creates an executable resource that runs `deno run`, followed by permission flags, the script path, and application arguments.
+<ApiReference name="Aspire.Hosting.DenoAppHostingExtensions.AddDenoApp" /> creates an executable resource that runs `deno run`, followed by permission flags, the script path, and application arguments.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -80,7 +81,7 @@ Script resources set `DENO_ENV` to `development` in the development environment
 
 ## Add a Deno task
 
-`AddDenoTask` / `addDenoTask` runs `deno task <taskName>`, using the task configuration in the resource's working directory.
+<ApiReference name="Aspire.Hosting.DenoAppHostingExtensions.AddDenoTask" /> runs `deno task <taskName>`, using the task configuration in the resource's working directory.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -120,7 +121,7 @@ await builder.build().run();
 
 ## Install Deno packages before startup
 
-`WithDenoPackageInstallation` / `withDenoPackageInstallation` adds a `deno install` setup resource named `<resource-name>-deno-install`. The application waits for that setup resource to complete.
+<ApiReference name="Aspire.Hosting.DenoAppHostingExtensions.WithDenoPackageInstallation" /> adds a `deno install` setup resource named `<resource-name>-deno-install`. The application waits for that setup resource to complete.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -195,11 +196,11 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The application must read the `PORT` variable and listen on that port. It must also have the Deno permissions required to read its environment and serve network traffic. `WithHttpHealthCheck` / `withHttpHealthCheck` makes Aspire poll the specified HTTP path. Add `WithEndpoint` / `withEndpoint` when you need an additional endpoint definition, as in the Toolkit Deno samples.
+The application must read the `PORT` variable and listen on that port. It must also have the Deno permissions required to read its environment and serve network traffic. <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> makes Aspire poll the specified HTTP path. Add <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> when you need an additional endpoint definition, as in the Toolkit Deno samples.
 
 ## Resource actions and references
 
-The dashboard exposes the normal executable-resource lifecycle controls for Deno resources. Other AppHost resources can use `WithReference` / `withReference` and dependency APIs with a Deno resource because it supports service discovery. Add explicit endpoints before consumers need an address.
+The dashboard exposes the normal executable-resource lifecycle controls for Deno resources. Other AppHost resources can use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> and dependency APIs with a Deno resource because it supports service discovery. Add explicit endpoints before consumers need an address.
 
 ## Publishing behavior
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-get-started.mdx b/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-get-started.mdx
index 4433e4fc18..10d09eb460 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-get-started.mdx
@@ -6,6 +6,7 @@ description: Understand how the Aspire Dotnet hosting integration runs C# projec
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import ThemeImage from '@components/ThemeImage.astro';
 import csharpIcon from '@assets/icons/csharp.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <ThemeImage
   light={csharpIcon}
@@ -22,7 +23,7 @@ The Aspire `Aspire.Hosting.Dotnet` integration lets you add C# projects and file
 :::note
 `Aspire.Hosting.Dotnet` is a prerelease package. Its APIs remain unstable and may change in future releases.
 
-Starting with Aspire 13.6, `AddDotnetProject` / `addDotnetProject` no longer requires suppressing [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for these APIs after upgrading.
+Starting with Aspire 13.6, <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.AddDotnetProject" /> no longer requires suppressing [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for these APIs after upgrading.
 :::
 
 ## Why use the Dotnet hosting integration
@@ -31,7 +32,7 @@ Adding C# apps by path through `Aspire.Hosting.Dotnet` gives you:
 
 - **Path-based orchestration for C#.** Model a C# project or a file-based `.cs` app in the AppHost the same way you'd model a Go, Python, or JavaScript app added by path, without adding the project to the AppHost's solution.
 - **File-based app support.** Add a single `.cs` file-based app (requires .NET 10 or later) directly, matching the file-based apps experience for `dotnet run --file`.
-- **Familiar launch and configuration behavior.** Endpoints, environment variables, and service discovery are configured from the project's `launchSettings.json` and Kestrel configuration, matching `AddProject<T>`.
+- **Familiar launch and configuration behavior.** Endpoints, environment variables, and service discovery are configured from the project's `launchSettings.json` and Kestrel configuration, matching <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />.
 
 ## How the pieces fit together
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-host.mdx
index 7273d9709b..b4d4bce9e0 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/dotnet/dotnet-host.mdx
@@ -8,6 +8,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import csharpIcon from '@assets/icons/csharp.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <ThemeImage
   light={csharpIcon}
@@ -26,7 +27,7 @@ If you're new to the Dotnet integration, start with the [Get started with the .N
 :::note
 `Aspire.Hosting.Dotnet` is a prerelease package. Its APIs remain unstable and may change in future releases.
 
-Starting with Aspire 13.6, `AddDotnetProject`, `DotnetProjectResource`, and the related `WithBuildEnvironment` overloads no longer require suppressing [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for these APIs after upgrading.
+Starting with Aspire 13.6, <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.AddDotnetProject" />, `DotnetProjectResource`, and the related <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.WithBuildEnvironment" /> overloads no longer require suppressing [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/). You can remove existing suppressions for these APIs after upgrading.
 :::
 
 If your C# AppHost needs to reference the resource type directly — for example, to declare a strongly typed variable or a method parameter — import it from the `Aspire.Hosting.Dotnet` namespace, matching the pattern used by the Go, Python, and JavaScript hosting integrations:
@@ -130,7 +131,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-The resource launches with `dotnet run --project <path>` for a project file, or `dotnet run --file <path>` for a file-based app. Endpoints, environment variables, and service discovery are configured from the project's `launchSettings.json` and Kestrel configuration, matching `AddProject<T>`.
+The resource launches with `dotnet run --project <path>` for a project file, or `dotnet run --file <path>` for a file-based app. Endpoints, environment variables, and service discovery are configured from the project's `launchSettings.json` and Kestrel configuration, matching <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />.
 
 ## Add a file-based C# app
 
@@ -240,7 +241,7 @@ await builder.build().run();
 - `excludeLaunchProfile: true` disables launch profiles entirely and takes precedence over a supplied `launchProfileName`.
 - `excludeKestrelEndpoints: true` stops Aspire from deriving model endpoints from the project's Kestrel configuration. It doesn't rewrite or disable the service's own Kestrel configuration.
 
-These properties have the same behavior as the corresponding `LaunchProfileName`, `ExcludeLaunchProfile`, and `ExcludeKestrelEndpoints` properties on the C# `ProjectResourceOptions` type. The options are polyglot-specific to `addDotnetProject`; they don't change the shared `ProjectResourceOptions` handle used by the legacy `addProject` / `addCSharpApp` exports.
+These properties have the same behavior as the corresponding `LaunchProfileName`, `ExcludeLaunchProfile`, and `ExcludeKestrelEndpoints` properties on the C# `ProjectResourceOptions` type. The options are polyglot-specific to `addDotnetProject`; they don't change the shared `ProjectResourceOptions` handle used by the legacy `addProject` / <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> exports.
 
 ## Publishing
 
@@ -255,7 +256,7 @@ Use one of these alternatives:
   should use standard .NET project publishing.
 - Call `PublishAsDockerFile(...)` / `publishAsDockerFile(...)` to configure container publishing
   explicitly.
-- Call `ExcludeFromManifest()` / `excludeFromManifest()` when the resource is intentionally
+- Call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" /> when the resource is intentionally
   available only during local orchestration.
 
 ## See also
diff --git a/src/frontend/src/content/docs/integrations/frameworks/go/go-get-started.mdx b/src/frontend/src/content/docs/integrations/frameworks/go/go-get-started.mdx
index fba14adb34..85196481f5 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/go/go-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/go/go-get-started.mdx
@@ -7,6 +7,7 @@ import { LinkButton, Steps } from '@astrojs/starlight/components';
 import ThemeImage from '@components/ThemeImage.astro';
 import goIcon from '@assets/icons/go-icon.png';
 import goLightIcon from '@assets/icons/go-light-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <ThemeImage
   light={goLightIcon}
@@ -21,7 +22,7 @@ import goLightIcon from '@assets/icons/go-light-icon.png';
 The Aspire Go hosting integration lets you run Go applications alongside your other Aspire resources from the AppHost. Aspire runs Go apps with the local Go toolchain during development, wires them into the Aspire app model, supports service discovery and endpoint configuration, and can emit Dockerfile-based container build artifacts for deployment targets that need them.
 
 :::caution[Community Toolkit package deprecated]
-As of Aspire 13.4, Go hosting support is available in the official `Aspire.Hosting.Go` package. The previous `CommunityToolkit.Aspire.Hosting.Golang` package is deprecated because Go support has graduated into core Aspire. Use `Aspire.Hosting.Go` and `AddGoApp` / `addGoApp` for new Aspire 13.4+ applications.
+As of Aspire 13.4, Go hosting support is available in the official `Aspire.Hosting.Go` package. The previous `CommunityToolkit.Aspire.Hosting.Golang` package is deprecated because Go support has graduated into core Aspire. Use `Aspire.Hosting.Go` and <ApiReference name="Aspire.Hosting.GoHostingExtensions.AddGoApp" /> for new Aspire 13.4+ applications.
 :::
 
 ## Why use Go with Aspire
diff --git a/src/frontend/src/content/docs/integrations/frameworks/go/go-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/go/go-host.mdx
index 7288914782..9056fb1646 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/go/go-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/go/go-host.mdx
@@ -9,6 +9,7 @@ import LearnMore from '@components/LearnMore.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import goIcon from '@assets/icons/go-icon.png';
 import goLightIcon from '@assets/icons/go-light-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <ThemeImage
   light={goLightIcon}
@@ -25,7 +26,7 @@ This article is the reference for the Aspire Go hosting integration. It enumerat
 If you're new to the Go integration, start with the [Get started with the Go integration](/integrations/frameworks/go/go-get-started/) guide.
 
 :::caution[Community Toolkit package deprecated]
-As of Aspire 13.4, Go hosting support is available in the official `Aspire.Hosting.Go` package. The previous `CommunityToolkit.Aspire.Hosting.Golang` package is deprecated because Go support has graduated into core Aspire. Use `Aspire.Hosting.Go` and `AddGoApp` / `addGoApp` for new Aspire 13.4+ applications.
+As of Aspire 13.4, Go hosting support is available in the official `Aspire.Hosting.Go` package. The previous `CommunityToolkit.Aspire.Hosting.Golang` package is deprecated because Go support has graduated into core Aspire. Use `Aspire.Hosting.Go` and <ApiReference name="Aspire.Hosting.GoHostingExtensions.AddGoApp" /> for new Aspire 13.4+ applications.
 :::
 
 :::note[Prerequisites]
@@ -134,7 +135,7 @@ The method accepts the following common parameters:
 - **appDirectory**: The path to the Go module root. This directory usually contains `go.mod` and is also the Docker build context for deployment targets that emit container build artifacts.
 - **packagePath**: The Go package to run or build relative to `appDirectory`. Defaults to `"."`.
 
-Go applications commonly read the `PORT` environment variable set by `WithHttpEndpoint` / `withHttpEndpoint`:
+Go applications commonly read the `PORT` environment variable set by <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" />:
 
 ```go title="main.go"
 package main
@@ -267,7 +268,7 @@ The options map to Go command-line flags:
 
 ## Pass app arguments
 
-Use `WithAppArgs` / `withAppArgs` to pass arguments to the Go program after the package path.
+Use <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithAppArgs" /> to pass arguments to the Go program after the package path.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -345,10 +346,10 @@ await builder.build().run();
 
 The helper methods run these commands:
 
-- `WithModTidy` / `withModTidy`: Runs `go mod tidy -e`.
-- `WithModVendor` / `withModVendor`: Runs `go mod vendor`.
-- `WithModDownload` / `withModDownload`: Runs `go mod download`.
-- `WithVetTool` / `withVetTool`: Runs `go vet ./...`.
+- <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithModTidy" />: Runs `go mod tidy -e`.
+- <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithModVendor" />: Runs `go mod vendor`.
+- <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithModDownload" />: Runs `go mod download`.
+- <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithVetTool" />: Runs `go vet ./...`.
 
 When multiple module helpers are configured, Aspire orders them so dependency-changing steps complete before later module cache or vendor steps.
 
@@ -361,7 +362,7 @@ Go app resources automatically support VS Code debugging when the [Go extension
 The Aspire VS Code extension detects the `golang.go` extension and, when you start your AppHost in debug mode, launches the Go debugger via `dlv-dap`. No additional configuration is required beyond `AddGoApp` / `addGoApp`. Any `buildTags`, `ldFlags`, or `gcFlags` configured on the resource are automatically forwarded to Delve as build flags, so the debugger compiles your program with the same flags used during normal development.
 
 :::note
-When `WithDelveServer` / `withDelveServer` is applied to a resource, VS Code debugging is disabled for that resource. The two modes are mutually exclusive: `WithDelveServer` starts a headless Delve server that an IDE attaches to manually, while VS Code debugging hands control of launch and build to the `golang.go` extension.
+When <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithDelveServer" /> is applied to a resource, VS Code debugging is disabled for that resource. The two modes are mutually exclusive: `WithDelveServer` starts a headless Delve server that an IDE attaches to manually, while VS Code debugging hands control of launch and build to the `golang.go` extension.
 :::
 
 ### Headless Delve server
@@ -473,7 +474,7 @@ When a publisher or deployment target emits container build artifacts for a Go a
 - The runtime stage uses a small runtime image, installs certificate and time zone data for Alpine-based images, creates a non-root `app` user, and starts the compiled binary.
 - The generated `go build` command uses the same `packagePath`, `buildTags`, `ldFlags`, and `gcFlags` configured on the Go app resource. It intentionally excludes `raceDetector` for publish builds.
 
-For private modules, use `WithGoPrivate` / `withGoPrivate` to configure the generated Dockerfile with `GOPRIVATE` and BuildKit secret-based authentication. This setting only affects generated Dockerfiles; local run mode continues to use the developer's local Go and Git credentials.
+For private modules, use <ApiReference name="Aspire.Hosting.GoHostingExtensions.WithGoPrivate" /> to configure the generated Dockerfile with `GOPRIVATE` and BuildKit secret-based authentication. This setting only affects generated Dockerfiles; local run mode continues to use the developer's local Go and Git credentials.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/frameworks/java/java-connect.mdx b/src/frontend/src/content/docs/integrations/frameworks/java/java-connect.mdx
index bc3382ab15..d118e0616a 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/java/java-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/java/java-connect.mdx
@@ -96,7 +96,7 @@ When a resource references a Java app, Aspire injects the URL of each of the Jav
 | `ORDERS_HTTP`               | The URL of the `orders` app's `http` endpoint, named `{RESOURCE}_{ENDPOINT}`. Read this variable from apps that don't use .NET service discovery. |
 | `services__orders__http__0` | The same URL, in the format that [.NET service discovery](/fundamentals/service-discovery/) reads.                                                |
 
-`AddSpringBootApp` and `AddQuarkusApp` name their endpoint `http`. When you add an endpoint with a different name to a Java app, the variables use that name instead — for example, an endpoint named `admin` produces `ORDERS_ADMIN`. For the naming rules, see [Endpoint URLs](/fundamentals/environment-variables/#endpoint-urls) and [Service discovery variables](/fundamentals/environment-variables/#service-discovery-variables).
+<ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddSpringBootApp" /> and <ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddQuarkusApp" /> name their endpoint `http`. When you add an endpoint with a different name to a Java app, the variables use that name instead — for example, an endpoint named `admin` produces `ORDERS_ADMIN`. For the naming rules, see [Endpoint URLs](/fundamentals/environment-variables/#endpoint-urls) and [Service discovery variables](/fundamentals/environment-variables/#service-discovery-variables).
 
 ### Variables that a Java app receives
 
@@ -124,7 +124,7 @@ The Java integration also sets the following variables on the Java app itself:
 | `QUARKUS_PROFILE`, `QUARKUS_HTTP_HOST`, and `QUARKUS_OBSERVABILITY_ENABLED`               | Quarkus apps, when you run the AppHost | Dev mode settings. For details, see [Add a Quarkus app](/integrations/frameworks/java/java-host/#add-a-quarkus-app).                                                                              |
 | `JAVA_TOOL_OPTIONS`                                                                       | Java resources that need JVM options   | The options from <ApiReference name="Aspire.Hosting.JavaHostingExtensions.WithJvmArgs" />, the `-javaagent` option for the OpenTelemetry Java agent, and the development certificate trust store. |
 
-For an app that you add with `AddJavaApp`, the port variable is the one that you name with the `env` parameter of `WithHttpEndpoint`.
+For an app that you add with <ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddJavaApp" />, the port variable is the one that you name with the `env` parameter of <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" />.
 
 ## Call a Java app from other apps
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/javascript.mdx b/src/frontend/src/content/docs/integrations/frameworks/javascript.mdx
index 203bff73c0..297e408ba0 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/javascript.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/javascript.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import InstallPackage from '@components/InstallPackage.astro';
 import LearnMore from '@components/LearnMore.astro';
 import jsIcon from '@assets/icons/javascript.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={jsIcon}
@@ -29,11 +30,11 @@ To start building an Aspire app that uses JavaScript and TypeScript, install the
 
 The integration exposes a number of app resource types:
 
-- `JavaScriptAppResource`: Added with `AddJavaScriptApp` / `addJavaScriptApp` for general JavaScript applications
-- `NodeAppResource`: Added with `AddNodeApp` / `addNodeApp` for running specific JavaScript files with Node.js
-- `ViteAppResource`: Added with `AddViteApp` / `addViteApp` for Vite applications with Vite-specific defaults
-- `NextJsAppResource`: Added with `AddNextJsApp` / `addNextJsApp` for Next.js applications with Next.js-specific run and publish defaults
-- `BunAppResource`: Added with `AddBunApp` / `addBunApp` for applications running on the [Bun](https://bun.sh/) runtime — see the [Bun integration](/integrations/frameworks/bun-apps/) for details
+- `JavaScriptAppResource`: Added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" /> for general JavaScript applications
+- `NodeAppResource`: Added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" /> for running specific JavaScript files with Node.js
+- `ViteAppResource`: Added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> for Vite applications with Vite-specific defaults
+- `NextJsAppResource`: Added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" /> for Next.js applications with Next.js-specific run and publish defaults
+- `BunAppResource`: Added with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddBunApp" /> for applications running on the [Bun](https://bun.sh/) runtime — see the [Bun integration](/integrations/frameworks/bun-apps/) for details
 
 ## Framework examples
 
@@ -41,7 +42,7 @@ The following TypeScript AppHost examples show validated ways to wire common Jav
 
 - A backend API app lives in `./frameworks/api` and listens on the `PORT` environment variable.
 - The framework app lives in `./frameworks/<framework-name>`.
-- Docker Compose is shown as an example deployment target with `addDockerComposeEnvironment`.
+- Docker Compose is shown as an example deployment target with <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.AddDockerComposeEnvironment" />.
 
 For production deployment choices, see [Deploy JavaScript apps](/deployment/javascript-apps/).
 
@@ -63,7 +64,7 @@ const apiEndpoint = await api.getEndpoint('http');
 
 ### Vite
 
-Plain Vite apps that produce static browser files use `addViteApp` and `publishAsStaticWebsite`. The `apiPath` / `apiTarget` options configure the deployed static website to proxy `/api` requests to the backend.
+Plain Vite apps that produce static browser files use `addViteApp` and <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsStaticWebsite" />. The `apiPath` / `apiTarget` options configure the deployed static website to proxy `/api` requests to the backend.
 
 ```typescript title="apphost.mts"
 await builder
@@ -196,7 +197,7 @@ export default async function Home() {
 
 ### Nuxt
 
-Nuxt apps need `node_modules` at runtime for server-side rendering, so publish them with `publishAsPackageScript`. Set both `API_URL` for direct server-side code and `NUXT_API_URL` for Nuxt runtime config.
+Nuxt apps need `node_modules` at runtime for server-side rendering, so publish them with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsPackageScript" />. Set both `API_URL` for direct server-side code and `NUXT_API_URL` for Nuxt runtime config.
 
 ```typescript title="apphost.mts"
 await builder
@@ -233,7 +234,7 @@ export default defineEventHandler(async () => {
 
 ### SvelteKit
 
-SvelteKit with `@sveltejs/adapter-node` produces a self-contained Node server artifact, so publish it with `publishAsNodeServer`.
+SvelteKit with `@sveltejs/adapter-node` produces a self-contained Node server artifact, so publish it with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsNodeServer" />.
 
 ```typescript title="apphost.mts"
 await builder
@@ -489,7 +490,7 @@ module.exports = nextConfig;
 
 :::
 
-To opt out of the configuration validation step, call `DisableBuildValidation` / `disableBuildValidation`:
+To opt out of the configuration validation step, call <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.DisableBuildValidation" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -565,10 +566,10 @@ const viteApp = await builder
 
 `AddViteApp` automatically configures:
 
-- **HTTP endpoint**: Registers an `http` endpoint and sets the `PORT` environment variable — you don't need to call `WithHttpEndpoint` yourself
+- **HTTP endpoint**: Registers an `http` endpoint and sets the `PORT` environment variable — you don't need to call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" /> yourself
 - **Development script**: Runs the "dev" script (typically `vite`) during local development
 - **Build script**: Runs the "build" script (typically `vite build`) when publishing
-- **Package manager**: Uses npm by default, but can be customized with `WithYarn()`, `WithPnpm()`, or `WithBun()`
+- **Package manager**: Uses npm by default, but can be customized with <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" />, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithPnpm" />, or <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithBun" />
 
 :::caution
 Do _not_ call `.WithHttpEndpoint()` on a Vite resource. `AddViteApp` already registers an `http` endpoint with the `PORT` environment variable, and adding another causes a duplicate endpoint error at runtime.
@@ -863,7 +864,7 @@ const app = await builder
 
 ### Pass arguments to scripts
 
-To pass command-line arguments to your scripts, use `WithArgs` / `withArgs`:
+To pass command-line arguments to your scripts, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -1075,7 +1076,7 @@ const viteApp = await builder
 
 </Tabs>
 
-The `WithViteConfig` / `withViteConfig` configuration accepts:
+The <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.WithViteConfig" /> configuration accepts:
 
 - **configPath**: The path to the Vite configuration file, relative to the Vite service project root.
 
@@ -1126,7 +1127,7 @@ The HTTPS configuration is automatically applied without modifying your `vite.co
 
 When your Vite app needs to communicate with a backend API, pass the API URL via an environment variable. Vite only exposes variables prefixed with `VITE_` to client-side code.
 
-In your AppHost, expose the API URL to the Vite app using `WithEnvironment` / `withEnvironment`:
+In your AppHost, expose the API URL to the Vite app using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/frameworks/nodejs-extensions.mdx b/src/frontend/src/content/docs/integrations/frameworks/nodejs-extensions.mdx
index e507b2f687..79015f363c 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/nodejs-extensions.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/nodejs-extensions.mdx
@@ -8,6 +8,7 @@ import InstallPackage from '@components/InstallPackage.astro';
 import ThemeImage from '@components/ThemeImage.astro';
 import nodejsIcon from '@assets/icons/nodejs-icon.png';
 import nodejsLightIcon from '@assets/icons/nodejs-light-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -27,12 +28,12 @@ Start with an existing Nx or Turborepo workspace. Pass the workspace root as `wo
 
 The extensions add:
 
-- `AddNxApp` / `addNxApp` for an Nx workspace.
-- `AddTurborepoApp` / `addTurborepoApp` for a Turborepo workspace.
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNxApp" /> for an Nx workspace.
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddTurborepoApp" /> for a Turborepo workspace.
 - `AddApp` / `addApp` for apps within those workspaces.
-- `WithNpm`, `WithYarn`, `WithPnpm`, and `WithBun` to select the workspace package manager.
+- `WithNpm`, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" />, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithPnpm" />, and <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithBun" /> to select the workspace package manager.
 - `WithPackageManagerLaunch` / `withPackageManagerLaunch` to launch the workspace through the selected package manager.
-- `WithMappedEndpointPort` / `withMappedEndpointPort` to pass an Aspire endpoint's allocated port to a JavaScript app.
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.WithMappedEndpointPort" /> to pass an Aspire endpoint's allocated port to a JavaScript app.
 
 ## Hosting integration
 
@@ -144,7 +145,7 @@ await builder.build().run();
 </Tabs>
 
 :::note[Use the official package for individual apps]
-`AddNodeApp`, `AddViteApp`, `AddNextJsApp`, and `AddBunApp`, together with the generic `WithNpm`, `WithYarn`, `WithPnpm`, and `WithBun` decorators for individual JavaScript resources, are provided by `Aspire.Hosting.JavaScript`. They aren't APIs from this Community Toolkit package.
+<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" />, <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" />, <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" />, and <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddBunApp" />, together with the generic `WithNpm`, `WithYarn`, `WithPnpm`, and `WithBun` decorators for individual JavaScript resources, are provided by `Aspire.Hosting.JavaScript`. They aren't APIs from this Community Toolkit package.
 :::
 
 ## See also
diff --git a/src/frontend/src/content/docs/integrations/frameworks/orleans.mdx b/src/frontend/src/content/docs/integrations/frameworks/orleans.mdx
index 80061b9c10..edb151816a 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/orleans.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/orleans.mdx
@@ -9,6 +9,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import InstallPackage from '@components/InstallPackage.astro';
 import orleansIcon from '@assets/icons/microsoft-orleans.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={orleansIcon}
@@ -78,7 +79,7 @@ This updates your `aspire.config.json` with the Orleans hosting integration pack
 
 ### Add an Orleans resource
 
-Call `addOrleans` (or `AddOrleans`) to add and return an Orleans service resource builder. The name provided to the Orleans resource is for diagnostic purposes. For most applications, a value of `"default"` suffices:
+Call <ApiReference name="Aspire.Hosting.OrleansServiceExtensions.AddOrleans" /> to add and return an Orleans service resource builder. The name provided to the Orleans resource is for diagnostic purposes. For most applications, a value of `"default"` suffices:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -118,7 +119,7 @@ To configure Orleans with Azure Storage clustering and grain storage, first inst
 
 <InstallPackage packageName="Aspire.Hosting.Azure.Storage" />
 
-Then configure the Orleans resource with clustering and grain storage using `withClustering` (or `WithClustering`) and `withGrainStorage` (or `WithGrainStorage`):
+Then configure the Orleans resource with clustering and grain storage using <ApiReference name="Aspire.Hosting.OrleansServiceExtensions.WithClustering" /> and <ApiReference name="Aspire.Hosting.OrleansServiceExtensions.WithGrainStorage" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/frameworks/perl/perl-get-started.mdx b/src/frontend/src/content/docs/integrations/frameworks/perl/perl-get-started.mdx
index c719c173a2..72d99d6023 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/perl/perl-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/perl/perl-get-started.mdx
@@ -10,6 +10,7 @@ import {
   TabItem,
   Tabs,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import { Image } from 'astro:assets';
 import perlIcon from '@assets/icons/perl-096-1500.svg';
 
@@ -50,7 +51,7 @@ architecture-beta
 ## Prerequisites
 
 - Install [Perl](https://www.perl.org/get.html) and ensure `perl` and `cpan` are on `PATH`.
-- Install `cpanm` when you use `WithCpanMinus`, `WithLocalLib`, or project dependency installation without Carton. Install `carton` when you use Carton.
+- Install `cpanm` when you use <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithCpanMinus" />, <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithLocalLib" />, or project dependency installation without Carton. Install `carton` when you use Carton.
 - Install the [Aspire CLI](/get-started/install-cli/) and create an AppHost.
 
 :::note
diff --git a/src/frontend/src/content/docs/integrations/frameworks/perl/perl-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/perl/perl-host.mdx
index 427e9d6cd5..6bf637fcc5 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/perl/perl-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/perl/perl-host.mdx
@@ -8,6 +8,7 @@ import { Badge, TabItem, Tabs } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import LearnMore from '@components/LearnMore.astro';
 import perlIcon from '@assets/icons/perl-096-1500.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -71,10 +72,10 @@ Each `AddPerl*` / `addPerl*` method accepts a resource name, an application dire
 
 | API                                       | Local command and arguments                    |
 | ----------------------------------------- | ---------------------------------------------- |
-| `AddPerlScript` / `addPerlScript`         | `perl -s <scriptName>`                         |
-| `AddPerlApi` / `addPerlApi`               | `perl <scriptName> daemon`                     |
-| `AddPerlModule` / `addPerlModule`         | `perl -M<moduleName> -e "<moduleName>->run()"` |
-| `AddPerlExecutable` / `addPerlExecutable` | Runs `<executablePath>` directly               |
+| <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.AddPerlScript" />         | `perl -s <scriptName>`                         |
+| <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.AddPerlApi" />               | `perl <scriptName> daemon`                     |
+| <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.AddPerlModule" />         | `perl -M<moduleName> -e "<moduleName>->run()"` |
+| <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.AddPerlExecutable" /> | Runs `<executablePath>` directly               |
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -111,11 +112,11 @@ const executable = await builder.addPerlExecutable(
 </TabItem>
 </Tabs>
 
-All entrypoints require `perl` and `cpan` to be available. Aspire adds the standard executable-resource lifecycle actions and process logs; the integration doesn't add a Perl-specific dashboard command. `WithCpanMinus` and `WithCarton` add their own command requirement checks.
+All entrypoints require `perl` and `cpan` to be available. Aspire adds the standard executable-resource lifecycle actions and process logs; the integration doesn't add a Perl-specific dashboard command. <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithCpanMinus" /> and <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithCarton" /> add their own command requirement checks.
 
 ## Configure endpoints, arguments, and environment
 
-Perl resources don't add an HTTP endpoint or health check automatically. For an API, configure the application to listen on a port and add the standard AppHost endpoint. Use normal resource APIs such as `WithArgs` / `withArgs`, `WithReference` / `withReference`, and `WaitFor` / `waitFor` to supply arguments and model dependencies.
+Perl resources don't add an HTTP endpoint or health check automatically. For an API, configure the application to listen on a port and add the standard AppHost endpoint. Use normal resource APIs such as <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" />, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> to supply arguments and model dependencies.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -142,7 +143,7 @@ Every Perl resource configures OTLP export and sets `OTEL_TRACES_EXPORTER`, `OTE
 
 ### Configure a local::lib
 
-`WithLocalLib` / `withLocalLib` isolates modules in a local directory. Relative paths are resolved from `appDirectory`; rooted paths are used as supplied. The default path is `local`.
+<ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithLocalLib" /> isolates modules in a local directory. Relative paths are resolved from `appDirectory`; rooted paths are used as supplied. The default path is `local`.
 
 It sets `PERL5LIB` to `<path>/lib/perl5`, `PERL_LOCAL_LIB_ROOT` to `<path>`, `PERL_MM_OPT` to `INSTALL_BASE=<path>`, and `PERL_MB_OPT` to `--install_base <path>`. If CPAN is active, the integration changes to cpanm because CPAN doesn't support the needed `--local-lib` option.
 
@@ -171,7 +172,7 @@ await worker.withLocalLib('local');
 
 ### Trust development certificates
 
-`WithPerlCertificateTrust` / `withPerlCertificateTrust` is experimental. When Aspire provides a certificate bundle, it sets `SSL_CERT_FILE`, `PERL_LWP_SSL_CA_FILE`, and `MOJO_CA_FILE` on the app and its dependency installers.
+<ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithPerlCertificateTrust" /> is experimental. When Aspire provides a certificate bundle, it sets `SSL_CERT_FILE`, `PERL_LWP_SSL_CA_FILE`, and `MOJO_CA_FILE` on the app and its dependency installers.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -194,7 +195,7 @@ await api.withPerlCertificateTrust();
 
 ## Install dependencies
 
-The default package manager is CPAN. `WithPackage` / `withPackage` creates a child installer resource in run mode and makes the Perl app wait for it to complete. Use `force` to force an install and `skipTest` to skip package tests.
+The default package manager is CPAN. <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithPackage" /> creates a child installer resource in run mode and makes the Perl app wait for it to complete. Use `force` to force an install and `skipTest` to skip package tests.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -221,7 +222,7 @@ await api.withPackage('Mojolicious', false, true);
 
 ### Install dependencies from a cpanfile
 
-`WithProjectDependencies` / `withProjectDependencies` creates one project installer in run mode. It expects `cpanfile` in the working directory:
+<ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithProjectDependencies" /> creates one project installer in run mode. It expects `cpanfile` in the working directory:
 
 - CPAN is automatically changed to cpanm, which runs `cpanm --installdeps --notest .`.
 - Carton runs `carton install`. Set `cartonDeployment` to add `--deployment`; this requires `cpanfile.snapshot`.
@@ -266,7 +267,7 @@ await worker.withProjectDependencies(true);
 
 ## Use perlbrew
 
-`WithPerlbrew` / `withPerlbrew` is an alias for `WithPerlbrewEnvironment` / `withPerlbrewEnvironment`. Both select a perlbrew version, accepting `5.40.0` or `perl-5.40.0`, and optionally accept the perlbrew root. The default root comes from `PERLBREW_ROOT` or `~/perl5/perlbrew`.
+<ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithPerlbrew" /> is an alias for <ApiReference name="Aspire.Hosting.PerlAppResourceBuilderExtensions.WithPerlbrewEnvironment" />. Both select a perlbrew version, accepting `5.40.0` or `perl-5.40.0`, and optionally accept the perlbrew root. The default root comes from `PERLBREW_ROOT` or `~/perl5/perlbrew`.
 
 The integration switches the command to the selected Perl executable, sets `PERLBREW_ROOT`, `PERLBREW_PERL`, and `PERLBREW_HOME`, and prepends the Perl bin directory to `PATH`. `WithLocalLib` remains useful to keep project modules separate from the perlbrew installation.
 
diff --git a/src/frontend/src/content/docs/integrations/frameworks/powershell/powershell-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/powershell/powershell-host.mdx
index 502b618a77..7847238152 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/powershell/powershell-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/powershell/powershell-host.mdx
@@ -6,6 +6,7 @@ description: Configure PowerShell runspace pools, scripts, arguments, dependenci
 import { Badge, TabItem, Tabs } from '@astrojs/starlight/components';
 import { Image } from 'astro:assets';
 import powershellIcon from '@assets/icons/powershell-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={powershellIcon}
@@ -50,7 +51,7 @@ This adds the package to `aspire.config.json` and generates the TypeScript AppHo
 
 ## Add a runspace pool
 
-`AddPowerShell` / `addPowerShell` adds a runspace-pool resource. The resource name is shown in the dashboard. By default, the pool uses `ConstrainedLanguage` mode with one to five runspaces.
+<ApiReference name="CommunityToolkit.Aspire.Hosting.PowerShell.DistributedApplicationBuilderExtensions.AddPowerShell" /> adds a runspace-pool resource. The resource name is shown in the dashboard. By default, the pool uses `ConstrainedLanguage` mode with one to five runspaces.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -89,9 +90,9 @@ Use the least-permissive language mode appropriate for the scripts you run. The
 
 ## Add scripts and arguments
 
-`AddScript` / `addScript` creates a child script resource. Aspire parses the script when the AppHost is built, starts it after the pool is running, and streams output, errors, warnings, information, verbose, and debug records to the resource logs.
+<ApiReference name="CommunityToolkit.Aspire.Hosting.PowerShell.PowerShellRunspacePoolResourceBuilderExtensions.AddScript" /> creates a child script resource. Aspire parses the script when the AppHost is built, starts it after the pool is running, and streams output, errors, warnings, information, verbose, and debug records to the resource logs.
 
-Use `WithArgs` / `withArgs` to bind values to a PowerShell `param()` block. The C# `object[]` overload accepts values of any type but is marked `[AspireExportIgnore]` because `object[]` isn't ATS-compatible. The exported TypeScript bridge accepts strings.
+Use <ApiReference name="CommunityToolkit.Aspire.Hosting.PowerShell.PowerShellScriptResourceBuilderExtensions.WithArgs" /> to bind values to a PowerShell `param()` block. The C# `object[]` overload accepts values of any type but is marked `[AspireExportIgnore]` because `object[]` isn't ATS-compatible. The exported TypeScript bridge accepts strings.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -131,7 +132,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-Scripts execute in the AppHost process's current working directory. The integration has no `WithWorkingDirectory` API, so use absolute paths or set a location in the script when its file operations must be independent of the host's launch directory.
+Scripts execute in the AppHost process's current working directory. The integration has no <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.WithWorkingDirectory" /> API, so use absolute paths or set a location in the script when its file operations must be independent of the host's launch directory.
 
 The script resource implements the standard environment annotation interface, but the in-process runner doesn't project those annotations into the runspace. A script can read environment variables inherited by the AppHost process through PowerShell's `$env:` provider.
 
@@ -168,7 +169,7 @@ The pool resolves these variables before it opens. This is distinct from an envi
 
 ## Order scripts and resources
 
-Use `WaitFor` / `waitFor` for readiness dependencies. Each script automatically waits for its parent pool. Use `WaitForCompletion` / `waitForCompletion` when one script must finish before another script starts.
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> for readiness dependencies. Each script automatically waits for its parent pool. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" /> when one script must finish before another script starts.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/frameworks/python.mdx b/src/frontend/src/content/docs/integrations/frameworks/python.mdx
index 5c11e45344..354f2cbf3c 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/python.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/python.mdx
@@ -8,6 +8,7 @@ import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallPackage from '@components/InstallPackage.astro';
 import { Image } from 'astro:assets';
 import pythonIcon from '@assets/icons/python.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={pythonIcon}
@@ -29,10 +30,10 @@ The Aspire Python hosting integration lets you model Python scripts, modules, ex
 
 Remove the deprecated `CommunityToolkit.Aspire.Hosting.Python.Extensions` package reference, then install `Aspire.Hosting.Python`. Replace Toolkit-specific helpers with the official APIs that match the process you run:
 
-- Use `AddUvicornApp` / `addUvicornApp` for ASGI apps.
-- Replace `AddUvApp` with `AddPythonApp` / `addPythonApp` and `WithUv` / `withUv`.
-- Use `AddPythonExecutable` / `addPythonExecutable` for an executable installed in the Python environment.
-- Pass application arguments with `WithArgs` / `withArgs` instead of the deprecated `AddPythonApp` overloads that accept script arguments.
+- Use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddUvicornApp" /> for ASGI apps.
+- Replace `AddUvApp` with <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" /> and <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithUv" />.
+- Use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonExecutable" /> for an executable installed in the Python environment.
+- Pass application arguments with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" /> instead of the deprecated `AddPythonApp` overloads that accept script arguments.
 
 The examples in this article use only `Aspire.Hosting.Python`.
 
@@ -93,7 +94,7 @@ await builder.build().run();
 
 ## Add Python module
 
-Use `AddPythonModule` to run a Python module (the equivalent of `python -m <module>`):
+Use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonModule" /> to run a Python module (the equivalent of `python -m <module>`):
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -293,7 +294,7 @@ The official integration doesn't expose a C# or TypeScript API to disable virtua
 
 ### Custom virtual environment
 
-To specify a custom virtual environment path, use `WithVirtualEnvironment`:
+To specify a custom virtual environment path, use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithVirtualEnvironment" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -371,7 +372,7 @@ await builder.build().run();
 
 ### pip package manager
 
-Use `WithPip` to explicitly select pip:
+Use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithPip" /> to explicitly select pip:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -414,7 +415,7 @@ If neither `WithUv` nor `WithPip` is specified, Aspire automatically selects the
 
 ## Configure endpoints
 
-Python apps typically read the port from an environment variable. Use `WithHttpEndpoint` to declare the port and inject the variable name:
+Python apps typically read the port from an environment variable. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" /> to declare the port and inject the variable name:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -529,7 +530,7 @@ await builder.build().run();
 
 ## Environment variables
 
-Inject arbitrary environment variables with `WithEnvironment`:
+Inject arbitrary environment variables with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -568,7 +569,7 @@ await builder.build().run();
 
 ## Service discovery
 
-Reference other Aspire resources from a Python app using `WithReference`. Aspire injects the connection string as the `ConnectionStrings__<resourcename>` environment variable in the Python process:
+Reference other Aspire resources from a Python app using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />. Aspire injects the connection string as the `ConnectionStrings__<resourcename>` environment variable in the Python process:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -621,7 +622,7 @@ For details about how resource names map to environment variable names, see [Env
 
 ## HTTPS configuration
 
-By default, Python apps run over HTTP in local development. To enable HTTPS, use `WithHttpsEndpoint` together with `WithHttpsDeveloperCertificate`:
+By default, Python apps run over HTTP in local development. To enable HTTPS, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsEndpoint" /> together with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsDeveloperCertificate" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -683,7 +684,7 @@ HTTPS is needed primarily when your Python service is exposed externally. For in
 
 ## Internal versus external service exposure
 
-By default, Aspire services are only accessible within the distributed application. Use `WithExternalHttpEndpoints` to expose a service to external traffic:
+By default, Aspire services are only accessible within the distributed application. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" /> to expose a service to external traffic:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/frameworks/rust/rust-host.mdx b/src/frontend/src/content/docs/integrations/frameworks/rust/rust-host.mdx
index 6adf98b840..632bc83095 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/rust/rust-host.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/rust/rust-host.mdx
@@ -206,7 +206,7 @@ Each of the following methods adds a Cargo option. Aspire places the options in
 | <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoManifestPath" /> | `--manifest-path` | Builds from a `Cargo.toml` file other than the one that Cargo finds from the app directory, such as a workspace member's manifest. To publish, the path must be relative to the app directory and inside it. |
 | <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoTarget" />       | `--target`        | Builds for a target triple, such as `x86_64-unknown-linux-musl`.                                                                                                                                             |
 | <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoLocked" />       | `--locked`        | Fails the build rather than updating `Cargo.lock`. Pass `false` to turn off the publishing default.                                                                                                          |
-| <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoProfile" />      | `--profile`       | Builds with a named profile. It takes precedence over `WithCargoReleaseBuild`, because Cargo rejects `--profile` together with `--release`.                                                                  |
+| <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoProfile" />      | `--profile`       | Builds with a named profile. It takes precedence over <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoReleaseBuild" />, because Cargo rejects `--profile` together with `--release`.                                                                  |
 | <ApiReference name="Aspire.Hosting.RustHostingExtensions.WithCargoReleaseBuild" /> | `--release`       | Builds with the `release` profile. Pass `false` to turn off the publishing default.                                                                                                                          |
 
 Aspire passes the values of `WithCargoArgs` to Cargo without interpreting them. Debugging and publishing work out which binary Cargo produces from the methods in the preceding table alone, so select the package, binary, example, manifest, profile, and target triple with those methods rather than with `WithCargoArgs`. In C#, [another overload of `WithCargoArgs`](/reference/api/csharp/aspire.hosting.rust/rusthostingextensions/methods/#withcargoargs-iresourcebuilder-t-action-rustcargoargscallbackcontext) takes a callback that computes Cargo arguments when the app starts.
diff --git a/src/frontend/src/content/docs/integrations/frameworks/wpf-winforms.mdx b/src/frontend/src/content/docs/integrations/frameworks/wpf-winforms.mdx
index c5a78bcc74..97f096a07e 100644
--- a/src/frontend/src/content/docs/integrations/frameworks/wpf-winforms.mdx
+++ b/src/frontend/src/content/docs/integrations/frameworks/wpf-winforms.mdx
@@ -6,6 +6,7 @@ description: Learn how to orchestrate WPF and Windows Forms desktop applications
 import { Image } from 'astro:assets';
 import { Steps } from '@astrojs/starlight/components';
 import dotnetIcon from '@assets/icons/dotnet.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -16,7 +17,7 @@ import dotnetIcon from '@assets/icons/dotnet.svg';
   data-zoom-off
 />
 
-WPF (Windows Presentation Foundation) and Windows Forms are .NET desktop UI frameworks for building Windows applications. Because they are standard .NET projects, you can register them in an Aspire AppHost alongside your backend services using the same `AddProject` API you use for web and worker services. Aspire then starts and monitors the desktop app as a local process resource when you run the AppHost during development.
+WPF (Windows Presentation Foundation) and Windows Forms are .NET desktop UI frameworks for building Windows applications. Because they are standard .NET projects, you can register them in an Aspire AppHost alongside your backend services using the same <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> API you use for web and worker services. Aspire then starts and monitors the desktop app as a local process resource when you run the AppHost during development.
 
 :::note
 WPF and Windows Forms applications require Windows and are **not** containerized or included in [`aspire deploy`](/reference/cli/commands/aspire-deploy/) output. Aspire orchestrates them as local processes during development only. For production deployment, use your existing desktop tooling (MSIX, ClickOnce, and so on).
diff --git a/src/frontend/src/content/docs/integrations/messaging/apache-kafka/apache-kafka-host.mdx b/src/frontend/src/content/docs/integrations/messaging/apache-kafka/apache-kafka-host.mdx
index 638c0ebfec..2f4180b450 100644
--- a/src/frontend/src/content/docs/integrations/messaging/apache-kafka/apache-kafka-host.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/apache-kafka/apache-kafka-host.mdx
@@ -8,6 +8,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import kafkaIcon from '@assets/icons/apache-kafka-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={kafkaIcon}
@@ -159,7 +160,7 @@ The Kafka UI is a free, open-source web UI to monitor and manage Apache Kafka cl
 
 ## Change the Kafka UI host port
 
-To change the host port the Kafka UI listens on, chain a call to `WithHostPort` (or `withHostPort`):
+To change the host port the Kafka UI listens on, chain a call to <ApiReference name="Aspire.Hosting.KafkaBuilderExtensions.WithHostPort" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/messaging/lavinmq/lavinmq-host.mdx b/src/frontend/src/content/docs/integrations/messaging/lavinmq/lavinmq-host.mdx
index bf8f69a80f..1b38a1052d 100644
--- a/src/frontend/src/content/docs/integrations/messaging/lavinmq/lavinmq-host.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/lavinmq/lavinmq-host.mdx
@@ -7,6 +7,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import lavinmqIcon from '@assets/icons/lavinmq-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
@@ -48,7 +49,7 @@ Or add the package manually:
 aspire add CommunityToolkit.Aspire.Hosting.LavinMQ
 ```
 
-This adds the package to `aspire.config.json`. After `aspire restore`, `.aspire/modules/aspire.mjs` includes `addLavinMQ`, the persistence APIs, and the exported endpoint properties.
+This adds the package to `aspire.config.json`. After `aspire restore`, `.aspire/modules/aspire.mjs` includes <ApiReference name="Aspire.Hosting.LavinMQHostingExtension.AddLavinMQ" />, the persistence APIs, and the exported endpoint properties.
 
 </TabItem>
 </Tabs>
@@ -143,7 +144,7 @@ When you omit these parameters, the integration binds host ports `5672` and
 
 ## Persist data in a volume
 
-`WithDataVolume` and `withDataVolume` require a volume name and mount it at `/var/lib/lavinmq`:
+<ApiReference name="Aspire.Hosting.LavinMQHostingExtension.WithDataVolume" /> requires a volume name and mounts it at `/var/lib/lavinmq`:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/messaging/nats/nats-get-started.mdx b/src/frontend/src/content/docs/integrations/messaging/nats/nats-get-started.mdx
index 01f9558f89..99a369251d 100644
--- a/src/frontend/src/content/docs/integrations/messaging/nats/nats-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/nats/nats-get-started.mdx
@@ -7,6 +7,7 @@ description: "Use the Aspire NATS hosting and client integrations to spin up NAT
 import { Image } from 'astro:assets';
 import { LinkButton, Steps } from '@astrojs/starlight/components';
 import natsIcon from '@assets/icons/nats-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={natsIcon}
@@ -27,7 +28,7 @@ Adding NATS through Aspire — rather than wiring up containers and connection s
 - **Consistent connection info across languages.** Once you reference the NATS resource from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when NATS is ready.
 - **Dashboard observability.** The NATS resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
-- **JetStream support.** Enable persistent streaming with a single call to `WithJetStream` (or `withJetStream`), and combine it with a data volume for durable storage across container restarts.
+- **JetStream support.** Enable persistent streaming with a single call to <ApiReference name="Aspire.Hosting.NatsBuilderExtensions.WithJetStream" />, and combine it with a data volume for durable storage across container restarts.
 - **A first-class C# client integration.** C# apps can use the `Aspire.NATS.Net` package for dependency injection, health checks, and OpenTelemetry, all wired up from the same resource name.
 
 ## How the pieces fit together
diff --git a/src/frontend/src/content/docs/integrations/messaging/nats/nats-host.mdx b/src/frontend/src/content/docs/integrations/messaging/nats/nats-host.mdx
index e264b9e814..ea1f8f70a7 100644
--- a/src/frontend/src/content/docs/integrations/messaging/nats/nats-host.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/nats/nats-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import natsIcon from '@assets/icons/nats-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={natsIcon}
@@ -123,7 +124,7 @@ await builder.addNodeApp("api", "./api", "index.js")
 
 ## Add NATS resource with JetStream
 
-[JetStream](https://docs.nats.io/nats-concepts/jetstream) is NATS's built-in persistence engine that provides at-least-once delivery, replay, and stream retention. To enable JetStream on the NATS resource, use `WithJetStream` (or `withJetStream`):
+[JetStream](https://docs.nats.io/nats-concepts/jetstream) is NATS's built-in persistence engine that provides at-least-once delivery, replay, and stream retention. To enable JetStream on the NATS resource, use <ApiReference name="Aspire.Hosting.NatsBuilderExtensions.WithJetStream" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-connect.mdx b/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-connect.mdx
index ad83f1c093..ee9bf4c7a1 100644
--- a/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-connect.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Badge, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import rabbitmqIcon from '@assets/icons/rabbitmq-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={rabbitmqIcon}
@@ -67,7 +68,7 @@ This is the **recommended approach** because Aspire manages the resource lifecyc
 
 When your AppHost uses `builder.AddConnectionString("messaging")` to reference an existing, pre-configured RabbitMQ server outside Aspire's control, only a **single connection string** environment variable is injected:
 
-- `ConnectionStrings__messaging` = the full connection string provided to `AddConnectionString`
+- `ConnectionStrings__messaging` = the full connection string provided to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />
 
 With this approach, there are **no individual property variables** (`MESSAGING_HOST`, `MESSAGING_PORT`, etc.). Consuming apps must parse the connection string themselves or use client libraries that accept a connection string directly.
 
diff --git a/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-host.mdx b/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-host.mdx
index 253d5f57d1..58da8cc969 100644
--- a/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-host.mdx
+++ b/src/frontend/src/content/docs/integrations/messaging/rabbitmq/rabbitmq-host.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import LearnMore from '@components/LearnMore.astro';
 import rabbitmqIcon from '@assets/icons/rabbitmq-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={rabbitmqIcon}
@@ -248,7 +249,7 @@ When no `password` parameter is provided, Aspire generates a strong password aut
 
 ## Add RabbitMQ server resource with management plugin
 
-To add the [RabbitMQ management plugin](https://www.rabbitmq.com/docs/management) as a sub-resource, call `WithManagementPlugin` (or `withManagementPlugin`). You'll need the credentials you configured to log in to the management UI:
+To add the [RabbitMQ management plugin](https://www.rabbitmq.com/docs/management) as a sub-resource, call <ApiReference name="Aspire.Hosting.RabbitMQBuilderExtensions.WithManagementPlugin" />. You'll need the credentials you configured to log in to the management UI:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -354,7 +355,7 @@ await builder.build().run();
 
 ## Connect to an existing RabbitMQ instance
 
-To reference an externally managed RabbitMQ instance instead of running one as a container, use `AddConnectionString`:
+To reference an externally managed RabbitMQ instance instead of running one as a container, use <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -396,7 +397,7 @@ For the full reference of RabbitMQ resource connection properties — and how co
 
 ## RabbitMQ 4.3 queue declaration requirements
 
-Starting with Aspire 13.4, the default RabbitMQ container image used by `AddRabbitMQ` is **4.3**. RabbitMQ 4.3 disables the deprecated `transient_nonexcl_queues` feature by default. Declaring a queue that is simultaneously non-durable (transient) and non-exclusive is rejected by the broker with AMQP error 541 (`INTERNAL_ERROR - Feature 'transient_nonexcl_queues' is deprecated.`).
+Starting with Aspire 13.4, the default RabbitMQ container image used by <ApiReference name="Aspire.Hosting.RabbitMQBuilderExtensions.AddRabbitMQ" /> is **4.3**. RabbitMQ 4.3 disables the deprecated `transient_nonexcl_queues` feature by default. Declaring a queue that is simultaneously non-durable (transient) and non-exclusive is rejected by the broker with AMQP error 541 (`INTERNAL_ERROR - Feature 'transient_nonexcl_queues' is deprecated.`).
 
 If your application declares such queues, switch to one of the supported patterns:
 
diff --git a/src/frontend/src/content/docs/integrations/observability/seq/seq-connect.mdx b/src/frontend/src/content/docs/integrations/observability/seq/seq-connect.mdx
index 1bd43db333..783b64b7e1 100644
--- a/src/frontend/src/content/docs/integrations/observability/seq/seq-connect.mdx
+++ b/src/frontend/src/content/docs/integrations/observability/seq/seq-connect.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import seqIcon from '@assets/icons/seq-icon.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={seqIcon}
@@ -317,5 +318,5 @@ await logger.close();
 </Tabs>
 
 <Aside type="tip">
-    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using `WithEnvironment` (C#) or `withEnvironment` (TypeScript). See [Pass custom environment variables](../seq-host/) in the hosting integration reference.
+    If your app expects specific environment variable names different from the Aspire defaults, you can pass individual connection properties from the AppHost using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" />. See [Pass custom environment variables](../seq-host/) in the hosting integration reference.
 </Aside>
diff --git a/src/frontend/src/content/docs/integrations/reverse-proxies/yarp.mdx b/src/frontend/src/content/docs/integrations/reverse-proxies/yarp.mdx
index 0184c8633e..148152ff7d 100644
--- a/src/frontend/src/content/docs/integrations/reverse-proxies/yarp.mdx
+++ b/src/frontend/src/content/docs/integrations/reverse-proxies/yarp.mdx
@@ -8,6 +8,7 @@ import { Image } from 'astro:assets';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import ContainerImages from '@components/ContainerImages.astro';
 import yarpIcon from '@assets/icons/yarp-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={yarpIcon}
@@ -116,9 +117,9 @@ await builder.build().run();
 When Aspire adds a YARP resource to the AppHost, it creates a new containerized YARP instance using the [mcr.microsoft.com/dotnet/nightly/yarp](https://mcr.microsoft.com/product/dotnet/nightly/yarp/about) container image.
 
 <Aside type="caution">
-  Starting with Aspire 9.4, the `WithConfigFile` method has been removed. YARP
+  Starting with Aspire 9.4, the <ApiReference name="Aspire.Hosting.FlociHostingExtension.WithConfigFile" /> method has been removed. YARP
   configuration is now done exclusively through code-based configuration using
-  the `WithConfiguration` method. This provides better IntelliSense support,
+  the <ApiReference name="Aspire.Hosting.YarpResourceExtensions.WithConfiguration" /> method. This provides better IntelliSense support,
   type safety, and works seamlessly with deployment scenarios.
 </Aside>
 
@@ -264,7 +265,7 @@ Common transform methods include:
 - **Path transforms**: `WithTransformPathRemovePrefix`, `WithTransformPathPrefix`, `WithTransformPathSet`; TypeScript uses `withTransformPathRemovePrefix`, `withTransformPathPrefix`, and `withTransformPathSet`.
 - **Header transforms**: `WithTransformRequestHeader`, `WithTransformResponseHeader`; TypeScript uses `withTransformRequestHeader` and `withTransformResponseHeader`.
 - **Query transforms**: `WithTransformQueryParameter`, `WithTransformQueryRemoveParameter`; TypeScript uses `withTransformQueryValue`, `withTransformQueryRouteValue`, and `withTransformQueryRemoveKey`.
-- **Custom transforms**: `WithTransform` or `withTransform` for custom transformation logic.
+- **Custom transforms**: <ApiReference name="Aspire.Hosting.Yarp.YarpRouteExtensions.WithTransform" /> for custom transformation logic.
 
 ### Customize host port
 
@@ -353,7 +354,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-For external services, use `AddExternalService` or `addExternalService`:
+For external services, use <ApiReference name="Aspire.Hosting.ExternalServiceBuilderExtensions.AddExternalService" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -516,7 +517,7 @@ await builder.build().run();
 
 ## HTTPS endpoints
 
-When both the YARP gateway and backend services use HTTPS, configure HTTPS endpoints using `WithHttpsEndpoint` or `withHttpsEndpoint` and the developer certificate. YARP can proxy HTTPS-to-HTTPS when the backend service exposes an HTTPS endpoint:
+When both the YARP gateway and backend services use HTTPS, configure HTTPS endpoints using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsEndpoint" /> and the developer certificate. YARP can proxy HTTPS-to-HTTPS when the backend service exposes an HTTPS endpoint:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/integrations/security/keycloak.mdx b/src/frontend/src/content/docs/integrations/security/keycloak.mdx
index bdfd22061e..4a42384271 100644
--- a/src/frontend/src/content/docs/integrations/security/keycloak.mdx
+++ b/src/frontend/src/content/docs/integrations/security/keycloak.mdx
@@ -10,6 +10,7 @@ import InstallPackage from '@components/InstallPackage.astro';
 import InstallDotNetPackage from '@components/InstallDotNetPackage.astro';
 import { Image } from 'astro:assets';
 import keycloakIcon from '@assets/icons/keycloak-icon.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Badge text="🧪 Preview" variant="note" size="large" />
 
@@ -37,7 +38,7 @@ The Keycloak hosting integration models the server as the `KeycloakResource` typ
 
 ### Add Keycloak resource
 
-In your AppHost, call `AddKeycloak` to add and return a Keycloak resource builder:
+In your AppHost, call <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.AddKeycloak" /> to add and return a Keycloak resource builder:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -104,7 +105,7 @@ When the AppHost runs, the password is stored in the AppHost's secret store in t
 
 <Aside type="tip">
   If you'd rather connect to an existing Keycloak instance, call
-  `AddConnectionString` instead. For more information, see [Reference existing
+  <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> instead. For more information, see [Reference existing
   resources](/get-started/resources/).
 </Aside>
 
@@ -112,7 +113,7 @@ When the AppHost runs, the password is stored in the AppHost's secret store in t
 
 ### Add Keycloak resource with data volume
 
-To add a data volume to the Keycloak resource, call the `WithDataVolume` method on the Keycloak resource:
+To add a data volume to the Keycloak resource, call the <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.WithDataVolume" /> method on the Keycloak resource:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -156,7 +157,7 @@ The data volume is used to persist the Keycloak data outside the lifecycle of it
 
 ### Add Keycloak resource with data bind mount
 
-To add a data bind mount to the Keycloak resource, call the `WithDataBindMount` method:
+To add a data bind mount to the Keycloak resource, call the <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.WithDataBindMount" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -246,7 +247,7 @@ For more information on providing parameters, see [External parameters](/get-sta
 
 ### Add Keycloak resource with realm import
 
-To import a realm into Keycloak, call the `WithRealmImport` method:
+To import a realm into Keycloak, call the <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.WithRealmImport" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -300,8 +301,8 @@ For production environments, consider these alternatives to seed your Keycloak
 instance:
 
 **Custom Keycloak image**: Bake realm files into a custom image. Apply
-`WithDockerfile` to the Keycloak resource instead of replacing `AddKeycloak`
-with `AddContainer`:
+<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfile" /> to the Keycloak resource instead of replacing `AddKeycloak`
+with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" />:
 
 ```dockerfile title="keycloak/Dockerfile"
 FROM quay.io/keycloak/keycloak:25.0.0
@@ -384,7 +385,7 @@ to manage realm configuration separately from your application deployment.
 
 ### Export telemetry to <abbr title="OpenTelemetry Protocol" data-tooltip-placement="top">OTLP</abbr> collector
 
-Keycloak containers can export telemetry to your OTLP collector using the `WithOtlpExporter` method:
+Keycloak containers can export telemetry to your OTLP collector using the <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.WithOtlpExporter" /> method:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -425,7 +426,7 @@ This enables Keycloak to send traces, metrics, and logs to the Aspire dashboard,
 
 <Badge text="⭐ Community Toolkit" variant="tip" size="large" />
 
-The [📦 CommunityToolkit.Aspire.Hosting.Keycloak.Extensions](https://www.nuget.org/packages/CommunityToolkit.Aspire.Hosting.Keycloak.Extensions) package decorates the official `KeycloakResource` with `WithPostgres` / `withPostgres`. It configures Keycloak to use an official `PostgresDatabaseResource`, supplies the JDBC URL and credentials, and makes Keycloak wait for the database.
+The [📦 CommunityToolkit.Aspire.Hosting.Keycloak.Extensions](https://www.nuget.org/packages/CommunityToolkit.Aspire.Hosting.Keycloak.Extensions) package decorates the official `KeycloakResource` with <ApiReference name="Aspire.Hosting.KeycloakPostgresExtension.WithPostgres" />. It configures Keycloak to use an official `PostgresDatabaseResource`, supplies the JDBC URL and credentials, and makes Keycloak wait for the database.
 
 <InstallPackage
   packageName="CommunityToolkit.Aspire.Hosting.Keycloak.Extensions"
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-docs-api-search.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-docs-api-search.mdx
index c01183986f..7eacebe51b 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-docs-api-search.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-docs-api-search.mdx
@@ -4,6 +4,7 @@ description: Learn about the aspire docs api search command and its usage. This
 ---
 
 import Include from '@components/Include.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 ## Name
 
@@ -27,7 +28,7 @@ Optionally filter results to a specific language using the `--language` option.
 
 - **`<query>`**
 
-  The search query. Use type names, method names, or keywords to describe the API you are looking for. For example, `AddRedis`, `IResourceBuilder`, or `WithReference`.
+  The search query. Use type names, method names, or keywords to describe the API you are looking for. For example, <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" />, `IResourceBuilder`, or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />.
 
 ## Options
 
diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-init.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-init.mdx
index cf2e07952f..a65a78de26 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-init.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-init.mdx
@@ -6,6 +6,7 @@ description: Learn about the aspire init command and how it uses the aspireify a
 
 import { Aside } from '@astrojs/starlight/components';
 import Include from '@components/Include.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 ## Name
 
@@ -98,7 +99,7 @@ The skill instructs the agent to:
 
 - Scan the repo and discovering existing projects, services, and containers
 - Ask you clarifying questions before making decisions — for example, which services to orchestrate, whether a hardcoded port is significant, or whether to map an existing env var or switch to Aspire's service discovery
-- Wire resources into the AppHost with `WithReference`, `WaitFor`, endpoints, and volumes
+- Wire resources into the AppHost with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" />, endpoints, and volumes
 - Optionally configure OpenTelemetry
 - Validate the wiring with a smoke-test `aspire start`
 
diff --git a/src/frontend/src/content/docs/testing/accessing-resources.mdx b/src/frontend/src/content/docs/testing/accessing-resources.mdx
index 6bd78e6bbb..1392ee1048 100644
--- a/src/frontend/src/content/docs/testing/accessing-resources.mdx
+++ b/src/frontend/src/content/docs/testing/accessing-resources.mdx
@@ -5,6 +5,7 @@ description: Resolve and inspect Aspire AppHost resources from your tests — co
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 In this article, you learn how to access the resources from the Aspire AppHost in your tests. The AppHost represents the full application environment and contains all the resources that are available to the application. When writing functional or integration tests with Aspire, you might need to access these resources to verify the behavior of your application.
 
@@ -58,7 +59,7 @@ This resource-notification pattern ensures that the resources are available befo
 
 ## Start & Stop
 
-In some cases, you may want to manually start a resource when it is not initially started, for when the resource was created `WithExplicitStart` for example.
+In some cases, you may want to manually start a resource when it is not initially started, for when the resource was created <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> for example.
 
 ```csharp
 using var cts = new CancellationTokenSource(TimeSpan.FromSeconds(30));
diff --git a/src/frontend/src/content/docs/testing/advanced-scenarios.mdx b/src/frontend/src/content/docs/testing/advanced-scenarios.mdx
index d3d8f33746..f18e322038 100644
--- a/src/frontend/src/content/docs/testing/advanced-scenarios.mdx
+++ b/src/frontend/src/content/docs/testing/advanced-scenarios.mdx
@@ -6,6 +6,7 @@ description: Advanced patterns for DistributedApplicationTestingBuilder — sele
 
 import { Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 This article covers advanced patterns for testing Aspire applications, including selectively disabling resources during tests, overriding environment variables, and customizing the AppHost for specific test scenarios.
 
@@ -15,7 +16,7 @@ When running integration tests, you might want to exclude certain resources to r
 
 ### Use `WithExplicitStart` to control resource startup
 
-The recommended way to make a resource optional is to use `WithExplicitStart` in the AppHost, and then let tests choose whether to start that resource. Resources marked with `WithExplicitStart` are created but don't start automatically with the rest of the application.
+The recommended way to make a resource optional is to use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> in the AppHost, and then let tests choose whether to start that resource. Resources marked with `WithExplicitStart` are created but don't start automatically with the rest of the application.
 
 In your AppHost, mark the resource as explicitly started:
 
@@ -95,7 +96,7 @@ public async Task ApiStartsWithoutDatabase()
 
 ### Remove wait annotations in tests
 
-Resources in Aspire can have wait dependencies (via `WaitFor` or `WaitForCompletion`). In some tests, you may want to remove these wait annotations to speed up test startup or to test behavior when dependent resources are unavailable.
+Resources in Aspire can have wait dependencies (via <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" />). In some tests, you may want to remove these wait annotations to speed up test startup or to test behavior when dependent resources are unavailable.
 
 You can remove `WaitAnnotation` instances after building the testing builder, before calling `BuildAsync`:
 
@@ -135,7 +136,7 @@ Because Aspire tests run services in separate processes, you can't inject servic
 
 ### Override environment variables via the AppHost builder
 
-Use `WithEnvironment` on the resource builder after creating the testing builder to set environment variables for specific resources. You access the resource builder through the `CreateResourceBuilder` method:
+Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> on the resource builder after creating the testing builder to set environment variables for specific resources. You access the resource builder through the `CreateResourceBuilder` method:
 
 ```csharp title="IntegrationTest.cs"
 [Fact]
diff --git a/src/frontend/src/content/docs/testing/write-your-first-test.mdx b/src/frontend/src/content/docs/testing/write-your-first-test.mdx
index 4fe65cb373..56850b3bba 100644
--- a/src/frontend/src/content/docs/testing/write-your-first-test.mdx
+++ b/src/frontend/src/content/docs/testing/write-your-first-test.mdx
@@ -9,6 +9,7 @@ import { Aside, Steps } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import PivotSelector from '@components/PivotSelector.astro';
 import Pivot from '@components/Pivot.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 <PivotSelector
     title="Select your testing framework"
@@ -518,7 +519,7 @@ The preceding code:
 
 - Relies on the `DistributedApplicationTestingBuilder.CreateAsync` API to asynchronously create the AppHost.
 - The `builder` instance is used to retrieve an `IResourceWithEnvironment` instance named "webfrontend" from the `Resources` property.
-- Builds an `ExecutionConfiguration` for the `webfrontend` resource using `ExecutionConfigurationBuilder`, explicitly enabling environment variable configuration via `WithEnvironmentVariablesConfig`.
+- Builds an `ExecutionConfiguration` for the `webfrontend` resource using `ExecutionConfigurationBuilder`, explicitly enabling environment variable configuration via <ApiReference name="Aspire.Hosting.ApplicationModel.ExecutionConfigurationBuilderExtensions.WithEnvironmentVariablesConfig" />.
 - Calls `BuildAsync` with `DistributedApplicationOperation.Publish` to generate the environment variables that will be published for the resource, including unresolved binding expressions.
 - With the returned environment variables, the test asserts that the `webfrontend` resource has an HTTPS environment variable that resolves to the `apiservice` resource.
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
index f9db71a0d4..3838258136 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-1.mdx
@@ -19,6 +19,7 @@ import ReleaseCommunity from '@components/ReleaseCommunity.astro';
 import { Code, Tabs, Steps, TabItem, Aside, Icon } from '@astrojs/starlight/components';
 import resourcesParametersView from '@assets/whats-new/resources-parameters-view.png';
 import genaiVisualizerTooldefinitions from '@assets/whats-new/genai-visualizer-tooldefinitions.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.1 builds on Aspire 13's multi-language foundation with expanded <abbr title="Model Context Protocol" data-tooltip-placement="top">MCP</abbr> support for AI coding agents, CLI and dashboard improvements, and more streamlined Azure deployments.
 
@@ -27,7 +28,7 @@ This release introduces:
 - The new `aspire agent init` command and MCP tools help AI assistants discover integrations and interact with Aspire applications.
 - CLI improvements include channel persistence, automatic instance detection, and installation path options.
 - The dashboard adds a dedicated Parameters tab and GenAI visualizer enhancements.
-- Azure Managed Redis is renamed from `AddAzureRedisEnterprise` to `AddAzureManagedRedis` with improved validation.
+- Azure Managed Redis is renamed from `AddAzureRedisEnterprise` to <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.AddAzureManagedRedis" /> with improved validation.
 - The new `ContainerRegistryResource` supports general-purpose container registries.
 - JavaScript updates include a new frontend starter template, Vite HTTPS configuration, and pnpm fixes.
 - [📦 Aspire.Hosting.DevTunnels](https://www.nuget.org/packages/Aspire.Hosting.DevTunnels) is now **stable**.
@@ -206,7 +207,7 @@ Resources now expose additional properties such as `HostName`, `Port`, and `Jdbc
 
 ### Azure App Service deployment slots
 
-New `WithDeploymentSlot` extension method to configure deployment slots for Azure App Service:
+New <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.WithDeploymentSlot" /> extension method to configure deployment slots for Azure App Service:
 
 ```csharp title="Configure deployment slot"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -217,7 +218,7 @@ builder.AddAzureAppServiceEnvironment("appservice")
 
 ### Clear default role assignments
 
-New `ClearDefaultRoleAssignments` extension method to disable automatic role assignments on Azure resources when you need fine-grained control over permissions.
+New <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> extension method to disable automatic role assignments on Azure resources when you need fine-grained control over permissions.
 
 ### Bug fixes
 
@@ -289,7 +290,7 @@ $ aspire do push
 
 ### Explicit container registry support for Azure deployments
 
-Prior to Aspire 13.1, when deploying to Azure Container Apps using `AddAzureContainerAppEnvironment`, the Azure Container Registry (ACR) was provisioned implicitly as part of the environment. This automatic provisioning could cause deployment delays and made it difficult for developers to discover which registry was being used.
+Prior to Aspire 13.1, when deploying to Azure Container Apps using <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />, the Azure Container Registry (ACR) was provisioned implicitly as part of the environment. This automatic provisioning could cause deployment delays and made it difficult for developers to discover which registry was being used.
 
 Aspire 13.1 addresses this by moving toward explicit container registry configuration, giving developers more control and visibility into where and when images are pushed. With the configuration below, the ACR associated with the "myenv" environment will be provisioned in parallel with the environment and image pushes will begin as soon as the registry has been successfully provisioned.
 
@@ -312,7 +313,7 @@ For a deeper dive into container registry improvements and their impact on Azure
 - Resource endpoints are displayed after Docker Compose deployment.
 - Fixed race condition in Dockerfile materialization during parallel pipeline execution.
 
-For advanced scenarios, use `ConfigureEnvFile` to customize the generated `.env` file:
+For advanced scenarios, use <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureEnvFile" /> to customize the generated `.env` file:
 
 ```csharp title="Customize Docker Compose .env file"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
index a7e4b83d12..5a7306f3fa 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
@@ -33,6 +33,7 @@ import manageDialog from '@assets/whats-new/aspire-13.2/manage-dialog.png';
 import exportJsonMenu from '@assets/whats-new/aspire-13.2/export-json-menu.png';
 import exportJsonDialog from '@assets/whats-new/aspire-13.2/export-json-dialog.png';
 import exportEnvDialog from '@assets/whats-new/aspire-13.2/export-env-dialog.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.2 expands the CLI, adds preview TypeScript AppHost support, and improves the dashboard, AI agent integrations, multi-language development, and cloud deployment. It also strengthens the infrastructure used to ship stable releases more frequently. Share questions and feedback on [Discord](https://aka.ms/aspire-discord) or [GitHub](https://github.com/microsoft/aspire/issues).
 
@@ -413,7 +414,7 @@ When an Aspire apphost is running, the extension now shows inline CodeLens above
 - Action buttons: Start, Stop, Restart, View Logs
 - Custom resource commands from the runtime
 
-Colored gutter decorations appear alongside resource definitions — green for running, blue for starting, red for errors, gray for stopped — giving you an at-a-glance view of your entire app's health right in the editor. Both features are backed by language-aware parsers that understand `DistributedApplication.CreateBuilder` in C# and `createBuilder()` in TypeScript.
+Colored gutter decorations appear alongside resource definitions — green for running, blue for starting, red for errors, gray for stopped — giving you an at-a-glance view of your entire app's health right in the editor. Both features are backed by language-aware parsers that understand `DistributedApplication.CreateBuilder` in C# and <ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" /> in TypeScript.
 
 ### Getting Started walkthrough
 
@@ -568,7 +569,7 @@ Additional dashboard refinements in 13.2:
 
 ### MCP endpoints from the app model
 
-Aspire 13.2 adds `WithMcpServer`, which lets you declare in the app model that a resource hosts a Model Context Protocol (MCP) server. Aspire tooling can then discover and proxy that endpoint directly.
+Aspire 13.2 adds <ApiReference name="Aspire.Hosting.McpServerResourceBuilderExtensions.WithMcpServer" />, which lets you declare in the app model that a resource hosts a Model Context Protocol (MCP) server. Aspire tooling can then discover and proxy that endpoint directly.
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -617,7 +618,7 @@ The OpenTelemetry Protocol (OTLP) endpoint is now modeled as a first-class resou
 
 ### Better secret and certificate handling
 
-Container build secrets got a clearer API in 13.2. `WithBuildSecret` replaces the old `WithSecretBuildArg` name and makes secure Docker or Podman build secret flows more readable.
+Container build secrets got a clearer API in 13.2. <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildSecret" /> replaces the old `WithSecretBuildArg` name and makes secure Docker or Podman build secret flows more readable.
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -678,7 +679,7 @@ builder.AddContainer("my-java-app", "my-image:latest")
     });
 ```
 
-`ReferenceExpression` now exposes `GetValueAsync()` and supports conditional mode in multi-language code generation, which makes advanced hosting extensions easier to build without relying on synchronous value access patterns.
+`ReferenceExpression` now exposes <ApiReference name="Aspire.Hosting.ApplicationModel.ReferenceExpression.GetValueAsync" /> and supports conditional mode in multi-language code generation, which makes advanced hosting extensions easier to build without relying on synchronous value access patterns.
 
 ### Enhanced debugging experience
 
@@ -874,7 +875,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-New APIs in this area include `AddProject`, `AddModelDeployment`, `WithAppInsights`, `WithKeyVault`, `WithContainerRegistry`, `PublishAsHostedAgent`, and `AddAndPublishPromptAgent`. `RunAsFoundryLocal` is still available for local model development, but Foundry Projects aren't supported when the parent resource is configured as Foundry Local.
+New APIs in this area include <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddProject" />, <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddModelDeployment" />, <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.WithAppInsights" />, <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.WithKeyVault" />, <ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" />, `PublishAsHostedAgent`, and `AddAndPublishPromptAgent`. <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> is still available for local model development, but Foundry Projects aren't supported when the parent resource is configured as Foundry Local.
 
 <Aside type="caution">
   This is a breaking change. `Aspire.Hosting.Azure.AIFoundry` has been replaced
@@ -915,10 +916,10 @@ peSubnet.AddPrivateEndpoint(storage.AddBlobs("blobs"));
 
 Key capabilities include:
 
-- Create virtual networks with `AddAzureVirtualNetwork` and add subnets with `AddSubnet`.
-- Provide deterministic outbound public IP addresses with `AddNatGateway` and `WithNatGateway`.
-- Control traffic with network security group shorthand methods (`AllowInbound`, `DenyInbound`, `AllowOutbound`, `DenyOutbound`) or explicit `AddNetworkSecurityGroup` with `WithSecurityRule`.
-- Connect securely to Azure services over private networks with `AddPrivateEndpoint`, which automatically creates private DNS zones and virtual network links and disables public access on the target resource.
+- Create virtual networks with <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddAzureVirtualNetwork" /> and add subnets with <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddSubnet" />.
+- Provide deterministic outbound public IP addresses with <ApiReference name="Aspire.Hosting.AzureNatGatewayExtensions.AddNatGateway" /> and <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithNatGateway" />.
+- Control traffic with network security group shorthand methods (<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowInbound" />, <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyInbound" />, <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowOutbound" />, <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyOutbound" />) or explicit <ApiReference name="Aspire.Hosting.AzureNetworkSecurityGroupExtensions.AddNetworkSecurityGroup" /> with <ApiReference name="Aspire.Hosting.AzureNetworkSecurityGroupExtensions.WithSecurityRule" />.
+- Connect securely to Azure services over private networks with <ApiReference name="Aspire.Hosting.AzurePrivateEndpointExtensions.AddPrivateEndpoint" />, which automatically creates private DNS zones and virtual network links and disables public access on the target resource.
 
 <LearnMore>
   For more details, see [Azure Virtual Network
@@ -966,14 +967,14 @@ Keyed embeddings are also supported with `AddKeyedEmbeddingGenerator`.
 
 ### Azure Container Registry
 
-The Azure Container Registry integration now supports scheduled image cleanup with the new `WithPurgeTask` method. This provisions an [ACR purge task](https://learn.microsoft.com/azure/container-registry/container-registry-auto-purge) that automatically removes old or unused container images on a cron schedule:
+The Azure Container Registry integration now supports scheduled image cleanup with the new <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.WithPurgeTask" /> method. This provisions an [ACR purge task](https://learn.microsoft.com/azure/container-registry/container-registry-auto-purge) that automatically removes old or unused container images on a cron schedule:
 
 ```csharp title="Schedule ACR image cleanup"
 var acr = builder.AddAzureContainerRegistry("my-acr")
     .WithPurgeTask("0 1 * * *", ago: TimeSpan.FromDays(7), keep: 5);
 ```
 
-Additionally, the new `GetAzureContainerRegistry` method makes it easy to access the registry from a compute environment for further configuration.
+Additionally, the new <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.GetAzureContainerRegistry" /> method makes it easy to access the registry from a compute environment for further configuration.
 
 <LearnMore>
   For more details, see [Azure Container Registry
@@ -1050,7 +1051,7 @@ If you register the `DbContext` yourself, you can still opt into Aspire instrume
 
 ### JavaScript hosting with Bun
 
-JavaScript resources can now opt into Bun as their package manager with `WithBun()`. Aspire configures the right package-manager annotations, install behavior, and container build image defaults for Bun-backed applications. This release also fixes reliability issues when using Yarn with `AddViteApp` via `WithYarn()`.
+JavaScript resources can now opt into Bun as their package manager with <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithBun" />. Aspire configures the right package-manager annotations, install behavior, and container build image defaults for Bun-backed applications. This release also fixes reliability issues when using Yarn with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> via <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" />.
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -1094,7 +1095,7 @@ await builder.build().run();
 - Azure App Configuration emulator updated to 1.0.2
 - CosmosDB preview emulator readiness check added
 - Azure Managed Redis now uses `rediss://` as the default scheme
-- Multiple Azurite storage accounts now supported with `RunAsEmulator`
+- Multiple Azurite storage accounts now supported with <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" />
 
 ### AI model updates
 
@@ -1107,7 +1108,7 @@ await builder.build().run();
 ### Kubernetes improvements
 
 - YAML publishing fixes for Kubernetes deployments
-- Better handling of resources with `ExcludeFromManifest`
+- Better handling of resources with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" />
 
 ### Azure deployment
 
@@ -1208,7 +1209,7 @@ The `BeforeResourceStartedEvent` now only fires when actually starting a resourc
 
 ### Connection property suffix
 
-Several connection properties for "named entity" resources gained an explicit `Name` suffix so the property clearly refers to the entity's name rather than the entity itself. This affects both the connection-property API (`GetConnectionProperty`) and the environment variables Aspire injects via `WithReference(...)` and `ReferenceEnvironmentInjectionFlags.ConnectionProperties`.
+Several connection properties for "named entity" resources gained an explicit `Name` suffix so the property clearly refers to the entity's name rather than the entity itself. This affects both the connection-property API (<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.GetConnectionProperty" />) and the environment variables Aspire injects via <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> and `ReferenceEnvironmentInjectionFlags.ConnectionProperties`.
 
 A subset of these renames first shipped in [13.1](/whats-new/aspire-13-1/#connection-properties-rename); 13.2 completes the rollout across the remaining built-in resources, so apps upgrading directly from 13.0 to 13.2 encounter all of them at once. The full list of renamed properties as of 13.2 is:
 
@@ -1291,7 +1292,7 @@ Aspire 13.2 standardizes the Foundry hosting surface under `Aspire.Hosting.Found
 | ------------------ | --------- |
 | Hosting package: `Aspire.Hosting.Azure.AIFoundry` | Hosting package: `Aspire.Hosting.Foundry` |
 | Resource and model namespace: `Aspire.Hosting.Azure` | Resource and model namespace: `Aspire.Hosting.Foundry` |
-| `AddAzureAIFoundry(...)` | `AddFoundry(...)` |
+| `AddAzureAIFoundry(...)` | <ApiReference name="Aspire.Hosting.FoundryExtensions.AddFoundry" /> |
 | `AzureAIFoundryResource` | `FoundryResource` |
 | `AzureAIFoundryExtensions` | `FoundryExtensions` |
 | `AzureAIFoundryDeploymentResource` | `FoundryDeploymentResource` |
@@ -1362,7 +1363,7 @@ The following TypeScript AppHost APIs were renamed. Update any affected `apphost
 | `runAsExistingFromParameters(name, resourceGroup)` | `runAsExisting(name, { resourceGroup })` | Name change plus positional → options object. |
 | `publishAsExistingFromParameters(name, resourceGroup)` | `publishAsExisting(name, { resourceGroup })` | Name change plus positional → options object. |
 | `withConnectionPropertyValue(name, value)` | `withConnectionProperty(name, value)` | Unified API for string/reference values. |
-| `withParameterBuildArg(name, parameter)` | `withBuildArg(name, parameter)` | Renamed to the unified `withBuildArg` surface. |
+| `withParameterBuildArg(name, parameter)` | `withBuildArg(name, parameter)` | Renamed to the unified <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildArg" /> surface. |
 
 <Aside type="note">
   `withConnectionPropertyValue` is still available as a compatibility alias in the generated SDKs, so it is not a runtime SDK break.
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-3.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-3.mdx
index fd63c3df9d..b421819b8b 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-3.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-3.mdx
@@ -18,6 +18,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import { Image } from 'astro:assets';
 import ReleaseCommunity from '@components/ReleaseCommunity.astro';
 import LearnMore from '@components/LearnMore.astro';
@@ -37,8 +38,8 @@ This release introduces:
 
 - The new `aspire destroy` command tears down provisioned resources across Azure, Kubernetes, and Compose, while `aspire dashboard` runs the dashboard standalone. The Aspire CLI is also now available as a `dotnet tool`.
 - The new `Aspire.Hosting.Browsers` integration captures frontend console logs, network requests, and screenshots and surfaces them in the dashboard next to server-side telemetry.
-- Preview support for `aspire deploy` to Kubernetes generates a Helm chart and runs an end-to-end deployment pipeline from an `AddKubernetesEnvironment`. New Ingress and Gateway API routing resources describe traffic at the AppHost level.
-- Preview JavaScript publish methods provide a unified `PublishAs*` family for static SPAs, SSR Node servers, and npm-script-based deployments, plus the new `AddNextJsApp` helper and first-class support for Bun, Yarn, and pnpm.
+- Preview support for `aspire deploy` to Kubernetes generates a Helm chart and runs an end-to-end deployment pipeline from an <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.AddKubernetesEnvironment" />. New Ingress and Gateway API routing resources describe traffic at the AppHost level.
+- Preview JavaScript publish methods provide a unified `PublishAs*` family for static SPAs, SSR Node servers, and npm-script-based deployments, plus the new <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" /> helper and first-class support for Bun, Yarn, and pnpm.
 - The container tunnel is enabled by default, providing uniform host connectivity across Docker Desktop, Docker Engine, and Podman.
 - TypeScript AppHost improvements close most of the remaining gap with C# AppHosts.
 - The preview `aspire init` command bootstraps an AppHost into an existing repository with the new `aspireify` agent skill.
@@ -636,11 +637,11 @@ Thanks to community contributor [@afscrome](https://github.com/afscrome) for thi
 
 ### `WithEndpoint` updates existing endpoints
 
-`WithEndpoint` no longer throws when an endpoint of the same name already exists. Calling it a second time updates the existing endpoint instead — making it easier to layer endpoint configuration across extension methods.
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> no longer throws when an endpoint of the same name already exists. Calling it a second time updates the existing endpoint instead — making it easier to layer endpoint configuration across extension methods.
 
 ### Exclude management endpoints from `WithReference()`
 
-Endpoint annotations now have an `ExcludeReferenceEndpoint` flag. Setting it to `true` excludes the endpoint (e.g. management or health endpoints) from the default `WithReference()` injection, so consumers don't accidentally receive admin URLs:
+Endpoint annotations now have an `ExcludeReferenceEndpoint` flag. Setting it to `true` excludes the endpoint (e.g. management or health endpoints) from the default <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> injection, so consumers don't accidentally receive admin URLs:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -681,9 +682,9 @@ The Aspire trusted developer certificate is now used in more places — includin
 
 Aspire 13.3 closes most of the remaining functional gap between C# AppHosts and the TypeScript AppHost SDK:
 
-- A unified `withEnvironment` API handles all environment variable value kinds, including endpoints, parameters, connection strings, and expressions. Apps using the earlier per-kind helpers must migrate to the unified method.
+- A unified <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> API handles all environment variable value kinds, including endpoints, parameters, connection strings, and expressions. Apps using the earlier per-kind helpers must migrate to the unified method.
 - Endpoint property expressions (`endpoint.url`, `endpoint.host`, `endpoint.port`) are now usable inside TypeScript AppHost expressions.
-- `PublishAsDockerComposeService`-equivalent hooks and post-processing provide Docker Compose API parity.
+- <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.PublishAsDockerComposeService" />-equivalent hooks and post-processing provide Docker Compose API parity.
 - Azure Container Apps custom domain configuration is now exposed in the TypeScript AppHost SDK.
 - Unified YARP TypeScript route helpers, `addRoute(...)` and `addCatchAllRoute(...)`, replace several earlier ad-hoc helpers.
 - `WithAdminDeploymentScriptSubnet` is now exported for TypeScript AppHosts.
@@ -715,11 +716,11 @@ The 13.3 TypeScript SDK doesn't generate the earlier per-kind helper aliases. Up
 
 Aspire 13.3 brings first-class JavaScript publishing to both C# and TypeScript AppHosts. A new family of `PublishAs*` extension methods replaces hand-rolled `Dockerfile` plumbing for the most common JS deployment shapes:
 
-- `PublishAsStaticWebsite` (preview) publishes a JS app as a static website served by a YARP image, with an optional API reverse proxy to a backend resource. It is intended for SPAs such as Vite and plain Next.js exports.
-- `PublishAsNodeServer` publishes a self-contained Node entry point such as `server.js` without copying `node_modules` at runtime. It is intended for pre-bundled Node servers.
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsStaticWebsite" /> (preview) publishes a JS app as a static website served by a YARP image, with an optional API reverse proxy to a backend resource. It is intended for SPAs such as Vite and plain Next.js exports.
+- <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsNodeServer" /> publishes a self-contained Node entry point such as `server.js` without copying `node_modules` at runtime. It is intended for pre-bundled Node servers.
 - `PublishAsNpmScript` publishes a Node app that runs an npm script (`start` or `serve`) at runtime, copying `package.json` and production dependencies. It is intended for full Nitro Next.js, Remix, and Astro SSR apps.
 
-Aspire 13.3 also adds `AddNextJsApp` as a first-class Next.js helper alongside the existing `AddViteApp` and `AddNodeApp`, plus first-class support for Bun, Yarn, and pnpm in TypeScript AppHosts (npm remains the default).
+Aspire 13.3 also adds `AddNextJsApp` as a first-class Next.js helper alongside the existing <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> and <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" />, plus first-class support for Bun, Yarn, and pnpm in TypeScript AppHosts (npm remains the default).
 
 <Aside type="caution">
   The `PublishAsStaticWebsite` method is experimental in 13.3. Use diagnostic
@@ -911,7 +912,7 @@ The extension now renders live resource state in the editor. CodeLens above each
 
 ### 🔍 Browser logs and screenshots
 
-The new `Aspire.Hosting.Browsers` integration captures browser console logs, network requests, and screenshots from your frontend resources during development, surfacing them in the dashboard alongside server-side telemetry. Add `WithBrowserLogs()` to any frontend resource to enable it.
+The new `Aspire.Hosting.Browsers` integration captures browser console logs, network requests, and screenshots from your frontend resources during development, surfacing them in the dashboard alongside server-side telemetry. Add <ApiReference name="Aspire.Hosting.BrowserLogsBuilderExtensions.WithBrowserLogs" /> to any frontend resource to enable it.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -986,7 +987,7 @@ The Npgsql client integration emits OpenTelemetry metrics that align with the .N
   data-zoom-off
 />
 
-You no longer need to stitch together ARM templates or click through portal blades to get a CDN in front of your app. Aspire 13.3 adds a new hosting integration for [Azure Front Door](https://learn.microsoft.com/azure/frontdoor/), Microsoft's global edge network for fast, secure, and highly available web apps. Add a Front Door profile in front of your backends with `AddAzureFrontDoor` and attach origins with `WithOrigin`:
+You no longer need to stitch together ARM templates or click through portal blades to get a CDN in front of your app. Aspire 13.3 adds a new hosting integration for [Azure Front Door](https://learn.microsoft.com/azure/frontdoor/), Microsoft's global edge network for fast, secure, and highly available web apps. Add a Front Door profile in front of your backends with <ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.AddAzureFrontDoor" /> and attach origins with <ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.WithOrigin" />:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -1033,7 +1034,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-Each `withOrigin` call provisions its own Front Door endpoint, origin group, origin, and route, so every backend is independently routable through its own `*.azurefd.net` hostname. The integration provisions Front Door in the Standard SKU by default; use `ConfigureInfrastructure` to customize the Front Door, for example to change SKUs, attach a Web Application Firewall (WAF) policy, enable caching, and more.
+Each `withOrigin` call provisions its own Front Door endpoint, origin group, origin, and route, so every backend is independently routable through its own `*.azurefd.net` hostname. The integration provisions Front Door in the Standard SKU by default; use <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> to customize the Front Door, for example to change SKUs, attach a Web Application Firewall (WAF) policy, enable caching, and more.
 
 <LearnMore>
   For more details, see [Azure Front Door
@@ -1111,7 +1112,7 @@ NSPs support **Enforced** mode (blocks traffic that violates the rules) and **Le
   marked stable.
 </Aside>
 
-Aspire 13.3 adds first-class support for provisioning and deploying to Azure Kubernetes Service without writing manifests by hand. Use `AddAzureKubernetesEnvironment` to declare an AKS environment, customize node pools, and generate a type-safe Bicep and Helm deployment pipeline from your AppHost.
+Aspire 13.3 adds first-class support for provisioning and deploying to Azure Kubernetes Service without writing manifests by hand. Use <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" /> to declare an AKS environment, customize node pools, and generate a type-safe Bicep and Helm deployment pipeline from your AppHost.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -1148,7 +1149,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithSystemNodePool` lets you customize the system node pool's VM size and autoscaling bounds. By default the AKS cluster uses the **Free** control-plane SKU; the `AksSkuTier` enum is no longer part of the public API.
+<ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithSystemNodePool" /> lets you customize the system node pool's VM size and autoscaling bounds. By default the AKS cluster uses the **Free** control-plane SKU; the `AksSkuTier` enum is no longer part of the public API.
 
 <LearnMore>
   For more details, see [Azure Kubernetes Service
@@ -1162,7 +1163,7 @@ await builder.build().run();
 
 ### Azure AI Foundry Prompt Agent
 
-Aspire 13.3 ships a new working implementation of Azure AI Foundry Prompt Agent support through `AddPromptAgent`. The previous `AddAndPublishPromptAgent` API and the original shape of `AzurePromptAgentResource` (which never functioned end-to-end) have been replaced. `AddPromptAgent` now returns a working `AzurePromptAgentResource`.
+Aspire 13.3 ships a new working implementation of Azure AI Foundry Prompt Agent support through <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddPromptAgent" />. The previous `AddAndPublishPromptAgent` API and the original shape of `AzurePromptAgentResource` (which never functioned end-to-end) have been replaced. `AddPromptAgent` now returns a working `AzurePromptAgentResource`.
 
 The Foundry model catalog also gained two new models: GPT-5.4 and Qwen3 VL.
 
@@ -1237,7 +1238,7 @@ Aspire is built in the open, and this release wouldn't be what it is without you
 | Change                                                                                                           | Migration                                                                                           |
 | ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
 | `--log-level` renamed to `--pipeline-log-level` on `aspire publish` and `aspire deploy`                          | Update scripts/CI to use `--pipeline-log-level`.                                                    |
-| `package.json` `engines.node` is no longer used to select Node images for generated Dockerfiles                  | Specify the Node version explicitly via `WithDockerfile` or your project's Dockerfile base image.   |
+| `package.json` `engines.node` is no longer used to select Node images for generated Dockerfiles                  | Specify the Node version explicitly via <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfile" /> or your project's Dockerfile base image.   |
 | `NameOutput` renamed to `NameOutputReference` in Azure Network resources                                         | Replace any usage of `*.NameOutput` with `*.NameOutputReference`.                                   |
 | `OtlpEndpointEnvironmentVariableName` property removed                                                           | Remove references; the OTLP endpoint env var is now managed automatically.                          |
 | **Dashboard MCP server removed** (along with `ASPIRE_DASHBOARD_MCP_ENDPOINT_URL`)                                | Use the AppHost-level MCP server with `aspire agent init`.                                          |
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-4.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-4.mdx
index 673dbc91b2..2229802c38 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-4.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-4.mdx
@@ -17,6 +17,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import FileTree from 'starlight-plugin-icons/components/FileTree.astro';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
@@ -29,10 +30,10 @@ We'd love to hear what you think. Drop by [<Icon name="discord" class='d-inline'
 This release introduces:
 
 - C# and TypeScript AppHosts are both supported as first-class options, with stronger TypeScript startup validation, more complete SDK generation, new TypeScript samples, and documentation parity with C# AppHost examples.
-- New hosting integrations provide AppHost APIs for [Go](/integrations/frameworks/go/go-get-started/) (`AddGoApp`) and first-party Bun support in `Aspire.Hosting.JavaScript` for [Bun](/integrations/frameworks/bun-apps/) (`AddBunApp`).
+- New hosting integrations provide AppHost APIs for [Go](/integrations/frameworks/go/go-get-started/) (<ApiReference name="Aspire.Hosting.GoHostingExtensions.AddGoApp" />) and first-party Bun support in `Aspire.Hosting.JavaScript` for [Bun](/integrations/frameworks/bun-apps/) (<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddBunApp" />).
 - Kubernetes and AKS deployment improvements include [cert-manager integration, Gateway API and Azure Application Gateway for Containers (AGC) support](/deployment/kubernetes/aks/#expose-your-app-to-the-internet), Kubernetes manifest resources, external Helm charts, and consolidated Helm chart configuration.
 - Aspire workflow skills move into the new [`microsoft/aspire-skills`](https://github.com/microsoft/aspire-skills) bundle, with clearer separation between first-run setup, lifecycle orchestration, monitoring, AppHost wiring, and deployment guidance, plus eval-driven iteration on agent routing.
-- Resource commands gain typed arguments, visibility controls, immediate result display, named CLI options, resource-scoped help, built-in parameter command options, and the experimental `WithProcessCommand` API.
+- Resource commands gain typed arguments, visibility controls, immediate result display, named CLI options, resource-scoped help, built-in parameter command options, and the experimental <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithProcessCommand" /> API.
 - CLI discovery and diagnostics add `aspire integration list`, `aspire integration search`, `--search` for logs and telemetry, version checks in `aspire doctor`, better logs output, and more consistent command error handling.
 - Dashboard and editor updates include the AI Agents dialog, resource state fixes, CodeLens actions that appear without opening the Aspire panel, and improved VS Code terminal and debug output integration.
 - NATS, Azure Front Door, Foundry hosted agents, and other integrations are updated.
@@ -253,7 +254,7 @@ await builder.build().run();
 
 ## 🌐 Blazor WebAssembly hosting preview
 
-The new preview `Aspire.Hosting.Blazor` integration models standalone Blazor WebAssembly projects in your AppHost. Use `AddBlazorWasmProject` / `addBlazorWasmProject` to add a Blazor WebAssembly project and `AddBlazorGateway` / `addBlazorGateway` to add a browser-facing gateway, then associate the hosted client with `WithBlazorClientApp` / `withBlazorClientApp`.
+The new preview `Aspire.Hosting.Blazor` integration models standalone Blazor WebAssembly projects in your AppHost. Use <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorWasmProject" /> to add a Blazor WebAssembly project and <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddBlazorGateway" /> to add a browser-facing gateway, then associate the hosted client with `WithBlazorClientApp` / `withBlazorClientApp`.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -413,7 +414,7 @@ Command results can be configured to display immediately in the dashboard, makin
 
 ### Hide implementation-detail resources
 
-AppHost authors can keep resource views focused with `WithHidden()` and `WithHiddenOnCompletion()`. Hidden resources stay in the app model and remain addressable by name, but are excluded from the dashboard and CLI resource lists — useful for setup helpers, one-off migration services, or certificate-collection resources that are implementation details rather than things you interact with directly.
+AppHost authors can keep resource views focused with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHidden" /> and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHiddenOnCompletion" />. Hidden resources stay in the app model and remain addressable by name, but are excluded from the dashboard and CLI resource lists — useful for setup helpers, one-off migration services, or certificate-collection resources that are implementation details rather than things you interact with directly.
 
 ### ⚙️ Process-backed resource commands
 
@@ -468,7 +469,7 @@ await builder.build().run();
 
 ### 🔄 Persistent executable and project lifetimes
 
-Persistent lifetimes now extend beyond containers to executables and projects. Call `WithPersistentLifetime()` to leave a resource running when the AppHost exits and reuse the same instance on the next run, and `WithSessionLifetime()` to return a resource to the default behavior. This is useful for resources that are expensive to initialize, need stable local endpoints, or should stay available while you restart or rebuild the AppHost.
+Persistent lifetimes now extend beyond containers to executables and projects. Call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithPersistentLifetime" /> to leave a resource running when the AppHost exits and reuse the same instance on the next run, and <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithSessionLifetime" /> to return a resource to the default behavior. This is useful for resources that are expensive to initialize, need stable local endpoints, or should stay available while you restart or rebuild the AppHost.
 
 <Aside type="caution">
   The shared persistent and session lifetime APIs are experimental and emit
@@ -512,7 +513,7 @@ C# AppHost projects can opt in to using the installed Aspire CLI bundle as the s
 
 Kubernetes and Azure Kubernetes Service (AKS) deployment continue to expand in 13.4. Kubernetes environments can now model cert-manager resources through typed APIs, including cert-manager installation, ClusterIssuers backed by Let's Encrypt or custom ACME servers, and TLS wiring for gateways.
 
-For AKS, `AddAzureKubernetesEnvironment` now wires Azure Application Gateway for Containers (AGC) into the deployment flow. When `AddLoadBalancer(...)` is used, Aspire provisions the AGC ingress profile on AKS, assigns the required Network Contributor role to the controller identity, and exposes Gateway API routing for the application.
+For AKS, <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" /> now wires Azure Application Gateway for Containers (AGC) into the deployment flow. When <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddLoadBalancer" /> is used, Aspire provisions the AGC ingress profile on AKS, assigns the required Network Contributor role to the controller identity, and exposes Gateway API routing for the application.
 
 <LearnMore>
   For a complete walkthrough including custom domains, see [Deploy to AKS —
@@ -522,11 +523,11 @@ For AKS, `AddAzureKubernetesEnvironment` now wires Azure Application Gateway for
 
 ### Kubernetes manifests and external Helm charts
 
-Aspire 13.4 adds a Kubernetes manifest resource API for arbitrary manifests and an `AddHelmChart` API for installing external Helm charts as deployment pipeline steps. These APIs make it possible to include Kubernetes-native resources, ingress controllers, monitoring stacks, and other third-party charts alongside the resources generated from your Aspire application model.
+Aspire 13.4 adds a Kubernetes manifest resource API for arbitrary manifests and an <ApiReference name="Aspire.Hosting.KubernetesHelmChartExtensions.AddHelmChart" /> API for installing external Helm charts as deployment pipeline steps. These APIs make it possible to include Kubernetes-native resources, ingress controllers, monitoring stacks, and other third-party charts alongside the resources generated from your Aspire application model.
 
 ### Consolidated Helm chart configuration
 
-Helm chart name, version, description, release name, and namespace are now configured through the `WithHelm(...)` extension method. This replaces the previous parallel property-based configuration surface on `KubernetesEnvironmentResource` with one fluent entry point.
+Helm chart name, version, description, release name, and namespace are now configured through the <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.WithHelm" /> extension method. This replaces the previous parallel property-based configuration surface on `KubernetesEnvironmentResource` with one fluent entry point.
 
 <LearnMore>
   For examples of `WithHelm(...)`, see the [Kubernetes integration](/integrations/compute/kubernetes/#configure-helm-chart-options).
@@ -534,7 +535,7 @@ Helm chart name, version, description, release name, and namespace are now confi
 
 ### Reuse an existing ACR pull identity
 
-When deploying to Azure Container Apps, Aspire normally emits a new user-assigned managed identity and an `AcrPull` role assignment so container apps can pull their images. If your deployment principal can't create identities or role assignments, or you want to reuse an existing identity, supply one with `WithAcrPullIdentity` / `withAcrPullIdentity`. The same API is available for both Azure Container App Environments and Azure App Service Environments.
+When deploying to Azure Container Apps, Aspire normally emits a new user-assigned managed identity and an `AcrPull` role assignment so container apps can pull their images. If your deployment principal can't create identities or role assignments, or you want to reuse an existing identity, supply one with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithAcrPullIdentity" />. The same API is available for both Azure Container App Environments and Azure App Service Environments.
 
 <LearnMore>
   For details, see [Configure Azure Container Apps](/integrations/cloud/azure/configure-container-apps/).
@@ -542,7 +543,7 @@ When deploying to Azure Container Apps, Aspire normally emits a new user-assigne
 
 ### Azure Container Apps jobs are stable
 
-The Azure Container Apps jobs APIs — `PublishAsAzureContainerAppJob` and `PublishAsScheduledAzureContainerAppJob` — have graduated to stable. You can declare any project, container, or executable resource as a finite-duration job for batch processing, scheduled tasks, and event-driven workloads directly from your AppHost, without suppressing an experimental diagnostic.
+The Azure Container Apps jobs APIs — <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsAzureContainerAppJob" /> and <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsScheduledAzureContainerAppJob" /> — have graduated to stable. You can declare any project, container, or executable resource as a finite-duration job for batch processing, scheduled tasks, and event-driven workloads directly from your AppHost, without suppressing an experimental diagnostic.
 
 <LearnMore>
   For trigger types and scheduling, see [Azure Container Apps jobs](/integrations/cloud/azure/container-app-jobs/).
@@ -599,7 +600,7 @@ The [Go hosting integration](#go-hosting-integration) section covers the new Go
 Azure Front Door CDN resources now use Azure.Provisioning's built-in name-generation algorithm instead of Aspire's custom logic. This removes Aspire's manual name-length cap and aligns generated resource names with Azure.Provisioning behavior.
 
 <Aside type="caution">
-  Upgrading from Aspire 13.3 can produce duplicate Front Door endpoint, origin group, or route names in existing deployments. Remove and re-add the affected resource, or set the resource `Name` explicitly with `ConfigureInfrastructure`, to avoid conflicts.
+  Upgrading from Aspire 13.3 can produce duplicate Front Door endpoint, origin group, or route names in existing deployments. Remove and re-add the affected resource, or set the resource `Name` explicitly with <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" />, to avoid conflicts.
 </Aside>
 
 <LearnMore>
@@ -646,7 +647,7 @@ Microsoft Foundry hosted agents also include deployment fixes: project endpoints
 
 ### RabbitMQ default image
 
-The default RabbitMQ container image has been bumped from 4.2 to 4.3. Existing AppHosts pick up the new image automatically on the next run; pin a specific tag with `WithImageTag(...)` if you need to stay on a particular version.
+The default RabbitMQ container image has been bumped from 4.2 to 4.3. Existing AppHosts pick up the new image automatically on the next run; pin a specific tag with <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImageTag" /> if you need to stay on a particular version.
 
 <LearnMore>
   For RabbitMQ hosting setup, see the [RabbitMQ integration](/integrations/messaging/rabbitmq/rabbitmq-host/).
@@ -801,7 +802,7 @@ Update `ingress.WithRoute(...)` calls to `ingress.WithPath(...)`, and switch any
 
 Routing a non-external endpoint through a Kubernetes ingress or gateway now throws an `InvalidOperationException` at publish time instead of generating routes that can't resolve.
 
-Call `WithExternalHttpEndpoints()` (or otherwise mark the endpoint external) on any resource whose endpoint you route through an ingress or gateway.
+Call <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" /> (or otherwise mark the endpoint external) on any resource whose endpoint you route through an ingress or gateway.
 
 ### Kubernetes Helm configuration consolidated on `WithHelm(...)`
 
@@ -817,13 +818,13 @@ Remove and re-add the affected resource, or set its `Name` explicitly with `Conf
 
 ### Foundry hosted agents: `WithComputeEnvironment` and `AddPromptAgent`
 
-The Azure AI Foundry hosted-agent API has been aligned with the rest of the app model: `PublishAsHostedAgent` is renamed to `WithComputeEnvironment`, `AddPromptAgent` now takes the resource name as its first parameter (before the model), and the preview-only `AsHostedAgent` / `RunAsHostedAgent` methods were removed.
+The Azure AI Foundry hosted-agent API has been aligned with the rest of the app model: `PublishAsHostedAgent` is renamed to <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" />, <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddPromptAgent" /> now takes the resource name as its first parameter (before the model), and the preview-only <ApiReference name="Aspire.Hosting.HostedAgentResourceBuilderExtensions.AsHostedAgent" /> / `RunAsHostedAgent` methods were removed.
 
 Update hosted-agent registrations to call `WithComputeEnvironment` and pass the resource name first to `AddPromptAgent`.
 
 ### `PublishAsNpmPackageScript` renamed to `PublishAsPackageScript`
 
-The npm-specific publish helper has been generalized to support npm, pnpm, Yarn, and Bun. `PublishAsNpmPackageScript` is renamed to `PublishAsPackageScript`, and its `startScriptName` parameter is renamed to `scriptName`.
+The npm-specific publish helper has been generalized to support npm, pnpm, Yarn, and Bun. `PublishAsNpmPackageScript` is renamed to <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsPackageScript" />, and its `startScriptName` parameter is renamed to `scriptName`.
 
 Rename call sites from `PublishAsNpmPackageScript(...)` to `PublishAsPackageScript(...)` and update the parameter name.
 
@@ -835,7 +836,7 @@ Update references that assumed an HTTP primary endpoint to use the HTTPS endpoin
 
 ### PostgreSQL default image bumped to 18.3, breaking existing data volumes
 
-The default PostgreSQL container image used by `AddPostgres` moved from 17.6 to 18.3. PostgreSQL 18 changed the on-disk data layout: the official `postgres` image now stores cluster files under a major-version-specific subdirectory of `/var/lib/postgresql` (for example, `/var/lib/postgresql/18/docker`), whereas PostgreSQL 17 and earlier stored data directly in `/var/lib/postgresql/data`.
+The default PostgreSQL container image used by <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" /> moved from 17.6 to 18.3. PostgreSQL 18 changed the on-disk data layout: the official `postgres` image now stores cluster files under a major-version-specific subdirectory of `/var/lib/postgresql` (for example, `/var/lib/postgresql/18/docker`), whereas PostgreSQL 17 and earlier stored data directly in `/var/lib/postgresql/data`.
 
 As a result, existing PostgreSQL data persisted with `WithDataVolume()` (a Docker volume) or `WithDataBindMount()` (a host bind mount) on PostgreSQL 17 (Aspire 13.3 or earlier) is incompatible with PostgreSQL 18 after upgrading to 13.4. The container fails to start with an error similar to:
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-5.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-5.mdx
index 0a1ccd5352..cd6d740022 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-5.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-5.mdx
@@ -19,6 +19,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
 import ReleaseCommunity from '@components/ReleaseCommunity.astro';
@@ -153,7 +154,7 @@ The AppHost is where 13.5 invests most heavily. These additions make local devel
 
 ### 🖥️ Interactive terminal sessions with WithTerminal()
 
-AppHost authors can now call `WithTerminal()` on a resource to enable an interactive terminal session. The dashboard can attach to and detach from the session at will, so you can drive REPLs, shells, and other terminal programs that run as Aspire resources — right from the dashboard's terminal view. Terminal dimensions are configurable through `TerminalOptions`, which exposes `Columns` (default `120`), `Rows` (default `30`), and `ShowTerminalHost`.
+AppHost authors can now call <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" /> on a resource to enable an interactive terminal session. The dashboard can attach to and detach from the session at will, so you can drive REPLs, shells, and other terminal programs that run as Aspire resources — right from the dashboard's terminal view. Terminal dimensions are configurable through `TerminalOptions`, which exposes `Columns` (default `120`), `Rows` (default `30`), and `ShowTerminalHost`.
 
 <Aside type="caution">
   `WithTerminal()` and `TerminalOptions` are experimental. C# callers must suppress the `ASPIRETERMINAL001` diagnostic to use them, and the API may change in a future release. The matching `aspire terminal` CLI command is hidden behind a feature flag while the feature is experimental — enable it with `aspire config set features.terminalCommandsEnabled true`.
@@ -534,7 +535,7 @@ await builder.build().run();
 
 ### 🔐 HTTPS certificates for project resources
 
-Project and executable resources can now be configured with HTTPS certificates directly from the AppHost. Use `WithHttpsDeveloperCertificate()` to inject the local ASP.NET Core developer certificate, `WithHttpsCertificate(certificate, password)` to supply an explicit `X509Certificate2`, or `WithHttpsCertificateConfiguration(...)` for full control. `WithoutHttpsCertificate()` opts a resource out.
+Project and executable resources can now be configured with HTTPS certificates directly from the AppHost. Use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsDeveloperCertificate" /> to inject the local ASP.NET Core developer certificate, `WithHttpsCertificate(certificate, password)` to supply an explicit `X509Certificate2`, or <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsCertificateConfiguration" /> for full control. <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithoutHttpsCertificate" /> opts a resource out.
 
 <Aside type="caution">
   The HTTPS certificate APIs are experimental. C# callers must suppress [`ASPIRECERTIFICATES001`](/diagnostics/aspirecertificates001/) to use them.
@@ -684,7 +685,7 @@ await builder.build().run();
 TypeScript AppHost startup no longer waits a fixed delay before the CLI attempts to connect; the CLI now races the RPC connection retry loop against process exit, reducing the time from `aspire run` to an active AppHost. This release also fixes several reliability issues:
 
 - A deadlock where async callbacks stored in `IOptions.Configure` were invoked during `BeforeStartEvent`.
-- A startup reliability issue with `WithBrowserLogs()` where tracked browser sessions could fail even when the browser eventually became responsive; the CDP startup timeout has been increased.
+- A startup reliability issue with <ApiReference name="Aspire.Hosting.BrowserLogsBuilderExtensions.WithBrowserLogs" /> where tracked browser sessions could fail even when the browser eventually became responsive; the CDP startup timeout has been increased.
 - Failures when proxyless container endpoint references were accessed before the container was created.
 - `aspire run` failing for polyglot AppHosts that use `*.dev.localhost` resource service URLs.
 
@@ -781,7 +782,7 @@ Getting from local development to a deployed environment keeps getting smoother.
 
 ### 📦 Persistent volumes for Kubernetes and AKS
 
-You can now model Kubernetes `PersistentVolumeClaim`s as first-class resources. Call `AddPersistentVolume(name)` on a Kubernetes environment, configure it with `WithStorageClass`, `WithCapacity`, and `WithAccessMode`, and bind it to a workload with `WithPersistentVolume(...)`. Any workload bound to a persistent volume is rendered as a `StatefulSet` rather than a `Deployment`. The same `AddPersistentVolume` API is available on the AKS environment via `Aspire.Hosting.Azure.Kubernetes`.
+You can now model Kubernetes `PersistentVolumeClaim`s as first-class resources. Call `AddPersistentVolume(name)` on a Kubernetes environment, configure it with <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithStorageClass" />, <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithCapacity" />, and <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithAccessMode" />, and bind it to a workload with <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithPersistentVolume" />. Any workload bound to a persistent volume is rendered as a `StatefulSet` rather than a `Deployment`. The same <ApiReference name="Aspire.Hosting.AzureKubernetesPersistentVolumeExtensions.AddPersistentVolume" /> API is available on the AKS environment via `Aspire.Hosting.Azure.Kubernetes`.
 
 <Aside type="caution">
   The compute-environment volume APIs are experimental and emit [`ASPIRECOMPUTE002`](/diagnostics/aspirecompute002/), which C# callers must suppress to use them.
@@ -844,7 +845,7 @@ await builder.build().run();
 
 ### 🏷️ Unique resource naming for Azure Container Apps
 
-Azure Container Apps environments can opt into deterministic, collision-resistant resource names with `WithUniqueResourceNaming()`, which is useful when you deploy more than one environment into the same resource group. Names incorporate a `uniqueString(resourceGroup().id)` suffix while preserving each environment's digits, so `cae1` and `cae2` stay distinct.
+Azure Container Apps environments can opt into deterministic, collision-resistant resource names with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.WithUniqueResourceNaming" />, which is useful when you deploy more than one environment into the same resource group. Names incorporate a `uniqueString(resourceGroup().id)` suffix while preserving each environment's digits, so `cae1` and `cae2` stay distinct.
 
 <Aside type="caution">
   `WithUniqueResourceNaming()` is experimental and emits [`ASPIREACANAMING002`](/diagnostics/aspireacanaming002/), which C# callers must suppress to use it. Enabling it on an already-deployed environment changes the environment's `name`, which causes Azure to recreate it — apply it to new deployments, or to environments that specifically need distinct names.
@@ -897,13 +898,13 @@ Azure Container Apps and Azure App Service environments can now be placed into a
 
 <span id="new-and-updated-integrations"></span>
 
-Aspire 13.5 adds a preview [Radius](https://radapp.io/) deployment target through the new `Aspire.Hosting.Radius` package. Use `AddRadiusEnvironment(name)` with `WithNamespace(...)` to publish your app to a Radius environment. Publish-time infrastructure configuration (`ConfigureRadiusInfrastructure`) and project container-image overrides are gated behind experimental diagnostics.
+Aspire 13.5 adds a preview [Radius](https://radapp.io/) deployment target through the new `Aspire.Hosting.Radius` package. Use `AddRadiusEnvironment(name)` with <ApiReference name="Aspire.Hosting.RadiusExtensions.WithNamespace" /> to publish your app to a Radius environment. Publish-time infrastructure configuration (`ConfigureRadiusInfrastructure`) and project container-image overrides are gated behind experimental diagnostics.
 
 ## 📦 Integration updates
 
 Existing integrations pick up new capabilities:
 
-- **Foundry Local.** `AddFoundry(name).RunAsFoundryLocal()` now drives the installed **foundry CLI** for lifecycle management, and resources can be exposed as hosted agents with `AsHostedAgent(...)`, where `HostedAgentProtocol` is `Responses` or `Invocations`.
+- **Foundry Local.** `AddFoundry(name).RunAsFoundryLocal()` now drives the installed **foundry CLI** for lifecycle management, and resources can be exposed as hosted agents with <ApiReference name="Aspire.Hosting.HostedAgentResourceBuilderExtensions.AsHostedAgent" />, where `HostedAgentProtocol` is `Responses` or `Invocations`.
 - **Redis modules.** `AddRedis(...).WithModule(path)` loads a Redis module into the container, with `RedisModules` constants (`Json`, `Search`, `BloomFilter`, `TimeSeries`) pointing at the modules shipped in Redis 8+ images — see the sample below.
 - **Dev tunnels regions.** `DevTunnelOptions.Region` (a `DevTunnelRegion?` enum) lets you pin the region a tunnel is created in.
 - **Blazor gateway on Docker Compose.** Blazor gateway resources now support Docker Compose publishing.
@@ -955,7 +956,7 @@ The following breaking changes are included in Aspire 13.5:
 
 1. **`ServiceProvider` renamed to `Services`.** The `ServiceProvider` property on hosting context types is now `Services`. Update your code to use the new property name.
 
-2. **`PublishAsConnectionString` marked obsolete.** Switch to `AddConnectionString` in publish-mode app model code.
+2. **<ApiReference name="Aspire.Hosting.AzureResourceExtensions.PublishAsConnectionString" /> marked obsolete.** Switch to <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> in publish-mode app model code.
 
 3. **`aspire ps --resources` and `--include-hidden` removed.** `aspire ps` now focuses on AppHost-level summaries; use `aspire describe` for detailed resource data. (`--include-hidden` remains on the `aspire resource` subcommand.)
 
@@ -975,7 +976,7 @@ The following breaking changes are included in Aspire 13.5:
 
 11. **Orleans provider annotation is internal.** `OrleansProviderTypeAnnotation` and `ProviderConfiguration` are now internal.
 
-12. **`DotnetProjectResource` moved to `Aspire.Hosting.Dotnet` and made experimental.** It now lives in the `Aspire.Hosting.Dotnet` namespace and emits the `ASPIREDOTNETPROJECT001` diagnostic. The related `AddDotnetProject` API for modeling .NET projects by path is covered by the same diagnostic.
+12. **`DotnetProjectResource` moved to `Aspire.Hosting.Dotnet` and made experimental.** It now lives in the `Aspire.Hosting.Dotnet` namespace and emits the `ASPIREDOTNETPROJECT001` diagnostic. The related <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.AddDotnetProject" /> API for modeling .NET projects by path is covered by the same diagnostic.
 
 <Aside type="caution" title="Review deprecated APIs">
   Review your code for uses of `ServiceProvider` on hosting context types and `PublishAsConnectionString` extension methods. These generate compiler warnings in Aspire 13.5 and may become harder errors in future releases. If you use the `Aspire.Hosting.GitHub.Models` integration, plan to migrate off it before the package is removed.
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-6.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-6.mdx
index aee2ac6a68..336a921644 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-6.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-6.mdx
@@ -21,6 +21,7 @@ import {
   TabItem,
   Tabs,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import LearnMore from '@components/LearnMore.astro';
 import ReleaseCommunity from '@components/ReleaseCommunity.astro';
 import ThemeImage from '@components/ThemeImage.astro';
@@ -129,7 +130,7 @@ Terminal interactions bring setup workflows into a focused dialog:
   alt="Aspire 13.6 terminal interaction dialog running and completing a local configuration workflow."
 />
 
-These APIs use `ASPIRETERMINAL001`. An AppHost-owned terminal belongs to its creator: closing a viewer isn't a general substitute for disposing the terminal, and stopping the AppHost stops its owned terminals. Resource terminals configured with `WithTerminal` remain separate from AppHost-owned dock tabs. For example, the following AppHost gives a Python REPL its own resource terminal:
+These APIs use `ASPIRETERMINAL001`. An AppHost-owned terminal belongs to its creator: closing a viewer isn't a general substitute for disposing the terminal, and stopping the AppHost stops its owned terminals. Resource terminals configured with <ApiReference name="Aspire.Hosting.TerminalResourceBuilderExtensions.WithTerminal" /> remain separate from AppHost-owned dock tabs. For example, the following AppHost gives a Python REPL its own resource terminal:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
@@ -275,7 +276,7 @@ builder.Build().Run();
 </TabItem>
 </Tabs>
 
-`AddSpringBootApp` / `addSpringBootApp` detect Maven or Gradle from the build file, build the app, and declare an HTTP endpoint through `SERVER_PORT`. Use `AddJavaApp`, `AddQuarkusApp`, or `AddJavaContainer` for other application shapes.
+<ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddSpringBootApp" /> detect Maven or Gradle from the build file, build the app, and declare an HTTP endpoint through `SERVER_PORT`. Use <ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddJavaApp" />, <ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddQuarkusApp" />, or <ApiReference name="Aspire.Hosting.JavaHostingExtensions.AddJavaContainer" /> for other application shapes.
 
 <LearnMore>
   See [Java hosting and Toolkit
@@ -285,7 +286,7 @@ builder.Build().Run();
 
 #### 🦀 Rust
 
-The new `Aspire.Hosting.Rust` package models Cargo applications through `AddRustApp` / `addRustApp`. Configure the Cargo binary target, arguments, and features independently from application arguments, then let Aspire generate a multi-stage Dockerfile for publish and deploy. Visual Studio Code can discover, run, and debug both Rust resources and `apphost.rs` AppHosts.
+The new `Aspire.Hosting.Rust` package models Cargo applications through <ApiReference name="Aspire.Hosting.RustHostingExtensions.AddRustApp" />. Configure the Cargo binary target, arguments, and features independently from application arguments, then let Aspire generate a multi-stage Dockerfile for publish and deploy. Visual Studio Code can discover, run, and debug both Rust resources and `apphost.rs` AppHosts.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
@@ -340,7 +341,7 @@ The service requires preview access in your Azure subscription and region. Refer
 
 The prerelease `Aspire.Hosting.Azure.Sandboxes` package adds Azure Container Apps Sandboxes as a deployment target. Add a sandbox group to your AppHost, and `aspire deploy` provisions the group, an Azure Container Registry, and the identities and role assignments the group needs. It then runs your project, container, and Dockerfile resources as isolated sandboxes. When the sandbox group is the only compute environment, Aspire assigns compute resources to it automatically.
 
-When an AppHost defines multiple compute environments, select the target sandbox group with `WithComputeEnvironment` / `withComputeEnvironment`. `PublishAsAzureSandbox` / `publishAsAzureSandbox` configures sandbox-specific runtime options without taking a sandbox-group parameter.
+When an AppHost defines multiple compute environments, select the target sandbox group with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" />. <ApiReference name="Aspire.Hosting.AzureSandboxesExtensions.PublishAsAzureSandbox" /> configures sandbox-specific runtime options without taking a sandbox-group parameter.
 
 Use `PublishAsAzureSandbox` / `publishAsAzureSandbox` to choose one of five resource tiers and to configure auto-suspend and auto-delete:
 
@@ -418,9 +419,9 @@ Only endpoints marked as external get a public HTTPS URL. Those URLs require Mic
 
 #### Coordinated .NET project builds and publishing
 
-The `AddDotnetProject` / `addDotnetProject` APIs now coordinate compatible projects into shared restore and build groups, avoiding repeated restores of overlapping project graphs. File-based C# apps use serialized direct builds. Use the resource's **Rebuild** command after source changes; **Start** and **Restart** reuse the coordinated output.
+The <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.AddDotnetProject" /> APIs now coordinate compatible projects into shared restore and build groups, avoiding repeated restores of overlapping project graphs. File-based C# apps use serialized direct builds. Use the resource's **Rebuild** command after source changes; **Start** and **Restart** reuse the coordinated output.
 
-These resources also participate in .NET SDK container publishing. You can select launch profiles from either AppHost language and separate MSBuild inputs with `WithBuildEnvironment` / `withBuildEnvironment` from runtime environment variables. Build-only variables aren't supported for file-based apps and must not be used for secrets.
+These resources also participate in .NET SDK container publishing. You can select launch profiles from either AppHost language and separate MSBuild inputs with <ApiReference name="Aspire.Hosting.DotnetProjectHostingExtensions.WithBuildEnvironment" /> from runtime environment variables. Build-only variables aren't supported for file-based apps and must not be used for secrets.
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='typescript' label='TypeScript'>
@@ -453,7 +454,7 @@ builder.Build().Run();
 
 `AddDotnetProject`, `DotnetProjectResource`, and the related `WithBuildEnvironment` overloads no longer require [`ASPIREDOTNETPROJECT001`](/diagnostics/aspiredotnetproject001/) suppression in Aspire 13.6. This diagnostic was unnecessary for `Aspire.Hosting.Dotnet` because the package is already prerelease. Its APIs remain unstable and may change in future releases.
 
-The diagnostic is also removed from `AddDotnetProjectBlazorGateway` and its `WithBlazorClientApp` overload in `Aspire.Hosting.Blazor`. This package also remains prerelease, and its APIs remain unstable and may change. The separate [`ASPIREBLAZOR001`](/diagnostics/aspireblazor001/) diagnostic still applies to experimental Blazor hosting types.
+The diagnostic is also removed from <ApiReference name="Aspire.Hosting.BlazorGatewayExtensions.AddDotnetProjectBlazorGateway" /> and its `WithBlazorClientApp` overload in `Aspire.Hosting.Blazor`. This package also remains prerelease, and its APIs remain unstable and may change. The separate [`ASPIREBLAZOR001`](/diagnostics/aspireblazor001/) diagnostic still applies to experimental Blazor hosting types.
 
 Projects that depend on per-project restore hooks can opt into individual restore with `Aspire:Dotnet:RestoreProjectsIndividually` in the AppHost configuration.
 
@@ -653,7 +654,7 @@ The Aspire extension brings more of the development lifecycle into the Aspire pa
 
 #### Azure infrastructure customization from polyglot AppHosts
 
-The new experimental `Aspire.Hosting.Azure.Provisioning.*` packages expose Azure Provisioning SDK model proxies to polyglot AppHosts. Opt into the package for the service you need, then use `configureInfrastructure` to customize supported resource properties and compose Bicep expressions.
+The new experimental `Aspire.Hosting.Azure.Provisioning.*` packages expose Azure Provisioning SDK model proxies to polyglot AppHosts. Opt into the package for the service you need, then use <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> to customize supported resource properties and compose Bicep expressions.
 
 These packages extend existing hosting integrations; they aren't new deployment targets, and installing a hosting package doesn't automatically install its provisioning proxies. The shared runtime reports `ASPIREAZUREPROVISIONING001`, and the projected SDK surface has documented exclusions.
 
@@ -683,7 +684,7 @@ Deployment state and Kubernetes output are more portable and predictable:
 
 #### Azure Container Apps Express environments
 
-Azure Container Apps environments can opt into the Express preview with `AsExpress`. Express offers rapid provisioning and fewer infrastructure settings to configure, helping you get HTTP APIs, web frontends, and AI backends deployed quickly. Automatic scaling to zero when idle, on-demand scale-out, and optimized cold starts make it a good fit for apps with intermittent or unpredictable traffic.
+Azure Container Apps environments can opt into the Express preview with <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AsExpress" />. Express offers rapid provisioning and fewer infrastructure settings to configure, helping you get HTTP APIs, web frontends, and AI backends deployed quickly. Automatic scaling to zero when idle, on-demand scale-out, and optimized cold starts make it a good fit for apps with intermittent or unpredictable traffic.
 
 <Aside type="caution" title="Experimental">
   Express support is experimental and reports
@@ -703,13 +704,13 @@ Azure Container Apps environments can opt into the Express preview with `AsExpre
 Existing integrations add new workflows and safer defaults:
 
 - **Docked database and cache REPLs.** Opt into `WithRepl()` / `withRepl()` on PostgreSQL, Redis, Valkey, MongoDB, MySQL, and SQL Server resources to open an interactive client for the resource in the dashboard terminal dock, using bundled clients and the resource's configured credentials. It's run-mode only and leaves existing apps unchanged unless you enable it. See [Database and cache REPLs](#database-and-cache-repls).
-- **Deno hosting.** `Aspire.Hosting.JavaScript` adds experimental `AddDenoApp` / `addDenoApp`, which runs a script from an app directory, with task and serve modes, permission controls, and runtime flags. These APIs report `ASPIREDENO001`, and Deno must be installed for local execution. The first-party API differs from the Community Toolkit's [Deno integration](/integrations/frameworks/deno/deno-host/).
-- **MongoDB replica sets.** Experimental `WithReplicaSet` / `withReplicaSet` configures and initializes a single-member replica set, enabling transactions and change streams after readiness. A separate `AddMongoDBReplicaSet` API supports multi-member local scenarios. Both paths are local-run-only and reject publishing; see [MongoDB replica sets](/integrations/databases/mongodb/mongodb-host/#enable-transactions-and-change-streams-with-a-single-member-replica-set).
+- **Deno hosting.** `Aspire.Hosting.JavaScript` adds experimental <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddDenoApp" />, which runs a script from an app directory, with task and serve modes, permission controls, and runtime flags. These APIs report `ASPIREDENO001`, and Deno must be installed for local execution. The first-party API differs from the Community Toolkit's [Deno integration](/integrations/frameworks/deno/deno-host/).
+- **MongoDB replica sets.** Experimental <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.WithReplicaSet" /> configures and initializes a single-member replica set, enabling transactions and change streams after readiness. A separate <ApiReference name="Aspire.Hosting.MongoDBReplicaSetBuilderExtensions.AddMongoDBReplicaSet" /> API supports multi-member local scenarios. Both paths are local-run-only and reject publishing; see [MongoDB replica sets](/integrations/databases/mongodb/mongodb-host/#enable-transactions-and-change-streams-with-a-single-member-replica-set).
 - **MongoDB automatic TLS.** Local MongoDB resources now use Aspire's shared certificate configuration, including standalone servers. Existing plaintext clients should review the [TLS migration guidance](#mongodb-now-uses-automatic-tls-during-local-runs).
-- **Microsoft Foundry Toolboxes.** `AddToolbox` / `addToolbox` bundles tools behind one MCP endpoint and manages immutable versions as tool configuration changes. MCP approval policies are discovery metadata that the consuming application must enforce. See the [Toolbox walkthrough](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#add-a-toolbox).
-- **Remote Foundry Local services.** `RunAsFoundryLocal` / `runAsFoundryLocal` now accepts an endpoint, so an AppHost, including one on WSL2 or Linux, can observe a Foundry Local service already running on another host (for example, a Windows GPU box) without starting, stopping, or downloading models on it. The integration also handles the newer `foundry server` CLI generation. See [Connect to a remote Foundry Local service](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#connect-to-a-remote-foundry-local-service).
+- **Microsoft Foundry Toolboxes.** <ApiReference name="Aspire.Hosting.FoundryToolboxBuilderExtensions.AddToolbox" /> bundles tools behind one MCP endpoint and manages immutable versions as tool configuration changes. MCP approval policies are discovery metadata that the consuming application must enforce. See the [Toolbox walkthrough](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#add-a-toolbox).
+- **Remote Foundry Local services.** <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> now accepts an endpoint, so an AppHost, including one on WSL2 or Linux, can observe a Foundry Local service already running on another host (for example, a Windows GPU box) without starting, stopping, or downloading models on it. The integration also handles the newer `foundry server` CLI generation. See [Connect to a remote Foundry Local service](/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-host/#connect-to-a-remote-foundry-local-service).
 - **Blazor WebAssembly debugging.** Standalone and hosted WebAssembly apps can expose dashboard commands for starting and stopping an Edge or Chrome debugging session during local runs. The related Dotnet project gateway APIs are also available to polyglot AppHosts and participate in publishing, but remain unstable and may change. See [Blazor gateway hosting](/integrations/dotnet/blazor-hosting/#add-a-blazor-gateway-for-a-c-project-resource).
-- **Dev Tunnel discovery and expiration.** Tunnel, inspect, and local endpoint URLs appear as highlighted resource properties, and a **Show tunnel URLs** command surfaces them through the dashboard Interaction Service. `WithExpiration` / `withExpiration` also configures idle expiration for new or reused tunnels, in whole hours from one hour through 30 days.
+- **Dev Tunnel discovery and expiration.** Tunnel, inspect, and local endpoint URLs appear as highlighted resource properties, and a **Show tunnel URLs** command surfaces them through the dashboard Interaction Service. <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.WithExpiration" /> also configures idle expiration for new or reused tunnels, in whole hours from one hour through 30 days.
 - **Radius recipe configuration.** Experimental APIs configure recipe parameters and required secrets globally or per resource from the AppHost. The integration now recommends [Radius v0.60.2](https://github.com/radius-project/radius/releases/tag/v0.60.2); v0.60.0 remains the minimum supported control-plane version.
 - **Radius backing connections.** Consumer addresses and credentials now come from the backing resource's deployed schema and recipe outputs rather than local endpoint guesses. New publish diagnostics catch unsupported endpoints, database mappings, credentials, and secret collisions. Review the [Radius deployment guide](/deployment/radius/) before upgrading.
 - **Safer Azure location changes.** Changing a location-immutable Azure resource requires an explicit confirmation before Aspire deletes and recreates it. The CLI projects that confirmation as `--confirm-delete`.
@@ -717,7 +718,7 @@ Existing integrations add new workflows and safer defaults:
 - **Cosmos DB client health.** `AddAzureCosmosClient` and `AddKeyedAzureCosmosClient` register default-on health checks that probe account reachability. Set `DisableHealthChecks` to opt out.
 - **AI Inference client health.** Chat-completions and embeddings health checks now call `GetModelInfoAsync` against `/info`. Endpoints without this route may need `DisableHealthChecks`; this doesn't add Azure OpenAI health checks. See [AI Inference health checks](/integrations/cloud/azure/azure-ai-inference/azure-ai-inference-connect/#client-integration-health-checks).
 - **Cosmos DB emulator telemetry.** The vNext emulator exports its own traces and metrics to the dashboard automatically, separately from consuming application instrumentation.
-- **Cosmos DB emulator defaults.** `RunAsEmulator` / `runAsEmulator` now uses the Linux-based vNext emulator. Use `RunAsClassicEmulator` / `runAsClassicEmulator` to retain the classic emulator, or configure the vNext Data Explorer without suppressing `ASPIRECOSMOSDB001`. See the [Cosmos DB emulator guide](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/#run-as-emulator) and [migration guidance](#breaking-changes).
+- **Cosmos DB emulator defaults.** <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsEmulator" /> now uses the Linux-based vNext emulator. Use <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsClassicEmulator" /> to retain the classic emulator, or configure the vNext Data Explorer without suppressing `ASPIRECOSMOSDB001`. See the [Cosmos DB emulator guide](/integrations/cloud/azure/azure-cosmos-db/azure-cosmos-db-host/#run-as-emulator) and [migration guidance](#breaking-changes).
 - **Foundry model refreshes.** Generated Foundry model constants were refreshed throughout the release cycle without changing the hosting API shape.
 - **Typed guest callbacks.** Callbacks with `Action<IResourceBuilder<T>>` arguments retain the concrete resource identity, fixing Python callback methods that previously received an unwrapped handle. See [multi-language integration authoring](/extensibility/multi-language-integration-authoring/).
 - **Front Door origin identity.** Generated origin names now include the origin's backend hostname, so switching backends creates a distinct origin instead of reusing the previous origin's Azure identity. Review the [breaking-change guidance](#breaking-changes) before upgrading.
@@ -801,7 +802,7 @@ Two emulator defaults changed:
 | Azure App Configuration | `mcr.microsoft.com/azure-app-configuration/app-configuration-emulator` | `1.0.2`     | `1.2.0`        |
 | Azure Cosmos DB         | `mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator`               | `stable`    | `vnext-latest` |
 
-Aspire's App Configuration emulator now checks the `/health` endpoint on the `1.2.0` image, so `OnResourceReady` runs only after the emulator accepts requests. The Cosmos DB change also affects runtime behavior and persisted data; review the [breaking-change guidance](#breaking-changes) before upgrading.
+Aspire's App Configuration emulator now checks the `/health` endpoint on the `1.2.0` image, so <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceReady" /> runs only after the emulator accepts requests. The Cosmos DB change also affects runtime behavior and persisted data; review the [breaking-change guidance](#breaking-changes) before upgrading.
 
 ## 🐛 Bug fixes
 
@@ -821,11 +822,11 @@ Aspire is built in the open, and this release wouldn't be what it is without you
 
 #### MongoDB now uses automatic TLS during local runs
 
-Starting in Aspire 13.6, MongoDB server resources participate in shared certificate configuration. When a certificate is configured and available, normally the developer certificate under default settings, Aspire starts the server with `--tlsMode requireTLS` and adds `tls=true` to its generated connection string. This changes the previous plaintext default for **ordinary `AddMongoDB` resources**, even if you don't use replica sets.
+Starting in Aspire 13.6, MongoDB server resources participate in shared certificate configuration. When a certificate is configured and available, normally the developer certificate under default settings, Aspire starts the server with `--tlsMode requireTLS` and adds `tls=true` to its generated connection string. This changes the previous plaintext default for **ordinary <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.AddMongoDB" /> resources**, even if you don't use replica sets.
 
 Use the complete generated connection string instead of constructing a URI from host and port. Clients must trust the server certificate and use a hostname it covers. A container client connecting by the MongoDB resource name can encounter a hostname mismatch with the developer certificate; trusting the certificate alone doesn't fix that.
 
-For an explicit local-development opt-out, use `WithoutHttpsCertificate()` / `withoutHttpsCertificate()` on a standalone server or the simple `WithReplicaSet()` / `withReplicaSet()` configuration. This disables transport encryption. Don't apply it to advanced `AddMongoDBReplicaSet(...).WithMember(...)` members, which require TLS/SNI for split-horizon discovery.
+For an explicit local-development opt-out, use <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithoutHttpsCertificate" /> on a standalone server or the simple `WithReplicaSet()` / `withReplicaSet()` configuration. This disables transport encryption. Don't apply it to advanced `AddMongoDBReplicaSet(...).WithMember(...)` members, which require TLS/SNI for split-horizon discovery.
 
 `PreferTls` accepts plaintext and TLS clients but still advertises TLS in generated connection strings. The global `ASPIRE_DEVELOPER_CERTIFICATE_DEFAULT_HTTPS_TERMINATION=false` switch affects ambient defaults for other resources too; it doesn't disable explicit member certificates. These local-run defaults don't automatically configure certificates for published MongoDB containers.
 
@@ -870,9 +871,9 @@ builder.Build().Run();
 If you adopt the new default:
 
 - Re-seed persisted emulator data. The vNext emulator stores data under `/data`, while the classic emulator uses `/tmp/cosmos/appdata`; existing classic data doesn't carry over.
-- Remove `WithPartitionCount` / `withPartitionCount`. Partition count isn't supported by the vNext emulator and now throws `NotSupportedException`.
-- Call `WithDataExplorer` / `withDataExplorer` if you need the Data Explorer. Aspire disables it by default for vNext, and the API isn't supported with the classic emulator.
-- Update experimental calls from `RunAsPreviewEmulator` / `runAsPreviewEmulator` to `RunAsEmulator` / `runAsEmulator`. The preview methods remain as obsolete compatibility aliases, and `ASPIRECOSMOSDB001` is retired.
+- Remove <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithPartitionCount" />. Partition count isn't supported by the vNext emulator and now throws `NotSupportedException`.
+- Call <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithDataExplorer" /> if you need the Data Explorer. Aspire disables it by default for vNext, and the API isn't supported with the classic emulator.
+- Update experimental calls from <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.RunAsPreviewEmulator" /> to `RunAsEmulator` / `runAsEmulator`. The preview methods remain as obsolete compatibility aliases, and `ASPIRECOSMOSDB001` is retired.
 - Revalidate emulator-dependent tests and startup expectations. The classic emulator requires its TLS certificate, while the vNext emulator uses a different startup and health model.
 
 <LearnMore>
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13.mdx b/src/frontend/src/content/docs/whats-new/aspire-13.mdx
index 4875b81760..bac5603d24 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13.mdx
@@ -27,6 +27,7 @@ import colorTweaks from '@assets/whats-new/color-tweaks.png';
 import healthChecksLastRun from '@assets/whats-new/health-checks-last-run.png';
 import resourcesParametersView from '@assets/whats-new/resources-parameters-view.png';
 import genaiVisualizerTooldefinitions from '@assets/whats-new/genai-visualizer-tooldefinitions.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 13 represents a major milestone in the Aspire product line.
 
@@ -214,7 +215,7 @@ var api = builder.AddPythonExecutable("api", "../api", "gunicorn")
 
 #### Uvicorn integration for ASGI applications
 
-For Python web applications using ASGI frameworks like FastAPI, Starlette, or Quart, Aspire provides dedicated `AddUvicornApp` support:
+For Python web applications using ASGI frameworks like FastAPI, Starlette, or Quart, Aspire provides dedicated <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddUvicornApp" /> support:
 
 ```csharp title="Uvicorn integration"
 var api = builder.AddUvicornApp("api", "./api", "main:app")
@@ -243,7 +244,7 @@ var api = builder.AddUvicornApp("api", "./api", "main:app");
 
 In most cases, you don't need to configure package management explicitly because Aspire detects it automatically.
 
-For modern Python projects using [uv](https://github.com/astral-sh/uv), explicitly opt in with `WithUv()`:
+For modern Python projects using [uv](https://github.com/astral-sh/uv), explicitly opt in with <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithUv" />:
 
 ```csharp title="Using uv for package management"
 builder.AddUvicornApp("api", "./api", "main:app")
@@ -257,7 +258,7 @@ When using `WithUv()`, Aspire:
 - Leverages uv's performance benefits (10-100x faster than pip).
 - Auto-detects Python version from project configuration.
 
-To configure pip behavior explicitly, use `WithPip()`:
+To configure pip behavior explicitly, use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithPip" />:
 
 ```csharp title="Using pip for package management"
 builder.AddUvicornApp("api", "./api", "main:app")
@@ -270,7 +271,7 @@ When using `WithPip()`, Aspire:
 - Detects virtual environments (`.venv`) by walking up parent directories.
 - Creates a virtual environment if one doesn't exist.
 
-By default, Aspire uses `.venv` in the app directory as the virtual environment path. Use `WithVirtualEnvironment()` to specify a custom path or control automatic creation:
+By default, Aspire uses `.venv` in the app directory as the virtual environment path. Use <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithVirtualEnvironment" /> to specify a custom path or control automatic creation:
 
 ```csharp title="Configuring virtual environment path"
 // Use a custom venv path
@@ -290,8 +291,8 @@ Python applications can be debugged directly in VS Code with full breakpoint sup
 
 Supported debugging scenarios include:
 
-- Debug Python scripts added with `AddPythonApp`, including breakpoints and variable inspection.
-- Debug Python modules added with `AddPythonModule`, including module resolution.
+- Debug Python scripts added with <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" />, including breakpoints and variable inspection.
+- Debug Python modules added with <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonModule" />, including module resolution.
 - Debug Flask apps with auto-reload.
 - Debug Uvicorn and FastAPI ASGI applications with async and await support.
 
@@ -365,7 +366,7 @@ import pythonStarterLightPng from '@assets/get-started/python-starter-light.png'
 
 ### JavaScript as a first-class citizen
 
-Aspire 13.0 refactors and expands JavaScript support. In earlier versions, the `Aspire.Hosting.NodeJs` integration enabled JavaScript applications. In Aspire 13.0, the integration was renamed to `Aspire.Hosting.JavaScript` and it introduces `AddJavaScriptApp` as the foundational method for all JavaScript applications.
+Aspire 13.0 refactors and expands JavaScript support. In earlier versions, the `Aspire.Hosting.NodeJs` integration enabled JavaScript applications. In Aspire 13.0, the integration was renamed to `Aspire.Hosting.JavaScript` and it introduces <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" /> as the foundational method for all JavaScript applications.
 
 #### Unified JavaScript application model
 
@@ -430,7 +431,7 @@ var app = builder.AddJavaScriptApp("app", "./app")
 
 Unlike the deprecated `AddNpmApp` API, `AddJavaScriptApp` does not support an `args` constructor parameter for passing command-line arguments directly to scripts. You have two options to pass arguments:
 
-Option 1 uses `WithArgs` to pass arguments directly:
+Option 1 uses <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" /> to pass arguments directly:
 
 ```csharp title="Pass arguments using WithArgs"
 // Before (Aspire 9.x with AddNpmApp)
@@ -470,7 +471,7 @@ Option 2 keeps all script configuration in `package.json`, making your scripts m
 
 #### Vite support
 
-`AddViteApp` is now a specialization of `AddJavaScriptApp` with Vite-specific optimizations:
+<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> is now a specialization of `AddJavaScriptApp` with Vite-specific optimizations:
 
 ```csharp title="Vite support"
 var frontend = builder.AddViteApp("frontend", "./frontend")
@@ -504,7 +505,7 @@ For information about using JavaScript build artifacts in other containers, see
 
 #### Node support
 
-`AddNodeApp` has now been refactored to align with other language integrations.
+<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" /> has now been refactored to align with other language integrations.
 
 ```csharp title="Node support"
 var app = builder.AddNodeApp("frontend", "./frontend", "app.js")
@@ -541,7 +542,7 @@ var javaApp = builder.AddExecutable("java-app", "java", "./app", ["-jar", "app.j
     .WithEnvironment("DB_JDBC", postgres.Resource.JdbcConnectionStringExpression);
 ```
 
-When you reference a database resource with `WithReference`, Aspire automatically exposes multiple connection properties as environment variables. For example, a PostgreSQL resource named `db` exposes:
+When you reference a database resource with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />, Aspire automatically exposes multiple connection properties as environment variables. For example, a PostgreSQL resource named `db` exposes:
 
 - `DB_URI` - PostgreSQL URI format: `postgresql://user:pass@host:port/dbname`.
 - `DB_JDBCCONNECTIONSTRING` - JDBC format: `jdbc:postgresql://host:port/dbname`.
@@ -630,7 +631,7 @@ When you run `aspire init`, the CLI will:
 The init command simplifies the initial project setup through an interactive workflow that ensures consistent configuration across team members.
 
 > [!NOTE]
-> The `aspire init` command sets up the Aspire project structure and configuration, but does not automatically add resources (databases, caches, message queues, etc.) to your AppHost. You'll need to manually add resource definitions to your AppHost code using methods like `AddPostgres`, `AddRedis`, `AddRabbitMQ`, etc.
+> The `aspire init` command sets up the Aspire project structure and configuration, but does not automatically add resources (databases, caches, message queues, etc.) to your AppHost. You'll need to manually add resource definitions to your AppHost code using methods like <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" />, <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" />, <ApiReference name="Aspire.Hosting.RabbitMQBuilderExtensions.AddRabbitMQ" />, etc.
 
 ### aspire new: Curated starter templates
 
@@ -829,7 +830,7 @@ Steps registered in the pipeline can be run via the CLI:
 aspire do validate
 ```
 
-The pipeline system supports global steps, resource-specific steps, dependency configuration, parallel execution, and built-in logging. Resources can contribute their own steps via `WithPipelineStepFactory` and control ordering with `WithPipelineConfiguration`.
+The pipeline system supports global steps, resource-specific steps, dependency configuration, parallel execution, and built-in logging. Resources can contribute their own steps via <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" /> and control ordering with <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineConfiguration" />.
 
 #### Running pipeline steps
 
@@ -1256,9 +1257,9 @@ This enables proper service-to-service communication whether the consumer is run
 
 ### Other app model improvements
 
-- The `WithComputeEnvironment` API is now **stable**, so you can deploy resources to specific compute environments without experimental warnings.
-- The `ExcludeFromMcp` extension controls which resources are visible to AI assistants and MCP clients.
-- `WithReferenceEnvironment` and `ReferenceEnvironmentInjectionFlags` provide fine-grained control over how references inject environment variables.
+- The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" /> API is now **stable**, so you can deploy resources to specific compute environments without experimental warnings.
+- The <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromMcp" /> extension controls which resources are visible to AI assistants and MCP clients.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReferenceEnvironment" /> and `ReferenceEnvironmentInjectionFlags` provide fine-grained control over how references inject environment variables.
 - `TryCreateResourceBuilder` safely attempts resource builder creation and returns `false` instead of throwing when creation fails.
 
 ## 🚀 Deployment improvements
@@ -1547,7 +1548,7 @@ await resource.ProcessArgumentValuesAsync(
 
 The `containerHostName` parameter has been removed. Network context is now handled through `NetworkIdentifier`.
 
-`EndpointReference.GetValueAsync` behavior changed:
+<ApiReference name="Aspire.Hosting.ApplicationModel.EndpointReference.GetValueAsync" /> behavior changed:
 ```csharp
 // Before (9.x) - would throw immediately if not allocated
 var value = await endpointRef.GetValueAsync(cancellationToken);
@@ -1608,7 +1609,7 @@ Behavior also changed:
 
 1. If `package.json` exists in `appDirectory`, npm is configured automatically with auto-install enabled.
 2. Docker publishing support generates multi-stage builds by default.
-3. Use `WithNpm()`, `WithYarn()`, or `WithPnpm()` with `WithRunScript()` to execute `package.json` scripts.
+3. Use `WithNpm()`, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" />, or <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithPnpm" /> with <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.WithRunScript" /> to execute `package.json` scripts.
 
 </Steps>
 
@@ -1645,8 +1646,8 @@ This change ensures `DefaultAzureCredential` always uses `ManagedIdentityCredent
 
 The affected APIs are:
 
-- `AddAzureContainerAppEnvironment`
-- `AddAzureAppServiceEnvironment`
+- <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />
+- <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.AddAzureAppServiceEnvironment" />
 
 If you were relying on `EnvironmentCredential` or `WorkloadIdentityCredential` in your application, choose one of the following options:
 
@@ -1752,8 +1753,8 @@ builder.Services.TryAddEventingSubscriber<MyEventSubscriber>();
 
 The following features are marked as `[Experimental]` and may change in future releases:
 
-- The Dockerfile builder APIs: `WithDockerfileBuilder`, `AddDockerfileBuilder`, and `WithDockerfileBaseImage`.
-- C# file-based app support through `AddCSharpApp`.
+- The Dockerfile builder APIs: <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" />, <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" />, and <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBaseImage" />.
+- C# file-based app support through <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" />.
 - Dynamic inputs through `InputLoadOptions` and dynamic input loading.
 - Pipeline features through `IDistributedApplicationPipeline` and related APIs.
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-1.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-1.mdx
index 8b9beb7dbf..099954024f 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-1.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-1.mdx
@@ -16,6 +16,7 @@ import dashboardRemoveTelemetry from '@assets/whats-new/aspire-9.1/dashboard-rem
 import dashboardFilter from '@assets/whats-new/aspire-9.1/dashboard-filter.png';
 import dashboardResourceDetails from '@assets/whats-new/aspire-9.1/dashboard-resourcedetails.png';
 import consoleLogsDownload from '@assets/whats-new/aspire-9.1/consolelogs-download.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.1 is the next minor version release of Aspire; it supports _both_:
 
@@ -154,7 +155,7 @@ In Aspire 9.1, several improvements to streamline your local development experie
 
 ### ▶️ Start resources on demand
 
-You can now tell resources not to start with the rest of your app by using `WithExplicitStart` on the resource in your AppHost. Then, you can start it whenever you're ready from inside the dashboard.
+You can now tell resources not to start with the rest of your app by using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> on the resource in your AppHost. Then, you can start it whenever you're ready from inside the dashboard.
 
 ### 🐳 Better Docker integration
 
@@ -212,7 +213,7 @@ Along with support for the new emulator, Cosmos DB added the following features.
 
 ##### 🔒 Support for Entra ID authentication by default
 
-Previously, the Cosmos DB integration used access keys and a Key Vault secret to connect to the service. Aspire 9.1 added support for using more secure authentication using managed identities by default. If you need to keep using access key authentication, you can get back to the previous behavior by calling `WithAccessKeyAuthentication`.
+Previously, the Cosmos DB integration used access keys and a Key Vault secret to connect to the service. Aspire 9.1 added support for using more secure authentication using managed identities by default. If you need to keep using access key authentication, you can get back to the previous behavior by calling <ApiReference name="Aspire.Hosting.AzureCosmosExtensions.WithAccessKeyAuthentication" />.
 
 ##### 💽 Support for modeling Database and Containers in the AppHost
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
index 50396089ed..c9cbba24e5 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
@@ -14,6 +14,7 @@ import dashboardCardinalityLimit from '@assets/whats-new/aspire-9.2/dashboard-ca
 import dashboardConsoleLogsUtc from '@assets/whats-new/aspire-9.2/dashboard-console-logs-utc.png';
 import dashboardPauseTelemetry from '@assets/whats-new/aspire-9.2/dashboard-pause-telemetry.png';
 import dashboardResourceIcons from '@assets/whats-new/aspire-9.2/dashboard-resource-icons.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.2 is the next minor version release of Aspire; it supports:
 
@@ -149,7 +150,7 @@ We've added a search text box to trace details. Now you can quickly filter large
 
 ### 🌐 HTTP-based resource command functionality
 
-[Custom resource commands](/fundamentals/custom-resource-commands/) now support HTTP-based functionality with the addition of the `WithHttpCommand` API, enabling you to define endpoints for tasks like database migrations or resets. These commands can be run directly from the Aspire dashboard.
+[Custom resource commands](/fundamentals/custom-resource-commands/) now support HTTP-based functionality with the addition of the <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpCommand" /> API, enabling you to define endpoints for tasks like database migrations or resets. These commands can be run directly from the Aspire dashboard.
 
 Adds WithHttpCommand(), which lets you define a resource command that sends an HTTP request to your app during development. Useful for triggering endpoints like seed or reset from the dashboard.
 
@@ -212,7 +213,7 @@ The `ImagePullPolicy` is set to `Always`, which means the image will always be p
 
 ### 📂 New container files API
 
-In Aspire 9.2, we've added a new `WithContainerFiles` API, a way to create files and folders inside a container at runtime by defining them in code. Under the hood, it uses `docker cp` / `podman cp` to copy the files in. Supports setting contents, permissions, and ownership—no bind mounts or temp files needed.
+In Aspire 9.2, we've added a new <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerFiles" /> API, a way to create files and folders inside a container at runtime by defining them in code. Under the hood, it uses `docker cp` / `podman cp` to copy the files in. Supports setting contents, permissions, and ownership—no bind mounts or temp files needed.
 
 ## 🤝 Integrations updates
 
@@ -224,7 +225,7 @@ The Redis, Valkey, and Garnet containers enable password authentication by defau
 
 ### 💾 Automatic database creation support
 
-There's [plenty of feedback and confusion](https://github.com/microsoft/aspire/issues/7101) around the `AddDatabase` API. The name implies that it adds a database, but it didn't actually create the database. In Aspire 9.2, the `AddDatabase` API now creates a database for the following hosting integrations:
+There's [plenty of feedback and confusion](https://github.com/microsoft/aspire/issues/7101) around the <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.AddDatabase" /> API. The name implies that it adds a database, but it didn't actually create the database. In Aspire 9.2, the `AddDatabase` API now creates a database for the following hosting integrations:
 
 | Hosting integration | API reference |
 |--|--|
@@ -266,7 +267,7 @@ In Aspire 9.2, we've made significant updates to Azure integrations, including:
 
 ### ⚙️ Configure Azure Container Apps environments
 
-Aspire 9.2 introduces `AddAzureContainerAppEnvironment`, allowing you to define an Azure Container App environment directly in your app model. This adds an `AzureContainerAppsEnvironmentResource` that lets you configure the environment and its supporting infrastructure (like container registries and volume file shares) using C# and the Azure Provisioning APIs—without relying on `azd` for infrastructure generation.
+Aspire 9.2 introduces <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />, allowing you to define an Azure Container App environment directly in your app model. This adds an `AzureContainerAppsEnvironmentResource` that lets you configure the environment and its supporting infrastructure (like container registries and volume file shares) using C# and the Azure Provisioning APIs—without relying on `azd` for infrastructure generation.
 
 <Aside type="caution">
 This uses a different resource naming scheme than `azd`. If you're upgrading an existing deployment, this may create duplicate resources. To avoid this, you can opt into `azd`'s naming convention:
@@ -430,7 +431,7 @@ builder.AddProject<Projects.Api>("api")
 
 **New behavior in 9.2:**
 
-Calling `WithKeyAccessAuthentication` or `WithPasswordAuthentication` now creates an actual `AzureKeyVaultResource` (or accepts a reference to one), and stores connection strings there. Secret names follow the pattern `connectionstrings--{resourcename}` to prevent naming conflicts with other vault entries.
+Calling `WithKeyAccessAuthentication` or <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.WithPasswordAuthentication" /> now creates an actual `AzureKeyVaultResource` (or accepts a reference to one), and stores connection strings there. Secret names follow the pattern `connectionstrings--{resourcename}` to prevent naming conflicts with other vault entries.
 
 ### 🔒 Improved default permissions for Azure Key Vault references
 
@@ -494,7 +495,7 @@ aspire publish --publisher docker-compose
 #### Available commands:
 
 - `new <template>` – Create a new Aspire sample project
-- `run` – Run an Aspire AppHost in development mode
+- <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> – Run an Aspire AppHost in development mode
 - `add <integration>` – Add an integration to your project
 - `publish` – Generate deployment artifacts from your AppHost
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
index e54c87b0ec..e593e6305b 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-3.mdx
@@ -15,6 +15,7 @@ import dashboardFilter from '@assets/whats-new/aspire-9.3/dashboard-filter.png';
 import dashboardMetricsWarning from '@assets/whats-new/aspire-9.3/dashboard-metrics-warning.png';
 import dashboardTracesUninstrumentedResources from '@assets/whats-new/aspire-9.3/dashboard-traces-uninstrumented-resources.png';
 import dashboardContextMenu from '@assets/whats-new/aspire-9.3/dashboard-context-menu.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.3 is the next minor version release of Aspire. It supports:
 
@@ -51,7 +52,7 @@ The new `WithHostPort`, `WithPassword`, and `WithUserName` (or equivalent per-se
 
 - **Pick where a link appears** – each link now carries a `UrlDisplayLocation` (`SummaryAndDetails` or `DetailsOnly`), so you can keep diagnostic links out of the main grid yet still see them in the details pane.
 - **Relative paths are auto-resolved** – hand the helper `"/health"` and Aspire rewrites it to the full host-qualified URL when the endpoint is allocated.
-- **Multiple links per endpoint** – an overload of `WithUrlForEndpoint` lets you attach extra URLs (docs, admin UIs, probes) to the same endpoint without redefining it.
+- **Multiple links per endpoint** – an overload of <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrlForEndpoint" /> lets you attach extra URLs (docs, admin UIs, probes) to the same endpoint without redefining it.
 - **Endpoint helper inside callbacks** – `context.GetEndpoint("https")` fetches the fully-resolved endpoint so you can build custom links programmatically.
 - **Custom URLs for any resource** – `WithUrl*` also works for custom resources.
 
@@ -77,7 +78,7 @@ With these tweaks you can further customize your local dev stack by surfacing th
 
 Historically the only way to keep a resource out of the Dashboard was to put it in the **`Hidden`** *state*—a hack that also made the resource look "terminal" to APIs such as `WaitForResourceAsync`. In 9.3 every snapshot now carries a **boolean `IsHidden` flag**, completely decoupling *visibility* from *lifecycle state*.
 
-- **Cleaner defaults** – low-level helpers like `AddParameter` and `AddConnectionString` mark themselves hidden so they don't clutter the UI:
+- **Cleaner defaults** – low-level helpers like <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> and <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddConnectionString" /> mark themselves hidden so they don't clutter the UI:
 
   ```csharp
   var apiKey = builder.AddParameter("api-key", secret: true);   // IsHidden = true ✔
@@ -202,7 +203,7 @@ The `.WithReference(...)` calls automatically ensure that the proxy container ca
 
 ### 🐬 MySQL `AddDatabase` now creates the database
 
-In Aspire 9.3, the MySQL integration now supports **automatic database creation** via the `AddDatabase` API—matching the behavior already available for SQL Server and PostgreSQL.
+In Aspire 9.3, the MySQL integration now supports **automatic database creation** via the <ApiReference name="Aspire.Hosting.AzureSqlExtensions.AddDatabase" /> API—matching the behavior already available for SQL Server and PostgreSQL.
 
 Previously, calling `.AddDatabase("dbname")` on a MySQL resource only created a logical reference in Aspire's app model—it did **not** create the database on the server. This mismatch caused confusion, especially when users expected Aspire to provision the database like it does for other integrations.
 
@@ -345,7 +346,7 @@ In this case, Aspire applies the correct publishing behavior to all compute reso
 
 If you add **multiple compute environments**, Aspire needs to know which resource goes where. Compute environments apply their transformations to **all applicable compute resources** (projects, containers, executables). If more than one environment matches a given resource, Aspire throws an **ambiguous environment exception** at publish time.
 
-You can resolve this by using `WithComputeEnvironment(...)`:
+You can resolve this by using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" />:
 
 ```csharp
 var k8s = builder.AddKubernetesEnvironment("k8s-env");
@@ -370,10 +371,10 @@ This (contrived) example shows how you could explicitly map services to differen
 
 Aspire 9.3 has preview support for the following environment resources:
 
-- `AddDockerComposeEnvironment(...)`
-- `AddKubernetesEnvironment(...)`
-- `AddAzureContainerAppEnvironment(...)`
-- `AddAzureAppServiceEnvironment(...)` — [see new App Service support →](#-azure-app-service-preview-support)
+- <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.AddDockerComposeEnvironment" />
+- <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.AddKubernetesEnvironment" />
+- <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />
+- <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.AddAzureAppServiceEnvironment" /> — [see new App Service support →](#-azure-app-service-preview-support)
 
 These represent deployment targets that can transform and emit infrastructure-specific artifacts from your app model.
 
@@ -385,8 +386,8 @@ Aspire 9.3 introduces powerful new capabilities for customizing Docker Compose o
 
 You can now programmatically configure the top-level Compose file and the behavior of each individual service using two new APIs:
 
-- `ConfigureComposeFile(...)` — customize the `docker-compose.yml` metadata
-- `PublishAsDockerComposeService(...)` — modify the generated service for any compute resource (like a container or project)
+- <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureComposeFile" /> — customize the `docker-compose.yml` metadata
+- <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.PublishAsDockerComposeService" /> — modify the generated service for any compute resource (like a container or project)
 
 ```csharp
 builder.AddDockerComposeEnvironment("env")
@@ -450,7 +451,7 @@ Like Docker Compose, Aspire now supports both **global environment-level setting
 You can use the following APIs to configure Kubernetes output in C#:
 
 - `WithProperties(...)` on the compute environment to set global behaviors
-- `PublishAsKubernetesService(...)` on compute resources to modify their specific Kubernetes resources
+- <ApiReference name="Aspire.Hosting.KubernetesServiceExtensions.PublishAsKubernetesService" /> on compute resources to modify their specific Kubernetes resources
 
 ```csharp
 builder.AddKubernetesEnvironment("env")
@@ -524,7 +525,7 @@ This integration lets you deploy your project as a **containerized Linux Web App
 
 This first release is scoped to the most common use cases:
 
-- Supports **.NET projects only** (via `AddProject(...)`)
+- Supports **.NET projects only** (via <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />)
 - Each project must expose a **single public HTTP endpoint**
 - **Projects are published as containers** to Azure Container Registry
 - **Containers within the AppHost** are not supported
@@ -554,13 +555,13 @@ In this example:
 - Your project is built as a container and published to **Azure Container Registry**
 - The container is deployed to App Service with the configuration you provide
 
-> 🧠 Use `PublishAsAzureAppServiceWebsite(...)` to customize settings like site config, authentication, or SKU.
+> 🧠 Use <ApiReference name="Aspire.Hosting.AzureAppServiceComputeResourceExtensions.PublishAsAzureAppServiceWebsite" /> to customize settings like site config, authentication, or SKU.
 
 💬 This feature is in **preview**—we're looking for your feedback as we expand support!
 
 ### 📤 Use an existing Azure Container Registry (ACR)
 
-Aspire 9.3 adds support for modeling an existing **Azure Container Registry (ACR)** using the new `AddAzureContainerRegistry(...)` API. This enables you to **push images to an ACR you already manage**—without Aspire provisioning a new one.
+Aspire 9.3 adds support for modeling an existing **Azure Container Registry (ACR)** using the new <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.AddAzureContainerRegistry" /> API. This enables you to **push images to an ACR you already manage**—without Aspire provisioning a new one.
 
 This is ideal for teams that:
 
@@ -696,7 +697,7 @@ builder.AddContainer("myContainer", "nginx")
 
 #### 🧩 Reference secrets from existing Key Vaults
 
-You can also use this with **existing Azure Key Vaults** by marking the resource with `AsExisting(...)`, `RunAsExisting(...)`, or `PublishAsExisting(...)`. This lets you consume secrets from **already-provisioned vaults**—perfect for shared environments or team-managed infrastructure.
+You can also use this with **existing Azure Key Vaults** by marking the resource with <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.AsExisting" />, <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.RunAsExisting" />, or <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" />. This lets you consume secrets from **already-provisioned vaults**—perfect for shared environments or team-managed infrastructure.
 
 ```csharp
 var keyVaultNameParam = builder.AddParameter("key-vault-name");
@@ -860,7 +861,7 @@ sql.AddDatabase("appdb")
    .WithDefaultAzureSku(); // Uses the previous (General Purpose) default
 ```
 
-If you want to specify what SKU to use, you the `ConfigureInfrastructure` method as explained here: [Setting a specific SKU](https://github.com/microsoft/aspire/tree/main/src/Aspire.Hosting.Azure.Sql#setting-a-specific-sku).
+If you want to specify what SKU to use, you the <ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> method as explained here: [Setting a specific SKU](https://github.com/microsoft/aspire/tree/main/src/Aspire.Hosting.Azure.Sql#setting-a-specific-sku).
 
 #### ⚠️ Breaking change
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-4.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-4.mdx
index 0cf316b02d..d14204afa4 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-4.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-4.mdx
@@ -17,6 +17,7 @@ import dashboardUpdateNotification from '@assets/whats-new/aspire-9.4/dashboard-
 import dashboardConnectionStrings from '@assets/whats-new/aspire-9.4/dashboard-connection-strings.png';
 import dashboardTracingPeers from '@assets/whats-new/aspire-9.4/dashboard-tracing-peers.png';
 import dashboardConsoleLogsWrapping from '@assets/whats-new/aspire-9.4/dashboard-console-logs-wrapping.gif';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.4 is the next minor version release of Aspire. It supports:
 
@@ -123,7 +124,7 @@ The `aspire deploy` command introduced extensible deployment workflows, enabling
 
 **Key capabilities:**
 
-- **Custom deployment steps** using `WithPipelineStepFactory` to execute custom logic during the `aspire deploy` command
+- **Custom deployment steps** using <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" /> to execute custom logic during the `aspire deploy` command
 - **Workflow activity reporting** through tasks created from `PipelineStepContext.ReportingStep`, with prompts provided by `IInteractionService`
 - **Pipeline ordering and dependencies** using `dependsOn`, `requiredBy`, and well-known pipeline steps
 
@@ -790,7 +791,7 @@ The [YARP integration](https://aspire.dev/integrations/reverse-proxies/yarp/) is
 
 Building sophisticated reverse proxy configurations has traditionally required deep knowledge of YARP's transform system and manual JSON configuration. Aspire 9.4 introduces a comprehensive set of fluent APIs that make advanced routing transformations accessible through strongly-typed C# code.
 
-**Breaking change in 9.4:** The `WithConfigFile()` method has been removed and replaced with a code-based configuration model. This new approach works seamlessly with deployment scenarios as the strongly-typed configuration methods translate directly into the appropriate environment variables.
+**Breaking change in 9.4:** The <ApiReference name="Aspire.Hosting.FlociHostingExtension.WithConfigFile" /> method has been removed and replaced with a code-based configuration model. This new approach works seamlessly with deployment scenarios as the strongly-typed configuration methods translate directly into the appropriate environment variables.
 
 You can now programmatically configure request/response transformations, header manipulation, path rewriting, and query string handling directly from your app model—no more wrestling with complex configuration files.
 
@@ -1078,7 +1079,7 @@ builder.Build().Run();
 
 <Aside type="note">
   These Aspire 9.4 examples intentionally use `AddAzureAIFoundry`, the hosting
-  API available in that release. Aspire 13.2 renamed it to `AddFoundry`; see the
+  API available in that release. Aspire 13.2 renamed it to <ApiReference name="Aspire.Hosting.FoundryExtensions.AddFoundry" />; see the
   [Foundry package and namespace
   transition](/whats-new/aspire-13-2/#foundry-package-and-namespace-transition).
 </Aside>
@@ -1133,7 +1134,7 @@ builder.AddOpenAIClient("chat")
 - **Azure AI Foundry** - Cloud-hosted models with enterprise-grade scaling, supports all Azure AI model deployments
 - **Foundry Local** - On-device inference with different model selection optimized for local hardware, no Azure subscription required
 
-The `RunAsFoundryLocal()` method enables local development scenarios using [Azure AI Foundry Local](https://learn.microsoft.com/azure/ai-foundry/foundry-local/), allowing you to test AI capabilities without requiring cloud resources during development. This supports automatic model downloading, loading, and management through the integrated Foundry Local runtime.
+The <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> method enables local development scenarios using [Azure AI Foundry Local](https://learn.microsoft.com/azure/ai-foundry/foundry-local/), allowing you to test AI capabilities without requiring cloud resources during development. This supports automatic model downloading, loading, and management through the integrated Foundry Local runtime.
 
 ### 🗄️ Database hosting improvements
 
@@ -1319,7 +1320,7 @@ var webApi = builder.AddProject<Projects.WebAPI>("webapi")
 
 - `Aspire.Hosting.AzureKeyVaultResourceExtensions.AddSecret*` method for adding new secrets to Key Vault from parameters or expressions
 - `Aspire.Hosting.Azure.AzureKeyVaultResource.GetSecret*` method for referencing existing secrets in Key Vault
-- **Strongly-typed secret references** that can be used with `WithEnvironment()` for environment variables
+- **Strongly-typed secret references** that can be used with <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> for environment variables
 - **Custom secret naming** support with optional `secretName` parameter
 
 #### 📥Resource Deep Linking for Azure Storage Queues
@@ -1558,7 +1559,7 @@ builder.AddProject<Projects.Api>("api")
        .WithEnvironment("API_KEY", secretRef);  // Using IAzureKeyVaultSecretReference
 ```
 
-**Migration impact**: Replace `GetSecretOutput()` and `BicepSecretOutputReference` usage with the new `GetSecret()` method that returns `IAzureKeyVaultSecretReference`.
+**Migration impact**: Replace `GetSecretOutput()` and `BicepSecretOutputReference` usage with the new <ApiReference name="Aspire.Hosting.AzureKeyVaultResourceExtensions.GetSecret" /> method that returns `IAzureKeyVaultSecretReference`.
 
 ### 📦 Azure Storage blob container creation changes
 
@@ -1575,11 +1576,11 @@ var storage = builder.AddAzureStorage("storage");
 var container = storage.AddBlobContainer("images");   // Direct on storage resource
 ```
 
-**Migration impact**: Use `AddBlobContainer()` directly on `AzureStorageResource` instead of on specialized blob storage resources.
+**Migration impact**: Use <ApiReference name="Aspire.Hosting.AzureStorageExtensions.AddBlobContainer" /> directly on `AzureStorageResource` instead of on specialized blob storage resources.
 
 ### 🔐 Keycloak realm import simplification
 
-The `WithRealmImport` method signature has been **simplified by removing the confusing `isReadOnly` parameter**:
+The <ApiReference name="Aspire.Hosting.KeycloakResourceBuilderExtensions.WithRealmImport" /> method signature has been **simplified by removing the confusing `isReadOnly` parameter**:
 
 ```csharp
 // ❌ Before (deprecated):
@@ -1611,7 +1612,7 @@ var milvus = builder.AddMilvus("milvus")
     .WithConfigurationFile("./milvus.yaml");  // Method renamed for clarity
 ```
 
-**Migration impact**: Update method calls to use `WithConfigurationFile` instead of `WithConfigurationBindMount` for Milvus configuration.
+**Migration impact**: Update method calls to use <ApiReference name="Aspire.Hosting.MilvusBuilderExtensions.WithConfigurationFile" /> instead of `WithConfigurationBindMount` for Milvus configuration.
 
 ### 🔄 Azure Storage client registration updates
 
@@ -1702,7 +1703,7 @@ var api = builder.AddProject<Projects.Api>("api")
     });
 ```
 
-**Migration impact**: Replace usage of `AfterEndpointsAllocatedEvent` with resource-specific lifecycle events like `OnBeforeResourceStarted` or `OnResourceEndpointsAllocated` for better type safety and clarity.
+**Migration impact**: Replace usage of `AfterEndpointsAllocatedEvent` with resource-specific lifecycle events like <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnBeforeResourceStarted" /> or <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceEndpointsAllocated" /> for better type safety and clarity.
 
 ### 🧊 Azure Container Apps hybrid mode removal
 
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
index 09597c8f1f..a9deb34fe4 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-5.mdx
@@ -17,6 +17,7 @@ import dashboardTraceType from '@assets/whats-new/aspire-9.5/dashboard-trace-typ
 import aspireUpdate from '@assets/whats-new/aspire-9.5/aspire-update.gif';
 import dashboardRichPropertyGrid from '@assets/whats-new/aspire-9.5/dashboard-rich-property-grid.png';
 import dashboardContainerWarning from '@assets/whats-new/aspire-9.5/dashboard-container-warning.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.5 is the next minor version release of Aspire. It supports:
 
@@ -226,7 +227,7 @@ A new "All" option in the console logs view streams logs from every running reso
 
 ### Custom resource icons
 
-Resources can now specify custom icons and their variant (Filled, which is the default, or Regular) using `WithIconName()` for better visual identification in dashboard views. Any [Fluent UI system icons](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) can be used.
+Resources can now specify custom icons and their variant (Filled, which is the default, or Regular) using <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithIconName" /> for better visual identification in dashboard views. Any [Fluent UI system icons](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) can be used.
 
 ```csharp
 var postgres = builder.AddPostgres("database")
@@ -295,11 +296,11 @@ The trace detail page includes several quality-of-life improvements:
 
 ### OpenAI hosting integration
 
-The new `AddOpenAI` integration provides first-class support for modeling OpenAI endpoints and their associated models within your Aspire application model. For more information, see [Aspire OpenAI integration (Preview)](https://aspire.dev/integrations/ai/openai/openai-get-started/).
+The new <ApiReference name="Aspire.Hosting.OpenAIExtensions.AddOpenAI" /> integration provides first-class support for modeling OpenAI endpoints and their associated models within your Aspire application model. For more information, see [Aspire OpenAI integration (Preview)](https://aspire.dev/integrations/ai/openai/openai-get-started/).
 
 **Features:**
 
-- **Single OpenAI endpoint** resource with child model resources using `AddModel`.
+- **Single OpenAI endpoint** resource with child model resources using <ApiReference name="Aspire.Hosting.OpenAIExtensions.AddModel" />.
 - **Resource referencing** so other projects automatically receive connection information.
 
 ```csharp
@@ -579,7 +580,7 @@ You can use this container **with or without Aspire**—it's just a normal conta
 - Local development parity for Azure App Configuration scenarios.
 - Built-in browser UI for CRUD (create, read, update, delete) of configuration entries.
 - Persistent data via a mounted volume (optional).
-- Seamless integration with other Aspire resources via `WithReference`.
+- Seamless integration with other Aspire resources via <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />.
 - Supports inner-loop testing without network latency or secrets in Azure.
 
 **Add emulator via Aspire:**
@@ -665,7 +666,7 @@ builder.Build().Run();
 
 Aspire 9.5 introduces new resource lifecycle event APIs that allow you to register callbacks for when resources stop, providing better control over cleanup and coordination during application shutdown.
 
-The new `OnResourceStopped` extension method allows you to register callbacks that execute when a resource enters the stopped state:
+The new <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceStopped" /> extension method allows you to register callbacks that execute when a resource enters the stopped state:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -706,7 +707,7 @@ var redis = builder.AddRedis("cache")
 
 ### Context-based endpoint resolution
 
-**Breaking change**: Endpoint resolution in `WithEnvironment` callbacks now correctly resolves container hostnames instead of always using "localhost."
+**Breaking change**: Endpoint resolution in <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> callbacks now correctly resolves container hostnames instead of always using "localhost."
 
 ```csharp
 var redis = builder.AddRedis("redis");
@@ -807,13 +808,13 @@ This feature enhances deployment reliability by providing fine-grained health mo
 
 ### Enhanced resource waiting patterns
 
-New `WaitForStart` method provides granular control over startup ordering, complementing existing `WaitFor` semantics. It also pairs with improved `ExternalService` health honoring which ensures dependents truly wait for external resources to be healthy.
+New <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForStart" /> method provides granular control over startup ordering, complementing existing <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> semantics. It also pairs with improved `ExternalService` health honoring which ensures dependents truly wait for external resources to be healthy.
 
 **Understanding wait behaviors:**
 
 - **`WaitFor`**: Waits for dependency to be Running AND pass all health checks.
 - **`WaitForStart`**: Waits only for dependency to reach Running (ignores health checks).
-- **`WaitForCompletion`**: Waits for dependency to reach a terminal state.
+- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" />**: Waits for dependency to reach a terminal state.
 
 ```csharp
 var postgres = builder.AddPostgres("postgres");
@@ -890,7 +891,7 @@ Container App Jobs complement the existing Container Apps functionality by provi
 
 #### Publishing resources as Container App Jobs
 
-Use the new `PublishAsAzureContainerAppJob` extension method to publish resources as jobs:
+Use the new <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsAzureContainerAppJob" /> extension method to publish resources as jobs:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -902,7 +903,7 @@ var dataProcessor = builder.AddProject<Projects.DataProcessor>("data-processor")
 builder.Build().Run();
 ```
 
-Or use the `PublishAsScheduledAzureContainerAppJob` extension method to publish a resource as a job that runs on a schedule:
+Or use the <ApiReference name="Aspire.Hosting.ContainerAppExtensions.PublishAsScheduledAzureContainerAppJob" /> extension method to publish a resource as a job that runs on a schedule:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -1014,7 +1015,7 @@ The `InteractionInputCollection` provides indexed access by name and improved ty
 
 ### Docker Compose Aspire Dashboard forwarding headers
 
-`AddDockerComposeEnvironment(...).WithDashboard()` gained `WithForwardedHeaders()` to enable forwarded `Host` and `Proto` handling for dashboard scenarios behind reverse proxies or compose networks. This mirrors the standalone dashboard forwarded header support and fixes auth redirect edge cases.
+`AddDockerComposeEnvironment(...).WithDashboard()` gained <ApiReference name="Aspire.Hosting.DockerComposeAspireDashboardResourceBuilderExtensions.WithForwardedHeaders" /> to enable forwarded `Host` and `Proto` handling for dashboard scenarios behind reverse proxies or compose networks. This mirrors the standalone dashboard forwarded header support and fixes auth redirect edge cases.
 
 ```csharp
 builder.AddDockerComposeEnvironment("env")
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9.mdx b/src/frontend/src/content/docs/whats-new/aspire-9.mdx
index ef47bd9279..4ef44c1f5d 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9.mdx
@@ -21,6 +21,7 @@ import redisInsight from '@assets/whats-new/aspire-9/redis-insight.png';
 import functionsStep1 from '@assets/whats-new/aspire-9/functions-step-1.gif';
 import functionsDashboardScreenshot from '@assets/whats-new/aspire-9/functions-dashboard-screenshot.png';
 import functionsDebugScreenshot from '@assets/whats-new/aspire-9/functions-debug-screenshot.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 9.0 is the next major general availability (GA) release of Aspire; it supports _both_:
 
@@ -136,8 +137,8 @@ When the AppHost starts, it waits for the `rabbit` resource to be ready before s
 
 There are two methods exposed to wait for a resource:
 
-- `WaitFor`: Wait for a resource to be ready before starting another resource.
-- `WaitForCompletion`: Wait for a resource to complete before starting another resource.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" />: Wait for a resource to be ready before starting another resource.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitForCompletion" />: Wait for a resource to complete before starting another resource.
 
 For more information, see [Aspire AppHost: Waiting for resources](/get-started/app-host/#adding-an-api-resource-and-declaring-a-dependency).
 
@@ -211,7 +212,7 @@ This is useful when you want to keep the container running even after the AppHos
 To delete these containers, you must manually stop them using the container runtime.
 </Aside>
 
-To define an `IResourceBuilder<ContainerResource>` with a persistent lifetime, call the `WithLifetime` method and pass in persistent container lifetime:
+To define an `IResourceBuilder<ContainerResource>` with a persistent lifetime, call the <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> method and pass in persistent container lifetime:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -289,7 +290,7 @@ builder.AddRedis("redis")
                             // Redis instance.
 ```
 
-The `WithRedisInsight` extension method can be applied to multiple Redis resources and they'll each be visible on the Redis Insight dashboard.
+The <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.WithRedisInsight" /> extension method can be applied to multiple Redis resources and they'll each be visible on the Redis Insight dashboard.
 
 <Image src={redisInsight} alt="Redis Insight dashboard showing multiple Redis instances" />
 
@@ -313,7 +314,7 @@ Read [Azure-agnostic client resolution](https://github.com/microsoft/aspire/blob
 
 ### MongoDB
 
-Added support for specifying the MongoDB username and password when using the `AddMongoDB` extension method. If not specified, a random username and password is generated but can be manually specified using parameter resources.
+Added support for specifying the MongoDB username and password when using the <ApiReference name="Aspire.Hosting.MongoDBBuilderExtensions.AddMongoDB" /> extension method. If not specified, a random username and password is generated but can be manually specified using parameter resources.
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);
@@ -420,7 +421,7 @@ In the AppHost project, observe that there's a `PackageReference` to the new [
 </ItemGroup>
 ```
 
-This package provides an `AddAzureFunctionsProject` API that can be invoked in the AppHost to configure Azure Functions projects within an Aspire host:
+This package provides an <ApiReference name="Aspire.Hosting.AzureFunctionsProjectResourceExtensions.AddAzureFunctionsProject" /> API that can be invoked in the AppHost to configure Azure Functions projects within an Aspire host:
 
 ```csharp
 var builder = DistributedApplication.CreateBuilder(args);

From 46ab1821d1aae9f65d7a595773e54e759be0e79f Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Thu, 8 Oct 2026 16:02:12 +0100
Subject: [PATCH 2/9] Propagated the ApiReference Astro component to translated
 pages.

---
 .../ja/app-host/certificate-configuration.mdx | 11 ++---
 .../docs/ja/app-host/container-files.mdx      |  9 ++--
 .../docs/ja/app-host/container-registry.mdx   |  5 ++-
 .../src/content/docs/ja/app-host/eventing.mdx | 13 +++---
 .../docs/ja/app-host/executable-resources.mdx |  9 ++--
 .../app-host/migrate-from-docker-compose.mdx  | 21 ++++-----
 .../docs/ja/app-host/resource-lifetimes.mdx   |  5 ++-
 .../docs/ja/app-host/withdockerfile.mdx       |  9 ++--
 .../multi-language-architecture.mdx           |  5 ++-
 .../ja/architecture/resource-api-patterns.mdx |  3 +-
 .../ja/architecture/resource-examples.mdx     |  4 +-
 .../ja/architecture/resource-hierarchies.mdx  |  7 +--
 .../ja/architecture/resource-publishing.mdx   |  3 +-
 .../content/docs/ja/deployment/pipelines.mdx  |  9 ++--
 .../ja/extensibility/custom-resources.mdx     |  5 ++-
 .../ja/extensibility/interaction-service.mdx  |  3 +-
 .../multi-language-integration-authoring.mdx  |  3 +-
 .../fundamentals/custom-resource-commands.mdx |  3 +-
 .../ja/fundamentals/custom-resource-urls.mdx  | 11 ++---
 .../ja/fundamentals/external-parameters.mdx   | 13 +++---
 .../docs/ja/fundamentals/health-checks.mdx    |  7 +--
 .../docs/ja/fundamentals/http-commands.mdx    |  3 +-
 .../ja/fundamentals/networking-overview.mdx   |  9 ++--
 .../ja/fundamentals/persist-data-volumes.mdx  | 13 +++---
 .../ja/fundamentals/service-discovery.mdx     |  5 ++-
 .../get-started/add-aspire-existing-app.mdx   |  9 ++--
 .../docs/ja/get-started/aspire-mcp-server.mdx |  3 +-
 .../get-started/aspire-vscode-extension.mdx   |  3 +-
 .../docs/ja/get-started/deploy-first-app.mdx  |  9 ++--
 .../src/content/docs/ja/get-started/faq.mdx   |  6 ++-
 .../content/docs/ja/get-started/first-app.mdx | 17 ++++----
 .../ja/get-started/resource-mcp-servers.mdx   |  5 ++-
 .../docs/ja/get-started/troubleshooting.mdx   |  5 ++-
 .../integrations/dotnet/launch-profiles.mdx   |  7 +--
 .../docs/ja/testing/accessing-resources.mdx   |  3 +-
 .../docs/ja/testing/write-your-first-test.mdx |  3 +-
 .../content/docs/ja/whats-new/aspire-13-1.mdx | 11 ++---
 .../content/docs/ja/whats-new/aspire-13-2.mdx | 33 +++++++-------
 .../content/docs/ja/whats-new/aspire-13-3.mdx | 33 +++++++-------
 .../content/docs/ja/whats-new/aspire-13.mdx   | 43 ++++++++++---------
 40 files changed, 210 insertions(+), 168 deletions(-)

diff --git a/src/frontend/src/content/docs/ja/app-host/certificate-configuration.mdx b/src/frontend/src/content/docs/ja/app-host/certificate-configuration.mdx
index 78ad4d1e59..ca9f144c45 100644
--- a/src/frontend/src/content/docs/ja/app-host/certificate-configuration.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/certificate-configuration.mdx
@@ -4,13 +4,14 @@ description: Aspire でリソースの HTTPS エンドポイントと証明書
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire は、2 つの補完的な証明書 API セットを提供します:
 
 1. **HTTPS エンドポイント API**: リソースが自身の HTTPS エンドポイントで使用する証明書を設定します（サーバー認証）
 2. **証明書信頼 API**: リソースが送信 HTTPS 接続を行う際に信頼する証明書を設定します（クライアント認証）
 
-これらの API セットはともに動作し、ローカル開発中に安全な HTTPS 通信を実現します。たとえば、Vite フロントエンドは `WithHttpsDeveloperCertificate` を使用して HTTPS トラフィックを提供しながら、`WithDeveloperCertificateTrust` を使用してダッシュボードの <abbr title="OpenTelemetry Protocol" data-tooltip-placement="top">OTLP</abbr> エンドポイント証明書を信頼することもできます。
+これらの API セットはともに動作し、ローカル開発中に安全な HTTPS 通信を実現します。たとえば、Vite フロントエンドは <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsDeveloperCertificate" /> を使用して HTTPS トラフィックを提供しながら、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithDeveloperCertificateTrust" /> を使用してダッシュボードの <abbr title="OpenTelemetry Protocol" data-tooltip-placement="top">OTLP</abbr> エンドポイント証明書を信頼することもできます。
 
 <Aside type="caution">
   証明書のカスタマイズは実行時にのみ適用されます。カスタム証明書は
@@ -109,7 +110,7 @@ HTTPS エンドポイントの設定は、リソースが HTTPS トラフィッ
 
 ### デフォルトの動作
 
-`WithHttpsCertificateConfiguration` で証明書設定が定義されているリソースの場合、Aspire は利用可能であれば開発証明書を使用するように設定しようとします。この自動設定は、YARP、Redis、Keycloak コンテナ、Vite ベースの JavaScript アプリ、Uvicorn を使用する Python アプリなど、多くの一般的なリソースタイプで機能します。
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsCertificateConfiguration" /> で証明書設定が定義されているリソースの場合、Aspire は利用可能であれば開発証明書を使用するように設定しようとします。この自動設定は、YARP、Redis、Keycloak コンテナ、Vite ベースの JavaScript アプリ、Uvicorn を使用する Python アプリなど、多くの一般的なリソースタイプで機能します。
 
 この動作は、以下で説明する HTTPS エンドポイント API を使用して制御できます。
 
@@ -249,7 +250,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithoutHttpsCertificate` を使用するケース:
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithoutHttpsCertificate" /> を使用するケース:
 
 - リソースが HTTPS をサポートしていない場合
 - 手動で証明書を設定したい場合
@@ -424,7 +425,7 @@ builder.Build().Run();
 
 証明書信頼スコープは、カスタム証明書がリソースのデフォルト信頼証明書とどのように連携するかを制御します。スコープごとに異なる設定により、アプリケーションの要件に応じた証明書信頼の管理が柔軟に行えます。
 
-`WithCertificateTrustScope` API は、信頼動作を指定する `CertificateTrustScope` 値を受け取ります。
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCertificateTrustScope" /> API は、信頼動作を指定する `CertificateTrustScope` 値を受け取ります。
 
 #### 利用可能な信頼スコープ
 
@@ -605,7 +606,7 @@ Node.js、Python、コンテナリソース用のデフォルト実装が提供
 
 #### コンテナ証明書パスを設定する
 
-コンテナリソースでは、`WithContainerCertificatePaths` を使用して証明書の保存場所とアクセス場所をカスタマイズできます:
+コンテナリソースでは、<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerCertificatePaths" /> を使用して証明書の保存場所とアクセス場所をカスタマイズできます:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/ja/app-host/container-files.mdx b/src/frontend/src/content/docs/ja/app-host/container-files.mdx
index cf7cba8796..28729a2af9 100644
--- a/src/frontend/src/content/docs/ja/app-host/container-files.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/container-files.mdx
@@ -4,11 +4,12 @@ description: Aspire のコンテナー ファイル API を使用して、開発
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire には、ファイルやディレクトリをコンテナーへ挿入する API が用意されており、カスタムの構成ファイル、スクリプト、証明書、その他のアセットを使用してコンテナー化されたリソースを構成できます。相補的な API が 2 つあります:
 
-- **`WithContainerFiles`**: `aspire run` 実行時に、コンテナーの起動時点で開発用のファイルをコンテナーへ挿入します。
-- **`PublishWithContainerFiles`**: `aspire publish` 実行時に、発行用のビルド成果物として、あるリソースのコンテナーから別のリソースのコンテナーへファイルをコピーします。
+- **<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerFiles" />**: `aspire run` 実行時に、コンテナーの起動時点で開発用のファイルをコンテナーへ挿入します。
+- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" />**: `aspire publish` 実行時に、発行用のビルド成果物として、あるリソースのコンテナーから別のリソースのコンテナーへファイルをコピーします。
 
 ## 開発時にファイルを挿入する
 
@@ -416,7 +417,7 @@ await builder.build().run();
 
 ### ソース パスをカスタマイズする
 
-既定では、ソース リソースは構成済みの出力パスに基づいて、自身のコンテナーからファイルをエクスポートします。ソース コンテナー内のどのパスからコピーするかを指定するには、`WithContainerFilesSource` を使用します:
+既定では、ソース リソースは構成済みの出力パスに基づいて、自身のコンテナーからファイルをエクスポートします。ソース コンテナー内のどのパスからコピーするかを指定するには、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithContainerFilesSource" /> を使用します:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -435,7 +436,7 @@ var api = builder.AddProject<Projects.Api>("api")
 </TabItem>
 </Tabs>
 
-以前に構成したソース パスを削除してから新しいものを追加するには、`ClearContainerFilesSources` を使用します。
+以前に構成したソース パスを削除してから新しいものを追加するには、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ClearContainerFilesSources" /> を使用します。
 
 ## 関連項目
 
diff --git a/src/frontend/src/content/docs/ja/app-host/container-registry.mdx b/src/frontend/src/content/docs/ja/app-host/container-registry.mdx
index cd48d2ebeb..ee2fbd2248 100644
--- a/src/frontend/src/content/docs/ja/app-host/container-registry.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/container-registry.mdx
@@ -5,6 +5,7 @@ description: Aspire アプリケーションのコンテナーレジストリを
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.1 では明示的なコンテナーレジストリ設定が導入され、デプロイ時にコンテナーイメージをどこへいつプッシュするかを開発者が制御できるようになりました。この記事では、Aspire アプリケーションのコンテナーレジストリを設定する方法について説明します。
 
@@ -23,7 +24,7 @@ Aspire アプリケーションを本番環境にデプロイする際、コン
   この API は試験的であり、将来のリリースで変更される可能性があります。試験的な警告を抑制するには、診断コード `ASPIRECOMPUTE003` を使用してください。詳細については、[ASPIRECOMPUTE003](/ja/diagnostics/aspirecompute003/) を参照してください。
 </Aside>
 
-`AddContainerRegistry` メソッドを使用して、アプリケーションの汎用コンテナーレジストリを設定します。DockerHub、GitHub Container Registry、Harbor、プライベートレジストリなど、あらゆる Docker 互換レジストリで使用できます。
+<ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.AddContainerRegistry" /> メソッドを使用して、アプリケーションの汎用コンテナーレジストリを設定します。DockerHub、GitHub Container Registry、Harbor、プライベートレジストリなど、あらゆる Docker 互換レジストリで使用できます。
 
 ### 基本的な使い方
 
@@ -302,7 +303,7 @@ await builder.build().run();
 
 ### 既存の ACR を使用する
 
-既存の Azure Container Registry を使用するには、ACR を追加する際に `PublishAsExisting` メソッドを呼び出します:
+既存の Azure Container Registry を使用するには、ACR を追加する際に <ApiReference name="Aspire.Hosting.ExistingAzureResourceExtensions.PublishAsExisting" /> メソッドを呼び出します:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/ja/app-host/eventing.mdx b/src/frontend/src/content/docs/ja/app-host/eventing.mdx
index b6d26249dc..356eea775a 100644
--- a/src/frontend/src/content/docs/ja/app-host/eventing.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/eventing.mdx
@@ -5,6 +5,7 @@ description: ライフサイクルイベント、カスタムイベントの発
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire のイベント機能を使うと、様々な AppHost ライフサイクルでイベントを発行・購読できます。イベント機能はライフサイクルイベントより柔軟性が高く、どちらもイベントコールバック内で任意のコードを実行できますが、イベント機能はイベントのタイミング、発行、カスタムイベントのサポートをより細かく制御できます。
 
@@ -206,13 +207,13 @@ builder.AddProject<Projects.AspireApp_Web>("webfrontend")
 builder.Build().Run();
 ```
 
-上記のコードは、`cache` リソースの `InitializeResourceEvent`、`ResourceReadyEvent`、`ResourceEndpointsAllocatedEvent`、`ConnectionStringAvailableEvent`、`BeforeResourceStartedEvent` イベントを購読しています。`AddRedis` を呼び出すと、`T` が `RedisResource` である `IResourceBuilder<T>` が返されます。`On*` メソッドを呼び出してイベントを購読します。`On*` メソッドは同じ `IResourceBuilder<T>` インスタンスを返すため、複数の呼び出しをチェーンできます:
+上記のコードは、`cache` リソースの `InitializeResourceEvent`、`ResourceReadyEvent`、`ResourceEndpointsAllocatedEvent`、`ConnectionStringAvailableEvent`、`BeforeResourceStartedEvent` イベントを購読しています。<ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> を呼び出すと、`T` が `RedisResource` である `IResourceBuilder<T>` が返されます。`On*` メソッドを呼び出してイベントを購読します。`On*` メソッドは同じ `IResourceBuilder<T>` インスタンスを返すため、複数の呼び出しをチェーンできます:
 
-- `OnInitializeResource`: `InitializeResourceEvent` を購読します。
-- `OnResourceEndpointsAllocated`: `ResourceEndpointsAllocatedEvent` イベントを購読します。
-- `OnConnectionStringAvailable`: `ConnectionStringAvailableEvent` イベントを購読します。
-- `OnBeforeResourceStarted`: `BeforeResourceStartedEvent` イベントを購読します。
-- `OnResourceReady`: `ResourceReadyEvent` イベントを購読します。
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnInitializeResource" />: `InitializeResourceEvent` を購読します。
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceEndpointsAllocated" />: `ResourceEndpointsAllocatedEvent` イベントを購読します。
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnConnectionStringAvailable" />: `ConnectionStringAvailableEvent` イベントを購読します。
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnBeforeResourceStarted" />: `BeforeResourceStartedEvent` イベントを購読します。
+- <ApiReference name="Aspire.Hosting.DistributedApplicationEventingExtensions.OnResourceReady" />: `ResourceReadyEvent` イベントを購読します。
 
 AppHost を実行すると、Aspire ダッシュボードが表示される頃までに、コンソールに次のログ出力が表示されるはずです:
 
diff --git a/src/frontend/src/content/docs/ja/app-host/executable-resources.mdx b/src/frontend/src/content/docs/ja/app-host/executable-resources.mdx
index 8d878dd087..dbc6cce503 100644
--- a/src/frontend/src/content/docs/ja/app-host/executable-resources.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/executable-resources.mdx
@@ -4,8 +4,9 @@ description: AddExecutable を使用して Aspire AppHost で外部の実行可
 ---
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
-Aspire では、`AddExecutable` メソッドを使用して、プロジェクトと一緒に外部の実行可能アプリケーションをホストできます。この機能は、Node.js アプリケーション、Python スクリプト、特殊な CLI ツールなどの実行可能アプリケーションやツールを分散アプリケーションに統合する必要がある場合に役立ちます。
+Aspire では、<ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.AddExecutable" /> メソッドを使用して、プロジェクトと一緒に外部の実行可能アプリケーションをホストできます。この機能は、Node.js アプリケーション、Python スクリプト、特殊な CLI ツールなどの実行可能アプリケーションやツールを分散アプリケーションに統合する必要がある場合に役立ちます。
 
 ## 実行可能リソースを使用する場合
 
@@ -122,7 +123,7 @@ const app = await builder.addExecutable("worker", "python", ".", ["worker.py"])
 </TabItem>
 </Tabs>
 
-1 つのリソースが別のリソースに依存している場合、`WithReference` は依存先リソースの接続詳細を含む環境変数を渡します。たとえば、`worker` 実行可能ファイルが `redis` と `postgres` を参照すると、これらのリソースへの接続文字列を含む `ConnectionStrings__cache` および `ConnectionStrings__appdb` 環境変数が提供されます。
+1 つのリソースが別のリソースに依存している場合、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> は依存先リソースの接続詳細を含む環境変数を渡します。たとえば、`worker` 実行可能ファイルが `redis` と `postgres` を参照すると、これらのリソースへの接続文字列を含む `ConnectionStrings__cache` および `ConnectionStrings__appdb` 環境変数が提供されます。
 
 ### 特定のエンドポイント情報にアクセスする
 
@@ -276,7 +277,7 @@ const app = await builder.addExecutable("api", "uvicorn", ".", ["main:app", "--r
 
 ## PublishAsDockerFile を使った発行
 
-本番環境へデプロイするには、実行可能リソースをコンテナー化する必要があります。実行可能ファイルをどのようにパッケージ化するかを指定するには、`PublishAsDockerFile` メソッドを使用します:
+本番環境へデプロイするには、実行可能リソースをコンテナー化する必要があります。実行可能ファイルをどのようにパッケージ化するかを指定するには、<ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.PublishAsDockerFile" /> メソッドを使用します:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -347,7 +348,7 @@ const app = await builder.addExecutable("frontend", "npm", ".", ["start"])
 
 1. **明示的なパスを使用する**: 信頼性を高めるため、可能な場合は実行可能ファイルへの完全パスを使用します。
 1. **依存関係を処理する**: `WithReference` を使用して適切な依存関係を確立します。
-1. **明示的な開始を構成する**: 自動的に開始すべきでない実行可能ファイルには `WithExplicitStart()` を使用します。
+1. **明示的な開始を構成する**: 自動的に開始すべきでない実行可能ファイルには <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> を使用します。
 1. **デプロイに備える**: 本番シナリオでは常に `PublishAsDockerFile()` を使用します。
 1. **環境を分離する**: 機密な構成にはコマンドライン引数ではなく環境変数を使用します。
 1. **リソース名を工夫する**: 実行可能ファイルの目的が明確に分かる説明的な名前を使用します。
diff --git a/src/frontend/src/content/docs/ja/app-host/migrate-from-docker-compose.mdx b/src/frontend/src/content/docs/ja/app-host/migrate-from-docker-compose.mdx
index e83a666555..6b09ddea01 100644
--- a/src/frontend/src/content/docs/ja/app-host/migrate-from-docker-compose.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/migrate-from-docker-compose.mdx
@@ -5,6 +5,7 @@ description: Docker Compose アプリケーションを Aspire に移行する
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 本ガイドは、Docker Compose から Aspire へのアプリケーション移行方法を理解し、主要な概念的違いを強調し、一般的な移行シナリオに対する正確で実践的な例を提供します。
 
@@ -31,7 +32,7 @@ Docker Compose から Aspire に移行する際は、以下の概念的違いを
 - **コンテナからリソースへ** — Aspire はコンテナだけでなく、.NET プロジェクト、実行可能ファイル、パラメーター、クラウドリソースを管理します
 - **手動ネットワークから自動サービス検知へ** — Aspire は自動的にサービス検知と接続文字列を構成します
 - **開発ギャップから統合体験へ** — Aspire はダッシュボード、テレメトリー、デバッグ統合を提供します
-- **スタートアップオーケストレーションの違い** — Docker Compose の `depends_on` はスタートアップ順序を制御しますが、Aspire の `WithReference` はサービス検知のみを構成します。スタートアップ順序には `WaitFor` を使用してください
+- **スタートアップオーケストレーションの違い** — Docker Compose の `depends_on` はスタートアップ順序を制御しますが、Aspire の <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> はサービス検知のみを構成します。スタートアップ順序には <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> を使用してください
 
 <LearnMore>
 詳細な API マッピングについては、[Docker Compose to Aspire AppHost API reference](/ja/app-host/docker-compose-to-apphost-reference/) を参照してください。
@@ -155,7 +156,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="note" title="build: サービスはプロジェクトまたは Dockerfile リソースに変わります">
-Docker Compose では、`build:` ディレクティブは Dockerfile からコンテナイメージを作成します。Aspire では、.NET サービスは `AddProject<T>()` で直接プロジェクト参照として追加され、より優れたデバッグ、ホットリロード、テレメトリー統合を提供します。それでも Dockerfile からビルドするサービスについては、既存の Dockerfile に `AddDockerfile()` を使用するか、AppHost が Dockerfile をプログラムで生成する必要がある場合は `AddDockerfileBuilder()` を使用します。
+Docker Compose では、`build:` ディレクティブは Dockerfile からコンテナイメージを作成します。Aspire では、.NET サービスは <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> で直接プロジェクト参照として追加され、より優れたデバッグ、ホットリロード、テレメトリー統合を提供します。それでも Dockerfile からビルドするサービスについては、既存の Dockerfile に <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfile" /> を使用するか、AppHost が Dockerfile をプログラムで生成する必要がある場合は <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> を使用します。
 </Aside>
 
 **主な違いの説明:**
@@ -164,8 +165,8 @@ Docker Compose では、`build:` ディレクティブは Dockerfile からコ
 - **ポート** — どちらの例もポート (3000 と 5000) を明示的にマップします
 - **スタートアップ順序** — Docker Compose は正常性チェック条件付きの `depends_on` を使用します。Aspire はスタートアップ順序に `WaitFor()` を使用します
 - **サービス検知** — `WithReference()` はサービス検知と接続文字列のみを構成します。スタートアップ順序を制御しません
-- **接続文字列** — デフォルトでは、`WithReference(database)` は `AddDatabase()` のリソース名を使用して `ConnectionStrings__myapp` を提供します。`DefaultConnection` などの異なる名前に一致させるには、名前付き参照を使用します: `.WithReference(database, "DefaultConnection")`
-- **ボリューム** — `WithDataVolume()` は明示的に呼び出す必要があります。自動的ではありません
+- **接続文字列** — デフォルトでは、`WithReference(database)` は <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddDatabase" /> のリソース名を使用して `ConnectionStrings__myapp` を提供します。`DefaultConnection` などの異なる名前に一致させるには、名前付き参照を使用します: `.WithReference(database, "DefaultConnection")`
+- **ボリューム** — <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> は明示的に呼び出す必要があります。自動的ではありません
 - **イメージバージョン** — `WithImageTag("15")` は PostgreSQL をバージョン 15 にピン止めします
 
 ### コンテナベースのサービス
@@ -275,13 +276,13 @@ Aspire は .NET フォーマットの接続文字列を生成しており、Dock
 - Docker Compose: `DATABASE_URL=postgresql://postgres:secret@postgres:5432/main`
 - Aspire: `ConnectionStrings__main=Host=localhost;Port=12345;Username=postgres;Password=<generated>;Database=main`
 
-アプリケーションが URL フォーマットの環境変数を期待する場合は、`WithEnvironment()` で手動で構築してください。詳細は [環境変数と構成](#環境変数と構成) を参照してください。
+アプリケーションが URL フォーマットの環境変数を期待する場合は、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> で手動で構築してください。詳細は [環境変数と構成](#環境変数と構成) を参照してください。
 </Aside>
 
 **主な違いの説明:**
 
-- **イメージバージョン** — `WithImageTag()` で明示的に指定して Docker Compose と一致させます
-- **Dockerfile ビルド** — Docker Compose の `build: .` は `AddDockerfile("web", ".")` にマップしており、Dockerfile からコンテナイメージをビルドします。Docker Compose で `image:` を使用する事前ビルドイメージには `AddContainer()` を使用します
+- **イメージバージョン** — <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithImageTag" /> で明示的に指定して Docker Compose と一致させます
+- **Dockerfile ビルド** — Docker Compose の `build: .` は `AddDockerfile("web", ".")` にマップしており、Dockerfile からコンテナイメージをビルドします。Docker Compose で `image:` を使用する事前ビルドイメージには <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" /> を使用します
 - **ポート** — `WithHostPort()` は静的ホストポートにマップしており、なければ Aspire がランダムポートを割り当てます
 - **ボリューム** — `WithDataVolume()` は明示的に呼び出す必要があります
 - **スタートアップ順序** — `WaitFor()` はスタートアップ順序を制御し、Docker Compose の `depends_on` の条件に似ています
@@ -460,7 +461,7 @@ await builder.build().run();
 **主な違い:**
 
 - **名前付きボリューム** — `AddVolume()` で作成され、コンテナ間で共有されます
-- **バインドマウント** — ホストディレクトリアクセス用に `WithBindMount()` を使用します
+- **バインドマウント** — ホストディレクトリアクセス用に <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBindMount" /> を使用します
 
 ### ネットワーキング
 
@@ -530,14 +531,14 @@ Docker Compose から Aspire への正常な移行には体系的なアプロー
    - **`WithReference()` で依存関係を構成** してサービス検知のために
    - **`WaitFor()` でスタートアップ順序を追加** して `depends_on` の動作と一致させます
    - **環境変数を設定** — 接続文字列フォーマットが異なることに注意してください
-   - **正常性チェックを移行** — `WithHttpHealthCheck()` またはカスタムチェック用 `WithHealthCheck()` を使用します
+   - **正常性チェックを移行** — <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> またはカスタムチェック用 <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHealthCheck" /> を使用します
 
 4. ### データ移行を処理する
 
    永続データについて:
 
    - `WithDataVolume()` をインテグレーションで自動ボリューム管理に使用します
-   - `WithVolume()` をデータを永続化する必要があるという名前付きボリュームに使用します
+   - <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithVolume" /> をデータを永続化する必要があるという名前付きボリュームに使用します
    - `WithBindMount()` をホスト直接アクセスが必要な場合のホストディレクトリマウントに使用します
 
 5. ### テストと検証
diff --git a/src/frontend/src/content/docs/ja/app-host/resource-lifetimes.mdx b/src/frontend/src/content/docs/ja/app-host/resource-lifetimes.mdx
index 1e43dea2de..25756ba2c8 100644
--- a/src/frontend/src/content/docs/ja/app-host/resource-lifetimes.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/resource-lifetimes.mdx
@@ -9,6 +9,7 @@ import { Image } from 'astro:assets';
 import persistentContainer from '@assets/fundamentals/persistent-container-dark.png';
 import persistentContainerLight from '@assets/fundamentals/persistent-container-light.png';
 import persistentContainerDocker from '@assets/whats-new/aspire-9/persistent-container-docker-desktop.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire では、コンテナは典型的なライフサイクルに従い、AppHost の起動時に作成され停止時に破棄されます。ただし、この標準ライフサイクルから外れる**永続コンテナ**を使用するよう指定できます。永続コンテナは Aspire オーケストレーターによって作成・起動されますが、AppHost の停止時に破棄されず、実行をまたいで存続できます。
 
@@ -20,7 +21,7 @@ Aspire では、コンテナは典型的なライフサイクルに従い、AppH
 
 ## 永続コンテナを設定する
 
-永続的なライフタイムを持つコンテナリソースを設定するには、 `WithLifetime` メソッドを使用して `ContainerLifetime.Persistent` を渡します:
+永続的なライフタイムを持つコンテナリソースを設定するには、 <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithLifetime" /> メソッドを使用して `ContainerLifetime.Persistent` を渡します:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -96,7 +97,7 @@ AppHost が停止した後も、永続コンテナは動作し続け、コンテ
 
 ### カスタムコンテナ名
 
-高度なシナリオでは、 `WithContainerName` メソッドを使用してカスタムコンテナ名を設定できます:
+高度なシナリオでは、 <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerName" /> メソッドを使用してカスタムコンテナ名を設定できます:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/ja/app-host/withdockerfile.mdx b/src/frontend/src/content/docs/ja/app-host/withdockerfile.mdx
index 13c1b5da60..e51d68f22d 100644
--- a/src/frontend/src/content/docs/ja/app-host/withdockerfile.mdx
+++ b/src/frontend/src/content/docs/ja/app-host/withdockerfile.mdx
@@ -4,8 +4,9 @@ description: アプリモデルに Dockerfile を追加する方法について
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
-Aspire では、`AddDockerfile` または `WithDockerfile` 拡張メソッドを使用して、[AppHost](/ja/get-started/app-host/) の起動時にビルドする _Dockerfile_ を指定できます。
+Aspire では、<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfile" /> または <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfile" /> 拡張メソッドを使用して、[AppHost](/ja/get-started/app-host/) の起動時にビルドする _Dockerfile_ を指定できます。
 
 この 2 つのメソッドは異なる目的に使用します:
 
@@ -125,7 +126,7 @@ await pgsql.withPgAdmin(); // PostgreSQL リソースであることに変わり
 
 ## Dockerfile をプログラムで生成する
 
-`AddDockerfileBuilder` または `WithDockerfileBuilder` は、AppHost コードから Dockerfile を生成する必要がある場合に使用します。これらの API は、Dockerfile が AppHost の設定に依存する場合、Dockerfile フラグメントを組み合わせたい場合、またはマルチステージイメージのビルドロジックをリソース定義の近くに保ちたい場合に便利です。
+<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" /> または <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" /> は、AppHost コードから Dockerfile を生成する必要がある場合に使用します。これらの API は、Dockerfile が AppHost の設定に依存する場合、Dockerfile フラグメントを組み合わせたい場合、またはマルチステージイメージのビルドロジックをリソース定義の近くに保ちたい場合に便利です。
 
 <Aside type="caution">
   Dockerfile ビルダー API は実験的であり、将来の
@@ -248,7 +249,7 @@ await builder.build().run();
 
 ## ビルド引数を渡す
 
-`WithBuildArg` メソッドを使用して、コンテナーイメージのビルドに引数を渡すことができます。
+<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildArg" /> メソッドを使用して、コンテナーイメージのビルドに引数を渡すことができます。
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
@@ -323,7 +324,7 @@ CMD ["./mygoapp"]
 
 ## ビルドシークレットを渡す
 
-ビルド引数に加え、`WithBuildSecret` を使用してビルドシークレットを指定できます。シークレットは、`RUN` コマンドの `--mount=type=secret` 構文を使用して _Dockerfile_ 内の個別のコマンドに選択的に公開されます。
+ビルド引数に加え、<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildSecret" /> を使用してビルドシークレットを指定できます。シークレットは、`RUN` コマンドの `--mount=type=secret` 構文を使用して _Dockerfile_ 内の個別のコマンドに選択的に公開されます。
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/ja/architecture/multi-language-architecture.mdx b/src/frontend/src/content/docs/ja/architecture/multi-language-architecture.mdx
index 96dbf8b207..2339805303 100644
--- a/src/frontend/src/content/docs/ja/architecture/multi-language-architecture.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/multi-language-architecture.mdx
@@ -4,6 +4,7 @@ description: Aspire がマルチ言語 AppHost をサポートするために使
 ---
 
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire は複数の言語で AppHost を記述することをサポートしています。オーケストレーションエンジンは .NET 上に構築されていますが、ゲスト/ホストアーキテクチャにより、現在は TypeScript で記述された AppHost が、そして将来は他の言語で書かれた AppHost が、Aspire インテグレーション、サービス検知、およびダッシュボードにアクセスできます。
 
@@ -11,7 +12,7 @@ Aspire は複数の言語で AppHost を記述することをサポートして
 
 Aspire のホスティングインテグレーションとデプロイパブリッシャーは .NET で記述されており、ローカルオーケストレーション、診断、パブリッシングに必要なランタイム動作がすでに蓄積されています。それらのインテグレーションをゲスト言語ごとに書き直すと、大量の動作が重複し、メンテナンスコストが大幅に増加します。
 
-代わりに、ゲスト言語は `addRedis`、`addPostgres`、`withReference` などのリソースを宣言するだけで、.NET ホストがコンテナの起動、サービス検知の配線、正常性チェックの実行、デプロイ成果物の生成などのオーケストレーション処理を担当します。トレードオフはローカル IPC ホップですが、複数の言語で同じインテグレーションサーフェスを個別に維持するよりもはるかにコストが低くなります。
+代わりに、ゲスト言語は <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" />、<ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" />、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> などのリソースを宣言するだけで、.NET ホストがコンテナの起動、サービス検知の配線、正常性チェックの実行、デプロイ成果物の生成などのオーケストレーション処理を担当します。トレードオフはローカル IPC ホップですが、複数の言語で同じインテグレーションサーフェスを個別に維持するよりもはるかにコストが低くなります。
 
 ## ゲスト/ホストモデル
 
@@ -54,7 +55,7 @@ flowchart TB
 2. ATS スキャナーがエクスポート用のアセンブリを検査し、TypeScript SDK を `.modules/` に生成します。
 3. CLI がホストプロセスを起動し、ローカルソケットまたはパイプエンドポイントを作成します。
 4. CLI がゲストプロセスを起動し、環境変数を通じて接続詳細を渡します。
-5. ゲストが接続し、`createBuilder`、`addRedis`、`build`、`run` などの機能を呼び出します。
+5. ゲストが接続し、<ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" />、`addRedis`、`build`、<ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> などの機能を呼び出します。
 6. ホストがリソースをオーケストレーションし、ダッシュボードを起動して、アプリケーションのライフサイクルを管理します。
 
 ## トークンベース認証
diff --git a/src/frontend/src/content/docs/ja/architecture/resource-api-patterns.mdx b/src/frontend/src/content/docs/ja/architecture/resource-api-patterns.mdx
index 1c835018b7..e6a41e9c22 100644
--- a/src/frontend/src/content/docs/ja/architecture/resource-api-patterns.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/resource-api-patterns.mdx
@@ -4,6 +4,7 @@ description: リソースの追加と構成、注釈の使用、カスタム値
 ---
 
 import { Aside, Steps } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire のリソースモデルでは、構造化された方法でリソースを定義および構成でき、アプリケーションコンポーネントのシームレスな統合と管理を実現できます。このガイドでは、Aspire でリソースを追加および構成するための一般的なパターンについて詳しく説明します。
 
@@ -160,7 +161,7 @@ builder.WithAnnotation(new PersistenceAnnotation(
 | `IValueWithReferences` _(opt.)_ | `IEnumerable<object> References { get; }` | 両方（必要な場合） | 他リソースへの依存関係を宣言する |
 
 - すべての構造化値型で `IValueProvider` と `IManifestExpressionProvider` を **実装** します。  
-- `WithEnvironment(...)` などの API で構造化値型を受け入れさせたい場合は、`IExpressionValue` を **実装** します。
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> などの API で構造化値型を受け入れさせたい場合は、`IExpressionValue` を **実装** します。
 - 型がリソース参照を保持する場合にのみ、`IValueWithReferences` を **実装** します。
 
 ### リソースへの付与
diff --git a/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx b/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
index b88dce3776..26e9fe98c7 100644
--- a/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
@@ -4,6 +4,8 @@ description: Aspire の主要な概念を示す、実行可能な完全なサン
 next: false
 ---
 
+import ApiReference from '@components/ApiReference.astro';
+
 Aspire では柔軟なリソースモデルが提供されており、構造化された方法でリソースを定義および構成できます。このガイドでは、カスタムリソースの例とその実装方法を含め、リソースを追加して構成する一般的なパターンを紹介します。
 
 ### 例: 派生コンテナーリソース（Redis）
@@ -12,7 +14,7 @@ Aspire では柔軟なリソースモデルが提供されており、構造化
 
 - データのみを保持するリソースクラスの定義。
 - `ReferenceExpression` を使用した遅延評価での `IResourceWithConnectionString` の実装。
-- パラメーター検証、パスワード管理、イベント購読、正常性チェック、Fluent API を使ったコンテナー構成を処理する `AddRedis` 拡張メソッドの作成。
+- パラメーター検証、パスワード管理、イベント購読、正常性チェック、Fluent API を使ったコンテナー構成を処理する <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> 拡張メソッドの作成。
 
 ```csharp title="C# — RedisResourceExtensions.cs"
 public static class RedisResourceExtensions
diff --git a/src/frontend/src/content/docs/ja/architecture/resource-hierarchies.mdx b/src/frontend/src/content/docs/ja/architecture/resource-hierarchies.mdx
index 2da60756b6..a4936d93fd 100644
--- a/src/frontend/src/content/docs/ja/architecture/resource-hierarchies.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/resource-hierarchies.mdx
@@ -4,6 +4,7 @@ description: Aspire がアプリケーション内でリソースとその依存
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire は、所有、包含、グループ化を表現するために、リソース間の **親子関係** をモデル化できます。
 
@@ -27,7 +28,7 @@ Aspire は、所有、包含、グループ化を表現するために、リソ
 
 ### 視覚的グループ化（ライフサイクルへの影響なし）
 
-Aspire は、リソース構築時に `WithParentRelationship()` メソッドを使うことで、**視覚専用の親子関係** もサポートします。
+Aspire は、リソース構築時に <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithParentRelationship" /> メソッドを使うことで、**視覚専用の親子関係** もサポートします。
 
 視覚的関係:
 
@@ -112,7 +113,7 @@ architecture-beta
 
 リソースは次を通じて互いに接続されます:
 
-- **`WithReference()` 呼び出し**: 直接的なリソース間依存。
+- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> 呼び出し**: 直接的なリソース間依存。
 - **環境変数と CLI 引数**: 構造化参照を含む構成値。
 - **その他の構成ソース**: 構造化値参照で設定される値。
 
@@ -360,7 +361,7 @@ Error accessing Url: Endpoint has not been allocated.
 ```
 
 <Aside type="tip">
-  コールバックを受け取る `WithEnvironment` のオーバーロードは、
+  コールバックを受け取る <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> のオーバーロードは、
   エンドポイント割り当て後に実行されます。
 </Aside>
 
diff --git a/src/frontend/src/content/docs/ja/architecture/resource-publishing.mdx b/src/frontend/src/content/docs/ja/architecture/resource-publishing.mdx
index 1ce1acabc9..c768c0983e 100644
--- a/src/frontend/src/content/docs/ja/architecture/resource-publishing.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/resource-publishing.mdx
@@ -3,6 +3,7 @@ title: リソースの公開
 ---
 
 import { Steps } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire は、リソースマニフェストを公開するための柔軟な仕組みを提供し、様々なデプロイ環境とのシームレスな統合を可能にします。リソースは JSON 形式にシリアル化され、デプロイツールで利用できます。
 
@@ -16,7 +17,7 @@ JSON マニフェストエントリを公開するカスタムリソースでは
 
 </Steps>
 
-リソースは、`IResourceBuilder<T>` に対して `ExcludeFromManifest()` 拡張メソッドを呼び出すことで、公開マニフェストへの含有を完全にオプトアウトできます。この方法でマークされたリソースは、Docker Compose ファイルや Kubernetes マニフェストなどの公開アセットを生成する際に除外されます。
+リソースは、`IResourceBuilder<T>` に対して <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" /> 拡張メソッドを呼び出すことで、公開マニフェストへの含有を完全にオプトアウトできます。この方法でマークされたリソースは、Docker Compose ファイルや Kubernetes マニフェストなどの公開アセットを生成する際に除外されます。
 
 ### コールバックの登録
 
diff --git a/src/frontend/src/content/docs/ja/deployment/pipelines.mdx b/src/frontend/src/content/docs/ja/deployment/pipelines.mdx
index 1d668a9ba5..ac613d0452 100644
--- a/src/frontend/src/content/docs/ja/deployment/pipelines.mdx
+++ b/src/frontend/src/content/docs/ja/deployment/pipelines.mdx
@@ -8,6 +8,7 @@ lastUpdated: true
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire の**AppHost**で分散アプリを構成する場合、単にローカル開発とオーケストレーション用のサービスを定義しているのではなく、デプロイメントの基盤も設定しています。ローカルで実行およびデバッグするために使用する同じ構成は、アプリを発行する際にも活用され、開発から本番環境まで一貫性が確保されます。
 
@@ -147,8 +148,8 @@ Aspire パイプラインの依存関係は明示的で目的が明確です。
 
 ステップは以下を使用して関係を宣言します:
 
-- `PipelineStep.DependsOn`: このステップは別のステップが正常に完了した後に実行される必要があります
-- `PipelineStep.RequiredBy`: 別のステップはこのステップ後に実行される必要があります（逆の依存関係宣言）
+- <ApiReference name="Aspire.Hosting.Pipelines.PipelineStep.DependsOn" />: このステップは別のステップが正常に完了した後に実行される必要があります
+- <ApiReference name="Aspire.Hosting.Pipelines.PipelineStep.RequiredBy" />: 別のステップはこのステップ後に実行される必要があります（逆の依存関係宣言）
 
 **依存関係の例:**
 
@@ -518,7 +519,7 @@ aspire do validate
 
 ### リソースレベルステップ
 
-リソースは `WithPipelineStepFactory` を使用して独自のパイプラインステップを提供できます:
+リソースは <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" /> を使用して独自のパイプラインステップを提供できます:
 
 ```csharp title="Resource-level custom step"
 var api = builder.AddProject<Projects.Api>("api")
@@ -564,7 +565,7 @@ requiredBy: ["deploy-apiservice"]);
 
 ### パイプライン設定
 
-リソースは `WithPipelineConfiguration` を使用してパイプラインにどのように参加するかをカスタマイズすることもでき、ステップの順序付けとリソース固有のパイプライン動作を制御できます。
+リソースは <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineConfiguration" /> を使用してパイプラインにどのように参加するかをカスタマイズすることもでき、ステップの順序付けとリソース固有のパイプライン動作を制御できます。
 
 <Aside type="note">
 `WithPipelineConfiguration` API は実験的であり、将来のリリースで変更される可能性があります。
diff --git a/src/frontend/src/content/docs/ja/extensibility/custom-resources.mdx b/src/frontend/src/content/docs/ja/extensibility/custom-resources.mdx
index 2a70f8049f..2f022aeb0a 100644
--- a/src/frontend/src/content/docs/ja/extensibility/custom-resources.mdx
+++ b/src/frontend/src/content/docs/ja/extensibility/custom-resources.mdx
@@ -5,6 +5,7 @@ description: アプリケーション固有のインフラストラクチャ コ
 
 import { Aside } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 カスタム リソースを作成すると、組み込み統合でカバーされていないコンポーネントをモデル化できるように Aspire を拡張できます。このガイドでは、独自のリソース型を構築するためのパターンと API について説明します。
 
@@ -32,7 +33,7 @@ Aspire には、リソースに特定の機能を付与するいくつかのイ
 | `IResourceWithEndpoints` | リソースがネットワーク エンドポイントを持つ |
 | `IResourceWithEnvironment` | リソースが環境変数を構成できる |
 | `IResourceWithArgs` | リソースがコマンド ライン引数を受け取る |
-| `IResourceWithWaitSupport` | リソースが `WaitFor` オーケストレーションをサポートする |
+| `IResourceWithWaitSupport` | リソースが <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> オーケストレーションをサポートする |
 | `IResourceWithParent` | リソースが親リソースを持つ（ライフサイクル バインド） |
 
 ### IResourceWithConnectionString の実装
@@ -273,7 +274,7 @@ Aspire Dashboard でのリソース表示の詳細は、[Dashboard overview](/ja
 
 ## カスタム アイコン
 
-`WithIconName` を使うと、ダッシュボードでリソースにカスタム アイコンを表示できます。任意の [Fluent UI system icon](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) を使用できます:
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithIconName" /> を使うと、ダッシュボードでリソースにカスタム アイコンを表示できます。任意の [Fluent UI system icon](https://github.com/microsoft/fluentui-system-icons/blob/main/icons_filled.md) を使用できます:
 
 ```csharp title="カスタム ダッシュボード アイコンの設定"
 return builder.AddResource(resource)
diff --git a/src/frontend/src/content/docs/ja/extensibility/interaction-service.mdx b/src/frontend/src/content/docs/ja/extensibility/interaction-service.mdx
index 34a1a241de..1c4358e493 100644
--- a/src/frontend/src/content/docs/ja/extensibility/interaction-service.mdx
+++ b/src/frontend/src/content/docs/ja/extensibility/interaction-service.mdx
@@ -17,6 +17,7 @@ import multipleInputFilled from '@assets/extensibility/interaction-service-multi
 import multipleInputFilledLight from '@assets/extensibility/interaction-service-multiple-input-filled-light.png';
 import multipleInputLogs from '@assets/extensibility/interaction-service-multiple-input-logs.png';
 import multipleInputLogsLight from '@assets/extensibility/interaction-service-multiple-input-logs-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Interaction service（`Aspire.Hosting.IInteractionService`）を使うと、ユーザー入力の要求、確認依頼、メッセージ表示を行えます。Interaction service は 2 つの異なるコンテキストで動作します:
 
@@ -71,7 +72,7 @@ Interaction service には、ユーザーと対話したりメッセージを表
 
 - **カスタム リソース型**: カスタム リソース型を作成するときに、ユーザーから入力を取得したり、アクションを確認したりします。リソース型では、ユーザー入力の要求やメッセージ表示など、ダッシュボード対話を自由に定義できます。
 
-- **カスタム リソース コマンド**: Aspire ダッシュボードまたは CLI でリソースにコマンドを追加します。これらのコマンド実行時に、Interaction service を使ってユーザー入力や確認を求めます。対象の `IResourceBuilder<T>` に `WithCommand` 呼び出しをチェーンすると、コールバック内で Interaction service を使って入力収集や確認ができます。詳細は、[Custom resource commands](/ja/fundamentals/custom-resource-commands/) を参照してください。
+- **カスタム リソース コマンド**: Aspire ダッシュボードまたは CLI でリソースにコマンドを追加します。これらのコマンド実行時に、Interaction service を使ってユーザー入力や確認を求めます。対象の `IResourceBuilder<T>` に <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCommand" /> 呼び出しをチェーンすると、コールバック内で Interaction service を使って入力収集や確認ができます。詳細は、[Custom resource commands](/ja/fundamentals/custom-resource-commands/) を参照してください。
 
 - **公開とデプロイのワークフロー**: `aspire publish` または `aspire deploy` の実行中に、Interaction service を使ってデプロイ固有の構成を収集し、CLI から破壊的操作の確認を行います。
 
diff --git a/src/frontend/src/content/docs/ja/extensibility/multi-language-integration-authoring.mdx b/src/frontend/src/content/docs/ja/extensibility/multi-language-integration-authoring.mdx
index 3403ec70ac..8460c4ecf4 100644
--- a/src/frontend/src/content/docs/ja/extensibility/multi-language-integration-authoring.mdx
+++ b/src/frontend/src/content/docs/ja/extensibility/multi-language-integration-authoring.mdx
@@ -9,6 +9,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire hosting integration は、新しいリソース型で AppHost を拡張する C# ライブラリです。既定では、これらの統合は C# AppHost でのみ利用できます。TypeScript AppHost で利用可能にするには、ATS（Aspire Type System）属性で API に注釈を付けます。
 
@@ -217,7 +218,7 @@ TypeScript 側で値を一度読み取る async 操作として扱いたい場
 
 ## コールバック コンテキスト型と ATS-first の editor パターン
 
-`withEnvironmentCallback`、`withArgsCallback`、`withUrls` など、コールバックを受け取るメソッドをエクスポートする場合、コールバックは *context* オブジェクトを受け取ります。TypeScript 互換性のため、コンテキスト型は ATS-first 設計に従う必要があります:
+`withEnvironmentCallback`、`withArgsCallback`、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrls" /> など、コールバックを受け取るメソッドをエクスポートする場合、コールバックは *context* オブジェクトを受け取ります。TypeScript 互換性のため、コンテキスト型は ATS-first 設計に従う必要があります:
 
 1. コンテキスト クラスには `[AspireExport]` を使用します（`ExposeProperties = true` ではありません）。
 2. TypeScript 呼び出し元に必要なプロパティだけを個別の `[AspireExport]` 属性で注釈します。
diff --git a/src/frontend/src/content/docs/ja/fundamentals/custom-resource-commands.mdx b/src/frontend/src/content/docs/ja/fundamentals/custom-resource-commands.mdx
index 3fc004272e..d410678d49 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/custom-resource-commands.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/custom-resource-commands.mdx
@@ -9,6 +9,7 @@ import customClearCacheCommand from '@assets/fundamentals/custom-clear-cache-com
 import customClearCacheCommandLight from '@assets/fundamentals/custom-clear-cache-command-light.png';
 import customClearCacheCommandSucceeded from '@assets/fundamentals/custom-clear-cache-command-succeeded.png';
 import customClearCacheCommandSucceededLight from '@assets/fundamentals/custom-clear-cache-command-succeeded-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire アプリ モデル内の各リソースは `IResource` として表現され、分散アプリケーション ビルダーに追加されると、`IResourceBuilder<T>` インターフェイスのジェネリック型パラメーターになります。_resource builder_ API を使って呼び出しを連鎖し、基になるリソースを構成できます。状況によっては、そのリソースにカスタム コマンドを追加したいことがあります。カスタム コマンドを作成する一般的なシナリオには、データベース移行の実行やデータベースのシード/リセットなどがあります。この記事では、キャッシュをクリアする Redis リソースにカスタム コマンドを追加する方法を学びます。
 
@@ -151,7 +152,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithCommand` API は、リソースに適切な注釈を追加し、それらは [Aspire ダッシュボード](/ja/dashboard/overview/) で利用されます。ダッシュボードはこれらの注釈を使って UI にコマンドを描画します。詳細へ進む前に、まず `WithCommand` メソッドのパラメーターを理解しておきましょう。
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithCommand" /> API は、リソースに適切な注釈を追加し、それらは [Aspire ダッシュボード](/ja/dashboard/overview/) で利用されます。ダッシュボードはこれらの注釈を使って UI にコマンドを描画します。詳細へ進む前に、まず `WithCommand` メソッドのパラメーターを理解しておきましょう。
 
 - `name`: 呼び出すコマンド名。
 - `displayName`: ダッシュボードに表示するコマンド名。
diff --git a/src/frontend/src/content/docs/ja/fundamentals/custom-resource-urls.mdx b/src/frontend/src/content/docs/ja/fundamentals/custom-resource-urls.mdx
index d1153b25d5..552a8ee832 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/custom-resource-urls.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/custom-resource-urls.mdx
@@ -4,6 +4,7 @@ description: Aspire リソース用のカスタム URL を作成する方法を
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire では、エンドポイントを公開するリソースはホストとポートのみを構成しますが、これらは実行時まで確定しません。これらのエンドポイントの特定パスにアクセスする必要がある場合、特に [ダッシュボード](/ja/dashboard/overview/) からアクセスしたい場合は、カスタム リソース URL を定義できます。任意のエンドポイントに紐付かないカスタム URL を追加することも可能です。カスタム URL はダッシュボードで使うことを目的としているため、すべて "run" モードでのみ利用できます。この記事では、カスタム URL の定義方法を説明します。
 
@@ -11,10 +12,10 @@ Aspire では、エンドポイントを公開するリソースはホストと
 
 既定では、Aspire プロジェクト リソースは Kestrel や起動プロファイルなどの既存構成に基づいて、構成済みエンドポイント向けリソースのホストとポートを決定します。エンドポイントは常にダッシュボードに表示されます。
 
-同様に、`WithEndpoint` API を使ってエンドポイントを明示的に公開することもできます。この API ではリソースのホストとポートを指定でき、これを使ってそのリソースの既定 URL が作成されます。既定 URL は通常、`<scheme>://<host>:<port>` 形式です。ホスト ポートを省略するには、次のいずれかのメソッドを使います。
+同様に、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> API を使ってエンドポイントを明示的に公開することもできます。この API ではリソースのホストとポートを指定でき、これを使ってそのリソースの既定 URL が作成されます。既定 URL は通常、`<scheme>://<host>:<port>` 形式です。ホスト ポートを省略するには、次のいずれかのメソッドを使います。
 
-- `WithHttpEndpoint`
-- `WithHttpsEndpoint`
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpEndpoint" />
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpsEndpoint" />
 
 詳細は、[エンドポイント拡張メソッド](/ja/fundamentals/networking-overview/#エンドポイント拡張メソッド) を参照してください。
 
@@ -28,7 +29,7 @@ Aspire では、エンドポイントを公開するリソースはホストと
 
 ## リソース URL をカスタマイズする
 
-サポートされる任意のリソース ビルダーで、適切な `WithUrl` オーバーロード、`WithUrls`、または `WithUrlForEndpoint` API を使うと、リソースのカスタム URL を定義できます。次の例は、プロジェクト リソースにカスタム URL を設定する方法を示しています。
+サポートされる任意のリソース ビルダーで、適切な <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrl" /> オーバーロード、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrls" />、または <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithUrlForEndpoint" /> API を使うと、リソースのカスタム URL を定義できます。次の例は、プロジェクト リソースにカスタム URL を設定する方法を示しています。
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -100,7 +101,7 @@ builder.Build().Run();
 <Aside type="tip">
   `ResourceUrlsCallbackContext` には、基盤となるリソースの名前付きエンドポイントへ
   簡単にアクセスできる拡張メソッドが公開されています。これを行うには、
-  コンテキスト インスタンスで `GetEndpoint` API を呼び出します。
+  コンテキスト インスタンスで <ApiReference name="Aspire.Hosting.ApplicationModel.ResourceUrlsCallbackContext.GetEndpoint" /> API を呼び出します。
 </Aside>
 
 ## URL カスタマイズのライフサイクル
diff --git a/src/frontend/src/content/docs/ja/fundamentals/external-parameters.mdx b/src/frontend/src/content/docs/ja/fundamentals/external-parameters.mdx
index 223bbe2103..a311823382 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/external-parameters.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/external-parameters.mdx
@@ -9,6 +9,7 @@ import dashboardUnresolvedParams from '@assets/fundamentals/dashboard-unresolved
 import dashboardUnresolvedParamsLight from '@assets/fundamentals/dashboard-unresolved-parameters-message-light.png';
 import customizedParameterUi from '@assets/fundamentals/customized-parameter-ui.png';
 import customizedParameterUiLight from '@assets/fundamentals/customized-parameter-ui-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 環境は、アプリケーションが実行されるためのコンテキストを提供します。パラメーターは、アプリの実行時に外部の値を要求できる仕組みを表します。パラメーターは、ローカル実行時にアプリへ値を提供したり、デプロイ時に値の入力を求めたりするために使用できます。また、シークレットや接続文字列、その他の環境ごとに異なる可能性のある構成値など、幅広いシナリオをモデル化するためにも利用できます。
 
@@ -199,8 +200,8 @@ Aspire は、次の順序でパラメーター値を解決します:
 
 また、以下のメソッドを使用して、ダッシュボード上でのパラメーター表示方法を制御できます:
 
-- `WithDescription`: パラメーターの目的をユーザーが理解しやすくするための説明テキストを指定します。[Markdown](https://www.markdownguide.org/basic-syntax/) 形式で記述する場合は、`enableMarkdown: true` パラメーターを使用します。
-- `WithCustomInput`: コールバックメソッドを指定して、パラメーター ダイアログをカスタマイズします。たとえば、このコールバックでは既定値、入力タイプ、ラベル、プレースホルダー テキストをカスタマイズできます。`WithCustomInput` を使用する場合、Markdown のレンダリングを維持するために、`EnableDescriptionMarkdown` プロパティをパラメーターから `InteractionInput` オブジェクトにコピーする必要があります。
+- <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.WithDescription" />: パラメーターの目的をユーザーが理解しやすくするための説明テキストを指定します。[Markdown](https://www.markdownguide.org/basic-syntax/) 形式で記述する場合は、`enableMarkdown: true` パラメーターを使用します。
+- <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.WithCustomInput" />: コールバックメソッドを指定して、パラメーター ダイアログをカスタマイズします。たとえば、このコールバックでは既定値、入力タイプ、ラベル、プレースホルダー テキストをカスタマイズできます。`WithCustomInput` を使用する場合、Markdown のレンダリングを維持するために、`EnableDescriptionMarkdown` プロパティをパラメーターから `InteractionInput` オブジェクトにコピーする必要があります。
 
 以下のコードは、説明を設定し、コールバックを使用する方法を示しています:
 
@@ -350,7 +351,7 @@ await builder.build().run();
 
 ## 構成からパラメーターを追加する
 
-特定のシナリオでは、標準の `Parameters:*` パターンに従うのではなく、特定の構成キーから直接パラメーター値を読み取りたい場合があります。`AddParameterFromConfiguration` メソッドを使用すると、パラメーターに対してカスタムの構成キーを指定できます。
+特定のシナリオでは、標準の `Parameters:*` パターンに従うのではなく、特定の構成キーから直接パラメーター値を読み取りたい場合があります。<ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameterFromConfiguration" /> メソッドを使用すると、パラメーターに対してカスタムの構成キーを指定できます。
 
 <Aside type="note">
 `addParameterFromConfiguration` API は、TypeScript AppHost SDK ではまだ利用できません。
@@ -415,7 +416,7 @@ builder.Build().Run();
 パラメーターは接続文字列を表現する目的でも使用できます。アプリを公開する際には値の入力が求められ、安全な場所に保存されます。ローカルでアプリを実行する場合は、AppHost 構成の `ConnectionStrings` セクションから値が読み取られます。
 
 <Aside type="danger">
-シークレットをリソースに渡す場合は、必ず `AddParameter` を使用してください。パスワードや接続文字列などの機密情報をソースコードに直接含めてはいけません。
+シークレットをリソースに渡す場合は、必ず <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> を使用してください。パスワードや接続文字列などの機密情報をソースコードに直接含めてはいけません。
 
 ローカル データベースに接続し、統合セキュリティやパスワードレス認証を使用する場合は、接続文字列の保護について過度に心配する必要はありません。パスワードを使用する場合は、アプリ シークレットを使って安全に保存してください。
 
@@ -458,7 +459,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="note">
-  接続文字列に対して `WaitFor` を使用すると、その接続先となるリソースの起動を
+  接続文字列に対して <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> を使用すると、その接続先となるリソースの起動を
   暗黙的に待機します。
 </Aside>
 
@@ -474,7 +475,7 @@ await builder.build().run();
 
 ### 参照式を使用して接続文字列を構築する
 
-パラメーターから接続文字列を構築し、開発環境と本番環境の両方で正しく扱われるようにしたい場合は、`ReferenceExpression` を指定した `AddConnectionString` を使用します。
+パラメーターから接続文字列を構築し、開発環境と本番環境の両方で正しく扱われるようにしたい場合は、`ReferenceExpression` を指定した <ApiReference name="Aspire.Hosting.ConnectionStringBuilderExtensions.AddConnectionString" /> を使用します。
 
 たとえば、接続文字列の一部を保持するシークレット パラメーターがある場合、次のコードでそれを組み込めます:
 
diff --git a/src/frontend/src/content/docs/ja/fundamentals/health-checks.mdx b/src/frontend/src/content/docs/ja/fundamentals/health-checks.mdx
index 86c140307a..e105904d8f 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/health-checks.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/health-checks.mdx
@@ -7,6 +7,7 @@ import ThemeImage from '@components/ThemeImage.astro';
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
 import healthChecksDashboardStatus from '@assets/fundamentals/health-checks-dashboard-status.png';
 import healthChecksDashboardStatusLight from '@assets/fundamentals/health-checks-dashboard-status-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 正常性チェックは、アプリの可用性と状態に関する情報を提供します。正常性チェックは多くの場合 HTTP エンドポイントとして公開されますが、現在の正常性に基づいてログを書き込んだり、ほかのタスクを実行したりするために、アプリ内部でも使用できます。正常性チェックは通常、外部の監視サービスやコンテナー オーケストレーターと組み合わせて、アプリの状態確認に使用されます。
 
@@ -16,7 +17,7 @@ Aspire は、2 つの異なるコンテキストで正常性チェックを利
 
 | 正常性チェックの種類           | 実行場所             | チェック内容                   | 用途                                 |
 | ------------------------------ | -------------------- | ------------------------------ | ------------------------------------ |
-| **AppHost リソース チェック**  | AppHost プロジェクト | 「依存関係の準備はできているか?」 | 起動オーケストレーション、`WaitFor()` |
+| **AppHost リソース チェック**  | AppHost プロジェクト | 「依存関係の準備はできているか?」 | 起動オーケストレーション、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> |
 | **サービス エンドポイント チェック** | アプリケーション     | 「自分は正常か?」               | ロード バランサー、Kubernetes プローブ |
 
 <Aside type="tip" title="重要なポイント">
@@ -468,7 +469,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithHttpHealthCheck` メソッドは、プロジェクト リソースにも適用できます:
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> メソッドは、プロジェクト リソースにも適用できます:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -560,7 +561,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`AddCheck` メソッドは正常性チェックを登録し、`WithHealthCheck` はそれを特定リソースに関連付けます。カスタム正常性チェックの作成と登録の詳細は、[正常性チェックの作成](https://learn.microsoft.com/ja-jp/aspnet/core/host-and-deploy/health-checks#create-health-checks) を参照してください。
+`AddCheck` メソッドは正常性チェックを登録し、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHealthCheck" /> はそれを特定リソースに関連付けます。カスタム正常性チェックの作成と登録の詳細は、[正常性チェックの作成](https://learn.microsoft.com/ja-jp/aspnet/core/host-and-deploy/health-checks#create-health-checks) を参照してください。
 
 ### ダッシュボード統合
 
diff --git a/src/frontend/src/content/docs/ja/fundamentals/http-commands.mdx b/src/frontend/src/content/docs/ja/fundamentals/http-commands.mdx
index e495cfc5ce..22c01856c5 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/http-commands.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/http-commands.mdx
@@ -14,8 +14,9 @@ import customHttpCommandStarting from '@assets/fundamentals/custom-http-command-
 import customHttpCommandStartingLight from '@assets/fundamentals/custom-http-command-starting-light.png';
 import customHttpCommandSucceeded from '@assets/fundamentals/custom-http-command-succeeded.png';
 import customHttpCommandSucceededLight from '@assets/fundamentals/custom-http-command-succeeded-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
-Aspire では、`WithHttpCommand` API を使ってリソースにカスタム HTTP コマンドを追加できます。この API は、[リソースのカスタム コマンド](/ja/fundamentals/custom-resource-commands/) を提供する既存機能を拡張するものです。この機能により、指定したエンドポイントとパスへ HTTP 要求を送るコマンドをリソース上に定義できます。これは、データベース移行のトリガー、キャッシュのクリア、HTTP 要求を介したリソースへのカスタム操作などのシナリオで役立ちます。
+Aspire では、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpCommand" /> API を使ってリソースにカスタム HTTP コマンドを追加できます。この API は、[リソースのカスタム コマンド](/ja/fundamentals/custom-resource-commands/) を提供する既存機能を拡張するものです。この機能により、指定したエンドポイントとパスへ HTTP 要求を送るコマンドをリソース上に定義できます。これは、データベース移行のトリガー、キャッシュのクリア、HTTP 要求を介したリソースへのカスタム操作などのシナリオで役立ちます。
 
 カスタム HTTP コマンドを実装するには、リソース上のコマンドと、その要求を処理する対応 HTTP エンドポイントを定義します。この記事では、Aspire でカスタム HTTP コマンドを作成して構成する方法の概要を説明します。
 
diff --git a/src/frontend/src/content/docs/ja/fundamentals/networking-overview.mdx b/src/frontend/src/content/docs/ja/fundamentals/networking-overview.mdx
index 84a40cf6ee..3687418eb6 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/networking-overview.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/networking-overview.mdx
@@ -12,6 +12,7 @@ import proxyWithReplicas from '@assets/fundamentals/networking/proxy-with-replic
 import proxyHostPortAndRandomPort from '@assets/fundamentals/networking/proxy-host-port-and-random-port-1x.png';
 import proxyWithRandomPorts from '@assets/fundamentals/networking/proxy-with-random-ports-1x.png';
 import proxyWithDockerPortMapping from '@assets/fundamentals/networking/proxy-with-docker-port-mapping-1x.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire で開発する利点の 1 つは、クラウドネイティブ アプリをローカルで開発、テスト、デバッグできることです。内部ループ ネットワークは、開発環境でアプリ同士を通信させる Aspire の重要な要素です。この記事では、プロキシ、エンドポイント、エンドポイント構成、コンテナー ネットワークを通じて、Aspire がさまざまなネットワーク シナリオをどう処理するかを学びます。
 
@@ -51,7 +52,7 @@ flowchart LR
 
 内部ループとは、アプリをターゲット環境にデプロイする前に、ローカルで開発とテストを進めるプロセスです。Aspire は、内部ループでのネットワーク体験を簡素化して高めるために、次のようなツールと機能を提供します:
 
-- **エンドポイント / エンドポイント構成**: エンドポイントは、データベース、メッセージ キュー、API など、アプリが依存するサービスとの接続です。エンドポイントには、サービス名、ホスト ポート、スキーム、環境変数などの情報が含まれます。Aspire はリソース構成から自動でエンドポイントを作成でき、`WithEndpoint` の呼び出しで明示的に追加することもできます。
+- **エンドポイント / エンドポイント構成**: エンドポイントは、データベース、メッセージ キュー、API など、アプリが依存するサービスとの接続です。エンドポイントには、サービス名、ホスト ポート、スキーム、環境変数などの情報が含まれます。Aspire はリソース構成から自動でエンドポイントを作成でき、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> の呼び出しで明示的に追加することもできます。
 - **プロキシ**: Aspire は、アプリに追加した各サービス バインディングごとにプロキシを自動起動し、そのプロキシが待ち受けるポートを割り当てます。プロキシは、アプリが待ち受けるポート（プロキシ ポートと異なる場合があります）にリクエストを転送します。これにより、ポート競合を避けつつ、アプリとサービスに一貫した予測可能な URL でアクセスできます。
 - **コンテナー ネットワーク**: Aspire はコンテナー リソース用の専用ネットワークを作成・管理し、ローカル開発中にコンテナー同士が相互に検出して通信できるようにします。
 
@@ -101,7 +102,7 @@ Aspire はリソース構成からサービス バインディングを自動作
 
 既定では、コンテナーは DNS エイリアスとして **リソース名** を使ってコンテナー ネットワーク上からアクセスできます。たとえば `AddContainer("mydb", ...)` で追加したコンテナーは、他のコンテナーから `mydb:5432` で到達できます。
 
-サードパーティ ツールが特定のホスト名を期待する場合や、既存の Docker Compose 構成から移行する場合など、追加のエイリアスが必要になることがあります。カスタム DNS 名を追加するには `WithContainerNetworkAlias` を使います:
+サードパーティ ツールが特定のホスト名を期待する場合や、既存の Docker Compose 構成から移行する場合など、追加のエイリアスが必要になることがあります。カスタム DNS 名を追加するには <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerNetworkAlias" /> を使います:
 
 ```csharp title="AppHost.cs"
 var redis = builder.AddRedis("cache")
@@ -130,7 +131,7 @@ var redis = builder.AddRedis("cache")
 
 ## ポートとプロキシ
 
-サービス バインディングを定義するとき、ホスト ポートは _常に_ サービス手前のプロキシに割り当てられます。これにより、サービスが単一レプリカでも複数レプリカでも同様に動作できます。さらに、`WithReference` API を使うすべてのリソース依存関係は、環境変数経由で渡されるプロキシ エンドポイントに依存します。
+サービス バインディングを定義するとき、ホスト ポートは _常に_ サービス手前のプロキシに割り当てられます。これにより、サービスが単一レプリカでも複数レプリカでも同様に動作できます。さらに、<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> API を使うすべてのリソース依存関係は、環境変数経由で渡されるプロキシ エンドポイントに依存します。
 
 サービスが複数レプリカで動作する場合にも、同じプロキシ パターンが適用されます。ブラウザーは引き続き 1 つの安定したホスト ポートに接続し、プロキシが利用可能なレプリカへトラフィックを振り分けます:
 
@@ -328,7 +329,7 @@ var adminApp = builder.AddProject<Projects.Admin>("admin")
 
 **よくある原因**:
 - コンテナーの起動がまだ完了していない
-- `WaitFor()` 依存関係が不足している
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> 依存関係が不足している
 - コンテナー ネットワーク上のコンテナーに、ホスト側から接続しようとしている
 
 **解決策**:
diff --git a/src/frontend/src/content/docs/ja/fundamentals/persist-data-volumes.mdx b/src/frontend/src/content/docs/ja/fundamentals/persist-data-volumes.mdx
index 9efb35d1ff..be3c8c47bf 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/persist-data-volumes.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/persist-data-volumes.mdx
@@ -4,6 +4,7 @@ description: コンテナーでボリュームとバインド マウントを使
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire プロジェクトを開始して停止するたびに、アプリはアプリ リソース コンテナーも作成し、破棄します。デバッグ セッション中にそれらのコンテナーに保存されたデータやファイルは、次のセッションでは失われます。多くの開発チームは、たとえば実行のたびにサンプル データでデータベースを再投入しなくて済むように、デバッグ セッション間でこのデータを保持したいと考えます。
 
@@ -35,7 +36,7 @@ Aspire プロジェクトを開始して停止するたびに、アプリはア
 
 ## ボリュームの使用
 
-ボリュームはコンテナーによって生成されるデータを保持するための推奨方法で、Windows と Linux の両方でサポートされています。ボリュームは複数のコンテナーのデータを同時に保存でき、高いパフォーマンスを提供し、バックアップや移行も容易です。Aspire では `WithVolume` メソッドを使って各リソース コンテナーのボリュームを構成します。このメソッドは 3 つのパラメーターを受け取ります:
+ボリュームはコンテナーによって生成されるデータを保持するための推奨方法で、Windows と Linux の両方でサポートされています。ボリュームは複数のコンテナーのデータを同時に保存でき、高いパフォーマンスを提供し、バックアップや移行も容易です。Aspire では <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithVolume" /> メソッドを使って各リソース コンテナーのボリュームを構成します。このメソッドは 3 つのパラメーターを受け取ります:
 
 - **`name`**: ボリュームの省略可能な名前。
 - **`target`**: 保持したいデータのコンテナー内ターゲット パス。
@@ -99,7 +100,7 @@ const sqldb = await sql.addDatabase("sqldb");
 
 この例では `/var/opt/mssql` がコンテナー内のデータベース ファイルへのパスを設定します。
 
-すべての Aspire コンテナー リソースでボリュームを利用でき、さらに一部ではリソースから派生した名前付きボリュームを追加するための便利な API が提供されています。`WithDataVolume` メソッドを例にすると、次のコードは先ほどの例と機能的に等価ですが、より簡潔です:
+すべての Aspire コンテナー リソースでボリュームを利用でき、さらに一部ではリソースから派生した名前付きボリュームを追加するための便利な API が提供されています。<ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataVolume" /> メソッドを例にすると、次のコードは先ほどの例と機能的に等価ですが、より簡潔です:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -128,7 +129,7 @@ AppHost プロジェクト名が `VolumeMount.AppHost` の場合、`WithDataVolu
 
 ## バインド マウントの使用
 
-バインド マウントを使うと、コンテナー内部とホスト マシン上のプロセスの両方からデータへアクセスできます。たとえばバインド マウントを確立した後、ホスト コンピューター上でそこにファイルをコピーできます。そのファイルはリソースのコンテナー内でバインド先パスから利用できます。Aspire では `WithBindMount` メソッドを使って各リソース コンテナーのバインド マウントを構成します。このメソッドは 3 つのパラメーターを受け取ります:
+バインド マウントを使うと、コンテナー内部とホスト マシン上のプロセスの両方からデータへアクセスできます。たとえばバインド マウントを確立した後、ホスト コンピューター上でそこにファイルをコピーできます。そのファイルはリソースのコンテナー内でバインド先パスから利用できます。Aspire では <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBindMount" /> メソッドを使って各リソース コンテナーのバインド マウントを構成します。このメソッドは 3 つのパラメーターを受け取ります:
 
 - **`source`**: コンテナーにマウントするホスト マシン上のフォルダーへのパス。
 - **`target`**: フォルダーのコンテナー内ターゲット パス。
@@ -162,7 +163,7 @@ const sqldb = await sql.addDatabase("sqldb");
 - `source: @"C:\SqlServer\Data"` は、バインドされるホスト コンピューター上のフォルダーを設定します。
 - `target: "/var/opt/mssql"` は、コンテナー内のデータベース ファイルへのパスを設定します。
 
-ボリュームと同様に、一部の Aspire コンテナー リソースではバインド マウントを追加するための便利な API が提供されています。`WithDataBindMount` メソッドを例にすると、次のコードは先ほどの例と機能的に等価ですが、より簡潔です:
+ボリュームと同様に、一部の Aspire コンテナー リソースではバインド マウントを追加するための便利な API が提供されています。<ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithDataBindMount" /> メソッドを例にすると、次のコードは先ほどの例と機能的に等価ですが、より簡潔です:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
@@ -210,7 +211,7 @@ const sqldb = await sql.addDatabase("sqldb");
 </TabItem>
 </Tabs>
 
-`AddSqlServer` 呼び出し時に `password` パラメーターを指定しないため、Aspire は SQL Server リソース用パスワードを自動生成します。
+<ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.AddSqlServer" /> 呼び出し時に `password` パラメーターを指定しないため、Aspire は SQL Server リソース用パスワードを自動生成します。
 
 <Aside type="caution">
   これは永続パスワードではありません。代わりに AppHost を実行するたびに
@@ -237,7 +238,7 @@ aspire secret set Parameters:sql-password <password>
 | RabbitMQ      | [📦 Aspire.Hosting.RabbitMq](https://www.nuget.org/packages/Aspire.Hosting.RabbitMq)     | `rabbitmq`            | `Parameters:rabbitmq-password`   |
 | SQL Server    | [📦 Aspire.Hosting.SqlServer](https://www.nuget.org/packages/Aspire.Hosting.SqlServer)   | `sql`                 | `Parameters:sql-password`        |
 
-生成されたパスワードを上書きすることで、アプリ起動間でパスワードを一貫して保てます。別の方法として `AddParameter` メソッドを使用し、パスワードとして利用できるパラメーターを作成することもできます。次のコードは SQL Server リソースの永続パスワードを作成する方法を示しています:
+生成されたパスワードを上書きすることで、アプリ起動間でパスワードを一貫して保てます。別の方法として <ApiReference name="Aspire.Hosting.ParameterResourceBuilderExtensions.AddParameter" /> メソッドを使用し、パスワードとして利用できるパラメーターを作成することもできます。次のコードは SQL Server リソースの永続パスワードを作成する方法を示しています:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/ja/fundamentals/service-discovery.mdx b/src/frontend/src/content/docs/ja/fundamentals/service-discovery.mdx
index 2fbfebc8df..0c69b70267 100644
--- a/src/frontend/src/content/docs/ja/fundamentals/service-discovery.mdx
+++ b/src/frontend/src/content/docs/ja/fundamentals/service-discovery.mdx
@@ -4,12 +4,13 @@ description: Aspire における重要なサービス検出の概念を理解し
 ---
 
 import { Aside, Tabs, TabItem } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 サービス検出は、サービス同士が互いを見つけるための仕組みです。`http://localhost:5001` のような URL をハードコーディングする代わりに、フロントエンドは `catalog` サービスを名前で参照するだけで、実際のアドレス解決は Aspire が担当します。
 
 ## サービス検出の仕組み
 
-`WithReference()` を使ってサービスを接続すると、Aspire は自動的にサービス検出を構成します。
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> を使ってサービスを接続すると、Aspire は自動的にサービス検出を構成します。
 
 1. **AppHost がリソースを宣言** してエンドポイントを割り当てる
 2. **構成が注入される** 各サービスに環境変数経由で構成が渡される
@@ -342,7 +343,7 @@ const response = await fetch(`${dashboardUrl}/api/stats`);
 
 **よくある原因**:
 1. **`WithReference()` の不足**: 呼び出し元サービスが AppHost で対象サービスに接続されていない
-2. **サービス名の不一致**: URI 内の名前が `AddProject()` または `AddContainer()` の名前と一致していない
+2. **サービス名の不一致**: URI 内の名前が <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> または <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddContainer" /> の名前と一致していない
 3. **サービス未起動**: 対象サービスが起動に失敗している、または起動中である
 
 **対処方法**: AppHost でサービス同士が接続されていることを確認します。
diff --git a/src/frontend/src/content/docs/ja/get-started/add-aspire-existing-app.mdx b/src/frontend/src/content/docs/ja/get-started/add-aspire-existing-app.mdx
index 3583a96743..e9664c9b5e 100644
--- a/src/frontend/src/content/docs/ja/get-started/add-aspire-existing-app.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/add-aspire-existing-app.mdx
@@ -8,6 +8,7 @@ import { Steps, TabItem, Tabs } from '@astrojs/starlight/components';
 import FileTree from 'starlight-plugin-icons/components/FileTree.astro';
 import { Kbd } from 'starlight-kbd/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 新しいテンプレートを基準にソリューションを作り直す代わりに、すでにあるアプリへ Aspire を追加しましょう。最短ルートは `aspire init` と AI コーディング エージェントの組み合わせです。これによりサービスを自動検出し、 AppHost へ配線できます。より細かく制御したい場合は、下に手動手順も用意しています。
 
@@ -64,7 +65,7 @@ Aspire は段階的にも導入できます。まずは、コンテナー、デ
 
    - リポジトリをスキャンし、既存のプロジェクト、サービス、コンテナー、インフラストラクチャを検出する
    - 検出したリソース、含める対象、その他の確認事項を開始前に質問する
-   - `WithReference`、 `WaitFor`、エンドポイント、ボリュームを使って AppHost へ配線する
+   - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" />、 <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" />、エンドポイント、ボリュームを使って AppHost へ配線する
    - 各サービスに ServiceDefaults を追加し、 OpenTelemetry を構成する
    - `aspire start` を実行してセットアップを検証する
 
@@ -98,7 +99,7 @@ Aspire には C# AppHost のスタイルが 2 つあります:
 
 **ファイル ベース AppHost** - `#:sdk` と `#:package` ディレクティブを使う単一の `apphost.cs` ファイルです。 `.csproj` もソリューション統合も不要です。ポリグロット リポジトリや迅速なセットアップに最適です。
 
-**プロジェクト ベース AppHost** - 既存の C# プロジェクトと一緒に `.sln` 内で管理される従来型の `AppHost.csproj` です。 `ProjectReference` 項目と生成される `Projects` 名前空間を使い、型付きの `AddProject<T>()` 呼び出しを行います。すでにリポジトリが .NET ソリューションで、 IDE 統合されたオーケストレーションを望む場合に最適です。
+**プロジェクト ベース AppHost** - 既存の C# プロジェクトと一緒に `.sln` 内で管理される従来型の `AppHost.csproj` です。 `ProjectReference` 項目と生成される `Projects` 名前空間を使い、型付きの <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> 呼び出しを行います。すでにリポジトリが .NET ソリューションで、 IDE 統合されたオーケストレーションを望む場合に最適です。
 
 どちらのスタイルも同じ `Aspire.AppHost.Sdk` と同じホスティング API を使用します。
 
@@ -178,7 +179,7 @@ TypeScript AppHost は、リポジトリが Node.js ワークスペース中心
 </FileTree>
 
 :::caution[AddCSharpApp は実験的機能です]
-`AddCSharpApp` は現在実験的機能です。制限事項や診断抑制の詳細は、 [C# file-based apps](/ja/integrations/dotnet/csharp-file-based-apps/) を参照してください。
+<ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" /> は現在実験的機能です。制限事項や診断抑制の詳細は、 [C# file-based apps](/ja/integrations/dotnet/csharp-file-based-apps/) を参照してください。
 :::
 
 #### プロジェクト ベース AppHost（ .sln あり）
@@ -401,7 +402,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-ワークロードに専用ホスティング API がまだない場合でも、 `AddExecutable` または `addExecutable` を使って実行可能リソースとしてモデル化すれば、同じアプリケーション モデルに参加させられます。
+ワークロードに専用ホスティング API がまだない場合でも、 <ApiReference name="Aspire.Hosting.ExecutableResourceBuilderExtensions.AddExecutable" /> を使って実行可能リソースとしてモデル化すれば、同じアプリケーション モデルに参加させられます。
 
 <LearnMore>
 ファーストクラス ワークロードのガイダンスは、 [JavaScript integration](/ja/integrations/frameworks/javascript/)、 [Python integration](/ja/integrations/frameworks/python/)、 [Multi-language architecture](/ja/architecture/multi-language-architecture/) を参照してください。
diff --git a/src/frontend/src/content/docs/ja/get-started/aspire-mcp-server.mdx b/src/frontend/src/content/docs/ja/get-started/aspire-mcp-server.mdx
index fd30ebc98a..d5dd9b1863 100644
--- a/src/frontend/src/content/docs/ja/get-started/aspire-mcp-server.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/aspire-mcp-server.mdx
@@ -5,6 +5,7 @@ description: AI コーディングエージェント向けの Aspire MCP サー
 
 import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 :::note
 Aspire ダッシュボードに組み込まれていた MCP サーバーは削除されました。[`aspire agent mcp`](/ja/reference/cli/commands/aspire-agent-mcp/) CLI コマンドが Aspire MCP サーバーを起動する方法になりました。
@@ -121,7 +122,7 @@ Aspire MCP サーバーは、AI エージェントに次のツールを提供し
 
 ### MCP からリソースを除外する
 
-デフォルトでは、すべてのリソース、コンソールログ、テレメトリが MCP サーバーを通じてアクセス可能です。`ExcludeFromMcp()` でアノテーションを付けることで、特定のリソースとそれに関連するテレメトリを除外できます:
+デフォルトでは、すべてのリソース、コンソールログ、テレメトリが MCP サーバーを通じてアクセス可能です。<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromMcp" /> でアノテーションを付けることで、特定のリソースとそれに関連するテレメトリを除外できます:
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='C#'>
diff --git a/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
index e22c7d0c1f..da9cffbc2b 100644
--- a/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
@@ -13,6 +13,7 @@ import sidebarTreeLight from '@assets/get-started/code-extension-sidebar-light.p
 import debugSessions from '@assets/get-started/code-extension-debug.png';
 import debugSessionsLight from '@assets/get-started/code-extension-debug-light.png';
 import { Kbd } from 'starlight-kbd/components';
+import ApiReference from '@components/ApiReference.astro';
 
 [Visual Studio Code](https://code.visualstudio.com/) 用の公式 Aspire 拡張機能は、ポリグロットな Aspire アプリの構築、デバッグ、リリースを一流の体験で行える環境へ VS Code を進化させます。
 <Kbd windows='F5' /> を押すだけで、AppHost のビルド、リソースの起動、サポート対象リソース (C#、TypeScript、Python、ブラウザー アプリ、Azure Functions) のデバッグを、Aspire ダッシュボードと並行して実行できます。
@@ -115,7 +116,7 @@ Aspire は VS Code に AppHost ビューを登録します。**Workspace** モ
 ```
 
 サポートされている起動コマンドは次の 4 つです:
-- `run` は AppHost を実行します (省略した場合の既定)。
+- <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> は AppHost を実行します (省略した場合の既定)。
 - `deploy` は、AppHost で定義されたデプロイ先にプッシュします。
 - `publish` は、ターゲットへのプッシュを行わずに、Kubernetes マニフェストや Bicep ファイルなどのデプロイ成果物を生成します。
 - `do` は、AppHost のデプロイ パイプラインで定義された特定のステップを実行します。`step` には、実行するステップ名を設定します。
diff --git a/src/frontend/src/content/docs/ja/get-started/deploy-first-app.mdx b/src/frontend/src/content/docs/ja/get-started/deploy-first-app.mdx
index 2eccd3c809..204a19156e 100644
--- a/src/frontend/src/content/docs/ja/get-started/deploy-first-app.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/deploy-first-app.mdx
@@ -17,6 +17,7 @@ import dockerIcon from '@assets/icons/docker.svg';
 import csharpStarterPng from '@assets/get-started/csharp-starter.png';
 import javascriptStarterDarkPng from '@assets/get-started/javascript-starter-dark.png';
 import javascriptStarterLightPng from '@assets/get-started/javascript-starter-light.png';
+import ApiReference from '@components/ApiReference.astro';
 
 <PivotSelector
     title="プログラミング言語を選択してください"
@@ -90,7 +91,7 @@ architecture-beta
 React (Vite) および Express スターター テンプレートは、単一のコンテナーとしてデプロイされる 2 つのリソースで構成されます。 Express サーバーは、API と React によって生成された静的フロントエンド ファイルの両方をホストします。
 
 <LearnMore>
-このチュートリアルでは、**バックエンドがフロントエンドにサービスを提供する** デプロイメント モデルを使用します。リバース プロキシやゲートウェイ/BFF アプローチなど、`AddViteApp` と `AddJavaScriptApp` で利用できる他の運用パターンについては、[JavaScript アプリをデプロイする](/ja/deployment/javascript-apps/) を参照してください。
+このチュートリアルでは、**バックエンドがフロントエンドにサービスを提供する** デプロイメント モデルを使用します。リバース プロキシやゲートウェイ/BFF アプローチなど、<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> と <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" /> で利用できる他の運用パターンについては、[JavaScript アプリをデプロイする](/ja/deployment/javascript-apps/) を参照してください。
 </LearnMore>
 
 </Pivot>
@@ -266,8 +267,8 @@ AppHost で、適切な環境 API メソッドへの呼び出しを連鎖させ
     builder.Build().Run();
     ```
 
-    - `AddDockerComposeEnvironment` - デプロイ用に Docker Compose 環境を構成します。この呼び出しにより、デプロイの一部として AppHost 内のリソースをコンテナー化するサポートが暗黙的に追加されます。
-    - `WithExternalHttpEndpoints` - デプロイ時にリソースの HTTP エンドポイントを公開します。
+    - <ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.AddDockerComposeEnvironment" /> - デプロイ用に Docker Compose 環境を構成します。この呼び出しにより、デプロイの一部として AppHost 内のリソースをコンテナー化するサポートが暗黙的に追加されます。
+    - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExternalHttpEndpoints" /> - デプロイ時にリソースの HTTP エンドポイントを公開します。
 
   </TabItem>
   <TabItem id="azure" label="Azure">
@@ -290,7 +291,7 @@ AppHost で、適切な環境 API メソッドへの呼び出しを連鎖させ
     builder.Build().Run();
     ```
 
-    - `AddAzureContainerAppEnvironment` - デプロイ用に Azure App Container 環境を構成します。この呼び出しにより、デプロイの一部として AppHost 内のリソースをコンテナー化するサポートが暗黙的に追加されます。
+    - <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" /> - デプロイ用に Azure App Container 環境を構成します。この呼び出しにより、デプロイの一部として AppHost 内のリソースをコンテナー化するサポートが暗黙的に追加されます。
     - `WithExternalHttpEndpoints` - デプロイ時にリソースの HTTP エンドポイントを公開します。
 
   </TabItem>
diff --git a/src/frontend/src/content/docs/ja/get-started/faq.mdx b/src/frontend/src/content/docs/ja/get-started/faq.mdx
index 5236cc4274..478d02a0b2 100644
--- a/src/frontend/src/content/docs/ja/get-started/faq.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/faq.mdx
@@ -3,6 +3,8 @@ title: よくある質問 (FAQ)
 description: AppHost、ダッシュボード、統合、TypeScript サポート、デプロイ、そして Aspire と他ツールの比較を含む、Aspire に関するよくある質問への回答です。
 ---
 
+import ApiReference from '@components/ApiReference.astro';
+
 このページでは、Aspire とは何か、ワークフローにどう適合するのか、何ができるのか、そして他のテクノロジとどう違うのかについて、よくある質問に答えます。
 
 ## Aspire とは何ですか?
@@ -96,8 +98,8 @@ Aspire は、AI エージェントや Copilot と、人間の開発者と同じ
 Aspire はマルチ言語プラットフォームです。AppHost は **C# または TypeScript** で記述できます。サービスは任意の言語で記述できます:
 
 - **C# / .NET** — 第一級のプロジェクト参照、サービス既定値、統合
-- **Python** — uv/pip/venv パッケージ管理と Dockerfile 自動生成を備えた `AddPythonApp`、`AddUvicornApp`、`AddPythonModule`
-- **JavaScript / TypeScript** — npm/yarn/pnpm 自動検出を備えた `AddJavaScriptApp`、`AddViteApp`、`AddNodeApp`
+- **Python** — uv/pip/venv パッケージ管理と Dockerfile 自動生成を備えた <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" />、<ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddUvicornApp" />、<ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonModule" />
+- **JavaScript / TypeScript** — npm/yarn/pnpm 自動検出を備えた <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" />、<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" />、<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" />
 - **Go, Java, Rust** — コミュニティ ツールキット統合とコード生成パッケージ経由
 - **任意のコンテナー化アプリ** — コンテナーで動作するものはすべて AppHost に追加可能
 
diff --git a/src/frontend/src/content/docs/ja/get-started/first-app.mdx b/src/frontend/src/content/docs/ja/get-started/first-app.mdx
index 5f020c9c5b..ff5552d78d 100644
--- a/src/frontend/src/content/docs/ja/get-started/first-app.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/first-app.mdx
@@ -12,6 +12,7 @@ import {
   TabItem,
   Icon,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import FileTree from 'starlight-plugin-icons/components/FileTree.astro';
 import { Kbd } from 'starlight-kbd/components'
 import LearnMore from '@components/LearnMore.astro';
@@ -220,11 +221,11 @@ architecture-beta
 
     _何が起きているのでしょうか？_
 
-    - `CreateBuilder` は、分散アプリケーション用のビルダーを作成します。
-    - `AddProject` は、API サービスと Web フロントエンドを登録します。
-    - `WithReference` は、サービス間の接続を作成します。（Web アプリが API を呼び出せるようにします。）
-    - `WaitFor` は、サービスが正しい順序で起動するように制御します。
-    - `WithHttpHealthCheck` は、サービスの正常性状態を監視します。
+    - <ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" /> は、分散アプリケーション用のビルダーを作成します。
+    - <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> は、API サービスと Web フロントエンドを登録します。
+    - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> は、サービス間の接続を作成します。（Web アプリが API を呼び出せるようにします。）
+    - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> は、サービスが正しい順序で起動するように制御します。
+    - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithHttpHealthCheck" /> は、サービスの正常性状態を監視します。
     
     </Pivot>
     <Pivot id="python">
@@ -251,12 +252,12 @@ architecture-beta
 
     _何が起きているのでしょうか？_
     
-    - `AddUvicornApp` は、Uvicorn ベースの Python アプリを追加します。
+    - <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddUvicornApp" /> は、Uvicorn ベースの Python アプリを追加します。
     - `AddUv` は、`uv sync` を実行する Uv の環境セットアップタスクを追加します。
-    - `AddViteApp` は、React フロントエンドを登録します。
+    - <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> は、React フロントエンドを登録します。
     - `WithReference` は、フロントエンドと API を接続します。
     - `WaitFor` は、フロントエンドより先に API が起動するよう順序を制御します。
-    - `PublishWithContainerFiles` は、フロントエンドを本番デプロイ向けにバンドルします。
+    - <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" /> は、フロントエンドを本番デプロイ向けにバンドルします。
 
     </Pivot>
 
diff --git a/src/frontend/src/content/docs/ja/get-started/resource-mcp-servers.mdx b/src/frontend/src/content/docs/ja/get-started/resource-mcp-servers.mdx
index b46dc260ea..fee3a59b67 100644
--- a/src/frontend/src/content/docs/ja/get-started/resource-mcp-servers.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/resource-mcp-servers.mdx
@@ -5,12 +5,13 @@ description: Aspire リソースから MCP ツールを公開し、CLI を使用
 
 import { Aside, Code, Steps, Tabs, TabItem } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire リソースは、独自の <abbr title="Model Context Protocol" data-tooltip-placement="top">MCP</abbr> (Model Context Protocol) サーバーを公開でき、AI コーディング エージェントがデータベース、API、その他のサービスと直接対話できるようにします。例えば、PostgreSQL リソースは SQL クエリ ツールを公開でき、エージェントが会話を終了することなくクエリを実行できます。
 
 ## 仕組み
 
-AppHost で `WithMcpServer()` で注釈が付けられたリソースの場合、Aspire は MCP エンドポイントを検出し、そのツールを 2 つの方法で利用可能にします。
+AppHost で <ApiReference name="Aspire.Hosting.McpServerResourceBuilderExtensions.WithMcpServer" /> で注釈が付けられたリソースの場合、Aspire は MCP エンドポイントを検出し、そのツールを 2 つの方法で利用可能にします。
 
 - **Aspire MCP サーバーを通じて** — リソース ツールが、組み込みの [Aspire MCP サーバー](/ja/get-started/aspire-mcp-server/) ツールと共に自動的にプロキシされます。AI エージェントは追加の構成なしでツール リストにそれらを表示します。
 - **CLI を通じて** — `aspire mcp tools` と `aspire mcp call` を使用してリソース ツールをターミナルから直接検出して呼び出します。
@@ -54,7 +55,7 @@ await builder.build().run();
 </Tabs>
 
 <Aside type="note">
-`WithMcpServer()` と `WithPostgresMcp()` は実験的な API です。これらを使用するには `ASPIREMCP001` または `ASPIREPOSTGRES001` の診断を抑制します。
+`WithMcpServer()` と <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithPostgresMcp" /> は実験的な API です。これらを使用するには `ASPIREMCP001` または `ASPIREPOSTGRES001` の診断を抑制します。
 </Aside>
 
 ## 利用可能なツールを検出する
diff --git a/src/frontend/src/content/docs/ja/get-started/troubleshooting.mdx b/src/frontend/src/content/docs/ja/get-started/troubleshooting.mdx
index 356b21e5cd..b065c9ac37 100644
--- a/src/frontend/src/content/docs/ja/get-started/troubleshooting.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/troubleshooting.mdx
@@ -7,6 +7,7 @@ import { Aside, Code, Steps } from '@astrojs/starlight/components';
 import { Kbd } from 'starlight-kbd/components';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire の導入で問題が発生していますか? このページでは、開発者がよく遭遇する代表的な問題の解決策を紹介します。
 
@@ -72,7 +73,7 @@ Aspire の導入で問題が発生していますか? このページでは、
 
 **症状**: フロントエンドが API に接続できず、connection refused エラーが表示されます。
 
-**解決策**: AppHost で `WaitFor()` を使用していることを確認してください:
+**解決策**: AppHost で <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WaitFor" /> を使用していることを確認してください:
 
 ```csharp title="AppHost.cs"
 builder.AddProject<Projects.WebFrontend>("frontend")
@@ -84,7 +85,7 @@ builder.AddProject<Projects.WebFrontend>("frontend")
 
 **症状**: サービスで、注入されるはずの接続文字列や構成を見つけられません。
 
-**解決策**: リソース接続に `WithReference()` を使用していることを確認してください。
+**解決策**: リソース接続に <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> を使用していることを確認してください。
 
 ### 例: サービスにデータベースを接続する
 
diff --git a/src/frontend/src/content/docs/ja/integrations/dotnet/launch-profiles.mdx b/src/frontend/src/content/docs/ja/integrations/dotnet/launch-profiles.mdx
index 0ed14b3e71..8ee8f5f459 100644
--- a/src/frontend/src/content/docs/ja/integrations/dotnet/launch-profiles.mdx
+++ b/src/frontend/src/content/docs/ja/integrations/dotnet/launch-profiles.mdx
@@ -6,6 +6,7 @@ description: C# AppHost とサービス プロジェクト向けに、Aspire が
 import { Image } from 'astro:assets';
 import { Aside, Steps } from '@astrojs/starlight/components';
 import dotnetIcon from '@assets/icons/dotnet.svg';
+import ApiReference from '@components/ApiReference.astro';
 
 <Image
   src={dotnetIcon}
@@ -106,13 +107,13 @@ Aspire テンプレートでは、通常の ASP.NET Core アプリケーショ
 
 C# AppHost は、複数のサービス プロジェクトの起動を調整する責任を担います。コマンド ライン、Visual Studio、または別の開発環境から AppHost を実行すると、AppHost 用の起動プロファイルが選択されます。続いて AppHost は、起動するサービス プロジェクト内で一致する起動プロファイルを見つけようとし、そのオプションを使ってサービス プロジェクトの環境と既定のネットワーク構成を制御します。
 
-AppHost がサービス プロジェクトを起動する場合、`--launch-profile` オプションを直接使うわけではありません。代わりに、Aspire は有効な起動プロファイルを解決し、`dotnet run` および `dotnet watch` との整合性のために `DOTNET_LAUNCH_PROFILE` を設定し、（起動プロファイルの `applicationUrl` フィールドから導出される）`ASPNETCORE_URLS` 環境変数を別のポートになるよう調整します。既定では、Aspire は `WithReplicas` を通じた複数インスタンスのサポートのため、ASP.NET Core アプリケーションの前段にリバース プロキシを挿入します。
+AppHost がサービス プロジェクトを起動する場合、`--launch-profile` オプションを直接使うわけではありません。代わりに、Aspire は有効な起動プロファイルを解決し、`dotnet run` および `dotnet watch` との整合性のために `DOTNET_LAUNCH_PROFILE` を設定し、（起動プロファイルの `applicationUrl` フィールドから導出される）`ASPNETCORE_URLS` 環境変数を別のポートになるよう調整します。既定では、Aspire は <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.WithReplicas" /> を通じた複数インスタンスのサポートのため、ASP.NET Core アプリケーションの前段にリバース プロキシを挿入します。
 
 `environmentVariables` などのその他の設定は、変更せずにアプリケーションへ渡されます。
 
 ## 起動プロファイル選択の制御
 
-理想的には、AppHost とそのサービス プロジェクトの間で起動プロファイル名をそろえることで、AppHost 側でプロファイルを切り替えると連携する全プロジェクトでも一括で切り替えられます。ただし、`AddProject` に `launchProfileName` を渡すことで、特定プロジェクトで使うプロファイルを指定することもできます:
+理想的には、AppHost とそのサービス プロジェクトの間で起動プロファイル名をそろえることで、AppHost 側でプロファイルを切り替えると連携する全プロジェクトでも一括で切り替えられます。ただし、<ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" /> に `launchProfileName` を渡すことで、特定プロジェクトで使うプロファイルを指定することもできます:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -139,7 +140,7 @@ builder.Build().Run();
 
 ## ASP.NET Core プロジェクト向けの起動プロファイルとエンドポイント
 
-ASP.NET Core プロジェクトを AppHost に追加する際、Aspire は _launchSettings.json_ ファイルを解析し、適切な起動プロファイルを選択して、`applicationUrl` フィールド内の URL に基づきアプリケーション モデル内へエンドポイントを自動生成します。自動挿入されたエンドポイントを変更するには `WithEndpoint` を使用します:
+ASP.NET Core プロジェクトを AppHost に追加する際、Aspire は _launchSettings.json_ ファイルを解析し、適切な起動プロファイルを選択して、`applicationUrl` フィールド内の URL に基づきアプリケーション モデル内へエンドポイントを自動生成します。自動挿入されたエンドポイントを変更するには <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> を使用します:
 
 ```csharp title="AppHost.cs"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/ja/testing/accessing-resources.mdx b/src/frontend/src/content/docs/ja/testing/accessing-resources.mdx
index 77ee35f81b..da061c3001 100644
--- a/src/frontend/src/content/docs/ja/testing/accessing-resources.mdx
+++ b/src/frontend/src/content/docs/ja/testing/accessing-resources.mdx
@@ -4,6 +4,7 @@ description: テストから Aspire の AppHost に定義されたリソース
 ---
 
 import { Aside } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 
 この記事では、テストから Aspire AppHost に含まれるリソースへアクセスする方法について学びます。AppHost はアプリケーション全体の実行環境を表しており、アプリケーションで利用可能なすべてのリソースを含んでいます。Aspire を使って機能テストや統合テストを書く際、アプリケーションの挙動を検証するために、これらのリソースへアクセスする必要が出てくることがあります。
 
@@ -47,7 +48,7 @@ await app.ResourceNotifications.WaitForResourceHealthyAsync(
 
 ## 開始と停止
 
-場合によっては、最初は起動されていないリソースを手動で開始したいことがあります。たとえば、そのリソースが `WithExplicitStart` によって作成された場合などです。
+場合によっては、最初は起動されていないリソースを手動で開始したいことがあります。たとえば、そのリソースが <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithExplicitStart" /> によって作成された場合などです。
 
 ```csharp
 using var cts = new CancellationTokenSource(TimeSpan.FromSeconds(30));
diff --git a/src/frontend/src/content/docs/ja/testing/write-your-first-test.mdx b/src/frontend/src/content/docs/ja/testing/write-your-first-test.mdx
index 324ab7075e..ef511c4839 100644
--- a/src/frontend/src/content/docs/ja/testing/write-your-first-test.mdx
+++ b/src/frontend/src/content/docs/ja/testing/write-your-first-test.mdx
@@ -7,6 +7,7 @@ import { Aside, Steps } from '@astrojs/starlight/components';
 import LearnMore from '@components/LearnMore.astro';
 import PivotSelector from '@components/PivotSelector.astro';
 import Pivot from '@components/Pivot.astro';
+import ApiReference from '@components/ApiReference.astro';
 
 <PivotSelector
     title="使用するテストフレームワークを選択してください"
@@ -516,7 +517,7 @@ public class EnvVarTests
 
 - `DistributedApplicationTestingBuilder.CreateAsync` API を利用して、AppHost を非同期に作成しています。
 - `builder` インスタンスの `Resources` プロパティから 「webfrontend」 という名前の `IResourceWithEnvironment` インスタンスを取得しています。
-- `ExecutionConfigurationBuilder` を使用して `webfrontend` リソースの `ExecutionConfiguration` を構築し、`WithEnvironmentVariablesConfig` によって環境変数の構成を明示的に有効化しています。
+- `ExecutionConfigurationBuilder` を使用して `webfrontend` リソースの `ExecutionConfiguration` を構築し、<ApiReference name="Aspire.Hosting.ApplicationModel.ExecutionConfigurationBuilderExtensions.WithEnvironmentVariablesConfig" /> によって環境変数の構成を明示的に有効化しています。
 - `DistributedApplicationOperation.Publish` を指定して `BuildAsync` を呼び出し、未解決のバインディング式を含む、そのリソースに対して公開される環境変数を生成しています。
 - 返却された環境変数を用いて、テストでは `webfrontend` リソースが `apiservice` リソースへ解決される HTTPS の環境変数が存在することを検証しています。
 
diff --git a/src/frontend/src/content/docs/ja/whats-new/aspire-13-1.mdx b/src/frontend/src/content/docs/ja/whats-new/aspire-13-1.mdx
index bbe2fcaeb9..041e81510f 100644
--- a/src/frontend/src/content/docs/ja/whats-new/aspire-13-1.mdx
+++ b/src/frontend/src/content/docs/ja/whats-new/aspire-13-1.mdx
@@ -17,6 +17,7 @@ import ThemeImage from '@components/ThemeImage.astro';
 import { Code, Tabs, Steps, TabItem, Aside, Icon } from '@astrojs/starlight/components';
 import resourcesParametersView from '@assets/whats-new/resources-parameters-view.png';
 import genaiVisualizerTooldefinitions from '@assets/whats-new/genai-visualizer-tooldefinitions.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.1 は、Aspire 13 で確立されたポリグロット基盤をさらに発展させ、CLI 体験の大幅な改善、AI コーディングエージェント向けの MCP（Model Context Protocol）サポートの強化、ダッシュボードの改良、Azure へのデプロイの簡素化を提供します。本リリースは、開発者の生産性向上と、最新の AI 支援開発ワークフローとのシームレスな統合に重点を置いています。
 
@@ -25,7 +26,7 @@ Aspire 13.1 は、Aspire 13 で確立されたポリグロット基盤をさら
 - **AI コーディングエージェント向け MCP**: 新しい `aspire agent init` コマンドと、AI アシスタントが統合を発見し Aspire アプリケーションと連携するための MCP ツール。
 - **CLI の強化**: チャネルの永続化、自動インスタンス検出、インストールパスのオプション。
 - **ダッシュボードの改善**: 専用の Parameters タブと生成 AI ビジュアライザーの強化。
-- **Azure マネージド Redis**: `AddAzureRedisEnterprise` から `AddAzureManagedRedis` へ名称変更し、検証を改善。
+- **Azure マネージド Redis**: `AddAzureRedisEnterprise` から <ApiReference name="Aspire.Hosting.AzureManagedRedisExtensions.AddAzureManagedRedis" /> へ名称変更し、検証を改善。
 - **コンテナー レジストリ サポート**: 汎用コンテナー レジストリ向けの新しい `ContainerRegistryResource`。
 - **JavaScript の改善**: 新しいフロントエンド スターター テンプレート、Vite の HTTPS 設定、pnpm の修正。
 - **DevTunnels の安定化**: [📦 Aspire.Hosting.DevTunnels](https://www.nuget.org/packages/Aspire.Hosting.DevTunnels) が安定版パッケージになりました。
@@ -210,7 +211,7 @@ Azure リソースは、すべての対応言語で利用できる標準化さ
 
 ### Azure App Service のデプロイ スロット
 
-Azure App Service のデプロイ スロットを構成するための、新しい `WithDeploymentSlot` 拡張メソッドが追加されました:
+Azure App Service のデプロイ スロットを構成するための、新しい <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.WithDeploymentSlot" /> 拡張メソッドが追加されました:
 
 ```csharp title="デプロイ スロットの構成"
 var builder = DistributedApplication.CreateBuilder(args);
@@ -221,7 +222,7 @@ builder.AddAzureAppServiceEnvironment("appservice")
 
 ### 既定のロール割り当てのクリア
 
-権限を細かく制御したい場合に、Azure リソースへの自動的なロール割り当てを無効化できる、新しい `ClearDefaultRoleAssignments` 拡張メソッドが追加されました。
+権限を細かく制御したい場合に、Azure リソースへの自動的なロール割り当てを無効化できる、新しい <ApiReference name="Aspire.Hosting.AzureResourceExtensions.ClearDefaultRoleAssignments" /> 拡張メソッドが追加されました。
 
 ### バグ修正
 
@@ -289,7 +290,7 @@ $ aspire do push
 
 ### Azure デプロイにおける明示的なコンテナー レジストリ サポート
 
-Aspire 13.1 以前では、`AddAzureContainerAppEnvironment` を使用して Azure Container Apps にデプロイする際、Azure Container Registry（ACR）は環境の一部として暗黙的にプロビジョニングされていました。この自動プロビジョニングにより、デプロイの遅延が発生したり、どのレジストリが使用されているのかを開発者が把握しにくいという課題がありました。
+Aspire 13.1 以前では、<ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" /> を使用して Azure Container Apps にデプロイする際、Azure Container Registry（ACR）は環境の一部として暗黙的にプロビジョニングされていました。この自動プロビジョニングにより、デプロイの遅延が発生したり、どのレジストリが使用されているのかを開発者が把握しにくいという課題がありました。
 
 Aspire 13.1 では、この点を改善するために、コンテナー レジストリを明示的に構成する方向へと変更され、イメージが「どこに」「いつ」プッシュされるのかについて、開発者がより高い制御性と可視性を得られるようになりました。以下の構成では、「myenv」環境に関連付けられた ACR が環境と並行してプロビジョニングされ、レジストリのプロビジョニングが完了し次第、イメージのプッシュが開始されます。
 
@@ -312,7 +313,7 @@ var api = builder.AddProject<Projects.Api>("api")
 - Docker Compose デプロイ後に、リソースのエンドポイントが表示されるようになりました。
 - パイプラインを並列実行した際に発生していた、Dockerfile のマテリアライズ処理における競合状態を修正しました。
 
-高度なシナリオでは、`ConfigureEnvFile` を使用して生成される `.env` ファイルをカスタマイズできます:
+高度なシナリオでは、<ApiReference name="Aspire.Hosting.DockerComposeEnvironmentExtensions.ConfigureEnvFile" /> を使用して生成される `.env` ファイルをカスタマイズできます:
 
 ```csharp title="Docker Compose の .env file をカスタマイズ"
 var builder = DistributedApplication.CreateBuilder(args);
diff --git a/src/frontend/src/content/docs/ja/whats-new/aspire-13-2.mdx b/src/frontend/src/content/docs/ja/whats-new/aspire-13-2.mdx
index ff9714479c..6ed80550ae 100644
--- a/src/frontend/src/content/docs/ja/whats-new/aspire-13-2.mdx
+++ b/src/frontend/src/content/docs/ja/whats-new/aspire-13-2.mdx
@@ -29,6 +29,7 @@ import manageDialog from '@assets/whats-new/aspire-13.2/manage-dialog.png';
 import exportJsonMenu from '@assets/whats-new/aspire-13.2/export-json-menu.png';
 import exportJsonDialog from '@assets/whats-new/aspire-13.2/export-json-dialog.png';
 import exportEnvDialog from '@assets/whats-new/aspire-13.2/export-env-dialog.png';
+import ApiReference from '@components/ApiReference.astro';
 
 Aspire 13.2 へようこそ!長年の Aspire ユーザーでも、これから始めたばかりでも、新しい機能を試していただけることを楽しみにしています。質問やフィードバックがある場合、または問題に遭遇した場合は、[Discord](https://aka.ms/aspire-discord) で挨拶するか、[GitHub](https://github.com/microsoft/aspire/issues) で issue を開いてください。
 
@@ -452,7 +453,7 @@ Aspire 13.2 で最も期待されている機能の 1 つは、TypeScript での
 
 ### TypeScript で apphost を書く
 
-TypeScript アプリホストは、`createBuilder()` を介して慣用的な TypeScript で表現された C# と同じアプリ モデル (リソース、参照、統合) を使用します。
+TypeScript アプリホストは、<ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" /> を介して慣用的な TypeScript で表現された C# と同じアプリ モデル (リソース、参照、統合) を使用します。
 
 ```typescript title="apphost.mts" twoslash
 import { createBuilder } from './.aspire/modules/aspire.mjs';
@@ -577,7 +578,7 @@ Aspire を使用して AI を多用するワークロードを検査している
 
 ### アプリモデルからの MCP エンドポイント
 
-Aspire 13.2 には `WithMcpServer` が追加されており、リソースが Model Context Protocol (MCP) サーバーをホストすることをアプリ モデル内で宣言できます。 Aspire ツールは、そのエンドポイントを直接検出してプロキシすることができます。
+Aspire 13.2 には <ApiReference name="Aspire.Hosting.McpServerResourceBuilderExtensions.WithMcpServer" /> が追加されており、リソースが Model Context Protocol (MCP) サーバーをホストすることをアプリ モデル内で宣言できます。 Aspire ツールは、そのエンドポイントを直接検出してプロキシすることができます。
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -629,7 +630,7 @@ OpenTelemetry Protocol (OTLP) エンドポイントは、アプリケーショ
 
 ### シークレットと証明書の処理の改善
 
-13.2 では、コンテナー ビルド シークレットの API がより明確になりました。 `WithBuildSecret` は古い `WithSecretBuildArg` 名を置き換え、安全な Docker または Podman ビルドのシークレット フローを読みやすくします。
+13.2 では、コンテナー ビルド シークレットの API がより明確になりました。 <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildSecret" /> は古い `WithSecretBuildArg` 名を置き換え、安全な Docker または Podman ビルドのシークレット フローを読みやすくします。
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -690,7 +691,7 @@ builder.AddContainer("my-java-app", "my-image:latest")
     });
 ```
 
-`ReferenceExpression` は `GetValueAsync()` を公開し、多言語コード生成で条件付きモードをサポートするようになりました。これにより、同期値アクセス パターンに依存せずに高度なホスティング拡張機能を簡単に構築できるようになります。
+`ReferenceExpression` は <ApiReference name="Aspire.Hosting.ApplicationModel.ReferenceExpression.GetValueAsync" /> を公開し、多言語コード生成で条件付きモードをサポートするようになりました。これにより、同期値アクセス パターンに依存せずに高度なホスティング拡張機能を簡単に構築できるようになります。
 
 ### 強化されたデバッグエクスペリエンス
 
@@ -889,7 +890,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-この領域の新しい API には、`AddProject`、`AddModelDeployment`、`WithAppInsights`、`WithKeyVault`、`WithContainerRegistry`、`PublishAsHostedAgent`、`AddAndPublishPromptAgent` があります。 `RunAsFoundryLocal` は引き続きローカル モデル開発に使用できますが、親リソースが Foundry Local として構成されている場合、Foundry プロジェクトはサポートされません。
+この領域の新しい API には、<ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddProject" />、<ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddModelDeployment" />、<ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.WithAppInsights" />、<ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.WithKeyVault" />、<ApiReference name="Aspire.Hosting.ContainerRegistryResourceBuilderExtensions.WithContainerRegistry" />、`PublishAsHostedAgent`、`AddAndPublishPromptAgent` があります。 <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> は引き続きローカル モデル開発に使用できますが、親リソースが Foundry Local として構成されている場合、Foundry プロジェクトはサポートされません。
 
 <Aside type="caution">
 これは破壊的な変更です。`Aspire.Hosting.Azure.AIFoundry` が `Aspire.Hosting.Foundry`
@@ -930,10 +931,10 @@ peSubnet.AddPrivateEndpoint(storage.AddBlobs("blobs"));
 
 主な機能は次のとおりです:
 
-- **仮想ネットワークとサブネット**: `AddAzureVirtualNetwork` でネットワークを作成し、`AddSubnet` でサブネットを追加します。
-- **NAT ゲートウェイ**: `AddNatGateway` および `WithNatGateway` を使用して、決定的な送信パブリック IP アドレスを提供します。
-- **ネットワーク セキュリティ グループ**: 短縮方法 (`AllowInbound`、`DenyInbound`、`AllowOutbound`、`DenyOutbound`) を使用するか、明示的な `AddNetworkSecurityGroup` と `WithSecurityRule` を使用して完全に制御し、トラフィック フローを制御します。
-- **プライベート エンドポイント**: `AddPrivateEndpoint` を使用してプライベート ネットワーク経由で Azure サービスに安全に接続します。これにより、プライベート DNS ゾーン、仮想ネットワーク リンクが自動的に作成され、ターゲット リソースでのパブリック アクセスが無効になります。
+- **仮想ネットワークとサブネット**: <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddAzureVirtualNetwork" /> でネットワークを作成し、<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AddSubnet" /> でサブネットを追加します。
+- **NAT ゲートウェイ**: <ApiReference name="Aspire.Hosting.AzureNatGatewayExtensions.AddNatGateway" /> および <ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.WithNatGateway" /> を使用して、決定的な送信パブリック IP アドレスを提供します。
+- **ネットワーク セキュリティ グループ**: 短縮方法 (<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowInbound" />、<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyInbound" />、<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.AllowOutbound" />、<ApiReference name="Aspire.Hosting.AzureVirtualNetworkExtensions.DenyOutbound" />) を使用するか、明示的な <ApiReference name="Aspire.Hosting.AzureNetworkSecurityGroupExtensions.AddNetworkSecurityGroup" /> と <ApiReference name="Aspire.Hosting.AzureNetworkSecurityGroupExtensions.WithSecurityRule" /> を使用して完全に制御し、トラフィック フローを制御します。
+- **プライベート エンドポイント**: <ApiReference name="Aspire.Hosting.AzurePrivateEndpointExtensions.AddPrivateEndpoint" /> を使用してプライベート ネットワーク経由で Azure サービスに安全に接続します。これにより、プライベート DNS ゾーン、仮想ネットワーク リンクが自動的に作成され、ターゲット リソースでのパブリック アクセスが無効になります。
 
 <LearnMore>
 詳細については、 [Azure 仮想ネットワーク
@@ -983,14 +984,14 @@ app.MapGet("/embed", async (
 
 ### Azure コンテナー レジストリ
 
-Azure Container Registry 統合では、新しい `WithPurgeTask` メソッドによるスケジュールされたイメージ クリーンアップがサポートされるようになりました。これにより、古いまたは未使用のコンテナ イメージを cron スケジュールで自動的に削除する [ACR パージ タスク](https://learn.microsoft.com/ja-jp/azure/container-registry/container-registry-auto-purge) がプロビジョニングされます。
+Azure Container Registry 統合では、新しい <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.WithPurgeTask" /> メソッドによるスケジュールされたイメージ クリーンアップがサポートされるようになりました。これにより、古いまたは未使用のコンテナ イメージを cron スケジュールで自動的に削除する [ACR パージ タスク](https://learn.microsoft.com/ja-jp/azure/container-registry/container-registry-auto-purge) がプロビジョニングされます。
 
 ```csharp title="ACR イメージクリーンアップをスケジュール"
 var acr = builder.AddAzureContainerRegistry("my-acr")
     .WithPurgeTask("0 1 * * *", ago: TimeSpan.FromDays(7), keep: 5);
 ```
 
-さらに、新しい `GetAzureContainerRegistry` メソッドを使用すると、コンピューティング環境からレジストリに簡単にアクセスして、さらに構成を行うことができます。
+さらに、新しい <ApiReference name="Aspire.Hosting.AzureContainerRegistryExtensions.GetAzureContainerRegistry" /> メソッドを使用すると、コンピューティング環境からレジストリに簡単にアクセスして、さらに構成を行うことができます。
 
 <LearnMore>
 詳細については、 [Azure Container Registry
@@ -1067,7 +1068,7 @@ builder.AddMongoDbContext<MyDbContext>("mongodb", databaseName: "appdb");
 
 ### Bun を使用した JavaScript ホスティング
 
-JavaScript リソースは、`WithBun()` を使用してパッケージ マネージャーとして Bun をオプトインできるようになりました。 Aspire は、Bun-backed アプリケーションに対して適切なパッケージ マネージャー アノテーション、インストール動作、およびコンテナー ビルド イメージのデフォルトを構成します。このリリースでは、`WithYarn()` 経由で `AddViteApp` で Yarn を使用する場合の信頼性の問題も修正されています。
+JavaScript リソースは、<ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithBun" /> を使用してパッケージ マネージャーとして Bun をオプトインできるようになりました。 Aspire は、Bun-backed アプリケーションに対して適切なパッケージ マネージャー アノテーション、インストール動作、およびコンテナー ビルド イメージのデフォルトを構成します。このリリースでは、<ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" /> 経由で <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> で Yarn を使用する場合の信頼性の問題も修正されています。
 
 <Tabs>
 <TabItem label="C# AppHost">
@@ -1111,7 +1112,7 @@ await builder.build().run();
 - Azure App Configuration エミュレータが 1.0.2 に更新されました
 - CosmosDB プレビュー エミュレーターの準備状況チェックが追加されました
 - Azure Managed Redis は、既定のスキームとして `rediss://` を使用するようになりました
-- `RunAsEmulator` で複数の Azurite ストレージ アカウントがサポートされるようになりました
+- <ApiReference name="Aspire.Hosting.AzureStorageExtensions.RunAsEmulator" /> で複数の Azurite ストレージ アカウントがサポートされるようになりました
 
 ### AI モデルの更新
 
@@ -1124,7 +1125,7 @@ await builder.build().run();
 ### Kubernetes の改善
 
 - Kubernetes デプロイメントの YAML 公開の修正
-- `ExcludeFromManifest` によるリソースの処理の改善
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromManifest" /> によるリソースの処理の改善
 
 ### Azure のデプロイメント
 
@@ -1235,7 +1236,7 @@ Aspire 13.2 では、Foundry ホスティング サーフェスが `Aspire.Hosti
 | ---------------- | ----------- |
 | ホスティング パッケージ: `Aspire.Hosting.Azure.AIFoundry` | ホスティング パッケージ: `Aspire.Hosting.Foundry` |
 | リソース型とモデル型の名前空間: `Aspire.Hosting.Azure` | リソース型とモデル型の名前空間: `Aspire.Hosting.Foundry` |
-| `AddAzureAIFoundry(...)` | `AddFoundry(...)` |
+| `AddAzureAIFoundry(...)` | <ApiReference name="Aspire.Hosting.FoundryExtensions.AddFoundry" /> |
 | `AzureAIFoundryResource` | `FoundryResource` |
 | `AzureAIFoundryExtensions` | `FoundryExtensions` |
 | `AzureAIFoundryDeploymentResource` | `FoundryDeploymentResource` |
@@ -1306,7 +1307,7 @@ Aspire 13.2.1 は、信頼性の修正に重点を置いたパッチ リリー
 | `runAsExistingFromParameters(name, resourceGroup)` | `runAsExisting(name, { resourceGroup })` |名前の変更と位置 → オプション オブジェクト。 |
 | `publishAsExistingFromParameters(name, resourceGroup)` | `publishAsExisting(name, { resourceGroup })` |名前の変更と位置 → オプション オブジェクト。 |
 | `withConnectionPropertyValue(name, value)` | `withConnectionProperty(name, value)` |文字列/参照値の統合 API。 |
-| `withParameterBuildArg(name, parameter)` | `withBuildArg(name, parameter)` |名前が統合された `withBuildArg` サーフェスに変更されました。 |
+| `withParameterBuildArg(name, parameter)` | `withBuildArg(name, parameter)` |名前が統合された <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithBuildArg" /> サーフェスに変更されました。 |
 
 <Aside type="note">
 `withConnectionPropertyValue` は、生成された SDK の互換性エイリアスとして引き続き使用できるため、ランタイム SDK の中断ではありません。
diff --git a/src/frontend/src/content/docs/ja/whats-new/aspire-13-3.mdx b/src/frontend/src/content/docs/ja/whats-new/aspire-13-3.mdx
index 3a244b22bc..8f791c2c6f 100644
--- a/src/frontend/src/content/docs/ja/whats-new/aspire-13-3.mdx
+++ b/src/frontend/src/content/docs/ja/whats-new/aspire-13-3.mdx
@@ -17,6 +17,7 @@ import {
   Tabs,
   TabItem,
 } from '@astrojs/starlight/components';
+import ApiReference from '@components/ApiReference.astro';
 import { Image } from 'astro:assets';
 import LearnMore from '@components/LearnMore.astro';
 import OsAwareTabs from '@components/OsAwareTabs.astro';
@@ -35,8 +36,8 @@ Aspire 13.3 がリリースされました。今回は盛りだくさんの内
 
 - Azure、Kubernetes、Compose 全体でプロビジョニングされたリソースを破棄する新しい **`aspire destroy`** コマンド、および **`aspire dashboard`** CLI をスタンドアロンで実行します。Aspire CLI は `dotnet tool` として利用可能になりました。
 - **ブラウザログとスクリーンショット** — 新しい `Aspire.Hosting.Browsers` 統合はフロントエンドコンソールログ、ネットワークリクエスト、スクリーンショットをキャプチャし、ダッシュボードのサーバー側テレメトリの横に表示します。
-- **`aspire deploy` から Kubernetes** (プレビュー) — `AddKubernetesEnvironment` を宣言すると、Aspire は Helm チャートを生成し、エンドツーエンドのデプロイメントパイプラインを実行します。新しい **Ingress** と **Gateway API ルーティング** リソースは AppHost レベルでトラフィックを記述します。
-- **JavaScript パブリッシュメソッド** (プレビュー) — 静的 SPA、SSR Node サーバー、npm スクリプトベースのデプロイメント向けの統合された `PublishAs*` ファミリ、および新しい `AddNextJsApp` ヘルパーと Bun、Yarn、pnpm の ファーストクラスサポート。
+- **`aspire deploy` から Kubernetes** (プレビュー) — <ApiReference name="Aspire.Hosting.KubernetesEnvironmentExtensions.AddKubernetesEnvironment" /> を宣言すると、Aspire は Helm チャートを生成し、エンドツーエンドのデプロイメントパイプラインを実行します。新しい **Ingress** と **Gateway API ルーティング** リソースは AppHost レベルでトラフィックを記述します。
+- **JavaScript パブリッシュメソッド** (プレビュー) — 静的 SPA、SSR Node サーバー、npm スクリプトベースのデプロイメント向けの統合された `PublishAs*` ファミリ、および新しい <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNextJsApp" /> ヘルパーと Bun、Yarn、pnpm の ファーストクラスサポート。
 - **コンテナトンネル** がデフォルトで有効化され、Docker Desktop、Docker Engine、Podman 全体で均一なホスト接続性を提供します。
 - 大部分の残された C# AppHost とのギャップを閉じる **TypeScript AppHost** パリティの大規模な作業。
 - **`aspire init`** (プレビュー) — 新しい `aspireify` エージェントスキルで既存リポジトリに AppHost をブートストラップします。
@@ -637,11 +638,11 @@ await builder.build().run();
 
 ### `WithEndpoint` は既存のエンドポイントを更新
 
-`WithEndpoint` は同じ名前のエンドポイントが既に存在する場合、エラーをスローしなくなりました。2 回目の呼び出しは既存のエンドポイントを更新します — 拡張メソッド全体でエンドポイント設定をレイヤリングしやすくなります。
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEndpoint" /> は同じ名前のエンドポイントが既に存在する場合、エラーをスローしなくなりました。2 回目の呼び出しは既存のエンドポイントを更新します — 拡張メソッド全体でエンドポイント設定をレイヤリングしやすくなります。
 
 ### `WithReference()` から管理エンドポイントを除外
 
-エンドポイント注釈には `ExcludeReferenceEndpoint` フラグがあります。`true` に設定すると、エンドポイント (管理またはヘルスエンドポイントなど) はデフォルトの `WithReference()` 注入から除外されるため、コンシューマーが誤って管理 URL を受け取りません：
+エンドポイント注釈には `ExcludeReferenceEndpoint` フラグがあります。`true` に設定すると、エンドポイント (管理またはヘルスエンドポイントなど) はデフォルトの <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> 注入から除外されるため、コンシューマーが誤って管理 URL を受け取りません：
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -682,9 +683,9 @@ Aspire 信頼デベロッパー証明書は、より多くの場所で使用さ
 
 Aspire 13.3 は、C# AppHost と TypeScript AppHost SDK 間の機能的ギャップのほぼすべてを閉じます：
 
-- **統合 `withEnvironment` API** — すべての環境変数値の種類 (エンドポイント、パラメータ、接続文字列、式) を処理する単一のメソッド。以前の種類ごとのヘルパーは非推奨になります。
+- **統合 <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithEnvironment" /> API** — すべての環境変数値の種類 (エンドポイント、パラメータ、接続文字列、式) を処理する単一のメソッド。以前の種類ごとのヘルパーは非推奨になります。
 - **エンドポイントプロパティ式** (`endpoint.url`、`endpoint.host`、`endpoint.port`) は TypeScript AppHost 式内で使用できるようになりました。
-- **Docker Compose API パリティ**: `PublishAsDockerComposeService` 等価フック とポスト処理が TypeScript で公開されます。
+- **Docker Compose API パリティ**: <ApiReference name="Aspire.Hosting.DockerComposeServiceExtensions.PublishAsDockerComposeService" /> 等価フック とポスト処理が TypeScript で公開されます。
 - **Azure Container Apps のカスタムドメイン設定** は TypeScript AppHost SDK で公開されます。
 - **統合 YARP TS ルートヘルパー** — `addRoute(...)`と `addCatchAllRoute(...)` が以前のアドホックヘルパーに置き換わります。
 - **`WithAdminDeploymentScriptSubnet`** は TypeScript AppHost 向けにエクスポートされます。
@@ -717,11 +718,11 @@ await api
 
 Aspire 13.3 は、C# と TypeScript AppHost の両方にファーストクラスの **JavaScript パブリッシング** をもたらします。新しい `PublishAs*` 拡張メソッドファミリは、最も一般的な JS デプロイメント形式の手巻き `Dockerfile` 配管に置き換わります：
 
-- **`PublishAsStaticWebsite`** (プレビュー) — JS アプリを YARP イメージで提供される静的ウェブサイトとして公開し、オプションでバックエンドリソースへの API リバースプロキシを追加します。SPA (Vite、プレーン Next.js エクスポート) に最適です。
-- **`PublishAsNodeServer`** — `node_modules` をランタイムでコピーしない自己完結型 Node エントリポイント (例、`server.js`) を公開します。事前バンドルされた Node サーバーに最適です。
+- **<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsStaticWebsite" />** (プレビュー) — JS アプリを YARP イメージで提供される静的ウェブサイトとして公開し、オプションでバックエンドリソースへの API リバースプロキシを追加します。SPA (Vite、プレーン Next.js エクスポート) に最適です。
+- **<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.PublishAsNodeServer" />** — `node_modules` をランタイムでコピーしない自己完結型 Node エントリポイント (例、`server.js`) を公開します。事前バンドルされた Node サーバーに最適です。
 - **`PublishAsNpmScript`** — ランタイムで npm スクリプト (`start`/`serve`) を実行し、`package.json` と本番依存関係をコピーする Node アプリを公開します。完全な Nitro Next.js、Remix、Astro SSR に最適です。
 
-Aspire 13.3 は、既存の `AddViteApp` および `AddNodeApp` と共にファーストクラスの Next.js ヘルパーとしても **`AddNextJsApp`** を追加し、TypeScript AppHost での **Bun、Yarn、pnpm** のファーストクラスサポート (npm がデフォルト) を追加します。
+Aspire 13.3 は、既存の <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> および <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" /> と共にファーストクラスの Next.js ヘルパーとしても **`AddNextJsApp`** を追加し、TypeScript AppHost での **Bun、Yarn、pnpm** のファーストクラスサポート (npm がデフォルト) を追加します。
 
 <Aside type="caution">
   `PublishAsStaticWebsite` メソッドは 13.3 では実験的です。診断コード
@@ -917,7 +918,7 @@ VS Code から Aspire アプリを起動すると、ダッシュボード は **
 
 ### 🔍 ブラウザログとスクリーンショット
 
-新しい **Aspire.Hosting.Browsers** 統合は、開発中にフロントエンドリソースからブラウザコンソールログ、ネットワークリクエスト、スクリーンショットをキャプチャし、ダッシュボードにサーバー側テレメトリと共に表示します。フロントエンドリソースに `WithBrowserLogs()` を追加してこれを有効にします。
+新しい **Aspire.Hosting.Browsers** 統合は、開発中にフロントエンドリソースからブラウザコンソールログ、ネットワークリクエスト、スクリーンショットをキャプチャし、ダッシュボードにサーバー側テレメトリと共に表示します。フロントエンドリソースに <ApiReference name="Aspire.Hosting.BrowserLogsBuilderExtensions.WithBrowserLogs" /> を追加してこれを有効にします。
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -992,7 +993,7 @@ Npgsql クライアント統合が .NET 10 メトリック命名仕様に合致
   data-zoom-off
 />
 
-アプリの前に CDN を取得するために ARM テンプレートを ステッチしたり、ポータルブレードをクリックしたりする必要がなくなりました。Aspire 13.3 は [Azure Front Door](https://learn.microsoft.com/ja-jp/azure/frontdoor/) の新しいホスティング統合を追加します。これは、高速で安全で高度に利用可能なウェブアプリのための Microsoft のグローバルエッジネットワークです。`AddAzureFrontDoor` でバックエンドの前に Front Door プロファイルを追加し、`WithOrigin` で オリジンを接続します：
+アプリの前に CDN を取得するために ARM テンプレートを ステッチしたり、ポータルブレードをクリックしたりする必要がなくなりました。Aspire 13.3 は [Azure Front Door](https://learn.microsoft.com/ja-jp/azure/frontdoor/) の新しいホスティング統合を追加します。これは、高速で安全で高度に利用可能なウェブアプリのための Microsoft のグローバルエッジネットワークです。<ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.AddAzureFrontDoor" /> でバックエンドの前に Front Door プロファイルを追加し、<ApiReference name="Aspire.Hosting.AzureFrontDoorExtensions.WithOrigin" /> で オリジンを接続します：
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -1039,7 +1040,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-各 `withOrigin` 呼び出しは、独自の Front Door エンドポイント、オリジングループ、オリジン、ルートをプロビジョニングし、すべてのバックエンドが独自の `*.azurefd.net` ホスト名を介して独立してルーティング可能です。統合は標準 SKU でデフォルトの Front Door をプロビジョニングします；`ConfigureInfrastructure` を使用して、Front Door、たとえば SKU の変更、Web Application Firewall (WAF) ポリシーの接続、キャッシング有効化などをカスタマイズします。
+各 `withOrigin` 呼び出しは、独自の Front Door エンドポイント、オリジングループ、オリジン、ルートをプロビジョニングし、すべてのバックエンドが独自の `*.azurefd.net` ホスト名を介して独立してルーティング可能です。統合は標準 SKU でデフォルトの Front Door をプロビジョニングします；<ApiReference name="Aspire.Hosting.AzureProvisioningResourceExtensions.ConfigureInfrastructure" /> を使用して、Front Door、たとえば SKU の変更、Web Application Firewall (WAF) ポリシーの接続、キャッシング有効化などをカスタマイズします。
 
 <LearnMore>
   詳細については、[Azure Front Door 
@@ -1117,7 +1118,7 @@ NSP は **Enforced** モード (ルール違反トラフィックをブロック
   進化する可能性があります。
 </Aside>
 
-Kubernetes にデプロイしたいが、手書きでマニフェストを書くことを避けたい場合、これはあなたのためです。Aspire 13.3 は **Azure Kubernetes Service のプロビジョニングとデプロイ** にファーストクラスサポートを追加します。`AddAzureKubernetesEnvironment` を使用して AKS 環境を宣言し、ノードプールをカスタマイズし、AppHost を Bicep + Helm ベースのデプロイメントパイプライン を生成させます — すべてタイプセーフ、すべてコードから。
+Kubernetes にデプロイしたいが、手書きでマニフェストを書くことを避けたい場合、これはあなたのためです。Aspire 13.3 は **Azure Kubernetes Service のプロビジョニングとデプロイ** にファーストクラスサポートを追加します。<ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.AddAzureKubernetesEnvironment" /> を使用して AKS 環境を宣言し、ノードプールをカスタマイズし、AppHost を Bicep + Helm ベースのデプロイメントパイプライン を生成させます — すべてタイプセーフ、すべてコードから。
 
 <Tabs syncKey='aspire-lang'>
 <TabItem id='csharp' label='AppHost.cs'>
@@ -1154,7 +1155,7 @@ await builder.build().run();
 </TabItem>
 </Tabs>
 
-`WithSystemNodePool` により、システムノードプールの VM サイズと自動スケーリング境界をカスタマイズできます。デフォルトでは AKS クラスタは **Free** コントロールプレーン SKU を使用します；`AksSkuTier` enum はもはや公開 API の一部ではありません。
+<ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithSystemNodePool" /> により、システムノードプールの VM サイズと自動スケーリング境界をカスタマイズできます。デフォルトでは AKS クラスタは **Free** コントロールプレーン SKU を使用します；`AksSkuTier` enum はもはや公開 API の一部ではありません。
 
 <LearnMore>
   詳細については、[Azure Kubernetes Service 
@@ -1168,7 +1169,7 @@ await builder.build().run();
 
 ### Azure AI Foundry Prompt Agent
 
-Aspire 13.3 は **Azure AI Foundry Prompt Agent** サポート `AddPromptAgent` の新しい作業実装をシップします。以前の `AddAndPublishPromptAgent` API および `AzurePromptAgentResource` の元の形 (エンドツーエンドで機能しなかった) は置き換わりました — `AddPromptAgent` は現在作業 `AzurePromptAgentResource` を返します。
+Aspire 13.3 は **Azure AI Foundry Prompt Agent** サポート <ApiReference name="Aspire.Hosting.PromptAgentBuilderExtensions.AddPromptAgent" /> の新しい作業実装をシップします。以前の `AddAndPublishPromptAgent` API および `AzurePromptAgentResource` の元の形 (エンドツーエンドで機能しなかった) は置き換わりました — `AddPromptAgent` は現在作業 `AzurePromptAgentResource` を返します。
 
 Foundry モデルカタログは 2 つの新しいモデル も獲得しました：**GPT-5.4** と **Qwen3 VL**。
 
@@ -1241,7 +1242,7 @@ Aspire はオープンに構築され、このリリースはあなたなしで
 | 変更                                                                                                           | 移行                                                                                           |
 | ---------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
 | `aspire publish` および `aspire deploy` での `--log-level` を `--pipeline-log-level` に改名                          | スクリプト/CI を `--pipeline-log-level` を使用するように更新します。                                                    |
-| `package.json` `engines.node` はもはや生成 Dockerfile Node イメージを選択するために使用されません                  | `WithDockerfile` またはプロジェクトの Dockerfile ベースイメージで Node バージョンを明示的に指定します。   |
+| `package.json` `engines.node` はもはや生成 Dockerfile Node イメージを選択するために使用されません                  | <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfile" /> またはプロジェクトの Dockerfile ベースイメージで Node バージョンを明示的に指定します。   |
 | Azure Network リソースで `NameOutput` を `NameOutputReference` に改名                                         | `*.NameOutput` を `*.NameOutputReference` に置き換えます。                                   |
 | `OtlpEndpointEnvironmentVariableName` プロパティを削除                                                           | 参照を削除します；OTLP エンドポイント env var は自動的に管理されます。                          |
 | **ダッシュボード MCP サーバーを削除** (`ASPIRE_DASHBOARD_MCP_ENDPOINT_URL` とともに)                                | `aspire agent init` で AppHost レベルの MCP サーバーを使用します。                                          |
diff --git a/src/frontend/src/content/docs/ja/whats-new/aspire-13.mdx b/src/frontend/src/content/docs/ja/whats-new/aspire-13.mdx
index 7ec632a417..f68b6455ab 100644
--- a/src/frontend/src/content/docs/ja/whats-new/aspire-13.mdx
+++ b/src/frontend/src/content/docs/ja/whats-new/aspire-13.mdx
@@ -23,6 +23,7 @@ import colorTweaks from '@assets/whats-new/color-tweaks.png';
 import healthChecksLastRun from '@assets/whats-new/health-checks-last-run.png';
 import resourcesParametersView from '@assets/whats-new/resources-parameters-view.png';
 import genaiVisualizerTooldefinitions from '@assets/whats-new/genai-visualizer-tooldefinitions.png';
+import ApiReference from '@components/ApiReference.astro';
 
 📢 Aspire 13 は、Aspire 製品ラインにおける大きな節目となるリリースです。
 
@@ -212,7 +213,7 @@ var api = builder.AddPythonExecutable("api", "../api", "gunicorn")
 
 #### ASGI アプリケーション向けの Uvicorn 統合
 
-FastAPI、Starlette、Quart などの ASGI フレームワークを使用した Python Web アプリケーションに対して、Aspire は専用の `AddUvicornApp` サポートを提供します:
+FastAPI、Starlette、Quart などの ASGI フレームワークを使用した Python Web アプリケーションに対して、Aspire は専用の <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddUvicornApp" /> サポートを提供します:
 
 ```csharp title="Uvicorn 統合"
 var api = builder.AddUvicornApp("api", "./api", "main:app")
@@ -245,7 +246,7 @@ var api = builder.AddUvicornApp("api", "./api", "main:app");
 
 **uv を使用する場合（新規プロジェクトに推奨）:**
 
-[uv](https://github.com/astral-sh/uv)を使用したモダンな Python プロジェクトでは、 `WithUv()` を指定して明示的に有効化します:
+[uv](https://github.com/astral-sh/uv)を使用したモダンな Python プロジェクトでは、 <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithUv" /> を指定して明示的に有効化します:
 
 ```csharp title="uv を使用したパッケージ管理"
 builder.AddUvicornApp("api", "./api", "main:app")
@@ -261,7 +262,7 @@ builder.AddUvicornApp("api", "./api", "main:app")
 
 **pip の明示的な構成:**
 
-pip の挙動を明示的に設定するには、 `WithPip()` を使用します:
+pip の挙動を明示的に設定するには、 <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithPip" /> を使用します:
 
 ```csharp title="pip を使用したパッケージ管理"
 builder.AddUvicornApp("api", "./api", "main:app")
@@ -276,7 +277,7 @@ builder.AddUvicornApp("api", "./api", "main:app")
 
 **仮想環境パスの構成:**
 
-既定では、Aspire はアプリ ディレクトリ内の `.venv` を仮想環境のパスとして使用します。カスタム パスを指定したり、自動作成の挙動を制御したりするには `WithVirtualEnvironment()` を使用します:
+既定では、Aspire はアプリ ディレクトリ内の `.venv` を仮想環境のパスとして使用します。カスタム パスを指定したり、自動作成の挙動を制御したりするには <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.WithVirtualEnvironment" /> を使用します:
 
 ```csharp title="仮想環境パスの構成"
 // カスタムの仮想環境（venv）パスを使用する
@@ -296,8 +297,8 @@ Python アプリケーションは、ブレークポイントを含む完全な
 
 **サポートされるデバッグ シナリオ:**
 
-- **Python スクリプト**: ブレークポイントや変数の確認を行いながら `AddPythonApp` をデバッグ可能。
-- **Python モジュール**: モジュール解決を含めて `AddPythonModule` をデバッグ可能。
+- **Python スクリプト**: ブレークポイントや変数の確認を行いながら <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonApp" /> をデバッグ可能。
+- **Python モジュール**: モジュール解決を含めて <ApiReference name="Aspire.Hosting.PythonAppResourceBuilderExtensions.AddPythonModule" /> をデバッグ可能。
 - **Flask アプリケーション**: 自動リロード付きで Flask アプリをデバッグ可能。
 - **Uvicorn/FastAPI**: async/await をサポートした ASGI アプリケーションをデバッグ可能。
 
@@ -372,7 +373,7 @@ import pythonStarterLightPng from '@assets/get-started/python-starter-light.png'
 
 ### 第一級言語としての JavaScript
 
-Aspire 13.0 では、JavaScript サポートが再設計・拡張されました。従来のバージョンでは `Aspire.Hosting.NodeJs` 統合によって JavaScript アプリケーションが有効化されていましたが、Aspire 13.0 ではこの統合は `Aspire.Hosting.JavaScript` に名称変更され、すべての JavaScript アプリケーションの基盤となるメソッドとして `AddJavaScriptApp` が導入されています。
+Aspire 13.0 では、JavaScript サポートが再設計・拡張されました。従来のバージョンでは `Aspire.Hosting.NodeJs` 統合によって JavaScript アプリケーションが有効化されていましたが、Aspire 13.0 ではこの統合は `Aspire.Hosting.JavaScript` に名称変更され、すべての JavaScript アプリケーションの基盤となるメソッドとして <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddJavaScriptApp" /> が導入されています。
 
 #### 統一された JavaScript アプリケーション モデル
 
@@ -443,7 +444,7 @@ var app = builder.AddJavaScriptApp("app", "./app")
 
 非推奨となった `AddNpmApp` API とは異なり、`AddJavaScriptApp` では、スクリプトにコマンドライン引数を直接渡すための `args` コンストラクター パラメーターはサポートされていません。引数を渡す方法は 2 つあります:
 
-**方法 1: `WithArgs` を使用して引数を直接渡す**
+**方法 1: <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithArgs" /> を使用して引数を直接渡す**
 
 ```csharp title="WithArgs を使用して引数を渡す"
 // 以前の方法 (Aspire 9.x with AddNpmApp)
@@ -483,7 +484,7 @@ builder.AddJavaScriptApp("hasura-console", "../Web/ClientApp")
 
 #### Vite 対応
 
-`AddViteApp` は、`AddJavaScriptApp` が Vite 固有の最適化（特化した）ものとして提供されるようになりました:
+<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddViteApp" /> は、`AddJavaScriptApp` が Vite 固有の最適化（特化した）ものとして提供されるようになりました:
 
 ```csharp title="Vite 対応"
 var frontend = builder.AddViteApp("frontend", "./frontend")
@@ -517,7 +518,7 @@ var app = builder.AddJavaScriptApp("app", "./app");
 
 #### Node 対応
 
-`AddNodeApp` は、他の言語統合と整合するようにリファクタリングされました。
+<ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.AddNodeApp" /> は、他の言語統合と整合するようにリファクタリングされました。
 
 ```csharp title="Node 対応"
 var app = builder.AddNodeApp("frontend", "./frontend", "app.js")
@@ -554,7 +555,7 @@ var javaApp = builder.AddExecutable("java-app", "java", "./app", ["-jar", "app.j
     .WithEnvironment("DB_JDBC", postgres.Resource.JdbcConnectionStringExpression);
 ```
 
-`WithReference` を使ってデータベース リソースを参照すると、Aspire は複数の接続プロパティを環境変数として自動的に公開します。たとえば、`db` という名前の PostgreSQL リソースでは、次のような環境変数が公開されます。:
+<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> を使ってデータベース リソースを参照すると、Aspire は複数の接続プロパティを環境変数として自動的に公開します。たとえば、`db` という名前の PostgreSQL リソースでは、次のような環境変数が公開されます。:
 
 - `DB_URI` - PostgreSQL の URI 形式: `postgresql://user:pass@host:port/dbname`.
 - `DB_JDBCCONNECTIONSTRING` - JDBC 形式: `jdbc:postgresql://host:port/dbname`.
@@ -643,7 +644,7 @@ aspire init
 この init コマンドにより、対話型ワークフローを通じて初期プロジェクト設定が簡素化され、チーム メンバー間で一貫した構成が保証されます。
 
 > [!NOTE]
-> `aspire init` コマンドは Aspire のプロジェクト構成と設定をセットアップしますが、リソース（データベース、キャッシュ、メッセージ キューなど）を AppHost に自動で追加するわけではありません。 `AddPostgres`、`AddRedis`、`AddRabbitMQ`などのメソッドを使って、AppHost のコード内にリソース定義を手動で追加する必要があります。
+> `aspire init` コマンドは Aspire のプロジェクト構成と設定をセットアップしますが、リソース（データベース、キャッシュ、メッセージ キューなど）を AppHost に自動で追加するわけではありません。 <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.AddPostgres" />、<ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" />、<ApiReference name="Aspire.Hosting.RabbitMQBuilderExtensions.AddRabbitMQ" />などのメソッドを使って、AppHost のコード内にリソース定義を手動で追加する必要があります。
 
 ### aspire new：厳選されたスターター テンプレート
 
@@ -841,7 +842,7 @@ builder.Pipeline.AddStep("validate", (context) =>
 aspire do validate
 ```
 
-パイプラインシステムは、グローバルステップ、リソース固有のステップ、依存関係の構成、並列実行、組み込みのログ機能をサポートしています。各リソースは `WithPipelineStepFactory` を使用して独自のステップを提供でき、`WithPipelineConfiguration` によって実行順序を制御できます。
+パイプラインシステムは、グローバルステップ、リソース固有のステップ、依存関係の構成、並列実行、組み込みのログ機能をサポートしています。各リソースは <ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineStepFactory" /> を使用して独自のステップを提供でき、<ApiReference name="Aspire.Hosting.Pipelines.PipelineStepFactoryExtensions.WithPipelineConfiguration" /> によって実行順序を制御できます。
 
 #### パイプライン ステップの実行
 
@@ -1271,15 +1272,15 @@ API_URL=http://api:8080
 ### その他のアプリ モデル改善点
 
 **コンピューティング環境のサポート（実験的から昇格）**:
-- `WithComputeEnvironment`API が安定版となり、実験的（experimental）のマークが外れました
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithComputeEnvironment" />API が安定版となり、実験的（experimental）のマークが外れました
 - 実験的な警告なしで、特定のコンピューティング環境へリソースをデプロイできます
 
 **MCP からのリソース除外**:
-- 特定のリソースを Model Context Protocol の公開対象から除外するための `ExcludeFromMcp` 拡張が追加されました
+- 特定のリソースを Model Context Protocol の公開対象から除外するための <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.ExcludeFromMcp" /> 拡張が追加されました
 - AI アシスタントや MCP クライアントに表示されるリソースを制御できます
 
 **参照による環境変数注入の制御**:
-- 参照から環境変数をどのように注入するかを制御する `WithReferenceEnvironment`
+- 参照から環境変数をどのように注入するかを制御する <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReferenceEnvironment" />
 - 環境変数の挙動を細かく制御するための `ReferenceEnvironmentInjectionFlags`
 
 **ヘルパー メソッド**:
@@ -1649,7 +1650,7 @@ builder.AddNodeApp(
 
 1. **npm の自動統合**: `appDirectory` 内に `package.json` が存在する場合、npm が自動的に構成され、依存関係の自動インストールが有効になります
 2. **Dockerfile の自動生成**: マルチステージ ビルドを既定とした Docker 発行（パブリッシュ）対応が、自動的に含まれるようになりました
-3. **パッケージ マネージャーの柔軟性向上**: `WithNpm()`, `WithYarn()`, `WithPnpm()` を使用し、あわせて `WithRunScript()` を指定することで、`package.json` に定義されたスクリプトを実行できます
+3. **パッケージ マネージャーの柔軟性向上**: `WithNpm()`, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithYarn" />, <ApiReference name="Aspire.Hosting.McpInspectorResourceBuilderExtensions.WithPnpm" /> を使用し、あわせて <ApiReference name="Aspire.Hosting.JavaScriptHostingExtensions.WithRunScript" /> を指定することで、`package.json` に定義されたスクリプトを実行できます
 
 </Steps>
 
@@ -1692,8 +1693,8 @@ Azure Container Apps または Azure App Service にデプロイすると、Aspi
 
 **影響を受ける API:**
 
-- `AddAzureContainerAppEnvironment`
-- `AddAzureAppServiceEnvironment`
+- <ApiReference name="Aspire.Hosting.AzureContainerAppExtensions.AddAzureContainerAppEnvironment" />
+- <ApiReference name="Aspire.Hosting.AzureAppServiceEnvironmentExtensions.AddAzureAppServiceEnvironment" />
 
 **移行方法:**
 
@@ -1801,8 +1802,8 @@ builder.Services.TryAddEventingSubscriber<MyEventSubscriber>();
 
 以下の機能は `[Experimental]` として扱われており、将来のリリースで変更される可能性があります:
 
-- **Dockerfile ビルダー API**: `WithDockerfileBuilder`, `AddDockerfileBuilder`, `WithDockerfileBaseImage`
-- **C# ファイルベース アプリのサポート**: `AddCSharpApp`
+- **Dockerfile ビルダー API**: <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBuilder" />, <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.AddDockerfileBuilder" />, <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithDockerfileBaseImage" />
+- **C# ファイルベース アプリのサポート**: <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddCSharpApp" />
 - **動的入力**: `InputLoadOptions`、動的入力の読み込み
 - **パイプライン機能**: `IDistributedApplicationPipeline` と関連 API
 

From ef154fd1dd69480e21e4a9dbfaeada659c1fce1d Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Thu, 8 Oct 2026 17:30:01 +0100
Subject: [PATCH 3/9] Integrated one forbidden words fix.

---
 .../docs/integrations/cloud/azure/azure-log-analytics.mdx       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
index 9672c47cec..252f53e3b1 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-log-analytics.mdx
@@ -76,7 +76,7 @@ This updates your `aspire.config.json` with the Azure Log Analytics hosting inte
 
 ## Add Azure Log Analytics workspace resource
 
-The Aspire Azure Log Analytics hosting integration models the Log Analytics workspace as the `AzureLogAnalyticsWorkspaceResource` type. To add a Log Analytics workspace resource to your app host, call <ApiReference name="Aspire.Hosting.AzureLogAnalyticsWorkspaceExtensions.AddAzureLogAnalyticsWorkspace" />:
+The Aspire Azure Log Analytics hosting integration models the Log Analytics workspace as the `AzureLogAnalyticsWorkspaceResource` type. To add a Log Analytics workspace resource to your AppHost, call <ApiReference name="Aspire.Hosting.AzureLogAnalyticsWorkspaceExtensions.AddAzureLogAnalyticsWorkspace" />:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">

From b81577b1ff958c723b860b1fd8a4a6b451300b70 Mon Sep 17 00:00:00 2001
From: David Pine <david.pine@microsoft.com>
Date: Fri, 9 Oct 2026 22:01:27 -0500
Subject: [PATCH 4/9] Fix ApiReference formatting in documentation

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---
 .../src/content/docs/architecture/resource-examples.mdx         | 2 +-
 src/frontend/src/content/docs/diagnostics/aspireradius003.mdx   | 2 +-
 src/frontend/src/content/docs/get-started/ai-coding-agents.mdx  | 2 +-
 .../azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx     | 2 +-
 .../azure/azure-postgresql/azure-postgresql-get-started.mdx     | 2 +-
 .../docs/integrations/databases/efcore/seed-database.mdx        | 2 +-
 .../src/content/docs/integrations/devtools/dev-tunnels.mdx      | 2 +-
 .../src/content/docs/ja/architecture/resource-examples.mdx      | 2 +-
 .../src/content/docs/ja/get-started/aspire-vscode-extension.mdx | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/src/frontend/src/content/docs/architecture/resource-examples.mdx b/src/frontend/src/content/docs/architecture/resource-examples.mdx
index b8ea7321de..a9eacae81d 100644
--- a/src/frontend/src/content/docs/architecture/resource-examples.mdx
+++ b/src/frontend/src/content/docs/architecture/resource-examples.mdx
@@ -15,7 +15,7 @@ This example shows how to create a custom resource (`RedisResource`) that derive
 
 - Defining a data-only resource class.
 - Implementing `IResourceWithConnectionString` with deferred evaluation using `ReferenceExpression`.
-- Creating an <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> extension method that handles parameter validation, password management, event subscription, health checks, and container configuration using fluent APIs.
+- Creating an `AddRedis` extension method that handles parameter validation, password management, event subscription, health checks, and container configuration using fluent APIs.
 
 ```csharp title="RedisResourceExtensions.cs"
 public static class RedisResourceExtensions
diff --git a/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx b/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
index b1711491eb..9c55d11143 100644
--- a/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
+++ b/src/frontend/src/content/docs/diagnostics/aspireradius003.mdx
@@ -18,7 +18,7 @@ import ApiReference from '@components/ApiReference.astro';
 
 This diagnostic warning is reported when using the experimental Radius cloud-provider APIs from the `Aspire.Hosting.Radius` integration, `WithAzureProvider` and `WithAwsProvider`.
 
-The `[Experimental]` gate is on `WithAzureProvider` and `WithAwsProvider` themselves. The credential callbacks you configure through them—such as `WithServicePrincipal`, <ApiReference name="Aspire.Hosting.AzureKubernetesEnvironmentExtensions.WithWorkloadIdentity" />, `WithAccessKey`, and `WithIrsa`—are part of the same experimental surface; they don't each emit `ASPIRERADIUS003` on their own.
+The `[Experimental]` gate is on `WithAzureProvider` and `WithAwsProvider` themselves. The credential callbacks you configure through them—such as `WithServicePrincipal`, `WithWorkloadIdentity`, `WithAccessKey`, and `WithIrsa`—are part of the same experimental surface; they don't each emit `ASPIRERADIUS003` on their own.
 
 These APIs configure the Azure and AWS cloud providers that the Radius publisher emits and that the deploy pipeline registers credentials for.
 
diff --git a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
index c674a558b0..4139ee5142 100644
--- a/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
+++ b/src/frontend/src/content/docs/get-started/ai-coding-agents.mdx
@@ -68,7 +68,7 @@ The optional MCP server gives your AI agent direct runtime access to your runnin
 
 ## Start and stop AppHosts through VS Code
 
-With the [Aspire VS Code extension](/get-started/aspire-vscode-extension/#let-coding-agents-start-and-stop-apphosts), agents can use `#aspireStartAppHost` and `#aspireStopAppHost` to control a discovered AppHost through the editor. Start supports <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> and `debug` modes, and both tools require a trusted workspace and user confirmation.
+With the [Aspire VS Code extension](/get-started/aspire-vscode-extension/#let-coding-agents-start-and-stop-apphosts), agents can use `#aspireStartAppHost` and `#aspireStopAppHost` to control a discovered AppHost through the editor. Start supports `run` and `debug` modes, and both tools require a trusted workspace and user confirmation.
 
 > Use #aspireStartAppHost to start my AppHost in debug mode, then inspect the resource status.
 
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
index 0b6397a0a5..3bbed4c09f 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-ai-foundry/azure-ai-foundry-get-started.mdx
@@ -26,7 +26,7 @@ Adding Azure AI Foundry through Aspire — rather than hard-coding endpoints and
 
 - **Centralized credential management.** Endpoint and API key are stored once in the AppHost and injected into each consuming app automatically.
 - **Model deployments as first-class resources.** Each deployment composes a connection string from the parent Foundry endpoint, API key, and model name, giving consuming apps a single named connection.
-- **Foundry Projects for agents.** Model Foundry projects with <ApiReference name="Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject" />, attach model deployments, web-search tools, and hosted or prompt agents, and reference them from consuming services.
+- **Foundry Projects for agents.** Model Foundry projects with <ApiReference name="Aspire.Hosting.AzureCognitiveServicesProjectExtensions.AddProject" />, attach model deployments, web-search tools, and hosted or prompt agents, and reference them from consuming services.
 - **Consistent connection info across languages.** Once you reference a deployment from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
 - **Foundry Local for offline development.** Use <ApiReference name="Aspire.Hosting.FoundryExtensions.RunAsFoundryLocal" /> to run models locally without an Azure subscription.
 - **An upgrade path to the cloud.** The same AppHost model provisions Azure Cognitive Services accounts and deployments when you publish.
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
index e6575e01b5..9447227a16 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-postgresql/azure-postgresql-get-started.mdx
@@ -24,7 +24,7 @@ import ApiReference from '@components/ApiReference.astro';
 Adding Azure PostgreSQL through Aspire — rather than managing connection strings and credentials by hand — gives you:
 
 - **Managed identity by default.** Aspire configures [Microsoft Entra ID](https://learn.microsoft.com/azure/postgresql/flexible-server/concepts-azure-ad-authentication) authentication so no passwords are stored in your app configuration.
-- **Easy local development.** Call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.RunAsContainer" /> (TypeScript) or `RunAsContainer` (C#) to run a local PostgreSQL container with auto-generated credentials instead of provisioning an Azure resource during development.
+- **Easy local development.** Call <ApiReference name="Aspire.Hosting.AzurePostgresExtensions.RunAsContainer" /> to run a local PostgreSQL container with auto-generated credentials instead of provisioning an Azure resource during development.
 - **Consistent connection info across languages.** Once you reference the database from a consuming app, Aspire injects connection properties as environment variables in a predictable format that works from C#, TypeScript, Python, Go, or any other language.
 - **Built-in health checks.** The hosting integration automatically registers a health check so the dashboard and your orchestrator can tell when the server is ready.
 - **Dashboard observability.** The database resource shows up in the Aspire dashboard with logs, status, and telemetry alongside your other services.
diff --git a/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx b/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
index f863db8014..53da5e9072 100644
--- a/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
+++ b/src/frontend/src/content/docs/integrations/databases/efcore/seed-database.mdx
@@ -53,7 +53,7 @@ The recommended method for executing database seeding scripts depends on the dat
 <Tabs syncKey="efcore-db-provider">
 <TabItem label="SQL Server">
 
-With Aspire, you can use the <ApiReference name="Aspire.Hosting.PostgresBuilderExtensions.WithCreationScript" /> method to ensure a T-SQL script is run when the database is created. Add SQL code to this script that creates and populates the database, the necessary tables, and other database objects.
+With Aspire, you can use the <ApiReference name="Aspire.Hosting.SqlServerBuilderExtensions.WithCreationScript" /> method to ensure a T-SQL script is run when the database is created. Add SQL code to this script that creates and populates the database, the necessary tables, and other database objects.
 
 The following code is an example T-SQL script that creates and populates an address book database:
 
diff --git a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
index e1f7e6ecc6..faf5c18197 100644
--- a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
@@ -177,7 +177,7 @@ const tunnel = await builder.addDevTunnel("qa", "my-tunnel-id", false, "QA envir
 
 ### Configure for mixed access
 
-To allow anonymous access to specific endpoints, use the appropriate <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.WithReference" /> overload:
+To allow anonymous access to specific endpoints, use the appropriate <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.WithReference" /> overload:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">
diff --git a/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx b/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
index 26e9fe98c7..9cca1e01b8 100644
--- a/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
+++ b/src/frontend/src/content/docs/ja/architecture/resource-examples.mdx
@@ -14,7 +14,7 @@ Aspire では柔軟なリソースモデルが提供されており、構造化
 
 - データのみを保持するリソースクラスの定義。
 - `ReferenceExpression` を使用した遅延評価での `IResourceWithConnectionString` の実装。
-- パラメーター検証、パスワード管理、イベント購読、正常性チェック、Fluent API を使ったコンテナー構成を処理する <ApiReference name="Aspire.Hosting.RedisBuilderExtensions.AddRedis" /> 拡張メソッドの作成。
+- パラメーター検証、パスワード管理、イベント購読、正常性チェック、Fluent API を使ったコンテナー構成を処理する `AddRedis` 拡張メソッドの作成。
 
 ```csharp title="C# — RedisResourceExtensions.cs"
 public static class RedisResourceExtensions
diff --git a/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
index da9cffbc2b..1b93a2d6ee 100644
--- a/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/ja/get-started/aspire-vscode-extension.mdx
@@ -116,7 +116,7 @@ Aspire は VS Code に AppHost ビューを登録します。**Workspace** モ
 ```
 
 サポートされている起動コマンドは次の 4 つです:
-- <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> は AppHost を実行します (省略した場合の既定)。
+- `run` は AppHost を実行します (省略した場合の既定)。
 - `deploy` は、AppHost で定義されたデプロイ先にプッシュします。
 - `publish` は、ターゲットへのプッシュを行わずに、Kubernetes マニフェストや Bicep ファイルなどのデプロイ成果物を生成します。
 - `do` は、AppHost のデプロイ パイプラインで定義された特定のステップを実行します。`step` には、実行するステップ名を設定します。

From ae29203cf46f8c86e2e5f2a11a06f02c76097b43 Mon Sep 17 00:00:00 2001
From: David Pine <david.pine@microsoft.com>
Date: Fri, 9 Oct 2026 22:02:50 -0500
Subject: [PATCH 5/9] Update
 src/frontend/src/content/docs/app-host/container-files.mdx

---
 src/frontend/src/content/docs/app-host/container-files.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/frontend/src/content/docs/app-host/container-files.mdx b/src/frontend/src/content/docs/app-host/container-files.mdx
index 8db656de87..080ecfb63d 100644
--- a/src/frontend/src/content/docs/app-host/container-files.mdx
+++ b/src/frontend/src/content/docs/app-host/container-files.mdx
@@ -9,8 +9,8 @@ import ApiReference from '@components/ApiReference.astro';
 
 Aspire provides APIs to inject files and directories into containers, enabling you to configure containerized resources with custom configuration files, scripts, certificates, and other assets. There are two complementary APIs:
 
-- **<ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerFiles" />**: Injects files into containers at development time when they start during `aspire run`.
-- **<ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" />**: Copies files from one resource's container into another resource's container as build artifacts at publish time during `aspire publish`.
+- <ApiReference name="Aspire.Hosting.ContainerResourceBuilderExtensions.WithContainerFiles" />: Injects files into containers at development time when they start during `aspire run`.
+- <ApiReference name="Aspire.Hosting.ResourceBuilderExtensions.PublishWithContainerFiles" />: Copies files from one resource's container into another resource's container as build artifacts at publish time during `aspire publish`.
 
 ## Inject files at development time
 

From f483cb38f817a2c540b65583123ac12ed77c93f7 Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Mon, 12 Oct 2026 16:48:51 +0100
Subject: [PATCH 6/9] Removed several inappropriate uses of the ApiReference
 component.

---
 .../content/docs/deployment/kubernetes/persistent-volumes.mdx | 4 ++--
 .../src/content/docs/get-started/aspire-vscode-extension.mdx  | 2 +-
 .../cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx    | 2 +-
 src/frontend/src/content/docs/whats-new/aspire-13-2.mdx       | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
index cb7b93ab2d..248fb895ef 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
@@ -101,7 +101,7 @@ The available configuration methods are:
 |---|---|---|
 | `WithStorageClass(string)` | `withStorageClass` / `withStorageClassParam` | Sets `spec.storageClassName` on the PVC. In C#, the single method accepts a literal string or an Aspire parameter; in TypeScript, use `withStorageClass` for a literal and `withStorageClassParam` for a parameter. |
 | `WithCapacity(string)` | `withCapacity` / `withCapacityParam` | Sets the requested storage on `spec.resources.requests.storage` (for example, `"20Gi"`). In TypeScript, use `withCapacity` for a literal and `withCapacityParam` for a parameter. |
-| `WithAccessMode(PersistentVolumeAccessMode)` | <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithAccessMode" /> | Adds an entry to `spec.accessModes`. Call multiple times to declare more than one mode. |
+| `WithAccessMode(PersistentVolumeAccessMode)` | `withAccessMode` | Adds an entry to `spec.accessModes`. Call multiple times to declare more than one mode. |
 | `WithVolumeAnnotation(string, string)` | `withVolumeAnnotation` / `withVolumeAnnotationParam` | Adds a key-value pair to the PVC's `metadata.annotations`. Useful for CSI driver hints, dynamic provisioner parameters, or backup tooling tags. In TypeScript, use `withVolumeAnnotation` for a literal value and `withVolumeAnnotationParam` for a parameter. |
 
 The `PersistentVolumeAccessMode` values map directly to the Kubernetes access modes:
@@ -229,7 +229,7 @@ A Kubernetes access mode such as `ReadWriteOnce` controls how a volume can be at
   The automatic security context described in this section requires Aspire 13.6 or later.
 </Aside>
 
-To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, <ApiReference name="Aspire.Hosting.KubernetesPersistentVolumeExtensions.WithPersistentVolume" /> and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
+To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, `withPersistentVolume` and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
 
 ```yaml
 securityContext:
diff --git a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
index 592b5ef2bd..f0128cd0f2 100644
--- a/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
+++ b/src/frontend/src/content/docs/get-started/aspire-vscode-extension.mdx
@@ -87,7 +87,7 @@ In Aspire 13.6, the extension exposes two VS Code language model tools so a codi
 
 | Tool                   | Chat reference        | Action                                               |
 | ---------------------- | --------------------- | ---------------------------------------------------- |
-| `aspire_apphost_start` | `#aspireStartAppHost` | Start a discovered AppHost in <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> or `debug` mode. |
+| `aspire_apphost_start` | `#aspireStartAppHost` | Start a discovered AppHost in `run` or `debug` mode. |
 | `aspire_apphost_stop`  | `#aspireStopAppHost`  | Stop the selected discovered AppHost.                |
 
 Open a trusted workspace with the Aspire extension installed and an AppHost visible in the Aspire view. In an agent chat that supports VS Code tools, try:
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
index 7df6c19380..bc987f4d7d 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/azure-event-hubs/azure-event-hubs-host.mdx
@@ -404,7 +404,7 @@ builder.AddProject<Projects.ExampleService>()
 ```
 
 <Aside type="note">
-  <ApiReference name="Aspire.Hosting.YarpResourceExtensions.WithConfiguration" /> is not available in the TypeScript AppHost. Use `withConfigurationFile` to supply a fully customized configuration file instead.
+  `withConfiguration` is not available in the TypeScript AppHost. Use `withConfigurationFile` to supply a fully customized configuration file instead.
 </Aside>
 
 ## Connect to an existing Azure Event Hubs namespace
diff --git a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
index 5a7306f3fa..9a893633a8 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-13-2.mdx
@@ -414,7 +414,7 @@ When an Aspire apphost is running, the extension now shows inline CodeLens above
 - Action buttons: Start, Stop, Restart, View Logs
 - Custom resource commands from the runtime
 
-Colored gutter decorations appear alongside resource definitions — green for running, blue for starting, red for errors, gray for stopped — giving you an at-a-glance view of your entire app's health right in the editor. Both features are backed by language-aware parsers that understand `DistributedApplication.CreateBuilder` in C# and <ApiReference name="Aspire.Hosting.DistributedApplication.CreateBuilder" /> in TypeScript.
+Colored gutter decorations appear alongside resource definitions — green for running, blue for starting, red for errors, gray for stopped — giving you an at-a-glance view of your entire app's health right in the editor. Both features are backed by language-aware parsers that understand `DistributedApplication.CreateBuilder` in C# and `createBuilder` in TypeScript.
 
 ### Getting Started walkthrough
 

From 9ee0b4856887bbd8e6bae0e8d3a7492f2a92cae6 Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Mon, 12 Oct 2026 17:04:39 +0100
Subject: [PATCH 7/9] Fixed one failing unit test.

---
 .../src/content/docs/integrations/devtools/dev-tunnels.mdx      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
index faf5c18197..bd26342a9e 100644
--- a/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
+++ b/src/frontend/src/content/docs/integrations/devtools/dev-tunnels.mdx
@@ -177,7 +177,7 @@ const tunnel = await builder.addDevTunnel("qa", "my-tunnel-id", false, "QA envir
 
 ### Configure for mixed access
 
-To allow anonymous access to specific endpoints, use the appropriate <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.WithReference" /> overload:
+To allow anonymous access to specific endpoints, use the appropriate <ApiReference name="Aspire.Hosting.DevTunnelsResourceBuilderExtensions.WithReference" parameterTypes={['Aspire.Hosting.ApplicationModel.IResourceBuilder<Aspire.Hosting.DevTunnels.DevTunnelResource>', 'Aspire.Hosting.ApplicationModel.EndpointReference', 'bool']} /> overload:
 
 <Tabs syncKey="aspire-lang">
 <TabItem id="csharp" label="C#">

From 5611e4b70d1ffea52ffa1e84f5cb48ad73187a1b Mon Sep 17 00:00:00 2001
From: David Pine <7679720+IEvangelist@users.noreply.github.com>
Date: Mon, 12 Oct 2026 22:25:40 -0500
Subject: [PATCH 8/9] Fix command and TypeScript API reference regressions

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 92354b96-5c95-491b-93fe-453cb0e1499d
---
 .../deployment/kubernetes/persistent-volumes.mdx     |  2 +-
 .../integrations/cloud/azure/customize-resources.mdx |  2 +-
 .../src/content/docs/whats-new/aspire-9-2.mdx        |  2 +-
 src/frontend/tests/unit/api-reference.vitest.test.ts | 12 ++++++++++++
 4 files changed, 15 insertions(+), 3 deletions(-)

diff --git a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
index 248fb895ef..4624d9c4ff 100644
--- a/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
+++ b/src/frontend/src/content/docs/deployment/kubernetes/persistent-volumes.mdx
@@ -229,7 +229,7 @@ A Kubernetes access mode such as `ReadWriteOnce` controls how a volume can be at
   The automatic security context described in this section requires Aspire 13.6 or later.
 </Aside>
 
-To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, `withPersistentVolume` and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
+To avoid that out-of-the-box failure, both `WithPersistentVolume(...)` overloads — and their TypeScript equivalents, `withKubernetesPersistentVolume` and `withKubernetesPersistentVolumeMount` — add the following pod security context to the workload automatically:
 
 ```yaml
 securityContext:
diff --git a/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx b/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
index 157b0da1cb..d10d64a2cd 100644
--- a/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
+++ b/src/frontend/src/content/docs/integrations/cloud/azure/customize-resources.mdx
@@ -813,7 +813,7 @@ builder.Build().Run();
 
 <Aside type="tip">
   For inline Bicep snippets, use `AddBicepTemplateString` (C#) or
-  <ApiReference name="Aspire.Hosting.AzureBicepResourceExtensions.AddBicepTemplateString" /> (TypeScript) instead of `AddBicepTemplate`. Both APIs
+  `addBicepTemplateString` (TypeScript) instead of `AddBicepTemplate`. Both APIs
   return the same `AzureBicepResource` and support the same `WithParameter` and
   `GetOutput` patterns.
 </Aside>
diff --git a/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx b/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
index c9cbba24e5..64bc999c4a 100644
--- a/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
+++ b/src/frontend/src/content/docs/whats-new/aspire-9-2.mdx
@@ -495,7 +495,7 @@ aspire publish --publisher docker-compose
 #### Available commands:
 
 - `new <template>` – Create a new Aspire sample project
-- <ApiReference name="Aspire.Hosting.DistributedApplication.RunAsync" /> – Run an Aspire AppHost in development mode
+- `run` – Run an Aspire AppHost in development mode
 - `add <integration>` – Add an integration to your project
 - `publish` – Generate deployment artifacts from your AppHost
 
diff --git a/src/frontend/tests/unit/api-reference.vitest.test.ts b/src/frontend/tests/unit/api-reference.vitest.test.ts
index a018979206..3f3e5413e0 100644
--- a/src/frontend/tests/unit/api-reference.vitest.test.ts
+++ b/src/frontend/tests/unit/api-reference.vitest.test.ts
@@ -1234,6 +1234,18 @@ describe('API reference authoring validator', () => {
     ]);
   });
 
+  it.each([
+    ['whats-new/aspire-9-2.mdx', '- `run`'],
+    ['integrations/cloud/azure/customize-resources.mdx', '`addBicepTemplateString` (TypeScript)'],
+    [
+      'deployment/kubernetes/persistent-volumes.mdx',
+      '`withKubernetesPersistentVolume` and `withKubernetesPersistentVolumeMount`',
+    ],
+  ])('keeps command and language-specific identifiers literal in %s', (file, identifier) => {
+    const docsRoot = fileURLToPath(new URL('../../src/content/docs/', import.meta.url));
+    expect(fs.readFileSync(path.join(docsRoot, file), 'utf8')).toContain(identifier);
+  });
+
   it('resolves every authored API reference against the generated catalogs', () => {
     const frontendRoot = fileURLToPath(new URL('../..', import.meta.url));
     const readJsonDocuments = <T>(directory: string): T[] =>

From b9ba5b663c06d0f90963ff43c51bc947f3f21b16 Mon Sep 17 00:00:00 2001
From: AJ Matthews <alistairwebdojo@live.com>
Date: Tue, 13 Oct 2026 16:22:23 +0100
Subject: [PATCH 9/9] Fixed the failing unit test.

---
 .../tests/unit/dashboard-image-references.vitest.test.ts      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/frontend/tests/unit/dashboard-image-references.vitest.test.ts b/src/frontend/tests/unit/dashboard-image-references.vitest.test.ts
index a4960b8891..1de12e5ba9 100644
--- a/src/frontend/tests/unit/dashboard-image-references.vitest.test.ts
+++ b/src/frontend/tests/unit/dashboard-image-references.vitest.test.ts
@@ -81,10 +81,10 @@ describe('standalone dashboard container images', () => {
     expect(commands).toHaveLength(2);
     for (const command of commands) {
       expect(command).toContain(
-        '--mount type=volume,source=aspire-dashboard-data,target=/dashboard-data'
+        '--mount type=volume,source=aspire-dashboard-data,target=/home/app'
       );
       expect(command).toContain('-e ASPIRE_DASHBOARD_APPLICATION_NAME=my-app');
-      expect(command).toContain('-e ASPIRE_DASHBOARD_DATA_DIRECTORY=/dashboard-data');
+      expect(command).toContain('-e ASPIRE_DASHBOARD_DATA_DIRECTORY=/home/app/dashboard-data');
       expect(command).toContain('-e ASPIRE_DASHBOARD_PERSISTENCE_MODE=run');
     }
   });