diff --git a/antora.yml b/antora.yml index 2fbf5e3..63a4474 100644 --- a/antora.yml +++ b/antora.yml @@ -1,7 +1,7 @@ name: agentic-data-plane title: Agentic Data Plane version: ~ -start_page: ROOT:index.adoc +start_page: get-started:adp-overview.adoc nav: - modules/ROOT/nav.adoc asciidoc: diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index cf2a4ff..6d14780 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,8 +1,8 @@ -* xref:ROOT:index.adoc[Overview] -* xref:get-started:byoc-quickstart.adoc[Quickstart] +* xref:get-started:adp-overview.adoc[Overview] +* xref:get-started:byoc-quickstart.adoc[ADP Quickstart] * xref:agents:index.adoc[Agents] ** xref:agents:overview.adoc[Overview] -** xref:agents:quickstart.adoc[Quickstart] +** xref:agents:quickstart.adoc[AI Agent Quickstart] ** xref:agents:concepts.adoc[Concepts] ** xref:agents:a2a-concepts.adoc[Agent-to-Agent Concepts] ** xref:agents:create-agent.adoc[Create a Declarative Agent] @@ -41,7 +41,7 @@ *** xref:mcp:managed/zendesk.adoc[Zendesk] * xref:ai-gateway:index.adoc[AI Gateway] ** xref:ai-gateway:overview.adoc[Overview] -** xref:ai-gateway:gateway-quickstart.adoc[Quickstart] +** xref:ai-gateway:gateway-quickstart.adoc[AI Gateway Quickstart] ** xref:ai-gateway:gateway-architecture.adoc[Architecture] ** xref:ai-gateway:configure-provider.adoc[Configure Your LLM Provider] *** xref:ai-gateway:bedrock-setup.adoc[Set Up AWS Bedrock] diff --git a/modules/ROOT/partials/integrations/claude-code-admin.adoc b/modules/ROOT/partials/integrations/claude-code-admin.adoc index 3621420..2971e84 100644 --- a/modules/ROOT/partials/integrations/claude-code-admin.adoc +++ b/modules/ROOT/partials/integrations/claude-code-admin.adoc @@ -192,7 +192,7 @@ Enable Claude Code to discover and use tools from multiple MCP servers through a |Descriptive name (for example, `redpanda-data-catalog`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -467,4 +467,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/ROOT/partials/integrations/cline-admin.adoc b/modules/ROOT/partials/integrations/cline-admin.adoc index a670e93..3b2580d 100644 --- a/modules/ROOT/partials/integrations/cline-admin.adoc +++ b/modules/ROOT/partials/integrations/cline-admin.adoc @@ -205,7 +205,7 @@ Enable Cline to discover and use tools from multiple MCP servers through a singl |Descriptive name (for example, `filesystem-tools`, `code-analysis-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -547,4 +547,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/ROOT/partials/integrations/continue-admin.adoc b/modules/ROOT/partials/integrations/continue-admin.adoc index 10bae57..91dac29 100644 --- a/modules/ROOT/partials/integrations/continue-admin.adoc +++ b/modules/ROOT/partials/integrations/continue-admin.adoc @@ -301,7 +301,7 @@ Enable Continue.dev to discover and use tools from multiple MCP servers through |Descriptive name (for example, `redpanda-data-catalog`, `code-search-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -714,4 +714,4 @@ This is expected behavior, not a configuration issue: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/ROOT/partials/integrations/cursor-admin.adoc b/modules/ROOT/partials/integrations/cursor-admin.adoc index bdb6cb6..3753339 100644 --- a/modules/ROOT/partials/integrations/cursor-admin.adoc +++ b/modules/ROOT/partials/integrations/cursor-admin.adoc @@ -229,7 +229,7 @@ Enable Cursor to discover and use tools from multiple MCP servers through a sing |Descriptive name (for example, `redpanda-data-tools`, `code-search-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -681,4 +681,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/ROOT/partials/integrations/github-copilot-admin.adoc b/modules/ROOT/partials/integrations/github-copilot-admin.adoc index a929706..bb157af 100644 --- a/modules/ROOT/partials/integrations/github-copilot-admin.adoc +++ b/modules/ROOT/partials/integrations/github-copilot-admin.adoc @@ -615,7 +615,7 @@ Causes and solutions: * **Expired token**: Generate a new API token and update the GitHub Copilot configuration * **Network connectivity**: Verify the cluster endpoint is accessible from the client network * **Provider not enabled**: Ensure at least one provider is enabled and has models in the catalog -* **SSL/TLS issues**: Verify the cluster has valid SSL certificates +* **TLS issues**: Verify the cluster has valid TLS certificates * **Organization policy blocking custom endpoints**: Check GitHub organization settings === Model not found errors diff --git a/modules/ROOT/partials/observability-logs.adoc b/modules/ROOT/partials/observability-logs.adoc index 45006a3..f4cbc29 100644 --- a/modules/ROOT/partials/observability-logs.adoc +++ b/modules/ROOT/partials/observability-logs.adoc @@ -22,7 +22,7 @@ Use logs for: * Understanding which provider handled a request * Investigating latency spikes or errors for specific users -Use metrics for: Aggregate analytics, trends, cost tracking across time. See xref:ai-gateway/observability-metrics.adoc[]. +Use metrics for: Aggregate analytics, trends, cost tracking across time. See xref:observability:metrics.adoc[]. == Where to find logs @@ -603,7 +603,7 @@ Retention period: // PLACEHOLDER: for example, 30 days, 90 days, configurable After retention period: * Logs are deleted automatically -* Aggregate metrics retained longer (see xref:ai-gateway/observability-metrics.adoc[]) +* Aggregate metrics retained longer (see xref:observability:metrics.adoc[]) Export logs (if needed for longer retention): @@ -746,4 +746,4 @@ Note: Cost estimates are approximate. Use provider invoices for billing. == Next steps -* xref:ai-gateway/observability-metrics.adoc[] +* xref:observability:metrics.adoc[] diff --git a/modules/ROOT/partials/observability-metrics.adoc b/modules/ROOT/partials/observability-metrics.adoc index 248c4fd..258207c 100644 --- a/modules/ROOT/partials/observability-metrics.adoc +++ b/modules/ROOT/partials/observability-metrics.adoc @@ -22,7 +22,7 @@ Use metrics for: * Capacity planning * Model/provider comparison -Use logs for: Debugging specific requests, viewing full prompts/responses. See xref:ai-gateway/observability-logs.adoc[]. +Use logs for: Debugging specific requests, viewing full prompts/responses. See xref:observability:logs.adoc[]. == Where to find metrics @@ -855,4 +855,4 @@ Solution: == Next steps -* xref:ai-gateway/observability-logs.adoc[] +* xref:observability:logs.adoc[] diff --git a/modules/agents/pages/a2a-concepts.adoc b/modules/agents/pages/a2a-concepts.adoc index a22f003..153ca5b 100644 --- a/modules/agents/pages/a2a-concepts.adoc +++ b/modules/agents/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 ADP 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 *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`. diff --git a/modules/agents/pages/architecture-patterns.adoc b/modules/agents/pages/architecture-patterns.adoc index 896b638..d107fb3 100644 --- a/modules/agents/pages/architecture-patterns.adoc +++ b/modules/agents/pages/architecture-patterns.adoc @@ -79,7 +79,7 @@ Single agents are simpler to build and maintain. You have one system prompt, one However, all capabilities must coexist in one agent. Adding features increases complexity rapidly, making single agents difficult to scale to multi-domain problems. -TIP: You can migrate from a single agent to a root agent with subagents without starting over. Add subagents to an existing agent using the ADP UI, then gradually move tools and responsibilities to the new subagents. +TIP: You can migrate from a single agent to a root agent with subagents without starting over. Add subagents to an existing agent using the Agentic Data Plane UI, then gradually move tools and responsibilities to the new subagents. == Root agent with subagents pattern @@ -199,7 +199,7 @@ For best results: == Model selection guide -Choose models based on task complexity, latency requirements, and cost constraints. The ADP UI displays available models with descriptions when creating agents. +Choose models based on task complexity, latency requirements, and cost constraints. The Agentic Data Plane UI displays available models with descriptions when creating agents. === Match models to task complexity @@ -259,5 +259,3 @@ Provide clear error messages to users. Log errors for debugging. * xref:agents:integration-overview.adoc[] * xref:agents:a2a-concepts.adoc[] * xref:mcp:overview.adoc[] -* xref:agents:overview.adoc[] -* xref:mcp:overview.adoc[] diff --git a/modules/agents/pages/byoa-register.adoc b/modules/agents/pages/byoa-register.adoc index e9b2216..a33ab16 100644 --- a/modules/agents/pages/byoa-register.adoc +++ b/modules/agents/pages/byoa-register.adoc @@ -36,7 +36,7 @@ The two models differ in who runs the agent, who owns scaling, and how the agent |How is the agent defined? |It's already coded; you don't want to translate it into the declarative agent format. -|You want a YAML / declarative definition you edit in the ADP UI. +|You want a YAML / declarative definition you edit in the Agentic Data Plane UI. |Who scales and operates it? |Your team owns scaling, deploys, and the failure model. diff --git a/modules/agents/pages/create-agent.adoc b/modules/agents/pages/create-agent.adoc index fdd946e..c017160 100644 --- a/modules/agents/pages/create-agent.adoc +++ b/modules/agents/pages/create-agent.adoc @@ -10,7 +10,7 @@ // TODO: Refresh screenshots against `adp-production` during Track D polish pass. // TODO (pre-merge verification): Confirm with team-ai whether the cloudv2 main wizard ships before GA. If it does, restructure this page to match the wizard step flow (Basics, Model, Behavior, Tools, Subagents, Review) instead of the deployed single-page form. -Create a new glossterm:AI agent[] declaratively through the ADP UI. No Python or JavaScript code required. This guide walks the create form section by section, then covers the post-create steps for discovery metadata and testing. +Create a new glossterm:AI agent[] declaratively through the Agentic Data Plane UI. No Python or JavaScript code required. This guide walks the create form section by section, then covers the post-create steps for discovery metadata and testing. After reading this page, you will be able to: diff --git a/modules/agents/pages/monitor.adoc b/modules/agents/pages/monitor.adoc index c8d70c2..d0709c4 100644 --- a/modules/agents/pages/monitor.adoc +++ b/modules/agents/pages/monitor.adoc @@ -96,4 +96,3 @@ Monitor iteration counts during complex requests to ensure they complete within * xref:observability:concepts.adoc[] * xref:troubleshoot/troubleshoot-ai-agents.adoc[] -* xref:agents:concepts.adoc[] diff --git a/modules/agents/pages/overview.adoc b/modules/agents/pages/overview.adoc index 1750fb2..946148c 100644 --- a/modules/agents/pages/overview.adoc +++ b/modules/agents/pages/overview.adoc @@ -21,7 +21,7 @@ An AI agent is a system built around a glossterm:large language model (LLM)[] th == How agents work -When you create an agent, you configure the components through the ADP UI rather than writing code: +When you create an agent, you configure the components through the Agentic Data Plane UI rather than writing code: * *System prompt*: Defines the agent's role, responsibilities, and constraints * *LLM*: Interprets user intent and decides which tools to invoke diff --git a/modules/agents/pages/quickstart.adoc b/modules/agents/pages/quickstart.adoc index 989492e..05f9660 100644 --- a/modules/agents/pages/quickstart.adoc +++ b/modules/agents/pages/quickstart.adoc @@ -1,7 +1,7 @@ = AI Agent Quickstart :page-aliases: cloud-data-platform:ai-agents:agents/quickstart.adoc :description: Create your first AI agent in ADP that generates and publishes event data through natural language commands. -:page-topic-type: tutorial +:page-topic-type: quickstart :personas: agent_builder :learning-objective-1: Create an AI agent in ADP that uses MCP tools :learning-objective-2: Configure the agent with a system prompt and model selection @@ -17,11 +17,11 @@ After completing this quickstart, you will be able to: == Prerequisites -* An ADP environment +* A Redpanda Cloud BYOC environment on AWS with ADP enabled. -* xref:ai-gateway:gateway-quickstart.adoc[AI Gateway configured] with at least one LLM provider enabled (OpenAI, Anthropic, Google AI, or AWS Bedrock) +* An xref:ai-gateway:gateway-quickstart.adoc[AI Gateway] configured with at least one LLM provider (OpenAI, Anthropic, Google AI, or AWS Bedrock). -* Completed the xref:mcp:create-server.adoc[Remote MCP Quickstart] to create an MCP server with the following tools deployed: +* An MCP server created by following xref:mcp:create-server.adoc[Create an MCP Server], with the following tools deployed: + ** `generate_input`: Generates fake user event data ** `redpanda_output`: Publishes data to Redpanda topics @@ -34,7 +34,7 @@ An Event Data Manager agent that: * Publishes events to Redpanda topics * Understands natural language requests like "Generate 5 login events and publish them" -The agent orchestrates the `generate_input` and `redpanda_output` tools you created in the Remote MCP quickstart. +The agent orchestrates the `generate_input` and `redpanda_output` tools you created in xref:mcp:create-server.adoc[]. == Create the agent @@ -87,7 +87,7 @@ Response format: . Select MCP tools: + * Click *Add MCP Server* -* Select the `event-data-generator` server (created in the MCP quickstart) +* Select the `event-data-generator` server you created in xref:mcp:create-server.adoc[] * Check both tools: ** `generate_input` ** `redpanda_output` @@ -177,6 +177,7 @@ Common quickstart issue: == Next steps +* xref:get-started:byoc-quickstart.adoc[ADP Quickstart] * xref:agents:overview.adoc[] * xref:agents:create-agent.adoc[] * xref:agents:system-prompts.adoc[] diff --git a/modules/agents/pages/system-prompts.adoc b/modules/agents/pages/system-prompts.adoc index 96a91da..6212d21 100644 --- a/modules/agents/pages/system-prompts.adoc +++ b/modules/agents/pages/system-prompts.adoc @@ -420,5 +420,4 @@ Decision criteria enable reliable tool selection based on request context. == Next steps * xref:agents:quickstart.adoc[] -* xref:agents:overview.adoc[] * xref:mcp:overview.adoc[] diff --git a/modules/agents/pages/troubleshoot/troubleshoot-ai-agents.adoc b/modules/agents/pages/troubleshoot/troubleshoot-ai-agents.adoc index 9c00ff4..0e8211d 100644 --- a/modules/agents/pages/troubleshoot/troubleshoot-ai-agents.adoc +++ b/modules/agents/pages/troubleshoot/troubleshoot-ai-agents.adoc @@ -481,6 +481,5 @@ For comprehensive guidance on monitoring agent activity, analyzing conversation == Next steps * xref:agents:system-prompts.adoc[] -* xref:agents:concepts.adoc[] * xref:mcp:overview.adoc[] * xref:agents:architecture-patterns.adoc[] diff --git a/modules/agents/pages/tutorials/customer-support-agent.adoc b/modules/agents/pages/tutorials/customer-support-agent.adoc index de9c529..59644b7 100644 --- a/modules/agents/pages/tutorials/customer-support-agent.adoc +++ b/modules/agents/pages/tutorials/customer-support-agent.adoc @@ -267,7 +267,7 @@ Use these documented test IDs when testing the agent. If you replace the mock to == Next steps -* xref:mcp:overview.adoc[Call external APIs] +* xref:mcp:overview.adoc[] * xref:agents:system-prompts.adoc[] * xref:agents:architecture-patterns.adoc[] * xref:troubleshoot/troubleshoot-ai-agents.adoc[] diff --git a/modules/ai-gateway/pages/admin/setup-guide.adoc b/modules/ai-gateway/pages/admin/setup-guide.adoc index 6f2f4d1..857ba93 100644 --- a/modules/ai-gateway/pages/admin/setup-guide.adoc +++ b/modules/ai-gateway/pages/admin/setup-guide.adoc @@ -54,7 +54,7 @@ The infrastructure that serves the model differs based on the provider you selec . Click *Save changes*. -Only enabled models will be accessible through gateways. You can enable or disable models at any time without affecting existing gateways. +Only enabled models are accessible through gateways. You can enable or disable models at any time without affecting existing gateways. === Model naming convention diff --git a/modules/ai-gateway/pages/bedrock-setup.adoc b/modules/ai-gateway/pages/bedrock-setup.adoc index 9fd6ef9..0810a66 100644 --- a/modules/ai-gateway/pages/bedrock-setup.adoc +++ b/modules/ai-gateway/pages/bedrock-setup.adoc @@ -8,7 +8,7 @@ // Source: cloudv2 `apps/aigw/docs/customer/bedrock-setup-guide.md` on origin/main, verified 2026-05-19. -This guide walks you through the AWS-side setup AI Gateway needs to invoke Amazon Bedrock, then through the ADP UI flow that registers Bedrock as an LLM provider. For background on how Bedrock foundation models, cross-region inference profiles, and IAM patterns map to the provider form, see xref:ai-gateway:configure-provider.adoc#bedrock-inference-profiles[AWS Bedrock: Inference profiles and IAM] on the main provider configuration page. +This guide walks you through the AWS-side setup AI Gateway needs to invoke Amazon Bedrock, then through the Agentic Data Plane UI flow that registers Bedrock as an LLM provider. For background on how Bedrock foundation models, cross-region inference profiles, and IAM patterns map to the provider form, see xref:ai-gateway:configure-provider.adoc#bedrock-inference-profiles[AWS Bedrock: Inference profiles and IAM] on the main provider configuration page. After completing this guide, you will be able to: @@ -85,7 +85,7 @@ TIP: Don't reuse an existing IAM user. A dedicated user makes it easy to rotate == Generate access keys -Generate the access keys AI Gateway will use: +Generate the access keys AI Gateway uses: [,bash] ---- diff --git a/modules/ai-gateway/pages/configure-provider.adoc b/modules/ai-gateway/pages/configure-provider.adoc index 76c257e..ed6060a 100644 --- a/modules/ai-gateway/pages/configure-provider.adoc +++ b/modules/ai-gateway/pages/configure-provider.adoc @@ -402,7 +402,7 @@ AI Gateway does not provide these capabilities. For current status, consult the * *Multi-provider routing, failover, and retries across providers.* A synthetic provider that fans requests to multiple upstreams is not part of AI Gateway. * *Spend limits.* Per-user, per-org, and global cost caps are not available. AI Gateway records spend and token usage for reporting in the provider *Cost & Usage* view and Governance, but it does not enforce budget caps. See xref:governance:budgets.adoc[Token budgets and limits]. * *Rate limits.* Requests-per-second, per-minute, or per-day limits are not available. -* *Managed MCP aggregation at the gateway.* Register MCP tool servers separately under *MCP Servers* in the ADP UI. +* *Managed MCP aggregation at the gateway.* Register MCP tool servers separately under *MCP Servers* in the Agentic Data Plane UI. == Next steps diff --git a/modules/ai-gateway/pages/connect-agent.adoc b/modules/ai-gateway/pages/connect-agent.adoc index 99c1b02..a20bafc 100644 --- a/modules/ai-gateway/pages/connect-agent.adoc +++ b/modules/ai-gateway/pages/connect-agent.adoc @@ -422,7 +422,7 @@ AI Gateway returns standard HTTP status codes. The upstream provider's error bod * Implement retry with exponential backoff for 5xx and timeout conditions. * Respect `Retry-After` on 429 responses. * Rotate service account credentials on a schedule your organization accepts. -* Observe usage through the ADP UI on each provider's detail page. +* Observe usage through the Agentic Data Plane UI on each provider's detail page. == Troubleshooting diff --git a/modules/ai-gateway/pages/gateway-quickstart.adoc b/modules/ai-gateway/pages/gateway-quickstart.adoc index 12c4c57..49ded00 100644 --- a/modules/ai-gateway/pages/gateway-quickstart.adoc +++ b/modules/ai-gateway/pages/gateway-quickstart.adoc @@ -25,7 +25,7 @@ Providers represent upstream LLM services and their associated credentials. Prov . Navigate to *Agentic* > *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 "Active". +. Verify the provider status shows as active. == Enable models @@ -33,7 +33,7 @@ After enabling a provider, enable the specific models you want to make available . Navigate to *Agentic* > *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. +. Verify the models appear as enabled in the model catalog. TIP: Different providers have different reliability and cost characteristics. When choosing models, consider your use case requirements for quality, speed, and cost. @@ -196,10 +196,10 @@ Confirm your request was routed through AI Gateway. . On the *Overview* tab, check the aggregate metrics: + -* *Total Requests*: Should have incremented -* *Total Tokens*: Shows combined input and output tokens -* *Total Cost*: Estimated spend across all requests -* *Avg Latency*: Average response time in milliseconds +* Total Requests: Should have incremented. +* Total Tokens: Shows combined input and output tokens. +* Total Cost: Estimated spend across all requests. +* Avg Latency: Average response time in milliseconds. . Scroll to the *Models* table to see per-model statistics: + @@ -421,6 +421,7 @@ const openai = new OpenAI({ == Next steps +* xref:get-started:byoc-quickstart.adoc[ADP Quickstart] * xref:ai-gateway:aggregation.adoc[] * xref:integrations:index.adoc[] * xref:ai-gateway:gateway-architecture.adoc[] diff --git a/modules/ai-gateway/pages/overview.adoc b/modules/ai-gateway/pages/overview.adoc index c2a8c31..939cd62 100644 --- a/modules/ai-gateway/pages/overview.adoc +++ b/modules/ai-gateway/pages/overview.adoc @@ -50,11 +50,11 @@ Applications authenticate to ADP with OIDC service accounts instead of long-live === Per-provider observability -The provider's detail page in the ADP UI records spend, request counts, and token counts for the last 7 days. The *Cost & Usage* tab on the *LLM Providers* page expands that view with time-series charts, provider and model grouping, date ranges, and filters for provider, model, cost type, token type, and user. +The provider's detail page in the Agentic Data Plane UI records spend, request counts, and token counts for the last 7 days. The *Cost & Usage* tab on the *LLM Providers* page expands that view with time-series charts, provider and model grouping, date ranges, and filters for provider, model, cost type, token type, and user. == What's in the UI -In the ADP UI you'll find four areas: +In the Agentic Data Plane UI you'll find four areas: * *LLM Providers*: Create, edit, enable, and delete providers, and review provider-level cost and usage. This is the home of AI Gateway configuration. * *MCP Servers*: Register glossterm:MCP[] tool servers for agents. Separate from the AI Gateway proxy URL. @@ -112,7 +112,7 @@ AI Gateway does not provide these capabilities. For current status, consult the * *Multi-provider routing, failover, and retries.* A synthetic provider that fans requests to multiple upstreams is not part of AI Gateway. * *Spend limits.* Per-user, per-org, and global cost caps are not available. AI Gateway records spend and token usage for reporting in the provider *Cost & Usage* view and Governance, but it does not enforce budget caps. See xref:governance:budgets.adoc[Token budgets and limits] for the read-only spending visibility. * *Rate limits.* Requests-per-second, per-minute, or per-day caps are not available. -* *Managed MCP aggregation at the gateway.* Register MCP tool servers separately under *MCP Servers* in the ADP UI. +* *Managed MCP aggregation at the gateway.* Register MCP tool servers separately under *MCP Servers* in the Agentic Data Plane UI. == Next steps diff --git a/modules/ROOT/pages/index.adoc b/modules/get-started/pages/adp-overview.adoc similarity index 83% rename from modules/ROOT/pages/index.adoc rename to modules/get-started/pages/adp-overview.adoc index 1c8993a..b1223dc 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/get-started/pages/adp-overview.adoc @@ -22,15 +22,15 @@ After reading this page, you will be able to: * [ ] {learning-objective-2} * [ ] {learning-objective-3} -== AI agents +== AI Gateway -With Redpanda AI agents, you declare the agent behavior you want and Redpanda handles execution and orchestration. Instead of writing Python or JavaScript, you define behaviors in YAML. You can orchestrate multiple specialized glossterm:subagent[,sub-agents], or bring your own frameworks like LangChain or LlamaIndex. +The AI Gateway manages LLM provider access with two priorities: keeping your application up and keeping costs under control. -What makes this practical at scale is Redpanda Connect. More than 300 connectors with built-in filtering, enrichment, and routing give declarative definitions real power. Upcoming templates will provide default behaviors for common domains such as customer success, legal, and finance. +For high availability, the gateway provides provider-agnostic routing with intelligent failover. Your users don't care which provider serves a request. They care that the application stays up. You can also route different tasks to different models, such as a frontier model for analysis and a smaller model for classification or triage, and see usage and cost across every model in one view. For fiscal control, you get per-tenant budgets and rate limiting, so there are no runaway costs and no surprise bills. -The result is faster time-to-production, lower maintenance (declarative definitions instead of imperative code), and organizational consistency across teams. +The gateway also supports tenancy modeling for teams, individuals, applications, and service accounts, giving you chargeback transparency for internal cost allocation. You can proxy both models and MCP gateways, centralizing compliance for all LLM interactions without locking into any single provider. -For more information, see xref:agents:overview.adoc[]. +For more information, see xref:ai-gateway:overview.adoc[AI Gateway Overview]. == MCP servers @@ -42,25 +42,15 @@ With real-time debugging capabilities, you reduce integration time while getting For more information, see xref:mcp:overview.adoc[MCP Servers Overview]. -== Transcripts - -Every agent action is recorded in an end-to-end execution log. A single glossterm:transcript[] can span multiple agents, tools, and models, covering interactions that last minutes to days. - -Transcripts are the keystone of agent governance. They are built on Redpanda's immutable log with transcript consensus and TLA+ correctness proofs. No gaps, no tampering. For regulated industries that require multi-year audit trails, this provides a compliance-grade record of every decision an agent makes and every data source it uses. - -Redpanda captures 100% of agent actions through OpenTelemetry standards, with end-to-end lineage across the entire execution chain. You can materialize execution logs to Iceberg tables for long-term retention and analysis, or replay them to evaluate and improve agent performance over time. - -For more information, see xref:observability:concepts.adoc[Transcripts Overview]. - -== AI Gateway +== AI agents -The AI Gateway manages LLM provider access with two priorities: keeping your application up and keeping costs under control. +With Redpanda AI agents, you declare the agent behavior you want and Redpanda handles execution and orchestration. Instead of writing Python or JavaScript, you define behaviors in YAML. You can orchestrate multiple specialized glossterm:subagent[,sub-agents], or bring your own frameworks like LangChain or LlamaIndex. -For high availability, the gateway provides provider-agnostic routing with intelligent failover. Your users don't care which provider serves a request. They care that the application stays up. You can also route different tasks to different models, such as a frontier model for analysis and a smaller model for classification or triage, and see usage and cost across every model in one view. For fiscal control, you get per-tenant budgets and rate limiting, so there are no runaway costs and no surprise bills. +What makes this practical at scale is Redpanda Connect. More than 300 connectors with built-in filtering, enrichment, and routing give declarative definitions real power. Upcoming templates will provide default behaviors for common domains such as customer success, legal, and finance. -The gateway also supports tenancy modeling for teams, individuals, applications, and service accounts, giving you chargeback transparency for internal cost allocation. You can proxy both models and MCP gateways, centralizing compliance for all LLM interactions without locking into any single provider. +The result is faster time-to-production, lower maintenance (declarative definitions instead of imperative code), and organizational consistency across teams. -For more information, see xref:ai-gateway:overview.adoc[AI Gateway Overview]. +For more information, see xref:agents:overview.adoc[]. == Governance @@ -76,7 +66,7 @@ Redpanda ADP addresses critical enterprise requirements across all components. * *Unified authorization*: All components use OIDC-based authentication with an on-behalf-of authorization model. When a user invokes an agent, the agent inherits the intersection of its own permissions and the user's permissions. This ensures proper data access scoping. -* *Complete observability*: Redpanda ADP provides two levels of inspection. Execution logs (transcripts) capture every agent action with 100% sampling using OpenTelemetry standards. Real-time debugging tools allow you to inspect individual MCP server calls down to individual tool invocations with full timing data. You can view detailed agent actions in glossterm:Redpanda Console[] and replay data for agent evaluations. +* *Complete observability*: Redpanda ADP provides two levels of inspection. Execution logs (glossterm:transcript[,transcripts]) capture every agent action with 100% sampling using OpenTelemetry standards. Real-time debugging tools let you inspect individual MCP server calls down to individual tool invocations with full timing data. You can view detailed agent actions in the Agentic Data Plane UI and replay data for agent evaluations. For more information, see xref:observability:concepts.adoc[Transcripts Overview]. * *Compliance and audit*: For regulated industries with frameworks such as ISO 42001 and the EU AI Act, Redpanda ADP records every agent action and data source used in decision-making. Execution logs are stored in Redpanda topics and can be materialized to Iceberg tables for multi-year retention and analysis. @@ -92,8 +82,5 @@ Common Redpanda ADP use cases include: == Next steps -* xref:agents:overview.adoc[] -* xref:mcp:overview.adoc[] -* xref:ai-gateway:overview.adoc[] -* xref:governance:dashboard/index.adoc[] -* xref:observability:concepts.adoc[] +* xref:get-started:byoc-quickstart.adoc[ADP Quickstart] — Set up ADP for your organization (administrators). +* xref:agents:quickstart.adoc[AI Agent Quickstart] — Build your first AI agent (builders). diff --git a/modules/governance/pages/budgets.adoc b/modules/governance/pages/budgets.adoc index 32f4bd8..3b8fd69 100644 --- a/modules/governance/pages/budgets.adoc +++ b/modules/governance/pages/budgets.adoc @@ -280,4 +280,4 @@ If the cost still reflects the catalog price, the override may not have propagat * xref:governance:dashboard/overview.adoc[Read the governance overview] * xref:observability:transcripts.adoc[Read a transcript] -* xref:governance:guardrails/index.adoc[Configure guardrails] for selective request blocking +* xref:governance:guardrails/index.adoc[Configure guardrails] diff --git a/modules/governance/pages/dashboard/overview.adoc b/modules/governance/pages/dashboard/overview.adoc index 4a33d15..5f3ac5c 100644 --- a/modules/governance/pages/dashboard/overview.adoc +++ b/modules/governance/pages/dashboard/overview.adoc @@ -7,7 +7,7 @@ :learning-objective-3: Use the Agents table and Top users panel to investigate fleet and user-level spend // Source: `cloudv2` `apps/adp-ui/src/routes/governance/index.tsx`, governance components, and `apps/adp-ui/docs/design/0003-governance-v0.md` on `origin/main`, verified 2026-05-10. -// TODO: Capture screenshots and exact empty-state copy after an authenticated walkthrough of the protected ADP UI. +// TODO: Capture screenshots and exact empty-state copy after an authenticated walkthrough of the protected Agentic Data Plane UI. // TODO: Package 2 briefing (2026-05-22) lists "grouping by user / agent" and "drill-down into agent and user" as still-WIP for Jun 15 ship. The surfaces below already describe a *user* filter on the chart, a per-user *Top users* panel with heatmap, an *Agents* table, and `SpendingFilter.user_id` on the breakdown API. Before next release: reconcile with eng (Johannes / governance team) which of these are live in Package 2 today vs. coming with the Jun 15 cut. If any are still WIP, mark them as "coming in Package 2" or remove until they ship. Do not document unshipped surfaces. Specific items to confirm: (1) per-user filter on the dashboard chart, (2) Top users panel + heatmap, (3) Agents-table drill-down to per-agent spend, (4) per-agent grouping on `GetSpendingBreakdown`, (5) per-user filter on the AI Gateway *Cost & Usage* tab. The Governance dashboard brings AI Gateway usage and agent inventory into one view. Use it to compare spend, request volume, and token volume over a selected time range, then narrow the chart by provider, model, cost type, token type, or user. diff --git a/modules/governance/pages/guardrails/create-guardrail.adoc b/modules/governance/pages/guardrails/create-guardrail.adoc index 078c67a..ef9bbd0 100644 --- a/modules/governance/pages/guardrails/create-guardrail.adoc +++ b/modules/governance/pages/guardrails/create-guardrail.adoc @@ -6,7 +6,7 @@ :learning-objective-2: Attach the guardrail to one or more LLM providers and enable it :learning-objective-3: Verify the guardrail fires and trace the violation through the transcript -// TODO: this page lands at GA. The Guardrails plan (https://redpandadata.atlassian.net/wiki/spaces/DOC/pages/1881702438) lists this page as a must-ship deliverable; the live walkthrough fills in once eng confirms the post-pivot Guardrail resource shape and `aigwctl` (or the ADP UI) is reachable from a sandbox cluster. +// TODO: this page lands at GA. The Guardrails plan (https://redpandadata.atlassian.net/wiki/spaces/DOC/pages/1881702438) lists this page as a must-ship deliverable; the live walkthrough fills in once eng confirms the post-pivot Guardrail resource shape and `aigwctl` (or the Agentic Data Plane UI) is reachable from a sandbox cluster. This page walks through configuring your first guardrail end-to-end: pick an evaluator type, choose a phase, fill in the per-type config, attach it to LLM providers, and confirm it fires. @@ -26,9 +26,9 @@ After reading this page, you will be able to: == Open the Guardrails surface -// TODO: finalize this section once the ADP UI ships a Guardrails surface. As of 2026-04-28, `apps/adp-ui/src/routes/` has no `guardrails/` route. The walkthrough may need to lead with `aigwctl` instead of the UI and add the UI flow in a later refresh. Open Qs C4 and C5 in the companion plan. +// TODO: finalize this section once the Agentic Data Plane UI ships a Guardrails surface. As of 2026-04-28, `apps/adp-ui/src/routes/` has no `guardrails/` route. The walkthrough may need to lead with `aigwctl` instead of the UI and add the UI flow in a later refresh. Open Qs C4 and C5 in the companion plan. -In the ADP UI, open *Governance* → *Guardrails* → *Create guardrail*. +In the Agentic Data Plane UI, open *Governance* → *Guardrails* → *Create guardrail*. == Pick an evaluator type diff --git a/modules/integrations/pages/claude-code.adoc b/modules/integrations/pages/claude-code.adoc index 1cce356..e86ef63 100644 --- a/modules/integrations/pages/claude-code.adoc +++ b/modules/integrations/pages/claude-code.adoc @@ -159,8 +159,8 @@ claude "say hello" == Related topics -* xref:ai-gateway:configure-provider.adoc[Configure an LLM provider] -* xref:ai-gateway:connect-agent.adoc[Connect your agent] for the SDK and OIDC reference this page builds on -* xref:ai-gateway:configure-provider.adoc#anthropic-authorization-passthrough[Anthropic: Authorization passthrough] for the enterprise-subscription pattern -* xref:integrations:remote-mcp-clients.adoc[Connect remote MCP clients] for chat-app integrations (Claude Desktop, ChatGPT, Gemini, Cursor) -* xref:ai-gateway:aggregation.adoc[MCP aggregation] for fronting many MCP servers behind one URL +* xref:ai-gateway:configure-provider.adoc[] +* xref:ai-gateway:connect-agent.adoc[] +* xref:ai-gateway:configure-provider.adoc#anthropic-authorization-passthrough[Anthropic: Authorization passthrough] +* xref:integrations:remote-mcp-clients.adoc[] +* xref:ai-gateway:aggregation.adoc[] diff --git a/modules/integrations/pages/remote-mcp-clients.adoc b/modules/integrations/pages/remote-mcp-clients.adoc index 87f07b1..d8c23ee 100644 --- a/modules/integrations/pages/remote-mcp-clients.adoc +++ b/modules/integrations/pages/remote-mcp-clients.adoc @@ -160,7 +160,7 @@ This handshake runs *once per user* when the connector is first added. * The OAuth Client's name (for example, _Claude (GitHub Read demo) wants to access your data_). * The *Resource* being authorized: The MCP server name and URL. * The *Requested permissions*: The gateway's internal scopes for this handshake (`mcp` and `offline_access`). These are *not* the upstream system's scopes; the upstream's scopes appear during the next handshake. -* A footer reminding the user that they can revoke access from their *Connections* page in the ADP UI. +* A footer reminding the user that they can revoke access from their *Connections* page in the Agentic Data Plane UI. + . The user clicks *Allow*. AI Gateway redirects the chat client back to the redirect URI with an authorization code. . The chat client exchanges the code for an access token and a refresh token. Tokens are stored locally in the chat client's credential store. diff --git a/modules/integrations/partials/integrations/claude-code-admin.adoc b/modules/integrations/partials/integrations/claude-code-admin.adoc index 3621420..2971e84 100644 --- a/modules/integrations/partials/integrations/claude-code-admin.adoc +++ b/modules/integrations/partials/integrations/claude-code-admin.adoc @@ -192,7 +192,7 @@ Enable Claude Code to discover and use tools from multiple MCP servers through a |Descriptive name (for example, `redpanda-data-catalog`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -467,4 +467,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/integrations/partials/integrations/cline-admin.adoc b/modules/integrations/partials/integrations/cline-admin.adoc index a670e93..3b2580d 100644 --- a/modules/integrations/partials/integrations/cline-admin.adoc +++ b/modules/integrations/partials/integrations/cline-admin.adoc @@ -205,7 +205,7 @@ Enable Cline to discover and use tools from multiple MCP servers through a singl |Descriptive name (for example, `filesystem-tools`, `code-analysis-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -547,4 +547,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/integrations/partials/integrations/continue-admin.adoc b/modules/integrations/partials/integrations/continue-admin.adoc index 10bae57..91dac29 100644 --- a/modules/integrations/partials/integrations/continue-admin.adoc +++ b/modules/integrations/partials/integrations/continue-admin.adoc @@ -301,7 +301,7 @@ Enable Continue.dev to discover and use tools from multiple MCP servers through |Descriptive name (for example, `redpanda-data-catalog`, `code-search-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -714,4 +714,4 @@ This is expected behavior, not a configuration issue: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/integrations/partials/integrations/cursor-admin.adoc b/modules/integrations/partials/integrations/cursor-admin.adoc index bdb6cb6..3753339 100644 --- a/modules/integrations/partials/integrations/cursor-admin.adoc +++ b/modules/integrations/partials/integrations/cursor-admin.adoc @@ -229,7 +229,7 @@ Enable Cursor to discover and use tools from multiple MCP servers through a sing |Descriptive name (for example, `redpanda-data-tools`, `code-search-tools`) |Endpoint URL -|MCP server endpoint (for example, xref:mcp/remote/overview.adoc[Remote MCP server] URL) +|MCP server endpoint (for example, xref:integrations:remote-mcp-clients.adoc[Remote MCP server] URL) |Authentication |Bearer token or other authentication mechanism @@ -681,4 +681,4 @@ Causes and solutions: == Next steps -* xref:mcp/remote/overview.adoc[] +* xref:integrations:remote-mcp-clients.adoc[] diff --git a/modules/integrations/partials/integrations/github-copilot-admin.adoc b/modules/integrations/partials/integrations/github-copilot-admin.adoc index a929706..bb157af 100644 --- a/modules/integrations/partials/integrations/github-copilot-admin.adoc +++ b/modules/integrations/partials/integrations/github-copilot-admin.adoc @@ -615,7 +615,7 @@ Causes and solutions: * **Expired token**: Generate a new API token and update the GitHub Copilot configuration * **Network connectivity**: Verify the cluster endpoint is accessible from the client network * **Provider not enabled**: Ensure at least one provider is enabled and has models in the catalog -* **SSL/TLS issues**: Verify the cluster has valid SSL certificates +* **TLS issues**: Verify the cluster has valid TLS certificates * **Organization policy blocking custom endpoints**: Check GitHub organization settings === Model not found errors diff --git a/modules/mcp/pages/create-server.adoc b/modules/mcp/pages/create-server.adoc index b375f17..f72943d 100644 --- a/modules/mcp/pages/create-server.adoc +++ b/modules/mcp/pages/create-server.adoc @@ -2,7 +2,7 @@ :description: Create an MCP server in the Agentic Data Plane by picking a managed type from the marketplace or registering a self-managed server you host yourself, then configure authentication, code mode, and access. :page-topic-type: how-to :personas: agent_builder, platform_engineer -:learning-objective-1: Create a managed or self-managed MCP server in the ADP UI +:learning-objective-1: Create a managed or self-managed MCP server in the Agentic Data Plane UI :learning-objective-2: Configure each authentication mode and pick the right one for your use case :learning-objective-3: Save the server, verify the API URL, and confirm tools were discovered @@ -18,7 +18,7 @@ After completing this guide, you will be able to: * Access to the Agentic Data Plane. + -// TODO: confirm sign-in URL and IAM/role requirements once the standalone ADP UI ships. +// TODO: confirm sign-in URL and IAM/role requirements once the standalone Agentic Data Plane UI ships. * For any auth mode that uses upstream credentials: the credentials in hand and a secret already created in the ADP secret store. Secret references must be `UPPER_SNAKE_CASE` (proto regex `^[A-Z][A-Z0-9_]*$`). For example: `MCP_API_KEY`, `OPENAI_API_KEY`. + // TODO: xref the ADP secrets-management page once confirmed. @@ -26,7 +26,7 @@ After completing this guide, you will be able to: == Open the MCP Servers page -. Sign in to the ADP UI and open *MCP Servers*. +. Sign in to the Agentic Data Plane UI and open *MCP Servers*. + // TODO: screenshot of the MCP Servers list page on `adp-production`. . Click *Create Server*. The marketplace picker opens. @@ -240,9 +240,7 @@ The command resolves the gateway URL from your active rpk cloud profile and read == Related topics -This page covers creating an MCP server. For other capabilities you may need to configure separately, see: - -* xref:mcp:user-delegated-oauth.adoc[User-delegated OAuth] for the consent flow your end users will see. -* xref:mcp:test-tools.adoc[Test a server's tools] for using the Inspector tab to call tools, resources, and prompts. -* xref:ai-gateway:aggregation.adoc[MCP aggregation] for fronting many MCP servers behind a single URL with AI Gateway. -* xref:mcp:managed/managed-catalog.adoc[Managed catalog] for per-type configuration depth and deep-dive pages. +* xref:mcp:user-delegated-oauth.adoc[] +* xref:mcp:test-tools.adoc[] +* xref:ai-gateway:aggregation.adoc[] +* xref:mcp:managed/managed-catalog.adoc[] diff --git a/modules/mcp/pages/github-oauth-tutorial.adoc b/modules/mcp/pages/github-oauth-tutorial.adoc index 65c5f86..77ed5af 100644 --- a/modules/mcp/pages/github-oauth-tutorial.adoc +++ b/modules/mcp/pages/github-oauth-tutorial.adoc @@ -69,7 +69,7 @@ Throughout this tutorial, fields marked with * are required. == Create the GitHub OAuth provider in ADP -Register GitHub as an OAuth provider in the ADP UI. +Register GitHub as an OAuth provider in the Agentic Data Plane UI. . In ADP, navigate to **OAuth Providers** in the sidebar. . Click **Create provider** and select **GitHub** from the catalog. @@ -91,7 +91,7 @@ Register GitHub as an OAuth provider in the ADP UI. |**Display name** * |`GitHub` -|Human-readable name shown in the ADP UI. +|Human-readable name shown in the Agentic Data Plane UI. |**Authorization endpoint** * |`\https://github.com/login/oauth/authorize` @@ -310,7 +310,7 @@ For most scenarios where users need to access their own repositories or respect Test that the MCP server is correctly configured and can authenticate users. -. In the ADP UI, find your GitHub MCP server in the **MCP Servers** list. +. In the Agentic Data Plane UI, find your GitHub MCP server in the **MCP Servers** list. . Click it to view details. . If you tested the connection in My Connections, you're already connected and can test immediately. . If you skipped the My Connections test, the first time you call a tool from this server, you'll be prompted to authorize GitHub. @@ -365,13 +365,6 @@ You could next create an agent using this GitHub MCP server. Each user who calls |You need the `dataplane_aigateway_oauthprovider_attach` permission on the GitHub provider. Contact your ADP administrator to grant this permission. |=== -== Next steps - -* **Add more scopes**: If you need additional GitHub permissions, edit the OAuth provider to add scopes. Existing users will be prompted to re-consent with the upgraded scope. -* **Create additional MCP servers**: You can create multiple GitHub MCP servers (for example, "GitHub Read" and "GitHub Write") attached to the same OAuth provider but exposing different tool sets. -* **Monitor connections**: Users can view and revoke their GitHub connections anytime in **My Connections**. -* **Review audit logs**: As an admin, you can review which users have connected to GitHub and track MCP server usage. - == Related topics * xref:mcp:oauth-providers.adoc[Configure an OAuth Provider] diff --git a/modules/mcp/pages/managed/bamboohr.adoc b/modules/mcp/pages/managed/bamboohr.adoc index 947b1f0..898975e 100644 --- a/modules/mcp/pages/managed/bamboohr.adoc +++ b/modules/mcp/pages/managed/bamboohr.adoc @@ -48,7 +48,7 @@ Use BambooHR when an agent needs HR context from BambooHR without sharing one up * A BambooHR company subdomain, such as `mycompany` for `mycompany.bamboohr.com`. The managed config accepts letters, numbers, and hyphens. * BambooHR users with the permissions required to read the employee, time-off, or performance data your agent needs. -// TODO: Confirm the exact ADP UI field labels for attaching user-delegated OAuth to managed BambooHR after an authenticated UI walkthrough. +// TODO: Confirm the exact Agentic Data Plane UI field labels for attaching user-delegated OAuth to managed BambooHR after an authenticated UI walkthrough. // TODO: Add a CLI example only after confirming how `rpk ai` sets MCPServer `auth_config.user_oauth` for managed types that do not carry auth inside the managed config. == Configure BambooHR OAuth @@ -103,6 +103,6 @@ Test the server in the Inspector before you connect it to an agent. Start with ` == Next steps -* xref:mcp:user-delegated-oauth.adoc[Configure user-delegated OAuth] -* xref:mcp:test-tools.adoc[Test a server's tools] -* xref:agents:create-agent.adoc[Create a declarative agent] that uses the BambooHR server +* xref:mcp:user-delegated-oauth.adoc[] +* xref:mcp:test-tools.adoc[] +* xref:agents:create-agent.adoc[] diff --git a/modules/mcp/pages/managed/ironclad.adoc b/modules/mcp/pages/managed/ironclad.adoc index 6881a55..41eae4b 100644 --- a/modules/mcp/pages/managed/ironclad.adoc +++ b/modules/mcp/pages/managed/ironclad.adoc @@ -49,7 +49,7 @@ Set up the OAuth app on Ironclad and the matching OAuth Provider in ADP: == Configure -Create a new Ironclad MCP server in the ADP UI: +Create a new Ironclad MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Ironclad* from the marketplace picker. diff --git a/modules/mcp/pages/managed/jira.adoc b/modules/mcp/pages/managed/jira.adoc index f8c0f51..b0d4232 100644 --- a/modules/mcp/pages/managed/jira.adoc +++ b/modules/mcp/pages/managed/jira.adoc @@ -31,7 +31,7 @@ The Jira managed type exposes tools for: * An Atlassian OAuth 2.0 (3LO) app registered against `https://api.atlassian.com`. + // TODO: confirm whether Redpanda publishes a reference Atlassian app or whether each customer brings their own. -* An OAuth Provider in the ADP UI configured for Atlassian's authorize/token URLs and carrying the app's client credentials. +* An OAuth Provider in the Agentic Data Plane UI configured for Atlassian's authorize/token URLs and carrying the app's client credentials. * Familiarity with xref:mcp:user-delegated-oauth.adoc[]. == Atlassian's scope model diff --git a/modules/mcp/pages/managed/managed-catalog.adoc b/modules/mcp/pages/managed/managed-catalog.adoc index 0e363b7..2632707 100644 --- a/modules/mcp/pages/managed/managed-catalog.adoc +++ b/modules/mcp/pages/managed/managed-catalog.adoc @@ -3,7 +3,7 @@ :page-topic-type: reference :personas: agent_builder, platform_engineer -Managed MCP servers are in-process implementations Redpanda hosts for you. Each type has a fixed set of glossterm:tool[,tools] and a type-specific configuration schema. To create one, open *MCP Servers > Create Server* in the ADP UI and pick the type from the marketplace picker. See xref:mcp:create-server.adoc[Create an MCP Server] for the full create flow. +Managed MCP servers are in-process implementations Redpanda hosts for you. Each type has a fixed set of glossterm:tool[,tools] and a type-specific configuration schema. To create one, open *MCP Servers > Create Server* in the Agentic Data Plane UI and pick the type from the marketplace picker. See xref:mcp:create-server.adoc[Create an MCP Server] for the full create flow. // Source: `cloudv2` `apps/aigw/internal/mcp/managed/defaults.go` and managed type registration files on `origin/main`, verified 2026-05-10. This catalog lists the 36 managed MCP server types Redpanda registers by default, grouped by category. @@ -224,6 +224,6 @@ If any of these answers are "no," prefer xref:mcp:register-remote.adoc[a self-ma == Next steps -* xref:mcp:create-server.adoc[Create an MCP server] using the marketplace picker -* xref:mcp:test-tools.adoc[Test tools with the Inspector] before pointing an agent at the server -* xref:mcp:user-delegated-oauth.adoc[Configure user-delegated OAuth] for types that need per-user upstream identities +* xref:mcp:create-server.adoc[] +* xref:mcp:test-tools.adoc[] +* xref:mcp:user-delegated-oauth.adoc[] diff --git a/modules/mcp/pages/managed/metabase.adoc b/modules/mcp/pages/managed/metabase.adoc index ad5e50d..dcd304d 100644 --- a/modules/mcp/pages/managed/metabase.adoc +++ b/modules/mcp/pages/managed/metabase.adoc @@ -31,7 +31,7 @@ It is *not* a Metabase admin tool. Creating dashboards, editing cards, configuri Metabase API keys (v0.49+) inherit the *permissions of the group they're bound to*. The MCP sends the resolved key in the `X-API-Key` header on every upstream request. -There is no per-user delegation: one API key per MCP instance, applied to every tool call. To give different agents different access, mount multiple MCP instances bound to different Metabase groups. +The Metabase MCP uses one API key per MCP instance, applied to every tool call, with no per-user delegation. To give different agents different access, mount multiple MCP instances bound to different Metabase groups. Auth is implemented as `oneof auth { StaticKeyAuth api_key }` (single variant today, future-proof for adding session or OAuth modes without a wire-format break). @@ -63,7 +63,7 @@ Permission errors surface from the upstream Metabase API as `metabase API error == Configure -Create a new Metabase MCP server in the ADP UI: +Create a new Metabase MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Metabase* from the marketplace picker. diff --git a/modules/mcp/pages/managed/netsuite.adoc b/modules/mcp/pages/managed/netsuite.adoc index 3c1745c..e9ea6e8 100644 --- a/modules/mcp/pages/managed/netsuite.adoc +++ b/modules/mcp/pages/managed/netsuite.adoc @@ -56,7 +56,7 @@ The managed server does not expose write tools, saved-search execution, or repor * Your NetSuite account ID. Production accounts use a numeric ID such as `1234567`. Sandbox accounts include a suffix such as `1234567_SB1`; release-preview accounts can use a suffix such as `1234567_RP1`. * NetSuite users with the *REST Web Services* permission on at least one role. -// TODO: Confirm the exact ADP UI field labels for NetSuite OAuth Provider creation after an authenticated UI walkthrough. +// TODO: Confirm the exact Agentic Data Plane UI field labels for NetSuite OAuth Provider creation after an authenticated UI walkthrough. == Configure NetSuite OAuth @@ -140,6 +140,6 @@ NetSuite record filters use NetSuite-specific forms: == Next steps -* xref:mcp:user-delegated-oauth.adoc[Configure user-delegated OAuth] -* xref:mcp:test-tools.adoc[Test a server's tools] -* xref:agents:create-agent.adoc[Create a declarative agent] that uses the NetSuite server +* xref:mcp:user-delegated-oauth.adoc[] +* xref:mcp:test-tools.adoc[] +* xref:agents:create-agent.adoc[] diff --git a/modules/mcp/pages/managed/ramp.adoc b/modules/mcp/pages/managed/ramp.adoc index c66563b..f592365 100644 --- a/modules/mcp/pages/managed/ramp.adoc +++ b/modules/mcp/pages/managed/ramp.adoc @@ -55,7 +55,7 @@ Set up the OAuth app on Ramp and the matching OAuth Provider in ADP: == Configure -Create a new Ramp MCP server in the ADP UI: +Create a new Ramp MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Ramp* from the marketplace picker. diff --git a/modules/mcp/pages/managed/slack.adoc b/modules/mcp/pages/managed/slack.adoc index dd85b76..d41dac0 100644 --- a/modules/mcp/pages/managed/slack.adoc +++ b/modules/mcp/pages/managed/slack.adoc @@ -32,12 +32,12 @@ Before you create the server, make sure you have: * A Slack OAuth app registered (your own or a Redpanda-published reference app). + // TODO: confirm whether Redpanda ships a reference Slack OAuth app or whether each customer brings their own. Document the path. -* An OAuth Provider configured in the ADP UI under *OAuth Providers*, pointing at Slack's authorize/token URLs and carrying the OAuth app's client credentials. See xref:mcp:oauth-providers.adoc[Configure an OAuth Provider]. +* An OAuth Provider configured in the Agentic Data Plane UI under *OAuth Providers*, pointing at Slack's authorize/token URLs and carrying the OAuth app's client credentials. See xref:mcp:oauth-providers.adoc[Configure an OAuth Provider]. * Familiarity with xref:mcp:user-delegated-oauth.adoc[]. == Configure -Create a new Slack MCP server in the ADP UI: +Create a new Slack MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Slack* from the marketplace picker. diff --git a/modules/mcp/pages/managed/workday.adoc b/modules/mcp/pages/managed/workday.adoc index 1977eeb..cfb3812 100644 --- a/modules/mcp/pages/managed/workday.adoc +++ b/modules/mcp/pages/managed/workday.adoc @@ -56,7 +56,7 @@ Set up authentication on the Workday side before configuring the MCP: == Configure -Create a new Workday MCP server in the ADP UI: +Create a new Workday MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Workday* from the marketplace picker. diff --git a/modules/mcp/pages/managed/zendesk.adoc b/modules/mcp/pages/managed/zendesk.adoc index 3a28922..a9d0f60 100644 --- a/modules/mcp/pages/managed/zendesk.adoc +++ b/modules/mcp/pages/managed/zendesk.adoc @@ -57,7 +57,7 @@ For per-user authentication, register an OAuth client on Zendesk and a matching == Configure -Create a new Zendesk MCP server in the ADP UI: +Create a new Zendesk MCP server in the Agentic Data Plane UI: . Open *MCP Servers > Create Server*. . Pick *Zendesk* from the marketplace picker. diff --git a/modules/mcp/pages/overview.adoc b/modules/mcp/pages/overview.adoc index 73b0ba3..481b8a4 100644 --- a/modules/mcp/pages/overview.adoc +++ b/modules/mcp/pages/overview.adoc @@ -48,7 +48,7 @@ The default registry contains 36 managed MCP server types. See xref:mcp:managed/ |You manage |=== -== What's in the ADP UI +== What's in the Agentic Data Plane UI The Agentic Data Plane UI has four top-level areas: @@ -64,13 +64,13 @@ The Agentic Data Plane UI has four top-level areas: * *Tool discovery*: After you create or register a server, Redpanda performs a live `tools/list` against it and populates the server's detail page so you can see which tools are visible to agents. * *Service-account and user-delegated auth*: Pick a single shared upstream identity for all callers, or have each end-user authenticate against the upstream system with their own credentials. * *Code mode*: Optionally expose `{name}_search` and `{name}_execute` helpers so an agent can discover and orchestrate tools through generated Python or JavaScript instead of calling them one at a time. -* *Inspector*: Test each tool, resource, and prompt directly from the ADP UI before pointing an agent at the server. See xref:mcp:test-tools.adoc[Test a server's tools]. +* *Inspector*: Test each tool, resource, and prompt directly from the Agentic Data Plane UI before pointing an agent at the server. See xref:mcp:test-tools.adoc[Test a server's tools]. * *Aggregation*: Connect your agent to a single MCP URL and have Redpanda fan out across multiple registered MCP servers. See xref:ai-gateway:aggregation.adoc[MCP aggregation]. == Next steps -. *Create your first MCP server.* xref:mcp:create-server.adoc[Create an MCP Server] walks through the marketplace picker, the managed and self-managed flows, every authentication mode, and code mode. -. *Test what you built.* xref:mcp:test-tools.adoc[Test a server's tools] uses the Inspector tab to call tools, resources, and prompts live. -. *Wire up user-delegated OAuth* when your users authenticate against the upstream system with their own credentials. See xref:mcp:user-delegated-oauth.adoc[User-delegated OAuth]. -. *Register an existing server* you already run yourself. See xref:mcp:register-remote.adoc[Register a self-managed server]. -. *Browse the managed catalog* for the full list of types, their categories, and per-type configuration links. See xref:mcp:managed/managed-catalog.adoc[Managed catalog]. +* xref:mcp:create-server.adoc[] +* xref:mcp:test-tools.adoc[] +* xref:mcp:user-delegated-oauth.adoc[] +* xref:mcp:register-remote.adoc[] +* xref:mcp:managed/managed-catalog.adoc[] diff --git a/modules/mcp/pages/register-remote.adoc b/modules/mcp/pages/register-remote.adoc index a3a2c4d..234f927 100644 --- a/modules/mcp/pages/register-remote.adoc +++ b/modules/mcp/pages/register-remote.adoc @@ -2,7 +2,7 @@ :description: Front your own MCP server with a managed Redpanda URL. Pick a transport, configure authentication, and let agents discover the server's tools through Redpanda. :page-topic-type: how-to :personas: platform_engineer, agent_builder -:learning-objective-1: Register a self-managed MCP server in the ADP UI +:learning-objective-1: Register a self-managed MCP server in the Agentic Data Plane UI :learning-objective-2: Pick the right transport (SSE vs. Streamable HTTP) and authentication mode :learning-objective-3: Confirm tool discovery completed and the server is reachable through its proxy URL @@ -139,6 +139,5 @@ If the tools list is empty or stale, hit the *Refresh tools* action on the Overv == Related topics -* xref:mcp:user-delegated-oauth.adoc[User-delegated OAuth] for the consent flow. -* xref:ai-gateway:aggregation.adoc[MCP aggregation] for fronting many MCP servers behind a single URL with AI Gateway. -* Server hosting and deployment guidance is your responsibility: Redpanda doesn't operate self-managed servers; deployment, scaling, and patching are up to you. +* xref:mcp:user-delegated-oauth.adoc[] +* xref:ai-gateway:aggregation.adoc[] diff --git a/modules/mcp/pages/test-tools.adoc b/modules/mcp/pages/test-tools.adoc index c6c217f..cd33655 100644 --- a/modules/mcp/pages/test-tools.adoc +++ b/modules/mcp/pages/test-tools.adoc @@ -6,7 +6,7 @@ :learning-objective-2: Inspect resources, prompts, and call history :learning-objective-3: Diagnose common errors (auth missing, scope upgrade required, transport mismatch) before pointing an agent at the server -Test your MCP server's glossterm:tool[,tools], glossterm:resource[,resources], and glossterm:prompt[,prompts] using the Inspector: a built-in MCP client in the ADP UI. It runs on the same JSON-RPC connection that agents use, so a tool that works in the Inspector also works for an agent. Use this after creating your server (xref:mcp:create-server.adoc[Create an MCP Server]) or whenever you change a tool's schema. +Test your MCP server's glossterm:tool[,tools], glossterm:resource[,resources], and glossterm:prompt[,prompts] using the Inspector: a built-in MCP client in the Agentic Data Plane UI. It runs on the same JSON-RPC connection that agents use, so a tool that works in the Inspector also works for an agent. Use this after creating your server (xref:mcp:create-server.adoc[Create an MCP Server]) or whenever you change a tool's schema. After completing this guide, you will be able to: @@ -122,6 +122,5 @@ The command resolves the gateway URL from your active rpk cloud profile and read == Related topics -* xref:ai-gateway:aggregation.adoc[MCP aggregation] for fronting many MCP servers behind a single URL. -* For pointing an agent at the server, see the Agents docs. -* The Inspector tests the MCP server, not the upstream system. Debugging the upstream system itself (your SQL database, your Slack app) is outside the scope of MCP tooling. +* xref:ai-gateway:aggregation.adoc[] +* xref:agents:create-agent.adoc[] diff --git a/modules/mcp/pages/user-delegated-oauth.adoc b/modules/mcp/pages/user-delegated-oauth.adoc index c953d00..9498c5e 100644 --- a/modules/mcp/pages/user-delegated-oauth.adoc +++ b/modules/mcp/pages/user-delegated-oauth.adoc @@ -16,7 +16,7 @@ After completing this guide, you will be able to: == Prerequisites -* An OAuth provider resource configured in the ADP UI under *OAuth providers*. The provider declares the upstream's `authorize_url`, `token_url`, supported scopes, and client credentials. See xref:mcp:oauth-providers.adoc[Configure an OAuth Provider]. +* An OAuth provider resource configured in the Agentic Data Plane UI under *OAuth providers*. The provider declares the upstream's `authorize_url`, `token_url`, supported scopes, and client credentials. See xref:mcp:oauth-providers.adoc[Configure an OAuth Provider]. * The required scopes for the upstream API you plan to call. * For *self-managed* MCP servers: the server URL must be `https://` (proto rule `remote_mcp.user_oauth_requires_https`). HTTP is rejected at create time. * For *managed* MCP servers: the type must support user-delegated OAuth. SQL doesn't; Slack, Jira, and Google managed types do. Check xref:managed/managed-catalog.adoc[Managed catalog] before configuring. @@ -41,12 +41,12 @@ TIP: To configure user-delegated OAuth from the CLI, use `--user-oauth-provider` The first time a user calls a tool that needs this server's authentication, Redpanda doesn't have a stored token for them. The behavior is: . The MCP RPC returns `FAILED_PRECONDITION` with an `OAuthConnectionRequired` error detail. The detail carries an `authorize_url`. -. The ADP UI surfaces a consent prompt to the user, pointing at the `authorize_url`. +. The Agentic Data Plane UI surfaces a consent prompt to the user, pointing at the `authorize_url`. . The user completes the device-authorization flow with the upstream provider. . The upstream provider redirects back to Redpanda with a token. Redpanda stores it in the token vault under that user's identity. . The original tool call retries automatically. Subsequent calls reuse the stored token. -After consent, the user can see and revoke their connection under *My Connections* in the ADP UI. +After consent, the user can see and revoke their connection under *My Connections* in the Agentic Data Plane UI. // TODO: screenshot of the consent prompt and the resulting *My Connections* entry. @@ -80,7 +80,7 @@ For the field-by-field service-account-OAuth setup, see xref:mcp:create-server.a |Symptom |What to check |"OAuth provider not found" -|The provider name on the server doesn't match an OAuth provider in the ADP UI. Check spelling and that the provider exists. +|The provider name on the server doesn't match an OAuth provider in the Agentic Data Plane UI. Check spelling and that the provider exists. |"HTTPS required" on save (self-managed only) |User-delegated OAuth requires `https://` URLs on the MCP server (proto rule `remote_mcp.user_oauth_requires_https`). Switch the server's URL to HTTPS. @@ -97,6 +97,5 @@ For the field-by-field service-account-OAuth setup, see xref:mcp:create-server.a == Related topics -* xref:mcp:oauth-providers.adoc[Configure an OAuth Provider] for the separate workflow that creates the providers referenced from MCP servers. +* xref:mcp:oauth-providers.adoc[] * xref:mcp:create-server.adoc#configure-authentication[Service-account OAuth setup] for the shared-identity alternative. -* Token vault internals are not user-configurable. Redpanda manages the vault; users see their own connections under *My Connections*. diff --git a/modules/observability/pages/ingest-custom-traces.adoc b/modules/observability/pages/ingest-custom-traces.adoc index c896413..e49dfe5 100644 --- a/modules/observability/pages/ingest-custom-traces.adoc +++ b/modules/observability/pages/ingest-custom-traces.adoc @@ -29,7 +29,7 @@ If you're using LangChain with OpenTelemetry tracing, you can send traces to Red . Configure LangChain's OpenTelemetry integration by following the https://docs.langchain.com/langsmith/trace-with-opentelemetry[LangChain documentation^]. -. Deploy a Redpanda Connect pipeline using the `otlp_http` input to receive OTLP traces over HTTP. Today, create the pipeline in the **Connect** page of your Redpanda BYOC environment. See the <> section below for a sample configuration. +. Deploy a Redpanda Connect pipeline using the `otlp_http` input to receive OTLP traces over HTTP. Today, create the pipeline in the **Connect** page of your Redpanda BYOC environment. For a sample configuration, see <>. // TODO: Update the deployment entry point once the standalone-ADP ingestion flow is defined. . Configure your OTEL exporter to send traces to your Redpanda Connect pipeline using environment variables: @@ -569,7 +569,7 @@ Look for spans with your custom `instrumentationScope.name` to identify traces f === View traces in Transcripts -After your custom agent sends traces through the pipeline, they appear in the *Transcripts* view of the ADP UI alongside traces from Remote MCP servers, declarative agents, and AI Gateway. +After your custom agent sends traces through the pipeline, they appear in the *Transcripts* view of the Agentic Data Plane UI alongside traces from Remote MCP servers, declarative agents, and AI Gateway. ==== Identify custom agent transcripts @@ -620,6 +620,6 @@ If requests succeed but traces do not appear in `redpanda.otel_traces`: == Next steps * xref:observability:transcripts.adoc[] -* xref:agents:monitor.adoc[Observability for declarative agents] +* xref:agents:monitor.adoc[] * xref:connect:components:inputs/otlp_http.adoc[OTLP HTTP input reference] * xref:connect:components:inputs/otlp_grpc.adoc[OTLP gRPC input reference] diff --git a/modules/observability/pages/transcripts.adoc b/modules/observability/pages/transcripts.adoc index 2c54425..96fb89a 100644 --- a/modules/observability/pages/transcripts.adoc +++ b/modules/observability/pages/transcripts.adoc @@ -1,5 +1,5 @@ = Read a Transcript -:description: Open a transcript in the ADP UI, read the conversation turn by turn, and investigate errors, costs, and performance. +: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 :learning-objective-1: Filter and open a transcript for a specific agent or MCP server execution @@ -23,7 +23,7 @@ After reading this page, you will be able to: == Open the Transcripts view -. Sign in to the ADP UI. +. Sign in to the Agentic Data Plane UI. // TODO: Replace with the standalone ADP URL + sign-in flow once available. . Open *Transcripts* from the primary navigation. diff --git a/modules/observability/partials/observability-logs.adoc b/modules/observability/partials/observability-logs.adoc index 45006a3..f4cbc29 100644 --- a/modules/observability/partials/observability-logs.adoc +++ b/modules/observability/partials/observability-logs.adoc @@ -22,7 +22,7 @@ Use logs for: * Understanding which provider handled a request * Investigating latency spikes or errors for specific users -Use metrics for: Aggregate analytics, trends, cost tracking across time. See xref:ai-gateway/observability-metrics.adoc[]. +Use metrics for: Aggregate analytics, trends, cost tracking across time. See xref:observability:metrics.adoc[]. == Where to find logs @@ -603,7 +603,7 @@ Retention period: // PLACEHOLDER: for example, 30 days, 90 days, configurable After retention period: * Logs are deleted automatically -* Aggregate metrics retained longer (see xref:ai-gateway/observability-metrics.adoc[]) +* Aggregate metrics retained longer (see xref:observability:metrics.adoc[]) Export logs (if needed for longer retention): @@ -746,4 +746,4 @@ Note: Cost estimates are approximate. Use provider invoices for billing. == Next steps -* xref:ai-gateway/observability-metrics.adoc[] +* xref:observability:metrics.adoc[] diff --git a/modules/observability/partials/observability-metrics.adoc b/modules/observability/partials/observability-metrics.adoc index 248c4fd..258207c 100644 --- a/modules/observability/partials/observability-metrics.adoc +++ b/modules/observability/partials/observability-metrics.adoc @@ -22,7 +22,7 @@ Use metrics for: * Capacity planning * Model/provider comparison -Use logs for: Debugging specific requests, viewing full prompts/responses. See xref:ai-gateway/observability-logs.adoc[]. +Use logs for: Debugging specific requests, viewing full prompts/responses. See xref:observability:logs.adoc[]. == Where to find metrics @@ -855,4 +855,4 @@ Solution: == Next steps -* xref:ai-gateway/observability-logs.adoc[] +* xref:observability:logs.adoc[] diff --git a/package.json b/package.json index 5103292..1ec8f0e 100644 --- a/package.json +++ b/package.json @@ -7,8 +7,7 @@ "build": "antora --to-dir docs --fetch local-antora-playbook.yml", "serve": "wds --node-resolve --open / --watch --root-dir docs --port 5002", "start": "cross-env-shell LIVERELOAD=true npx gulp", - "test-quickstart": "cd tests/setup-tests && npx doc-detective --input ../../modules/get-started/pages/quick-start.adoc -l debug", - "test-console-auth": "cd tests/setup-tests && npx doc-detective --input ../../modules/console/pages/config/security/authentication.adoc -l debug", + "test-quickstart": "cd tests/setup-tests && npx doc-detective --input ../../modules/get-started/pages/byoc-quickstart.adoc -l debug", "test-docs": "cd tests/setup-tests && npx doc-detective --input ../../modules -l debug" }, "dependencies": {