Reframe ADP as standalone, and drop MCP-built-on-Connect claim

modules/ROOT/pages/index.adoc

@@ -36,9 +36,9 @@ For more information, see xref:agents:overview.adoc[].
 
 glossterm:MCP server[,MCP servers] translate agent intent into connections to databases, queues, HRIS, CRMs, and other business systems. They are the simplest way to give agents context and capabilities without writing glue code.
 
-Under the hood, MCP servers wrap the same proven connectors that power some of the world's largest e-commerce, EV, electricity, and AI companies. Built on xref:redpanda-cloud:develop:connect/about.adoc[Redpanda Connect], they are lightweight, support OIDC-based authentication, and enforce deterministic policies at the tool level. You define tools in YAML, and policy enforcement programmatically prevents prompt injection, SQL injection, and other agent-based attacks.
+MCP servers are lightweight, support OIDC-based authentication, and enforce deterministic policies at the tool level. You define tools in YAML, and policy enforcement programmatically prevents prompt injection, SQL injection, and other agent-based attacks.
 
-With over 300 connectors and real-time debugging capabilities, you reduce integration time while getting enterprise-grade security. You can reuse your existing infrastructure and data sources rather than building new integrations from scratch.
+With real-time debugging capabilities, you reduce integration time while getting enterprise-grade security. You can reuse your existing infrastructure and data sources rather than building new integrations from scratch.
 
 For more information, see xref:mcp:overview.adoc[MCP Servers Overview].
 

modules/ROOT/partials/ai-hub-mode-indicator.adoc

@@ -1,8 +1,8 @@
 [tabs]
 ====
-Redpanda Cloud Console::
+ADP UI::
 +
-In the Redpanda Cloud Console:
+In ADP:
 +
 . Navigate to *Agentic* → *AI Gateway* → *Gateways*.
 . Select a gateway from your list.

modules/ROOT/partials/ai-hub/configure-ai-hub.adoc

@@ -18,17 +18,17 @@ After reading this page, you will be able to:
 
 == Prerequisites
 
-* Access to the Redpanda Cloud Console with administrator privileges
+* Access to ADP with administrator privileges
 * API keys for at least one LLM provider:
 ** OpenAI: API key from https://platform.openai.com/api-keys
 ** Anthropic: API key from https://console.anthropic.com/settings/keys
-* A Redpanda Cloud workspace
+* An ADP workspace
 
 == Create an AI Hub gateway
 
 Creating an AI Hub gateway is significantly simpler than creating a Custom mode gateway because all routing rules and backend pools are pre-configured.
 
-. In the Redpanda Cloud Console, navigate to *Agentic* → *AI Gateway* → *Gateways*.
+. In ADP, navigate to *Agentic* → *AI Gateway* → *Gateways*.
 . Click *Create Gateway*.
 . Select *AI Hub* as the gateway mode.
 . Configure basic settings:

modules/ROOT/partials/ai-hub/use-ai-hub-gateway.adoc

@@ -19,7 +19,7 @@ After reading this page, you will be able to:
 == Before you begin
 
 * You have access to at least one AI Hub gateway (provided by your administrator)
-* You have a Redpanda Cloud API key
+* You have an ADP API key
 * You have Python 3.8+ or Node.js 18+ installed (for code examples)
 
 == Identify an AI Hub gateway

modules/ROOT/partials/integrations/claude-code-admin.adoc

@@ -44,7 +44,7 @@ Claude Code requires access to LLM providers through the gateway. Enable at leas
 
 Claude Code uses Anthropic models by default. To enable Anthropic:
 
-. Navigate to *AI Gateway* > *Providers* in the Redpanda Cloud console
+. Navigate to *AI Gateway* > *Providers* in ADP
 . Select *Anthropic* from the provider list
 . Click *Add configuration*
 . Enter your Anthropic API key
@@ -268,7 +268,7 @@ Claude Code clients authenticate using bearer tokens.
 
 === Generate API tokens
 
-. Navigate to *Security* > *API Tokens* in the Redpanda Cloud console
+. Navigate to *Security* > *API Tokens* in ADP
 . Click *Create Token*
 . Enter token details:
 +

modules/ROOT/partials/integrations/claude-code-user.adoc

@@ -202,7 +202,7 @@ If deferred tool loading is enabled in your gateway, you'll see a search tool an
 
 Check that requests route through the gateway by monitoring the AI Gateway dashboard:
 
