redpanda-data · micheleRP · Jul 1, 2026 · Jun 30, 2026 · Jun 30, 2026 · Jul 1, 2026
@@ -1,8 +1,8 @@
 * xref:home:index.adoc[Overview]
 
 * xref:get-started:index.adoc[Get Started]
-** xref:get-started:adp-overview.adoc[Redpanda ADP Overview]
-** xref:get-started:adp-quickstart.adoc[ADP Quickstart]
+** xref:get-started:adp-overview.adoc[Redpanda Agentic Data Plane Overview]
+** xref:get-started:adp-quickstart.adoc[Agentic Data Plane Quickstart]
 
 * xref:connect:agents.adoc[Build Agents]
 ** xref:connect:agents-overview.adoc[How Agents Work]
@@ -49,7 +49,7 @@
 ** xref:connect:integrations.adoc[Integrate with Your Stack]
 *** xref:connect:integration-overview.adoc[Choose an Integration Pattern]
 *** xref:connect:pipeline-integration-patterns.adoc[Integrate with Redpanda Pipelines]
-*** xref:connect:claude-code.adoc[Use Claude Code with ADP]
+*** xref:connect:claude-code.adoc[Use Claude Code with Agentic Data Plane]
 
 * xref:monitor:index.adoc[Monitor & Debug]
 ** xref:monitor:concepts.adoc[How Observability Works]
@@ -74,7 +74,7 @@
 *** xref:gateway:bedrock-setup.adoc[Set Up AWS Bedrock as an LLM Provider]
 ** xref:gateway:connect-agent.adoc[Connect Your App to AI Gateway]
 
-* xref:cli:index.adoc[Use the ADP CLI]
+* xref:cli:index.adoc[Use the Agentic Data Plane CLI]
 ** xref:cli:gitops.adoc[Manage Resources with GitOps]
 
 * xref:reference:index.adoc[Reference]

@@ -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 ADP account
+* AI Gateway configured in your Agentic Data Plane 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)

@@ -1,15 +1,15 @@
 = Manage Resources with GitOps
 :page-beta: true
-:description: Keep ADP resources in Git and reconcile them with rpk ai apply and diff: declarative create-or-update, drift detection, and CI gating.
+:description: Keep Agentic Data Plane resources in Git and reconcile them with rpk ai apply and diff: declarative create-or-update, drift detection, and CI gating.
 :page-topic-type: how-to
 :personas: platform_engineer, agent_builder
-:learning-objective-1: Export an ADP resource to a YAML manifest you can commit to Git
+:learning-objective-1: Export an Agentic Data Plane resource to a YAML manifest you can commit to Git
 :learning-objective-2: Reconcile resources with apply, and preview changes with diff
 :learning-objective-3: Gate continuous integration on configuration drift
 
 // Source: cloudv2 `apps/rpai/internal/gitops/` (engine.go, command.go, manifest.go, doc.go), the per-resource policies in `apps/rpai/internal/cmd/{llm,mcp,oauth,oauthclient,agent}/gitops.go`, `proto/public/cloud/redpanda/api/adp/v1alpha1/llm_provider.proto`, and `rpk ai <resource> apply|diff --help`. Console output verified against the engine and `apps/rpai/internal/gitops/engine_test.go`. Verified against origin/main 2026-06-26.
 
-GitOps keeps the definition of your glossterm:Agentic Data Plane (ADP)[] resources in Git and reconciles the live environment toward those files, instead of running imperative `create`, `update`, and `delete` commands by hand. With the xref:cli:index.adoc[ADP CLI], `rpk ai <resource> apply -f` creates what is missing and updates what has drifted, and `rpk ai <resource> diff -f` is a read-only dry-run that reports what `apply` would change. In these commands, `<resource>` is one of the resource command groups that support GitOps:
+GitOps keeps the definition of your glossterm:Agentic Data Plane (ADP)[] resources in Git and reconciles the live environment toward those files, instead of running imperative `create`, `update`, and `delete` commands by hand. With the xref:cli:index.adoc[Agentic Data Plane CLI], `rpk ai <resource> apply -f` creates what is missing and updates what has drifted, and `rpk ai <resource> diff -f` is a read-only dry-run that reports what `apply` would change. In these commands, `<resource>` is one of the resource command groups that support GitOps:
 
 * LLM providers (`rpk ai llm`)
 * MCP servers (`rpk ai mcp`)
