From 75170fdc0f5dc6d8c9fb66ac22963be8d4397b37 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 16:52:30 -0600 Subject: [PATCH 01/10] Align page titles with workflow nav voice Updates the H1 titles on 15 pages so the page header matches the nav label readers click to reach it. Uses the conversational/customer framing from the prototype where it's clearer, the standard term where the prototype phrasing was awkward, and a merged wording where both perspectives add value. Connect & tools: Managed MCP Server Catalog -> Plug in an App, Database, or Tool Configure User-Delegated OAuth (trimmed "for an MCP Server") Connect Remote MCP Clients (trimmed "to AI Gateway") Monitor & debug: Read a Transcript -> See What Your Agent Did Metrics -> Check Speed, Cost, and Errors Read Violations -> Review Blocked Requests BYOA Telemetry -> Send BYOA Telemetry (OpenTelemetry) Control & govern: Read the Governance Overview -> See All Your Agents in One Place Token Budgets and Limits -> Set Spending Limits and Token Budgets About ADP Permissions -> Control Who Can Do What Routing & LLM settings: AI Gateway Overview -> How AI Gateway Works Reference: Settings reference -> Reference ADP Permissions Reference -> Roles and Permissions Reference Evaluator Types Reference -> Guardrail Evaluator Types Reference rpk Commands -> rpk Command Reference Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/connect/pages/managed/managed-catalog.adoc | 2 +- modules/connect/pages/remote-mcp-clients.adoc | 2 +- modules/connect/pages/user-delegated-oauth.adoc | 2 +- modules/control/pages/budgets.adoc | 2 +- modules/control/pages/dashboard/overview.adoc | 2 +- modules/control/pages/guardrails/types-reference.adoc | 2 +- modules/control/pages/guardrails/violations.adoc | 2 +- modules/control/pages/permissions-overview.adoc | 2 +- modules/control/pages/permissions-reference.adoc | 2 +- modules/gateway/pages/overview.adoc | 2 +- modules/monitor/pages/byoa-telemetry.adoc | 2 +- modules/monitor/pages/metrics.adoc | 2 +- modules/monitor/pages/transcripts.adoc | 2 +- modules/reference/pages/index.adoc | 2 +- modules/reference/pages/rpk/index.adoc | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) diff --git a/modules/connect/pages/managed/managed-catalog.adoc b/modules/connect/pages/managed/managed-catalog.adoc index bec721d..ec716c7 100644 --- a/modules/connect/pages/managed/managed-catalog.adoc +++ b/modules/connect/pages/managed/managed-catalog.adoc @@ -1,4 +1,4 @@ -= Managed MCP Server Catalog += Plug in an App, Database, or Tool :description: Reference of every managed MCP server type Redpanda hosts in-process, grouped by category, with display name, description, and a link to a deep-dive where one exists. :page-topic-type: reference :personas: agent_builder, platform_engineer diff --git a/modules/connect/pages/remote-mcp-clients.adoc b/modules/connect/pages/remote-mcp-clients.adoc index 5f5ac44..ddfd47a 100644 --- a/modules/connect/pages/remote-mcp-clients.adoc +++ b/modules/connect/pages/remote-mcp-clients.adoc @@ -1,4 +1,4 @@ -= Connect Remote MCP Clients to AI Gateway += Connect Remote MCP Clients :description: Connect external MCP clients (Claude Desktop, ChatGPT desktop, Gemini Apps) to MCP servers hosted in AI Gateway. Covers the three-piece architecture (MCP server, OAuth Provider, OAuth Client) and the two-step OAuth flow that runs end-to-end. :page-topic-type: how-to :personas: agent_builder, platform_engineer, security_compliance_lead diff --git a/modules/connect/pages/user-delegated-oauth.adoc b/modules/connect/pages/user-delegated-oauth.adoc index 628eb53..3a9c0a1 100644 --- a/modules/connect/pages/user-delegated-oauth.adoc +++ b/modules/connect/pages/user-delegated-oauth.adoc @@ -1,4 +1,4 @@ -= Configure User-Delegated OAuth for an MCP Server += Configure User-Delegated OAuth :description: Have each end-user authenticate against the MCP server's upstream system with their own credentials. Redpanda stores their token in the vault and injects it at call time. :page-topic-type: how-to :personas: platform_engineer, agent_builder, security_compliance_lead diff --git a/modules/control/pages/budgets.adoc b/modules/control/pages/budgets.adoc index 3486464..4d03045 100644 --- a/modules/control/pages/budgets.adoc +++ b/modules/control/pages/budgets.adoc @@ -1,4 +1,4 @@ -= Token Budgets and Limits += Set Spending Limits and Token Budgets :description: See what AI spending the Agentic Data Plane records automatically and where to view it. :page-topic-type: overview :personas: platform_engineer, pilot_lead diff --git a/modules/control/pages/dashboard/overview.adoc b/modules/control/pages/dashboard/overview.adoc index c0b4410..c3a1188 100644 --- a/modules/control/pages/dashboard/overview.adoc +++ b/modules/control/pages/dashboard/overview.adoc @@ -1,4 +1,4 @@ -= Read the Governance Overview += See All Your Agents in One Place :description: Read ADP spend, request, token, agent, and top-user activity from the Governance dashboard. :page-topic-type: how-to :personas: pilot_lead, platform_engineer, security_compliance_lead diff --git a/modules/control/pages/guardrails/types-reference.adoc b/modules/control/pages/guardrails/types-reference.adoc index f0f842a..b3ba032 100644 --- a/modules/control/pages/guardrails/types-reference.adoc +++ b/modules/control/pages/guardrails/types-reference.adoc @@ -1,4 +1,4 @@ -= Evaluator Types Reference += Guardrail Evaluator Types Reference :description: Definitive reference for every evaluator type's config schema, supported phases, behavior on match, and gotchas. :page-topic-type: reference :personas: security_compliance_lead, platform_engineer diff --git a/modules/control/pages/guardrails/violations.adoc b/modules/control/pages/guardrails/violations.adoc index 8d50152..f8f7a48 100644 --- a/modules/control/pages/guardrails/violations.adoc +++ b/modules/control/pages/guardrails/violations.adoc @@ -1,4 +1,4 @@ -= Read Violations += Review Blocked Requests :description: Investigate why a guardrail fired, distinguish a violation from an evaluator failure, and tune the configuration. :page-topic-type: how-to :personas: security_compliance_lead, platform_engineer, agent_builder diff --git a/modules/control/pages/permissions-overview.adoc b/modules/control/pages/permissions-overview.adoc index 35fbd0d..63667b6 100644 --- a/modules/control/pages/permissions-overview.adoc +++ b/modules/control/pages/permissions-overview.adoc @@ -1,4 +1,4 @@ -= About ADP Permissions += Control Who Can Do What :description: Understand how ADP permissions, built-in roles, and role bindings fit together to control access to AI Gateway, MCP, agents, pipelines, and governance APIs. :page-topic-type: concept :personas: security_compliance_lead, platform_engineer diff --git a/modules/control/pages/permissions-reference.adoc b/modules/control/pages/permissions-reference.adoc index 4bbb5fa..e0b29c5 100644 --- a/modules/control/pages/permissions-reference.adoc +++ b/modules/control/pages/permissions-reference.adoc @@ -1,4 +1,4 @@ -= ADP Permissions Reference += Roles and Permissions Reference :description: Look up the permissions ADP enforces across LLM providers, MCP servers, agents, pipelines, knowledge bases, and governance APIs, and the built-in roles that grant them. :page-topic-type: reference :personas: security_compliance_lead, platform_engineer diff --git a/modules/gateway/pages/overview.adoc b/modules/gateway/pages/overview.adoc index 82f6a39..bef9b1d 100644 --- a/modules/gateway/pages/overview.adoc +++ b/modules/gateway/pages/overview.adoc @@ -1,4 +1,4 @@ -= AI Gateway Overview += How AI Gateway Works :description: AI Gateway is ADP's managed proxy for LLM APIs. Create a provider for OpenAI, Anthropic, Google AI, AWS Bedrock, or an OpenAI-compatible endpoint, and point your applications at a Redpanda-hosted URL with managed secrets, authentication, and observability. :page-topic-type: overview :personas: agent_builder, platform_engineer, security_compliance_lead diff --git a/modules/monitor/pages/byoa-telemetry.adoc b/modules/monitor/pages/byoa-telemetry.adoc index a7018ff..ca177b6 100644 --- a/modules/monitor/pages/byoa-telemetry.adoc +++ b/modules/monitor/pages/byoa-telemetry.adoc @@ -1,4 +1,4 @@ -= BYOA Telemetry (OpenTelemetry) += Send BYOA Telemetry (OpenTelemetry) :description: Emit OpenTelemetry traces from your BYOA (Bring Your Own Agent) so the Agentic Data Plane can attribute calls, costs, and tool invocations to your agent. Covers the minimum required span contract, common optional attributes, and how it differs from a Redpanda-managed agent. :page-topic-type: how-to :personas: agent_builder, platform_engineer diff --git a/modules/monitor/pages/metrics.adoc b/modules/monitor/pages/metrics.adoc index 5c5ab5e..e31ba82 100644 --- a/modules/monitor/pages/metrics.adoc +++ b/modules/monitor/pages/metrics.adoc @@ -1,4 +1,4 @@ -= Metrics += Check Speed, Cost, and Errors :description: Monitor AI agent metrics in Redpanda ADP. // TODO: Add content diff --git a/modules/monitor/pages/transcripts.adoc b/modules/monitor/pages/transcripts.adoc index fd29daf..c470892 100644 --- a/modules/monitor/pages/transcripts.adoc +++ b/modules/monitor/pages/transcripts.adoc @@ -1,4 +1,4 @@ -= Read a Transcript += See What Your Agent Did :description: Open a transcript in the Agentic Data Plane UI, read the conversation turn by turn, and investigate errors, costs, and performance. :page-topic-type: how-to :personas: agent_builder, domain_evaluator, platform_engineer, security_compliance_lead diff --git a/modules/reference/pages/index.adoc b/modules/reference/pages/index.adoc index a75d416..1fbe193 100644 --- a/modules/reference/pages/index.adoc +++ b/modules/reference/pages/index.adoc @@ -1,3 +1,3 @@ -= Settings reference += Reference :description: Field and command reference for Agentic Data Plane. :page-layout: index diff --git a/modules/reference/pages/rpk/index.adoc b/modules/reference/pages/rpk/index.adoc index 566fd50..a56eb8c 100644 --- a/modules/reference/pages/rpk/index.adoc +++ b/modules/reference/pages/rpk/index.adoc @@ -1,4 +1,4 @@ -= rpk Commands += rpk Command Reference :description: Reference for the rpk commands used to manage the Redpanda Agentic Data Plane from the command line. :page-layout: index From 6c8d198b5edc57229b90004f13e14033df78cbca Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 16:52:31 -0600 Subject: [PATCH 02/10] Align nav labels with page titles where the page wording is stronger Updates 17 nav labels in modules/ROOT/nav.adoc. Keeps the prototype's conversational voice for items where it's clearer (transcripts, metrics, dashboard overview, permissions) and adopts the page-side wording where the standard term reads more directly (Create an Agent, Create an MCP Server, Troubleshoot AI Agents, Guardrails Overview). Also renames the top-level section header from 'Settings reference' to 'Reference' to match the page title and to align with the docs and cloud-docs reference modules. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/ROOT/nav.adoc | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 8bdb9b7..31cf7ae 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -5,38 +5,38 @@ * xref:connect:index.adoc[Connect data & tools] ** xref:connect:managed/managed-catalog.adoc[Plug in any app, database, or tool] -** xref:connect:create-agent.adoc[Turn your data source into an agent] -** xref:connect:create-server.adoc[Build a tool server for your own data] -** xref:connect:register-remote.adoc[Connect a tool server you host yourself] -** xref:connect:user-delegated-oauth.adoc[Let agents act as the signed-in user] -** xref:connect:byoa-register.adoc[Register your own agent (BYOA)] -** xref:connect:claude-code.adoc[Claude Code] -** xref:connect:remote-mcp-clients.adoc[Remote MCP clients] +** xref:connect:create-agent.adoc[Create an Agent] +** xref:connect:create-server.adoc[Create an MCP Server] +** xref:connect:register-remote.adoc[Register a Self-Managed MCP Server] +** xref:connect:user-delegated-oauth.adoc[Configure User-Delegated OAuth] +** xref:connect:byoa-register.adoc[Register Your Own Agent (BYOA)] +** xref:connect:claude-code.adoc[Use Claude Code with ADP] +** xref:connect:remote-mcp-clients.adoc[Connect Remote MCP Clients] * xref:monitor:index.adoc[Monitor & debug] ** xref:monitor:transcripts.adoc[See what your agent did] -** xref:monitor:troubleshoot-ai-agents.adoc[Investigate a broken run] +** xref:monitor:troubleshoot-ai-agents.adoc[Troubleshoot AI Agents] ** xref:monitor:metrics.adoc[Check speed, cost, and errors] ** xref:control:guardrails/violations.adoc[Review blocked requests] ** xref:monitor:byoa-telemetry.adoc[Send telemetry from agents you host] * xref:control:index.adoc[Control & govern] ** xref:control:dashboard/overview.adoc[See all your agents in one place] -** xref:control:guardrails/overview.adoc[Fix agents calling things they shouldn't] -** xref:control:guardrails/create-guardrail.adoc[Set safety rules for all agents] +** xref:control:guardrails/overview.adoc[Guardrails Overview] +** xref:control:guardrails/create-guardrail.adoc[Create a Guardrail] ** xref:control:budgets.adoc[Set spending limits] ** xref:control:permissions-overview.adoc[Control who can do what] * xref:gateway:index.adoc[Routing & LLM settings] ** xref:gateway:overview.adoc[How the gateway works] -** xref:gateway:configure-provider.adoc[Configure LLM provider] -*** xref:gateway:bedrock-setup.adoc[Set up AWS Bedrock] +** xref:gateway:configure-provider.adoc[Configure an LLM Provider] +*** xref:gateway:bedrock-setup.adoc[Set Up AWS Bedrock as an LLM Provider] -* xref:reference:index.adoc[Settings reference] -** xref:control:permissions-reference.adoc[Roles and permissions matrix] -** xref:control:guardrails/types-reference.adoc[Safety rule providers] -** xref:reference:rpk-install.adoc[Install rpk] -** xref:reference:rpk/index.adoc[rpk command reference] +* xref:reference:index.adoc[Reference] +** xref:control:permissions-reference.adoc[Roles and Permissions Reference] +** xref:control:guardrails/types-reference.adoc[Guardrail Evaluator Types Reference] +** xref:reference:rpk-install.adoc[Install or Update rpk] +** xref:reference:rpk/index.adoc[rpk Command Reference] *** xref:reference:rpk/rpk-ai/rpk-ai.adoc[rpk ai] **** xref:reference:rpk/rpk-ai/rpk-ai-agent.adoc[] ***** xref:reference:rpk/rpk-ai/rpk-ai-agent-list.adoc[] From 63950697269324afb1e4e8aa3775d9e9337c4410 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:00:40 -0600 Subject: [PATCH 03/10] Drop obsolete 'Agentic' UI breadcrumb prefix The ADP UI used to nest AI Gateway, AI Agents, Remote MCP, Transcripts, and Providers under a top-level 'Agentic' (or 'Agentic AI') parent. That bucket is gone; those sections are now top-level in the sidebar. Strips '*Agentic* > ' and '*Agentic AI* > ' from every body-text breadcrumb so click paths match the current UI. 25 occurrences across 17 files. Examples: *Agentic* > *AI Gateway* > *Gateways* -> *AI Gateway* > *Gateways* *Agentic AI* > *AI Agents* -> *AI Agents* *Agentic AI* > *Remote MCP* -> *Remote MCP* The 'Agentic Data Plane' product name (no bold + no trailing >) is not matched by either pattern and is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/ROOT/partials/migration-guide.adoc | 4 ++-- modules/connect/pages/a2a-concepts.adoc | 2 +- .../pages/tutorials/customer-support-agent.adoc | 4 ++-- .../tutorials/transaction-dispute-resolution.adoc | 10 +++++----- .../partials/integrations/claude-code-admin.adoc | 2 +- modules/connect/partials/integrations/cline-admin.adoc | 2 +- .../connect/partials/integrations/continue-admin.adoc | 2 +- .../connect/partials/integrations/cursor-admin.adoc | 2 +- .../partials/integrations/github-copilot-admin.adoc | 2 +- modules/gateway/pages/aggregation.adoc | 2 +- modules/gateway/pages/builders/discover-gateways.adoc | 2 +- modules/get-started/pages/gateway-quickstart.adoc | 6 +++--- modules/get-started/pages/quickstart.adoc | 2 +- modules/monitor/pages/monitor-agents.adoc | 2 +- modules/monitor/pages/troubleshoot-ai-agents.adoc | 2 +- modules/monitor/partials/observability-logs.adoc | 2 +- modules/monitor/partials/observability-metrics.adoc | 2 +- 17 files changed, 25 insertions(+), 25 deletions(-) diff --git a/modules/ROOT/partials/migration-guide.adoc b/modules/ROOT/partials/migration-guide.adoc index 5d6ca1d..6c448d3 100644 --- a/modules/ROOT/partials/migration-guide.adoc +++ b/modules/ROOT/partials/migration-guide.adoc @@ -346,7 +346,7 @@ Common issues: After successful test: 1. Open AI Gateway observability dashboard -2. In the sidebar, navigate to *Agentic* > *AI Gateway* > *Gateways* > *{GATEWAY_NAME}*, then select the *Logs* tab. +2. In the sidebar, navigate to *AI Gateway* > *Gateways* > *{GATEWAY_NAME}*, then select the *Logs* tab. 3. Verify your test request appears 4. Check fields: * Model: `openai/gpt-5.2-mini` @@ -716,7 +716,7 @@ Causes: Solution: -1. Verify model is enabled: In the sidebar, navigate to *Agentic* > *AI Gateway* > *Models* and confirm the model is enabled. +1. Verify model is enabled: In the sidebar, navigate to *AI Gateway* > *Models* and confirm the model is enabled. 2. Confirm format: `vendor/model_id` (for example, `openai/gpt-5.2`, not `gpt-5.2` without prefix) 3. Check supported models: // PLACEHOLDER: link to model catalog diff --git a/modules/connect/pages/a2a-concepts.adoc b/modules/connect/pages/a2a-concepts.adoc index 3eda4f0..e2a2c7c 100644 --- a/modules/connect/pages/a2a-concepts.adoc +++ b/modules/connect/pages/a2a-concepts.adoc @@ -38,7 +38,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 agent overview page in the Agentic Data Plane UI 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 Agentic Data Plane UI under *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`. diff --git a/modules/connect/pages/tutorials/customer-support-agent.adoc b/modules/connect/pages/tutorials/customer-support-agent.adoc index a27fa74..67b74aa 100644 --- a/modules/connect/pages/tutorials/customer-support-agent.adoc +++ b/modules/connect/pages/tutorials/customer-support-agent.adoc @@ -62,7 +62,7 @@ This granularity enables the agent to chain tools (check order status, see it's Create a Remote MCP server with the three tools. . Sign in to ADP. -. Go to *Agentic AI* > *Remote MCP*. +. Go to *Remote MCP*. . Click *Create MCP Server*. . Configure the server: + @@ -113,7 +113,7 @@ The system prompt teaches the agent how to orchestrate tools. Without explicit g Create the customer support agent with the system prompt. -. Go to *Agentic AI* > *AI Agents*. +. Go to *AI Agents*. . Click *Create Agent*. . Configure the agent: + diff --git a/modules/connect/pages/tutorials/transaction-dispute-resolution.adoc b/modules/connect/pages/tutorials/transaction-dispute-resolution.adoc index d329736..a1a3c02 100644 --- a/modules/connect/pages/tutorials/transaction-dispute-resolution.adoc +++ b/modules/connect/pages/tutorials/transaction-dispute-resolution.adoc @@ -46,7 +46,7 @@ Before creating agents, create the tools they'll use. You'll organize tools by d Account tools retrieve customer and transaction data with PII protection. . Sign in to ADP. -. Go to *Agentic AI* > *Remote MCP*. +. Go to *Remote MCP*. . Click *Create MCP Server*. . Configure the server: + @@ -218,7 +218,7 @@ The root agent orchestrates sub-agents and makes final recommendations. You'll c Sub-agents inherit the LLM provider, model, resource tier, and max iterations from the root agent. This tutorial uses GPT-5 Mini and max iterations of 15 to optimize performance. Using slower models (GPT-5.2, Claude Sonnet 4.5) or high max iterations (50+) will cause sub-agents to execute slowly. Each sub-agent call could take 60-90 seconds instead of 10-15 seconds. ==== -. Go to *Agentic AI* > *AI Agents*. +. Go to *AI Agents*. . Click *Create Agent*. . Configure the root agent: + @@ -324,7 +324,7 @@ Wait for the agent status to show *Running*. Test the multi-agent system with realistic dispute scenarios. Each scenario demonstrates different patterns: clear fraud, legitimate transactions, escalation cases, and edge cases. -. Go to *Agentic AI* > *AI Agents*. +. Go to *AI Agents*. . Click on `dispute-resolution-agent`. . Open the *Inspector* tab. @@ -396,7 +396,7 @@ Process disputes automatically from transaction streams. When transactions meet The pipeline needs the agent card URL to invoke the dispute resolution agent. -. Go to *Agentic AI* > *AI Agents*. +. Go to *AI Agents*. . Click on `dispute-resolution-agent`. . Open the *A2A* tab. . Copy the agent URL displayed at the top. @@ -624,7 +624,7 @@ Only transactions meeting the risk threshold invoke the dispute resolution agent Use the pipeline metadata timestamp to find the corresponding agent execution in the *Transcripts* view. . Note the `processed_at` timestamp from the pipeline output (for example: `2026-01-26T18:30:45.000Z`). -. Go to *Agentic AI* > *Transcripts*. +. Go to *Transcripts*. . Find transcripts for `dispute-resolution-agent` that match your timestamp. [NOTE] diff --git a/modules/connect/partials/integrations/claude-code-admin.adoc b/modules/connect/partials/integrations/claude-code-admin.adoc index fe34f84..b5721f0 100644 --- a/modules/connect/partials/integrations/claude-code-admin.adoc +++ b/modules/connect/partials/integrations/claude-code-admin.adoc @@ -86,7 +86,7 @@ Create a dedicated gateway to isolate Claude Code traffic and apply specific pol === Gateway configuration -. Navigate to *Agentic* > *AI Gateway* > *Gateways* +. Navigate to *AI Gateway* > *Gateways* . Click *Create Gateway* . Enter gateway details: + diff --git a/modules/connect/partials/integrations/cline-admin.adoc b/modules/connect/partials/integrations/cline-admin.adoc index 8f21b8a..a69356e 100644 --- a/modules/connect/partials/integrations/cline-admin.adoc +++ b/modules/connect/partials/integrations/cline-admin.adoc @@ -97,7 +97,7 @@ Create a dedicated gateway to isolate Cline traffic and apply specific policies. === Gateway configuration -. Navigate to *Agentic* > *AI Gateway* > *Gateways* +. Navigate to *AI Gateway* > *Gateways* . Click *Create Gateway* . Enter gateway details: + diff --git a/modules/connect/partials/integrations/continue-admin.adoc b/modules/connect/partials/integrations/continue-admin.adoc index eb993cf..5e6c70f 100644 --- a/modules/connect/partials/integrations/continue-admin.adoc +++ b/modules/connect/partials/integrations/continue-admin.adoc @@ -118,7 +118,7 @@ Create a dedicated gateway to isolate Continue.dev traffic and apply specific po === Gateway configuration -. Navigate to *Agentic* > *AI Gateway* > *Gateways* +. Navigate to *AI Gateway* > *Gateways* . Click *Create Gateway* . Enter gateway details: + diff --git a/modules/connect/partials/integrations/cursor-admin.adoc b/modules/connect/partials/integrations/cursor-admin.adoc index 6b951fc..6c50b68 100644 --- a/modules/connect/partials/integrations/cursor-admin.adoc +++ b/modules/connect/partials/integrations/cursor-admin.adoc @@ -117,7 +117,7 @@ Create a dedicated gateway to isolate Cursor traffic and apply specific policies === Gateway configuration -. Navigate to *Agentic* > *AI Gateway* > *Gateways* +. Navigate to *AI Gateway* > *Gateways* . Click *Create Gateway* . Enter gateway details: + diff --git a/modules/connect/partials/integrations/github-copilot-admin.adoc b/modules/connect/partials/integrations/github-copilot-admin.adoc index bb157af..560f049 100644 --- a/modules/connect/partials/integrations/github-copilot-admin.adoc +++ b/modules/connect/partials/integrations/github-copilot-admin.adoc @@ -117,7 +117,7 @@ Create a dedicated gateway to isolate GitHub Copilot traffic and apply specific === Gateway configuration -. Navigate to *Agentic* > *AI Gateway* > *Gateways* +. Navigate to *AI Gateway* > *Gateways* . Click *Create Gateway* . Enter gateway details: + diff --git a/modules/gateway/pages/aggregation.adoc b/modules/gateway/pages/aggregation.adoc index d7d878f..52395c5 100644 --- a/modules/gateway/pages/aggregation.adoc +++ b/modules/gateway/pages/aggregation.adoc @@ -559,7 +559,7 @@ Steps: 1. Navigate to MCP servers: - * In the sidebar, navigate to *Agentic* > *AI Gateway* > *Gateways*, select your gateway, then select the *MCP* tab. + * In the sidebar, navigate to *AI Gateway* > *Gateways*, select your gateway, then select the *MCP* tab. 2. Configure server: + diff --git a/modules/gateway/pages/builders/discover-gateways.adoc b/modules/gateway/pages/builders/discover-gateways.adoc index af74d76..c95f666 100644 --- a/modules/gateway/pages/builders/discover-gateways.adoc +++ b/modules/gateway/pages/builders/discover-gateways.adoc @@ -25,7 +25,7 @@ After reading this page, you will be able to: ==== Using the UI:: + -. In ADP, navigate to *Agentic* > *AI Gateway* > *Gateways*. +. In ADP, navigate to *AI Gateway* > *Gateways*. . Review the list of gateways you can access. For each gateway, you'll see the gateway name, ID, endpoint URL, status, available models, and provider performance. + Click the Configuration, API, MCP Tools, and Changelog tabs for additional information. diff --git a/modules/get-started/pages/gateway-quickstart.adoc b/modules/get-started/pages/gateway-quickstart.adoc index c4f3b24..cbd7791 100644 --- a/modules/get-started/pages/gateway-quickstart.adoc +++ b/modules/get-started/pages/gateway-quickstart.adoc @@ -22,7 +22,7 @@ Before starting, ensure you have: Providers represent upstream LLM services and their associated credentials. Providers are disabled by default and must be enabled explicitly. -. Navigate to *Agentic* > *AI Gateway* > *Providers*. +. Navigate to *AI Gateway* > *Providers*. . Select a provider (for example, OpenAI, Anthropic, Google AI, AWS Bedrock). . On the Configuration tab, click *Add configuration* and enter the provider's credentials (API key for OpenAI, Anthropic, and Google AI; AWS access key and secret for Bedrock). . Verify the provider status shows as active. @@ -31,7 +31,7 @@ Providers represent upstream LLM services and their associated credentials. Prov After enabling a provider, enable the specific models you want to make available through your gateways. -. Navigate to *Agentic* > *AI Gateway* > *Models*. +. Navigate to *AI Gateway* > *Models*. . Enable the models you want to use (for example, `gpt-5.2-mini`, `claude-sonnet-4.5`, `claude-opus-4.6`). . Verify the models appear as enabled in the model catalog. @@ -55,7 +55,7 @@ A gateway is a logical configuration boundary that defines rate limits, spend li * Team isolation: One gateway per team for budget tracking * Customer multi-tenancy: One gateway per customer for isolated policies -. Navigate to *Agentic* > *AI Gateway* > *Gateways*. +. Navigate to *AI Gateway* > *Gateways*. . Click *Create Gateway*. . Configure the gateway: + diff --git a/modules/get-started/pages/quickstart.adoc b/modules/get-started/pages/quickstart.adoc index a48b390..fca2a1f 100644 --- a/modules/get-started/pages/quickstart.adoc +++ b/modules/get-started/pages/quickstart.adoc @@ -40,7 +40,7 @@ The agent orchestrates the `generate_input` and `redpanda_output` tools you crea . Sign in to ADP. -. Click *Agentic AI* > *AI Agents* in the left navigation. +. Click *AI Agents* in the left navigation. . Click *Create Agent*. diff --git a/modules/monitor/pages/monitor-agents.adoc b/modules/monitor/pages/monitor-agents.adoc index fe02d96..f8f42cc 100644 --- a/modules/monitor/pages/monitor-agents.adoc +++ b/modules/monitor/pages/monitor-agents.adoc @@ -79,7 +79,7 @@ The *Inspector* tab provides real-time conversation testing. Use it to test agen === Access Inspector -. In ADP, navigate to *Agentic AI* > *AI Agents*. +. In ADP, navigate to *AI Agents*. . Click your agent name. . Open the *Inspector* tab. . Enter test queries and review responses. diff --git a/modules/monitor/pages/troubleshoot-ai-agents.adoc b/modules/monitor/pages/troubleshoot-ai-agents.adoc index b8777f7..ffde8e3 100644 --- a/modules/monitor/pages/troubleshoot-ai-agents.adoc +++ b/modules/monitor/pages/troubleshoot-ai-agents.adoc @@ -25,7 +25,7 @@ Fix issues that prevent agents from connecting to required resources. **Solution:** -. Verify MCP server status in *Agentic AI* > *Remote MCP*. +. Verify MCP server status in *Remote MCP*. . Check MCP server logs for errors. . Restart the MCP server if needed. . Verify agent has permission to access the MCP server. diff --git a/modules/monitor/partials/observability-logs.adoc b/modules/monitor/partials/observability-logs.adoc index 3dde348..e947da0 100644 --- a/modules/monitor/partials/observability-logs.adoc +++ b/modules/monitor/partials/observability-logs.adoc @@ -27,7 +27,7 @@ Use metrics for: Aggregate analytics, trends, cost tracking across time. See xre == Where to find logs 1. Navigate to logs view: - * In the sidebar, navigate to *Agentic* > *AI Gateway* > *Gateways* > *{gateway-name}*, then select the *Logs* tab. + * In the sidebar, navigate to *AI Gateway* > *Gateways* > *{gateway-name}*, then select the *Logs* tab. * Or: Gateway detail page -> Logs tab 2. Select gateway: diff --git a/modules/monitor/partials/observability-metrics.adoc b/modules/monitor/partials/observability-metrics.adoc index 56a8d2b..f50ffa2 100644 --- a/modules/monitor/partials/observability-metrics.adoc +++ b/modules/monitor/partials/observability-metrics.adoc @@ -27,7 +27,7 @@ Use logs for: Debugging specific requests, viewing full prompts/responses. See x == Where to find metrics 1. Navigate to analytics dashboard: - * In the sidebar, navigate to *Agentic* > *AI Gateway* > *Gateways* > *{gateway-name}*, then select the *Analytics* tab. + * In the sidebar, navigate to *AI Gateway* > *Gateways* > *{gateway-name}*, then select the *Analytics* tab. * Or: Gateway detail page -> Analytics tab 2. Select gateway (optional): From d077107b5414d0ef0f389c6379ef93bcb179dd2a Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:08:31 -0600 Subject: [PATCH 04/10] Drop 'Redpanda Cloud' framing in body prose As ADP moves toward a standalone product surface, drop the 'Redpanda Cloud' parent framing from user-facing prose. 13 changes across 7 files: - 'Redpanda Cloud service account' -> 'Redpanda service account' - 'Redpanda Cloud's role-based access control' -> 'Redpanda's RBAC' - 'Redpanda Cloud's OIDC provider' -> 'Redpanda's OIDC provider' - 'Redpanda Cloud's Console' -> 'Redpanda Console' - 'Access to the Redpanda Cloud UI' -> 'Access to the Redpanda UI' - 'Sign in to the Redpanda Cloud UI' -> 'Sign in to Redpanda' - 'Log in to Redpanda Cloud' -> 'Log in to Redpanda' - 'register them as Redpanda Cloud secrets' -> '...as Redpanda secrets' For the quickstart prereqs and bedrock-setup prereq, normalize the phrasing to 'A Redpanda BYOC environment on AWS with ADP enabled'. Kept unchanged: the nine '// TODO:' comments that flag the standalone-ADP rewrite work (the 'Redpanda Cloud' reference there is intentional context for future authors), and the xref label 'Authenticate to Redpanda Cloud' that links to the cloud-docs page of that exact title. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/connect/pages/claude-code.adoc | 2 +- modules/connect/pages/create-agent.adoc | 2 +- modules/control/pages/permissions-overview.adoc | 6 +++--- modules/gateway/pages/bedrock-setup.adoc | 8 ++++---- modules/gateway/pages/connect-agent.adoc | 4 ++-- modules/get-started/pages/byoc-quickstart.adoc | 2 +- modules/get-started/pages/quickstart.adoc | 2 +- 7 files changed, 13 insertions(+), 13 deletions(-) diff --git a/modules/connect/pages/claude-code.adoc b/modules/connect/pages/claude-code.adoc index 0b7c51b..11c2b08 100644 --- a/modules/connect/pages/claude-code.adoc +++ b/modules/connect/pages/claude-code.adoc @@ -29,7 +29,7 @@ This guide does not cover building agents that *call* Claude Code. For that, see * An Anthropic LLM provider configured in AI Gateway. If you haven't created one, follow xref:gateway:configure-provider.adoc[Configure an LLM provider] and pick *Anthropic* as the type. Enable at least one Claude model (for example, `claude-sonnet-4-6` or `claude-opus-4-7`) in the model picker. * Claude Code installed on the developer's workstation. See https://docs.anthropic.com/claude-code[Anthropic's Claude Code documentation]. -* A Redpanda Cloud service account with permission to invoke the provider (`dataplane_adp_llmprovider_invoke`). See xref:control:permissions-reference.adoc#llm-provider-permissions[LLM provider permissions]. Both shared-developer-tooling and per-developer setups use the same OIDC client-credentials grant; the differences are operational. +* A Redpanda service account with permission to invoke the provider (`dataplane_adp_llmprovider_invoke`). See xref:control:permissions-reference.adoc#llm-provider-permissions[LLM provider permissions]. Both shared-developer-tooling and per-developer setups use the same OIDC client-credentials grant; the differences are operational. == Get the proxy URL diff --git a/modules/connect/pages/create-agent.adoc b/modules/connect/pages/create-agent.adoc index fb7fdea..87a148b 100644 --- a/modules/connect/pages/create-agent.adoc +++ b/modules/connect/pages/create-agent.adoc @@ -163,7 +163,7 @@ For multi-agent design patterns, see xref:connect:architecture-patterns.adoc[Age == Configure the service account -In the *Service Account* section, set the name for the service account that authenticates the agent to other systems in the Redpanda Cloud Platform (for example, MCP servers and the Redpanda broker). +In the *Service Account* section, set the name for the service account that authenticates the agent to other systems in Redpanda (for example, MCP servers and the Redpanda broker). . Review the auto-generated *Service Account Name*. The default uses the pattern `cluster--agent--sa`. . Optionally, override the name. Up to 128 characters. The name cannot contain `<` or `>`. diff --git a/modules/control/pages/permissions-overview.adoc b/modules/control/pages/permissions-overview.adoc index 63667b6..b128072 100644 --- a/modules/control/pages/permissions-overview.adoc +++ b/modules/control/pages/permissions-overview.adoc @@ -9,7 +9,7 @@ // Source: `cloudv2` `pkg/permissions/permissions_constants.go`, `apps/aigw/internal/llm/authz.go`, `apps/aigw/internal/mcp/authz.go`, and `apps/ai-agent/internal/agent/authorization.go` on origin/main, verified 2026-05-18. // TODO: confirm screenshots of the role-binding flow in the Cloud UI once UX-790 (Console-side fine-grained authZ) ships. -The Agentic Data Plane uses Redpanda Cloud's role-based access control (RBAC) to gate every API call. Each LLM provider, MCP server, agent, pipeline, knowledge base, and governance endpoint enforces a specific permission, and you assign permissions to users and service accounts by binding them to a role. This page explains the three-layer model so you can pick the right built-in role for a workload, or compose your own. +The Agentic Data Plane uses Redpanda's role-based access control (RBAC) to gate every API call. Each LLM provider, MCP server, agent, pipeline, knowledge base, and governance endpoint enforces a specific permission, and you assign permissions to users and service accounts by binding them to a role. This page explains the three-layer model so you can pick the right built-in role for a workload, or compose your own. After reading this page, you will be able to: @@ -83,10 +83,10 @@ Pick the narrowest role that covers a workload. For example, an application that ADP API calls authenticate as one of two identity types: -* *User identity (OIDC)*: A human user signed in through Redpanda Cloud's OIDC provider. The Cloud UI uses this identity when an admin manages ADP resources interactively. +* *User identity (OIDC)*: A human user signed in through Redpanda's OIDC provider. The Cloud UI uses this identity when an admin manages ADP resources interactively. * *Service account*: A non-human identity backed by OIDC client credentials. Applications, CI jobs, and `rpk ai` use service accounts. -Account impersonation, which lets Redpanda Cloud's Console reuse a user's identity for Kafka API and Schema Registry calls, applies to those two subsystems only. ADP endpoints continue to authenticate clients directly through their OIDC tokens, regardless of how account impersonation is configured at the cluster level. +Account impersonation, which lets Redpanda Console reuse a user's identity for Kafka API and Schema Registry calls, applies to those two subsystems only. ADP endpoints continue to authenticate clients directly through their OIDC tokens, regardless of how account impersonation is configured at the cluster level. == Where ADP fits in Cloud RBAC diff --git a/modules/gateway/pages/bedrock-setup.adoc b/modules/gateway/pages/bedrock-setup.adoc index 3199b31..e17df5b 100644 --- a/modules/gateway/pages/bedrock-setup.adoc +++ b/modules/gateway/pages/bedrock-setup.adoc @@ -18,10 +18,10 @@ After completing this guide, you will be able to: == Prerequisites -* A Redpanda Cloud cluster with ADP enabled. +* A Redpanda BYOC environment on AWS with ADP enabled. * An AWS account with Bedrock model access enabled in the region you plan to call. Model availability varies by region; see link:https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html[Bedrock models by region^]. * Access to the AWS CLI configured with credentials that can create IAM users, policies, and access keys. -* Access to the Redpanda Cloud UI. +* Access to the Redpanda UI. == Create the IAM policy @@ -92,7 +92,7 @@ Generate the access keys AI Gateway uses: aws iam create-access-key --user-name redpanda-bedrock-invoker ---- -Save the `AccessKeyId` and `SecretAccessKey` from the output. You need both in the next section to register them as Redpanda Cloud secrets. +Save the `AccessKeyId` and `SecretAccessKey` from the output. You need both in the next section to register them as Redpanda secrets. CAUTION: AWS displays the secret access key only at creation. Store it in a password manager or pass it directly into the secret-creation flow in the next section. @@ -116,7 +116,7 @@ A successful model response confirms the IAM policy, region, and credentials are == Register Bedrock as an LLM provider -. Sign in to the Redpanda Cloud UI and open ADP. +. Sign in to Redpanda and open ADP. . Open *LLM Providers* in the sidebar and click *Create provider*. . Select *AWS Bedrock* as the provider type. . Enter a Name such as `my-bedrock`. Use lowercase letters, digits, and hyphens. The name is immutable and appears in the proxy URL. diff --git a/modules/gateway/pages/connect-agent.adoc b/modules/gateway/pages/connect-agent.adoc index 015dc56..68b11a9 100644 --- a/modules/gateway/pages/connect-agent.adoc +++ b/modules/gateway/pages/connect-agent.adoc @@ -19,7 +19,7 @@ After completing this guide, you will be able to: * A configured LLM provider. If you haven't created one yet, see xref:gateway:configure-provider.adoc[Configure an LLM provider]. * For local development, nothing else. You'll install `rpk ai` in the next section. -* For CI or programmatic clients: A Redpanda Cloud service account with OIDC client credentials. See xref:cloud-data-platform:security:cloud-authentication.adoc[Authenticate to Redpanda Cloud]. +* For CI or programmatic clients: A Redpanda service account with OIDC client credentials. See xref:cloud-data-platform:security:cloud-authentication.adoc[Authenticate to Redpanda Cloud]. + // TODO: confirm whether ADP hosts its own service-account IAM post-standalone, or continues to share Redpanda Cloud Organization IAM. * A development environment with your chosen programming language. @@ -57,7 +57,7 @@ rpk ai install + Update later with xref:reference:rpk/rpk-ai/rpk-ai-upgrade.adoc[`rpk ai upgrade`]; remove with xref:reference:rpk/rpk-ai/rpk-ai-uninstall.adoc[`rpk ai uninstall`]. -. Log in to Redpanda Cloud: +. Log in to Redpanda: + [source,bash] ---- diff --git a/modules/get-started/pages/byoc-quickstart.adoc b/modules/get-started/pages/byoc-quickstart.adoc index adab893..3ef4df6 100644 --- a/modules/get-started/pages/byoc-quickstart.adoc +++ b/modules/get-started/pages/byoc-quickstart.adoc @@ -20,7 +20,7 @@ After completing this quickstart, you will be able to: == Prerequisites -* A Redpanda Cloud BYOC environment on AWS with ADP enabled. +* A Redpanda BYOC environment on AWS with ADP enabled. * The Writer or Admin xref:control:permissions-overview.adoc[built-in role] in ADP. The Reader role can list resources but cannot create them. * An Anthropic account. If you don't have one, the next section walks through signup. diff --git a/modules/get-started/pages/quickstart.adoc b/modules/get-started/pages/quickstart.adoc index fca2a1f..d0fe76f 100644 --- a/modules/get-started/pages/quickstart.adoc +++ b/modules/get-started/pages/quickstart.adoc @@ -17,7 +17,7 @@ After completing this quickstart, you will be able to: == Prerequisites -* A Redpanda Cloud BYOC environment on AWS with ADP enabled. +* A Redpanda BYOC environment on AWS with ADP enabled. * An xref:get-started:gateway-quickstart.adoc[AI Gateway] configured with at least one LLM provider (OpenAI, Anthropic, Google AI, or AWS Bedrock). From 8ff47ff6e72cb2076c34ac2e2e40ff94af173a0f Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:08:31 -0600 Subject: [PATCH 05/10] Rename 'spending limit' to 'spend limit' in pages, nav, and partials 22 replacements across 8 files. Matches the product's preferred terminology. Only the 'spending limit(s)' phrase is touched; standalone 'spending' words (spending pipeline, spending patterns, spending event, AI spending, the dataplane_adp_spending_* permission identifiers, the JSON field spending_limit_amount) are unchanged. The budgets.adoc page title becomes 'Set Spend Limits and Token Budgets'; the nav label becomes 'Set spend limits'. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/ROOT/nav.adoc | 2 +- .../partials/integrations/claude-code-admin.adoc | 6 +++--- modules/connect/partials/integrations/cline-admin.adoc | 6 +++--- .../connect/partials/integrations/continue-admin.adoc | 8 ++++---- .../connect/partials/integrations/cursor-admin.adoc | 10 +++++----- .../partials/integrations/github-copilot-admin.adoc | 8 ++++---- modules/control/pages/budgets.adoc | 2 +- modules/control/pages/index.adoc | 2 +- 8 files changed, 22 insertions(+), 22 deletions(-) diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 31cf7ae..ebf2882 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -24,7 +24,7 @@ ** xref:control:dashboard/overview.adoc[See all your agents in one place] ** xref:control:guardrails/overview.adoc[Guardrails Overview] ** xref:control:guardrails/create-guardrail.adoc[Create a Guardrail] -** xref:control:budgets.adoc[Set spending limits] +** xref:control:budgets.adoc[Set spend limits] ** xref:control:permissions-overview.adoc[Control who can do what] * xref:gateway:index.adoc[Routing & LLM settings] diff --git a/modules/connect/partials/integrations/claude-code-admin.adoc b/modules/connect/partials/integrations/claude-code-admin.adoc index b5721f0..715b432 100644 --- a/modules/connect/partials/integrations/claude-code-admin.adoc +++ b/modules/connect/partials/integrations/claude-code-admin.adoc @@ -153,7 +153,7 @@ Prevent runaway usage from Claude Code clients: The gateway blocks requests exceeding these limits and returns HTTP 429 errors. -=== Set spending limits +=== Set spend limits Control LLM costs: @@ -452,7 +452,7 @@ Causes and solutions: * **Deferred tool loading disabled**: Enable deferred tool loading to reduce tokens by 80-90% * **No rate limits**: Apply per-minute rate limits to prevent runaway usage -* **Missing spending limits**: Set monthly budget limits with blocking enforcement +* **Missing spend limits**: Set monthly budget limits with blocking enforcement * **Expensive models**: Route to cost-effective models (for example, Claude Sonnet instead of Opus) for non-critical requests === Requests failing with 429 errors @@ -463,7 +463,7 @@ Causes and solutions: * **Rate limit exceeded**: Review and increase rate limits if usage is legitimate * **Upstream provider rate limits**: Check if the upstream LLM provider is rate-limiting; configure failover pools -* **Budget exhausted**: Verify monthly spending limit has not been reached +* **Budget exhausted**: Verify monthly spend limit has not been reached == Next steps diff --git a/modules/connect/partials/integrations/cline-admin.adoc b/modules/connect/partials/integrations/cline-admin.adoc index a69356e..69ff135 100644 --- a/modules/connect/partials/integrations/cline-admin.adoc +++ b/modules/connect/partials/integrations/cline-admin.adoc @@ -164,7 +164,7 @@ Cline can generate multiple requests during autonomous operations. Higher limits The gateway blocks requests exceeding these limits and returns HTTP 429 errors. -=== Set spending limits +=== Set spend limits Control LLM costs during autonomous operations: @@ -520,7 +520,7 @@ Causes and solutions: * **Deferred tool loading disabled**: Enable deferred tool loading to reduce tokens by 80-90% * **Autonomous loops**: Monitor for repeated similar requests (may indicate autonomous operation stuck in a loop) * **No rate limits**: Apply per-minute rate limits to prevent runaway autonomous usage -* **Missing spending limits**: Set monthly budget limits with blocking enforcement +* **Missing spend limits**: Set monthly budget limits with blocking enforcement * **Expensive models for autonomous work**: Route autonomous operations to cost-effective models (for example, Claude Sonnet instead of Opus) * **Too many tools in context**: Reduce the number of aggregated MCP servers or enable deferred loading @@ -532,7 +532,7 @@ Causes and solutions: * **Rate limit exceeded**: Review and increase rate limits if autonomous usage is legitimate * **Upstream provider rate limits**: Check if the upstream LLM provider is rate-limiting; configure failover pools -* **Budget exhausted**: Verify monthly spending limit has not been reached +* **Budget exhausted**: Verify monthly spend limit has not been reached * **Autonomous operation too aggressive**: Configure Cline to slow down request rate === Autonomous operations timing out diff --git a/modules/connect/partials/integrations/continue-admin.adoc b/modules/connect/partials/integrations/continue-admin.adoc index 5e6c70f..e457f77 100644 --- a/modules/connect/partials/integrations/continue-admin.adoc +++ b/modules/connect/partials/integrations/continue-admin.adoc @@ -258,7 +258,7 @@ Continue.dev's autocomplete feature generates frequent, short requests. Configur * Autocomplete models (for example, `gpt-5.2-mini`): 100 requests per minute per user * Chat models (for example, `claude-sonnet-4.5`): 20 requests per minute per user -=== Set spending limits +=== Set spend limits Control LLM costs across all providers: @@ -667,7 +667,7 @@ Causes and solutions: * **Wrong model for autocomplete**: Use a fast model like `gpt-5.2-mini` in `tabAutocompleteModel` * **Rate limits too restrictive**: Increase rate limits for autocomplete backend * **High backend latency**: Check backend metrics and consider provider failover -* **Token exhaustion**: Verify spending limits haven't been reached +* **Token exhaustion**: Verify spend limits haven't been reached === Tools not appearing in Continue.dev @@ -689,7 +689,7 @@ Causes and solutions: * **Autocomplete using expensive model**: Configure `tabAutocompleteModel` to use `gpt-5.2-mini` instead of larger models * **Deferred tool loading disabled**: Enable deferred tool loading to reduce tokens by 80-90% * **No rate limits**: Apply per-minute rate limits to prevent runaway usage -* **Missing spending limits**: Set monthly budget limits with blocking enforcement +* **Missing spend limits**: Set monthly budget limits with blocking enforcement * **Chat using wrong model**: Route chat requests to cost-effective models (for example, `claude-sonnet-4.5` instead of `claude-opus-4.6`) === Requests failing with 429 errors @@ -700,7 +700,7 @@ Causes and solutions: * **Rate limit exceeded**: Review and increase rate limits if usage is legitimate (autocomplete needs higher limits) * **Upstream provider rate limits**: Check if the upstream LLM provider is rate-limiting; configure failover to alternate API keys -* **Budget exhausted**: Verify monthly spending limit has not been reached +* **Budget exhausted**: Verify monthly spend limit has not been reached === Different results from different providers diff --git a/modules/connect/partials/integrations/cursor-admin.adoc b/modules/connect/partials/integrations/cursor-admin.adoc index 6c50b68..48d74ed 100644 --- a/modules/connect/partials/integrations/cursor-admin.adoc +++ b/modules/connect/partials/integrations/cursor-admin.adoc @@ -187,7 +187,7 @@ Cursor's code completion feature generates frequent requests. Consider separate * Completion models (for example, `openai/gpt-5.2-mini`): Higher rate limits * Chat models (for example, `anthropic/claude-sonnet-4.5`): Standard rate limits -=== Set spending limits +=== Set spend limits Control LLM costs across all providers: @@ -339,7 +339,7 @@ For organizations with multiple teams, use one of these multi-tenant strategies. === Strategy 1: One gateway per team -Create a separate gateway for each tenant or team. Each gateway has its own rate limits, spending limits, and API tokens. +Create a separate gateway for each tenant or team. Each gateway has its own rate limits, spend limits, and API tokens. . In ADP, create one gateway per team (for example, `team-alpha-cursor-gateway`, `team-beta-cursor-gateway`). . Distribute each team's gateway endpoint and API token to its users. @@ -363,7 +363,7 @@ For simpler deployments, use one gateway for all Cursor users with shared access . Create one gateway for all Cursor users. . Generate a shared API token. . Distribute the endpoint and token to all users. -. Use overall rate limits and spending limits to control aggregate usage. +. Use overall rate limits and spend limits to control aggregate usage. This approach is the simplest but provides no per-team cost tracking or isolation. @@ -655,7 +655,7 @@ Causes and solutions: * **Code completion using expensive model**: Configure completion mode to use `openai/gpt-5.2-mini` instead of larger models * **Deferred tool loading disabled**: Enable deferred tool loading to reduce tokens by 80-90% * **No rate limits**: Apply per-minute rate limits to prevent runaway usage -* **Missing spending limits**: Set monthly budget limits with blocking enforcement +* **Missing spend limits**: Set monthly budget limits with blocking enforcement * **Chat using wrong model**: Route chat requests to cost-effective models (for example, `anthropic/claude-sonnet-4.5` instead of `anthropic/claude-opus-4.6-5`) * **Transform overhead**: Monitor if transforms add significant token overhead @@ -667,7 +667,7 @@ Causes and solutions: * **Rate limit exceeded**: Review and increase rate limits if usage is legitimate (code completion needs higher limits) * **Upstream provider rate limits**: Check if the upstream LLM provider is rate-limiting; configure failover to alternate providers -* **Budget exhausted**: Verify monthly spending limit has not been reached +* **Budget exhausted**: Verify monthly spend limit has not been reached * **Per-user limits too restrictive**: Adjust per-user rate limits if using multi-tenant strategies === Multi-tenant authorization failures diff --git a/modules/connect/partials/integrations/github-copilot-admin.adoc b/modules/connect/partials/integrations/github-copilot-admin.adoc index 560f049..5410218 100644 --- a/modules/connect/partials/integrations/github-copilot-admin.adoc +++ b/modules/connect/partials/integrations/github-copilot-admin.adoc @@ -221,7 +221,7 @@ GitHub Copilot's code completion feature generates extremely frequent requests ( * Separate rate limits for different request types if the gateway supports request classification * Monitoring initial usage patterns to adjust limits appropriately -=== Set spending limits +=== Set spend limits Control LLM costs across all providers: @@ -349,7 +349,7 @@ For simpler deployments, configure a single gateway with shared access: . Create one gateway for all GitHub Copilot users . Generate a shared API token . Configure GitHub Copilot at the organization level -. Use rate limits and spending limits to control overall usage +. Use rate limits and spend limits to control overall usage **Benefits:** @@ -648,7 +648,7 @@ Causes and solutions: * **Code completion using expensive model**: Configure completion to use `gpt-5.2-mini` instead of larger models * **No rate limits**: Apply per-minute rate limits to prevent runaway usage -* **Missing spending limits**: Set monthly budget limits with blocking enforcement +* **Missing spend limits**: Set monthly budget limits with blocking enforcement * **Chat using wrong model**: Ensure chat/explanation features use cost-effective models * **Transform overhead**: Monitor if transforms add significant token overhead * **High completion request volume**: Expected behavior, adjust budgets or implement stricter rate limits @@ -661,7 +661,7 @@ Causes and solutions: * **Rate limit exceeded**: Review and increase rate limits if usage is legitimate (code completion needs very high limits) * **Upstream provider rate limits**: Check if the upstream LLM provider is rate-limiting; configure failover to alternate providers -* **Budget exhausted**: Verify monthly spending limit has not been reached +* **Budget exhausted**: Verify monthly spend limit has not been reached * **Per-user limits too restrictive**: Adjust per-user rate limits if using multi-tenant strategies * **Spike in usage**: Code completion can generate sudden usage spikes, consider burstable rate limits diff --git a/modules/control/pages/budgets.adoc b/modules/control/pages/budgets.adoc index 4d03045..c590ad1 100644 --- a/modules/control/pages/budgets.adoc +++ b/modules/control/pages/budgets.adoc @@ -1,4 +1,4 @@ -= Set Spending Limits and Token Budgets += Set Spend Limits and Token Budgets :description: See what AI spending the Agentic Data Plane records automatically and where to view it. :page-topic-type: overview :personas: platform_engineer, pilot_lead diff --git a/modules/control/pages/index.adoc b/modules/control/pages/index.adoc index 7d83b21..1b2320b 100644 --- a/modules/control/pages/index.adoc +++ b/modules/control/pages/index.adoc @@ -1,3 +1,3 @@ = Control & govern -:description: Govern agent activity with the dashboard, guardrails, spending limits, and permissions. +:description: Govern agent activity with the dashboard, guardrails, spend limits, and permissions. :page-layout: index From 3e26ca4872397e32b076cb90bf8f481f4edc53e5 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:19:24 -0600 Subject: [PATCH 06/10] Trim budgets page title to 'Set Spend Limits' Resolves PR #40 open question Q1. The full title 'Set Spend Limits and Token Budgets' was long for an H1; the body intro already explains that budgets and limits are tracked together. The permissions-reference xref drops its explicit label so the link picks up the new title automatically. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/control/pages/budgets.adoc | 2 +- modules/control/pages/permissions-reference.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/control/pages/budgets.adoc b/modules/control/pages/budgets.adoc index c590ad1..6b50109 100644 --- a/modules/control/pages/budgets.adoc +++ b/modules/control/pages/budgets.adoc @@ -1,4 +1,4 @@ -= Set Spend Limits and Token Budgets += Set Spend Limits :description: See what AI spending the Agentic Data Plane records automatically and where to view it. :page-topic-type: overview :personas: platform_engineer, pilot_lead diff --git a/modules/control/pages/permissions-reference.adoc b/modules/control/pages/permissions-reference.adoc index e0b29c5..83844e5 100644 --- a/modules/control/pages/permissions-reference.adoc +++ b/modules/control/pages/permissions-reference.adoc @@ -234,7 +234,7 @@ The `dataplane_adp_agent_credential_*` permissions gate the OIDC client credenti == Spending permissions -The `dataplane_adp_spending_*` permissions gate the governance APIs that surface AI spend, request counts, and token volume. See xref:control:budgets.adoc[Token Budgets and Limits] for what spending data ADP records automatically. +The `dataplane_adp_spending_*` permissions gate the governance APIs that surface AI spend, request counts, and token volume. See xref:control:budgets.adoc[] for what spending data ADP records automatically. [cols="2,2,1,1"] |=== From 949805cc2e27866891d5f1fbe71d81f7c5846103 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:19:52 -0600 Subject: [PATCH 07/10] Drop '(OpenTelemetry)' parenthetical from BYOA telemetry title and labels Resolves PR #40 open question Q2. The page intro and the :description: attribute already explain that BYOA telemetry uses OpenTelemetry, so the parenthetical in the H1 was redundant. Same treatment for the four cross-link labels in byoa-register.adoc. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/connect/pages/byoa-register.adoc | 8 ++++---- modules/monitor/pages/byoa-telemetry.adoc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/connect/pages/byoa-register.adoc b/modules/connect/pages/byoa-register.adoc index 81a4dae..45d4d7b 100644 --- a/modules/connect/pages/byoa-register.adoc +++ b/modules/connect/pages/byoa-register.adoc @@ -67,7 +67,7 @@ Before you register a BYOA agent, make sure you have: * An agent running in your own infrastructure with a reachable HTTPS endpoint. * The ability to add an HTTPS route at `/.well-known/agent-card.json` (or equivalent) on that endpoint. See <>. -* The agent instrumented with OpenTelemetry, emitting the minimum required spans contract. See xref:monitor:byoa-telemetry.adoc[BYOA telemetry (OpenTelemetry)]. +* The agent instrumented with OpenTelemetry, emitting the minimum required spans contract. See xref:monitor:byoa-telemetry.adoc[BYOA telemetry]. * The `dataplane_adp_agent_create` permission, granted by the Writer built-in role. See xref:control:permissions-reference.adoc#agent-management-permissions[Agent management permissions]. * A name for the agent that follows DNS-1123 conventions (1–63 characters, lowercase letters / numbers / hyphens, starting with a letter). The name is immutable once the agent is registered. @@ -149,7 +149,7 @@ After registering, confirm three things end-to-end: . *Discovery*: The agent appears in *AgentRegistryService.ListAgents* and in the governance dashboard's Agents list. *Type* shows as *BYOA*. . *A2A reachability*: A test A2A call to `https://aigw..clusters.rdpa.co/agents//v1/message:send` returns the expected response (or a `FAILED_PRECONDITION` if your agent isn't running, but no `404 Not Found`). -. *Telemetry*: Open the transcripts list, filter by your agent's `service.name`, and confirm a recent execution shows up with non-zero token counts and a non-empty conversation ID. If it doesn't, see xref:monitor:byoa-telemetry.adoc[BYOA telemetry (OpenTelemetry)] troubleshooting. +. *Telemetry*: Open the transcripts list, filter by your agent's `service.name`, and confirm a recent execution shows up with non-zero token counts and a non-empty conversation ID. If it doesn't, see xref:monitor:byoa-telemetry.adoc[BYOA telemetry] troubleshooting. == Troubleshooting @@ -168,7 +168,7 @@ The symptom-driven checks in this section cover the three observable parts of th |The agent endpoint URL on the registration record doesn't match where your agent is actually running, or the agent isn't serving `/.well-known/agent-card.json`. Update the registration with the correct URL, or fix the well-known route. |Transcripts list shows the agent column blank for your agent's runs -|Your agent's OTel `service.name` resource attribute doesn't match the registered name (or isn't being emitted at all). See xref:monitor:byoa-telemetry.adoc[BYOA telemetry (OpenTelemetry)]. +|Your agent's OTel `service.name` resource attribute doesn't match the registered name (or isn't being emitted at all). See xref:monitor:byoa-telemetry.adoc[BYOA telemetry]. |Inbound A2A calls fail with `401 Unauthorized` |Your agent is rejecting the access token AI Gateway presents. Confirm your agent's token validator points at the right issuer and accepts the right audience. @@ -187,6 +187,6 @@ This page does not cover: == Related topics * xref:connect:a2a-concepts.adoc[Agent-to-agent concepts] -* xref:monitor:byoa-telemetry.adoc[BYOA telemetry (OpenTelemetry)] +* xref:monitor:byoa-telemetry.adoc[BYOA telemetry] * xref:connect:concepts.adoc[Agent concepts] * xref:connect:create-agent.adoc[Create a declarative agent] diff --git a/modules/monitor/pages/byoa-telemetry.adoc b/modules/monitor/pages/byoa-telemetry.adoc index ca177b6..edc1ac8 100644 --- a/modules/monitor/pages/byoa-telemetry.adoc +++ b/modules/monitor/pages/byoa-telemetry.adoc @@ -1,4 +1,4 @@ -= Send BYOA Telemetry (OpenTelemetry) += Send BYOA Telemetry :description: Emit OpenTelemetry traces from your BYOA (Bring Your Own Agent) so the Agentic Data Plane can attribute calls, costs, and tool invocations to your agent. Covers the minimum required span contract, common optional attributes, and how it differs from a Redpanda-managed agent. :page-topic-type: how-to :personas: agent_builder, platform_engineer From 7eb3692aa4af82f85c64e99ec21d6f430454f839 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:26:10 -0600 Subject: [PATCH 08/10] Restructure Quickstarts to Get Started + Title Case nav sweep Resolves PR #40 open question Q4 plus a Title Case sweep of every nav label. Q4: 'Quickstarts' becomes 'Get Started' to match docs and cloud-docs conventions. New modules/get-started/pages/index.adoc serves as the section landing (':page-layout: index' auto-renders the 4 sub-items as cards). adp-overview.adoc joins as the first sub-item labeled 'Redpanda ADP Overview'. Title Case sweep: every section header and every sub-item now uses Title Case. Sub-items that previously read in sentence case (e.g. 'See what your agent did') align to the page H1 ('See What Your Agent Did'). Three rows also had stale labels that didn't match the new page titles: - 'Plug in any app, database, or tool' -> 'Plug in an App, Database, or Tool' - 'Send telemetry from agents you host' -> 'Send BYOA Telemetry' - 'How the gateway works' -> 'How AI Gateway Works' Title Case rule: capitalize first/last words and major words; lowercase articles (a, an, the), coordinating conjunctions (and, but, or, nor), and short prepositions when not first/last. Exception: 'rpk' stays lowercase (literal command name). Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/ROOT/nav.adoc | 29 ++++++++++++++-------------- modules/get-started/pages/index.adoc | 3 +++ 2 files changed, 18 insertions(+), 14 deletions(-) create mode 100644 modules/get-started/pages/index.adoc diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index ebf2882..42e31ea 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,10 +1,11 @@ -* xref:get-started:adp-overview.adoc[Quickstarts] +* xref:get-started:index.adoc[Get Started] +** xref:get-started:adp-overview.adoc[Redpanda ADP Overview] ** xref:get-started:byoc-quickstart.adoc[ADP Quickstart] ** xref:get-started:gateway-quickstart.adoc[AI Gateway Quickstart] ** xref:get-started:quickstart.adoc[AI Agent Quickstart] -* xref:connect:index.adoc[Connect data & tools] -** xref:connect:managed/managed-catalog.adoc[Plug in any app, database, or tool] +* xref:connect:index.adoc[Connect Data & Tools] +** xref:connect:managed/managed-catalog.adoc[Plug in an App, Database, or Tool] ** xref:connect:create-agent.adoc[Create an Agent] ** xref:connect:create-server.adoc[Create an MCP Server] ** xref:connect:register-remote.adoc[Register a Self-Managed MCP Server] @@ -13,22 +14,22 @@ ** xref:connect:claude-code.adoc[Use Claude Code with ADP] ** xref:connect:remote-mcp-clients.adoc[Connect Remote MCP Clients] -* xref:monitor:index.adoc[Monitor & debug] -** xref:monitor:transcripts.adoc[See what your agent did] +* xref:monitor:index.adoc[Monitor & Debug] +** xref:monitor:transcripts.adoc[See What Your Agent Did] ** xref:monitor:troubleshoot-ai-agents.adoc[Troubleshoot AI Agents] -** xref:monitor:metrics.adoc[Check speed, cost, and errors] -** xref:control:guardrails/violations.adoc[Review blocked requests] -** xref:monitor:byoa-telemetry.adoc[Send telemetry from agents you host] +** xref:monitor:metrics.adoc[Check Speed, Cost, and Errors] +** xref:control:guardrails/violations.adoc[Review Blocked Requests] +** xref:monitor:byoa-telemetry.adoc[Send BYOA Telemetry] -* xref:control:index.adoc[Control & govern] -** xref:control:dashboard/overview.adoc[See all your agents in one place] +* xref:control:index.adoc[Control & Govern] +** xref:control:dashboard/overview.adoc[See All Your Agents in One Place] ** xref:control:guardrails/overview.adoc[Guardrails Overview] ** xref:control:guardrails/create-guardrail.adoc[Create a Guardrail] -** xref:control:budgets.adoc[Set spend limits] -** xref:control:permissions-overview.adoc[Control who can do what] +** xref:control:budgets.adoc[Set Spend Limits] +** xref:control:permissions-overview.adoc[Control Who Can Do What] -* xref:gateway:index.adoc[Routing & LLM settings] -** xref:gateway:overview.adoc[How the gateway works] +* xref:gateway:index.adoc[Routing & LLM Settings] +** xref:gateway:overview.adoc[How AI Gateway Works] ** xref:gateway:configure-provider.adoc[Configure an LLM Provider] *** xref:gateway:bedrock-setup.adoc[Set Up AWS Bedrock as an LLM Provider] diff --git a/modules/get-started/pages/index.adoc b/modules/get-started/pages/index.adoc new file mode 100644 index 0000000..96b9e19 --- /dev/null +++ b/modules/get-started/pages/index.adoc @@ -0,0 +1,3 @@ += Get Started +:description: Stand up Redpanda ADP and ship your first agent. +:page-layout: index From cae49c1e44b1b7c956bcd67f1533558525ce09a2 Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:26:20 -0600 Subject: [PATCH 09/10] Title Case the four workflow-section index page H1s connect, monitor, control, gateway index pages now match their Title Case nav labels. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/connect/pages/index.adoc | 2 +- modules/control/pages/index.adoc | 2 +- modules/gateway/pages/index.adoc | 2 +- modules/monitor/pages/index.adoc | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/connect/pages/index.adoc b/modules/connect/pages/index.adoc index 8bf7cef..04c64c3 100644 --- a/modules/connect/pages/index.adoc +++ b/modules/connect/pages/index.adoc @@ -1,3 +1,3 @@ -= Connect data & tools += Connect Data & Tools :description: Connect agents, MCP servers, and the apps and data sources behind them. :page-layout: index diff --git a/modules/control/pages/index.adoc b/modules/control/pages/index.adoc index 1b2320b..2766152 100644 --- a/modules/control/pages/index.adoc +++ b/modules/control/pages/index.adoc @@ -1,3 +1,3 @@ -= Control & govern += Control & Govern :description: Govern agent activity with the dashboard, guardrails, spend limits, and permissions. :page-layout: index diff --git a/modules/gateway/pages/index.adoc b/modules/gateway/pages/index.adoc index bb5867a..bef147f 100644 --- a/modules/gateway/pages/index.adoc +++ b/modules/gateway/pages/index.adoc @@ -1,3 +1,3 @@ -= Routing & LLM settings += Routing & LLM Settings :description: Configure AI Gateway, LLM providers, and routing. :page-layout: index diff --git a/modules/monitor/pages/index.adoc b/modules/monitor/pages/index.adoc index cc98d52..97d806f 100644 --- a/modules/monitor/pages/index.adoc +++ b/modules/monitor/pages/index.adoc @@ -1,3 +1,3 @@ -= Monitor & debug += Monitor & Debug :description: See what your agents did, investigate runs, and check speed, cost, and errors. :page-layout: index From 815afe8e16607e8e3510183a34e685e3557ee86e Mon Sep 17 00:00:00 2001 From: micheleRP Date: Thu, 28 May 2026 17:48:02 -0600 Subject: [PATCH 10/10] Retitle adp-overview to 'Redpanda ADP Overview' Matches the nav sub-item label, so clicking 'Redpanda ADP Overview' under 'Get Started' lands on a page whose H1 reads the same. Co-Authored-By: Claude Opus 4.7 (1M context) --- modules/get-started/pages/adp-overview.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/get-started/pages/adp-overview.adoc b/modules/get-started/pages/adp-overview.adoc index ebdd01f..477c92f 100644 --- a/modules/get-started/pages/adp-overview.adoc +++ b/modules/get-started/pages/adp-overview.adoc @@ -1,4 +1,4 @@ -= Redpanda Agentic Data Plane += Redpanda ADP Overview :description: Enterprise-grade infrastructure for building, deploying, and governing AI agents at scale with compliance-grade audit trails. :page-layout: index :page-topic-type: overview