-. Open the Redpanda Cloud Console
+. Sign in to ADP
 . Navigate to your gateway's observability dashboard
 . Send a test request from Claude Code:
 +
@@ -292,7 +292,7 @@ curl -H "Authorization: Bearer YOUR_API_KEY" \
      <your-gateway-endpoint>/mcp
 ----
 +
-You should receive a valid MCP protocol response. If you get `401 Unauthorized`, regenerate your API key in the Redpanda Cloud Console.
+You should receive a valid MCP protocol response. If you get `401 Unauthorized`, regenerate your API key in ADP.
 
 . **Gateway endpoint URL mismatch**
 +
@@ -335,7 +335,7 @@ Ensure requests use the `vendor/model_id` format (for example, `anthropic/claude
 
 . **Gateway geographic distance**
 +
-If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in the Redpanda Cloud Console.
+If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in ADP.
 
 . **Provider pool failover**
 +

modules/ROOT/partials/integrations/cline-admin.adoc

@@ -55,7 +55,7 @@ Cline requires access to LLM providers through the gateway. Enable at least one
 
 Cline uses Anthropic models by default. To enable Anthropic:
 
-. Navigate to *AI Gateway* > *Providers* in the Redpanda Cloud console
+. Navigate to *AI Gateway* > *Providers* in ADP
 . Select *Anthropic* from the provider list
 . Click *Add configuration*
 . Enter your Anthropic API key
@@ -286,7 +286,7 @@ Cline clients authenticate using bearer tokens.
 
 === Generate API tokens
 
-. Navigate to *Security* > *API Tokens* in the Redpanda Cloud console
+. Navigate to *Security* > *API Tokens* in ADP
 . Click *Create Token*
 . Enter token details:
 +

modules/ROOT/partials/integrations/cline-user.adoc

@@ -246,7 +246,7 @@ Send a test message in the Cline chat panel:
 
 Then verify in the AI Gateway dashboard:
 
-. Open the Redpanda Cloud Console
+. Sign in to ADP
 . Navigate to your gateway's observability dashboard
 . Filter by gateway ID
 . Verify:
@@ -466,7 +466,7 @@ curl -H "Authorization: Bearer YOUR_API_KEY" \
      <your-gateway-endpoint>/v1/models
 ----
 +
-You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in the Redpanda Cloud Console.
+You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in ADP.
 
 . **Gateway endpoint URL mismatch**
 +
@@ -715,7 +715,7 @@ This loads only essential tools initially. Cline queries for additional tools on
 
 Use AI Gateway spend limits to prevent runaway costs:
 
-. Navigate to your gateway in the Redpanda Cloud Console
+. Navigate to your gateway in ADP
 . Set monthly spend limit (for example, $500/month)
 . Configure alerts before reaching limit
 

modules/ROOT/partials/integrations/continue-admin.adoc

@@ -58,7 +58,7 @@ Continue.dev works with multiple providers. Enable the providers your users will
 
 To enable Anthropic with native format support:
 
-. Navigate to *AI Gateway* > *Providers* in the Redpanda Cloud console
+. Navigate to *AI Gateway* > *Providers* in ADP
 . Select *Anthropic* from the provider list
 . Click *Add configuration*
 . Enter your Anthropic API key
@@ -378,7 +378,7 @@ Continue.dev clients authenticate using bearer tokens.
 
 === Generate API tokens
 
-. Navigate to *Security* > *API Tokens* in the Redpanda Cloud console
+. Navigate to *Security* > *API Tokens* in ADP
 . Click *Create Token*
 . Enter token details:
 +

modules/ROOT/partials/integrations/continue-user.adoc

@@ -302,7 +302,7 @@ After configuring Continue.dev, verify it connects correctly to your AI Gateway.
 
 Then verify in the AI Gateway dashboard:
 
-. Open the Redpanda Cloud Console
+. Sign in to ADP
 . Navigate to your gateway's observability dashboard
 . Filter by gateway ID
 . Verify:
@@ -529,7 +529,7 @@ curl -H "Authorization: Bearer YOUR_API_KEY" \
      <your-gateway-endpoint>/v1/models
 ----
 +
-You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in the Redpanda Cloud Console.
+You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in ADP.
 
 . **Invalid JSON syntax**
 +

modules/ROOT/partials/integrations/cursor-admin.adoc

@@ -58,7 +58,7 @@ Cursor IDE works with multiple providers through OpenAI-compatible transforms. E
 
 Cursor sends OpenAI-formatted requests but can route to Anthropic models. Configure the gateway to transform these requests:
 
-. Navigate to *AI Gateway* > *Providers* in the Redpanda Cloud console
+. Navigate to *AI Gateway* > *Providers* in ADP
 . Select *Anthropic* from the provider list
 . Click *Add configuration*
 . Enter your Anthropic API key
@@ -342,7 +342,7 @@ Cursor clients authenticate using bearer tokens in the `Authorization` header.
 
 === Generate API tokens
 
-. Navigate to *Security* > *API Tokens* in the Redpanda Cloud console
+. Navigate to *Security* > *API Tokens* in ADP
 . Click *Create Token*
 . Enter token details:
 +

modules/ROOT/partials/integrations/cursor-user.adoc

@@ -319,7 +319,7 @@ After configuring Cursor IDE, verify it connects correctly to your AI Gateway.
 
 Then verify in the AI Gateway dashboard:
 
-. Open the Redpanda Cloud Console
+. Sign in to ADP
 . Navigate to your gateway's observability dashboard
 . Filter by gateway ID
 . Verify:
@@ -513,7 +513,7 @@ curl -H "Authorization: Bearer YOUR_API_KEY" \
      <your-gateway-endpoint>/models
 ----
 +
-You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in the Redpanda Cloud Console.
+You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in ADP.
 
 . **Gateway endpoint URL mismatch**
 +
@@ -665,7 +665,7 @@ Check if `.vscode/settings.json` in your project root overrides global settings
 
 . **Gateway geographic distance**
 +
-If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in the Redpanda Cloud Console.
+If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in ADP.
 
 . **Provider pool failover**
 +

modules/ROOT/partials/integrations/github-copilot-admin.adoc

@@ -59,7 +59,7 @@ GitHub Copilot works with multiple providers through OpenAI-compatible transform
 
 GitHub Copilot uses OpenAI by default. To enable OpenAI through the gateway:
 
-. Navigate to *AI Gateway* > *Providers* in the Redpanda Cloud console
+. Navigate to *AI Gateway* > *Providers* in ADP
 . Select *OpenAI* from the provider list
 . Click *Add configuration*
 . Enter your OpenAI API key
@@ -290,7 +290,7 @@ GitHub Copilot clients authenticate using bearer tokens in the `Authorization` h
 
 === Generate API tokens
 
-. Navigate to *Security* > *API Tokens* in the Redpanda Cloud console
+. Navigate to *Security* > *API Tokens* in ADP
 . Click *Create Token*
 . Enter token details:
 +

modules/ROOT/partials/integrations/github-copilot-user.adoc

@@ -449,7 +449,7 @@ Chat requests appear in the gateway dashboard with:
 
 === Verify in dashboard
 
-. Open the Redpanda Cloud Console
+. Sign in to ADP
 . Navigate to your gateway's observability dashboard
 . Filter by gateway ID
 . Verify:
@@ -599,7 +599,7 @@ curl -H "Authorization: Bearer YOUR_API_KEY" \
      https://gw.ai.panda.com/v1/models
 ----
 +
-You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in the Redpanda Cloud Console.
+You should receive a list of available models. If you get `401 Unauthorized`, regenerate your API key in ADP.
 
 . **Extension/plugin disabled**
 +
@@ -654,7 +654,7 @@ echo $REDPANDA_API_KEY  # Should print your API key
 
 . **Gateway geographic distance**
 +
-If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in the Redpanda Cloud Console.
+If your gateway is in a different region than you or the upstream provider, this adds network latency. Check gateway region in ADP.
 
 . **Slow model for completion**
 +
@@ -764,7 +764,7 @@ gpt-5.2
 +
 Verify the model is enabled in your AI Gateway configuration:
 +
-.. Open Redpanda Cloud Console
+.. Sign in to ADP
 .. Navigate to your gateway
 .. Check enabled providers and models
 

modules/ROOT/partials/migration-guide.adoc

@@ -16,7 +16,7 @@ This guide helps you migrate existing applications from direct LLM provider inte
 
 Before migrating, ensure you have:
 
-* AI Gateway configured in your Redpanda Cloud account
+* AI Gateway configured in your ADP account
 * Enabled providers and models in AI Gateway
 * Created gateway with appropriate policies
 * Your gateway endpoint URL (with the gateway ID embedded in the path)

modules/ROOT/partials/observability-logs.adoc

@@ -11,7 +11,7 @@ AI Gateway logs every LLM request that passes through it, capturing the full req
 == Before you begin
 
 * You have an active AI Gateway with at least one request processed.
-* You have access to the Redpanda Cloud Console.
+* You have access to ADP.
 * You have the appropriate permissions to view gateway logs.
 
 Use logs for:

modules/ROOT/partials/observability-metrics.adoc

@@ -11,7 +11,7 @@ AI Gateway provides aggregate metrics and analytics dashboards to help you under
 == Before you begin
 
 * You have an active AI Gateway with at least one request processed.
-* You have access to the Redpanda Cloud Console.
+* You have access to ADP.
 * You have the appropriate permissions to view gateway metrics.
 
 Use metrics for:

modules/ROOT/partials/service-account-authorization.adoc

@@ -1,7 +1,7 @@
 [[service-account-authorization]] 
 == Service account authorization
 
-When you create an MCP server or AI agent, Redpanda Cloud automatically creates a service account to authenticate requests to your cluster. The service account is created with the following:
+When you create an MCP server or AI agent, ADP automatically creates a service account to authenticate requests to ADP resources. The service account is created with the following:
 
 *Name*: Prepopulated as `cluster-<cluster-id>-<resource-type>-<resource-name>-sa`, where `sa` stands for service account. For example:
 

modules/agents/pages/a2a-concepts.adoc

@@ -6,7 +6,7 @@
 :learning-objective-2: Explain how agent cards enable discovery
 :learning-objective-3: Identify how authentication secures agent communication
 
-The Agent-to-Agent (A2A) protocol is an open standard for agent communication and discovery. Redpanda Cloud uses A2A for both external integration and internal pipeline-to-agent communication.
+The Agent-to-Agent (A2A) protocol is an open standard for agent communication and discovery. ADP uses A2A for both external integration and internal pipeline-to-agent communication.
 
 After reading this page, you will be able to:
 
@@ -38,21 +38,21 @@ The agent card is a JSON document that describes what the agent can do and how t
 [#agent-card-location]
 === Agent card location
 
-Redpanda Cloud agents expose their agent cards at the `/.well-known/agent-card.json` subpath of the agent URL. You can find the agent URL on the agent overview page in the Redpanda Cloud Console under *Agentic AI* > *AI Agents*.
+ADP agents expose their agent cards at the `/.well-known/agent-card.json` subpath of the agent URL. You can find the agent URL on the agent overview page in the ADP UI under *Agentic AI* > *AI Agents*.
 
 For example, if your agent URL is `\https://my-agent.ai-agents.abc123.cloud.redpanda.com`, your agent card URL is `\https://my-agent.ai-agents.abc123.cloud.redpanda.com/.well-known/agent-card.json`.
 
 The `.well-known` path follows internet standards for service discovery, making agents discoverable without configuration.
 
 To configure the agent card, see xref:create-agent.adoc#configure-a2a-discovery-metadata-optional[Configure A2A discovery metadata].
 
-== Where A2A is used in Redpanda Cloud
+== Where A2A is used in ADP
 
-Redpanda Cloud uses the A2A protocol in two contexts:
+ADP uses the A2A protocol in two contexts:
 
 === External integration
 
-External applications and agents hosted outside Redpanda Cloud use A2A to call Redpanda Cloud agents. This includes backend services, CLI tools, custom UIs, and agents hosted on other platforms.
+External applications and agents hosted outside ADP use A2A to call ADP agents. This includes backend services, CLI tools, custom UIs, and agents hosted on other platforms.
 
 For integration pattern guidance, see xref:integration-overview.adoc[].
 
@@ -85,7 +85,7 @@ This discovery model allows:
 
 A2A-compliant agents require authentication to prevent unauthorized access.
 
-Redpanda Cloud agents use OAuth2 client credentials flow. When you create an agent, the system provisions a service account with a client ID and secret.
+ADP agents use OAuth2 client credentials flow. When you create an agent, the system provisions a service account with a client ID and secret.
 
 External callers use these credentials to obtain access tokens:
 
@@ -108,7 +108,7 @@ For step-by-step authentication instructions, see xref:redpanda-cloud:security:c
 
 === Internal integration
 
-The `a2a_message` processor handles authentication automatically. Pipelines don't need to manage credentials explicitly because they run within the Redpanda Cloud cluster with appropriate permissions.
+The `a2a_message` processor handles authentication automatically. Pipelines don't need to manage credentials explicitly because they run within ADP with appropriate permissions.
 
 == Protocol versions