@@ -25,9 +25,9 @@ After reading this page, you will be able to:
 
 == Prerequisites
 
-* The xref:cli:index.adoc[ADP CLI installed and connected] to an ADP environment.
+* The xref:cli:index.adoc[Agentic Data Plane CLI installed and connected] to an Agentic Data Plane environment.
 * Permission to create and update the resources you manage. The reconcile commands call the same APIs as `create` and `update`. See xref:control:permissions-reference.adoc[Roles and Permissions Reference].
-* Any secrets your manifests reference already created in ADP. Manifests name secrets by reference, for example, `OPENAI_API_KEY`; the CLI does not create secrets.
+* Any secrets your manifests reference already created in Agentic Data Plane. Manifests name secrets by reference, for example, `OPENAI_API_KEY`; the CLI does not create secrets.
 
 == How apply and diff reconcile
 

@@ -1,17 +1,17 @@
-= Use the ADP CLI
+= Use the Agentic Data Plane CLI
 :page-beta: true
 :description: Manage Agentic Data Plane resources from the terminal with rpk ai. Install the CLI, connect it to an AI Gateway, and script LLM providers, MCP servers, OAuth, and agents.
 :page-topic-type: how-to
 :personas: platform_engineer, agent_builder
-:learning-objective-1: Install the ADP CLI and connect it to an AI Gateway
-:learning-objective-2: Manage ADP resources from the terminal: LLM providers, MCP servers, OAuth providers and clients, and agents
+:learning-objective-1: Install the Agentic Data Plane CLI and connect it to an AI Gateway
+:learning-objective-2: Manage Agentic Data Plane resources from the terminal: LLM providers, MCP servers, OAuth providers and clients, and agents
 :learning-objective-3: Format command output for scripts and pipelines
 
-// Source: cloudv2 `apps/rpai/README.md`, `apps/rpai/internal/cmd/root.go` (plugin-mode command surface + persistent flags), `apps/rpai/internal/cmd/env/cmd.go`, and `rpk ai <command> --help`, cross-referenced against `modules/gateway/pages/connect-agent.adoc` and `modules/reference/pages/rpk/rpk-ai/`. Connect/auth model reflects cloudv2 PR #27510: rpk ai is self-contained (its own `auth login` device flow + ADP environment selection), not tied to the rpk cloud session. Verified against origin/main 2026-06-29 (cloudv2 PR #27510 merged).
+// Source: cloudv2 `apps/rpai/README.md`, `apps/rpai/internal/cmd/root.go` (plugin-mode command surface + persistent flags), `apps/rpai/internal/cmd/env/cmd.go`, and `rpk ai <command> --help`, cross-referenced against `modules/gateway/pages/connect-agent.adoc` and `modules/reference/pages/rpk/rpk-ai/`. Connect/auth model reflects cloudv2 PR #27510: rpk ai is self-contained (its own `auth login` device flow + Agentic Data Plane environment selection), not tied to the rpk cloud session. Verified against origin/main 2026-06-29 (cloudv2 PR #27510 merged).
 
-The ADP command-line interface, `rpk ai`, manages glossterm:Agentic Data Plane (ADP)[] resources from your terminal. It drives the same control surface as the ADP UI: glossterm:large language model (LLM)[] providers, glossterm:Model Context Protocol (MCP)[] servers, OAuth providers and clients, and agents. Because every action is a command, you can script it and run it in continuous integration.
+The Agentic Data Plane command-line interface, `rpk ai`, manages glossterm:Agentic Data Plane (ADP)[] resources from your terminal. It drives the same control surface as the Agentic Data Plane UI: glossterm:large language model (LLM)[] providers, glossterm:Model Context Protocol (MCP)[] servers, OAuth providers and clients, and agents. Because every action is a command, you can script it and run it in continuous integration.
 
-The ADP CLI, also called the Redpanda AI CLI, runs as an xref:reference:rpk/rpk-ai/rpk-ai.adoc[`rpk`] plugin, so you install and run it through your existing `rpk` setup.
+The Agentic Data Plane CLI, also called the Redpanda AI CLI, runs as an xref:reference:rpk/rpk-ai/rpk-ai.adoc[`rpk`] plugin, so you install and run it through your existing `rpk` setup.
 
 After reading this page, you will be able to:
 
@@ -21,7 +21,7 @@ After reading this page, you will be able to:
 
 == Install the CLI
 
-The ADP CLI is an `rpk` managed plugin. Install `rpk` first (see xref:reference:rpk-install.adoc[Install or Update rpk]), then install the plugin:
+The Agentic Data Plane CLI is an `rpk` managed plugin. Install `rpk` first (see xref:reference:rpk-install.adoc[Install or Update rpk]), then install the plugin:
 
 [,bash]
 ----
@@ -32,9 +32,9 @@ Update the plugin later with xref:reference:rpk/rpk-ai/rpk-ai-upgrade.adoc[`rpk
 
 == Connect to an AI Gateway
 
-The `rpk ai` command is self-contained: it has its own login and its own environment selection, independent of any `rpk cloud` session. You sign in once, choose an ADP environment, and `rpk ai` targets that environment's AI Gateway for every command.
+The `rpk ai` command is self-contained: it has its own login and its own environment selection, independent of any `rpk cloud` session. You sign in once, choose an Agentic Data Plane environment, and `rpk ai` targets that environment's AI Gateway for every command.
 
-. Sign in to Redpanda Cloud. This runs an OAuth device-authorization flow in your browser, caches credentials in `~/.rpai/credentials` (readable only by you), then lists the ADP environments in your organization so you can pick one:
+. Sign in to Redpanda Cloud. This runs an OAuth device-authorization flow in your browser, caches credentials in `~/.rpai/credentials` (readable only by you), then lists the Agentic Data Plane environments in your organization so you can pick one:
 +
 [,bash]
 ----
@@ -49,7 +49,7 @@ rpk ai env list
 rpk ai env use <environment>
 ----
 +
-In these commands, `<environment>` is the name or ID of an ADP environment. `rpk ai env use` repoints the active profile at that environment's AI Gateway in place. Inspect the resolved environment and token state at any time with `rpk ai env show` and `rpk ai auth status`.
+In these commands, `<environment>` is the name or ID of an Agentic Data Plane environment. `rpk ai env use` repoints the active profile at that environment's AI Gateway in place. Inspect the resolved environment and token state at any time with `rpk ai env show` and `rpk ai auth status`.
 
 . Verify the connection:
 +
@@ -77,7 +77,7 @@ rpk ai env use local
 
 == Manage resources
 
-Each ADP resource has its own command group, and each group supports the standard `create`, `get`, `list`, `update`, and `delete` actions. The model catalog is read-only.
+Each Agentic Data Plane resource has its own command group, and each group supports the standard `create`, `get`, `list`, `update`, and `delete` actions. The model catalog is read-only.
 
 [cols="1m,2,1a"]
 |===
@@ -116,7 +116,7 @@ rpk ai llm create --name openai --type openai --api-key-ref OPENAI_API_KEY
 rpk ai llm get openai
 ----
 
-In this command, `--api-key-ref` names a secret already stored in ADP. The CLI never takes a raw API key, so secrets stay out of your shell history and out of any file you commit.
+In this command, `--api-key-ref` names a secret already stored in Agentic Data Plane. The CLI never takes a raw API key, so secrets stay out of your shell history and out of any file you commit.
 
 To create, update, and delete resources declaratively from YAML manifests instead of imperative flags, see xref:cli:gitops.adoc[Manage Resources with GitOps].
 

@@ -5,11 +5,11 @@
       "description": "Create a managed MCP server following the documented procedure",
       "steps": [
         {
-          "description": "Navigate to ADP UI",
+          "description": "Navigate to Agentic Data Plane UI",
           "goTo": "https://adp.redpanda.com"
         },
         {
-          "description": "Verify user is on the ADP UI home page",
+          "description": "Verify user is on the Agentic Data Plane UI home page",
           "find": "MCP Servers"
         },
         {

@@ -1,6 +1,6 @@
 = Connect Agents with A2A
 :page-aliases: cloud-data-platform:ai-agents:agents/a2a-concepts.adoc, cloud-data-platform:ai-agents:agents/agent-to-agent-integration.adoc
-:description: The A2A protocol enables agents to discover and call each other across platforms. Learn how agent cards, authentication, and protocol versioning work in ADP.
+:description: The A2A protocol enables agents to discover and call each other across platforms. Learn how agent cards, authentication, and protocol versioning work in Agentic Data Plane.
 :page-topic-type: concepts
 :personas: agent_builder
 :learning-objective-1: Describe the A2A protocol and its role in agent communication
@@ -9,7 +9,7 @@
 
 The Agent-to-Agent (A2A) protocol is an open standard that defines how agents discover, communicate with, and call each other across platforms. Each A2A-compliant agent exposes a machine-readable agent card at a well-known URL, describing its capabilities and how to authenticate with it. Callers fetch the card at runtime, so they reach any A2A agent without prior knowledge of its implementation, and agents can update their capabilities without breaking existing callers.
 
-In Redpanda ADP, A2A enables two integration paths: external applications and agents calling ADP agents over HTTP, and Redpanda Connect pipelines invoking agents for each event in a stream.
+In Redpanda Agentic Data Plane, A2A enables two integration paths: external applications and agents calling Agentic Data Plane agents over HTTP, and Redpanda Connect pipelines invoking agents for each event in a stream.
 
 After reading this page, you will be able to:
 
@@ -41,7 +41,7 @@ The agent card is a JSON document that describes what the agent can do and how t
 [#agent-card-location]
 === Agent card location
 
-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 *Agents* page.
+Agentic Data Plane 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 *Agents* page.
 
 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`.
 
@@ -51,13 +51,13 @@ The agent card is served without authentication. The A2A protocol requires the d
 
 To configure the agent card, see xref:connect:create-agent.adoc#configure-a2a-discovery-metadata-optional[Configure A2A discovery metadata].
 
-== Where A2A is used in ADP
+== Where A2A is used in Agentic Data Plane
 
-ADP uses the A2A protocol in two contexts:
+Agentic Data Plane uses the A2A protocol in two contexts:
 
 === External integration
 
-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.
+External applications and agents hosted outside Agentic Data Plane use A2A to call Agentic Data Plane agents. This includes backend services, CLI tools, custom UIs, and agents hosted on other platforms.
 
 For integration pattern guidance, see xref:connect:integration-overview.adoc[].
 
@@ -91,9 +91,9 @@ This discovery model allows:
 
 A2A-compliant agents require authentication to prevent unauthorized access.
 
-The agent card is the exception. ADP serves the card at the `/.well-known/agent-card.json` subpath without authentication, so that callers can discover how to authenticate before they hold a token. Every other request to the agent, including agent invocation, requires a valid access token.
+The agent card is the exception. Agentic Data Plane serves the card at the `/.well-known/agent-card.json` subpath without authentication, so that callers can discover how to authenticate before they hold a token. Every other request to the agent, including agent invocation, requires a valid access token.
 
-ADP agents use OAuth2 client credentials flow. When you create an agent, the system provisions a service account with a client ID and secret.
+Agentic Data Plane 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:
 
@@ -116,7 +116,7 @@ For step-by-step authentication instructions, see xref:cloud-data-platform:secur
 
 === Internal integration
 
-The `a2a_message` processor handles authentication automatically. Pipelines don't need to manage credentials explicitly because they run within ADP with appropriate permissions.
+The `a2a_message` processor handles authentication automatically. Pipelines don't need to manage credentials explicitly because they run within Agentic Data Plane with appropriate permissions.
 
 == Protocol versions