docs: Agent Gateway, API key usage dashboard, agents, and LLM Serving - #20
Closed
tmvfb wants to merge 1 commit into
Closed
docs: Agent Gateway, API key usage dashboard, agents, and LLM Serving#20tmvfb wants to merge 1 commit into
tmvfb wants to merge 1 commit into
Conversation
…M Serving - Flesh out Agent Gateway overview: path families (/ai, /serving, /mcp, /a2a, /sandbox), public vs. internal traffic, and admin-only External Model Providers (AI Gateway) workflow. - Add a Usage Dashboard section to API Keys covering the per-workspace Usage tab (time windows, cohorts, token/cost estimates, usage-by-key table). - Flesh out Agents: the Secret -> Model Configuration -> Agent -> MCP tools -> chat-test workflow, and tool-calling caveats for internal models. - Add a new LLM Serving page (deploy, advanced configuration, tool-call parsers, testing, editing, external access via Agent Gateway). - Correct /ai and /serving path-family ownership against the actual route builders in pkui.
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/agentops/agent_gateway.md): fleshed out from a stub — path families (/ai,/serving,/mcp,/a2a,/sandbox), public vs. internal traffic, and a new admin-only External Model Providers section disambiguating the two sidebar entries both labeled AI Gateway (API Keys under Serving vs. provider management under Admin).docs/platform/api_keys.md): new Usage Dashboard section documenting the per-workspace Usage tab (time windows, request-attribution cohorts, token/cost estimates, usage-by-key table, caveats).docs/agentops/agents.md): fleshed out from a stub — the typical workflow (Secret → Model Configuration → Agent → MCP tools → chat test), the fixed OpenAI/Anthropic/Gemini vs. internal provider list, and the tool-calling caveat for internal models.docs/agentops/llm_serving.md, new page): deploying self-hosted models, Advanced Configuration (deployment mode, quantization, autoscaling), the tool-call parser table for agent tool calling, testing/editing, and external access via Agent Gateway. Wired into the sidebar nav and cross-linked from Agents, Agent Gateway, and Model Serving./aivs/servingpath-family ownership in Agent Gateway docs against the actual pkui route builders (both are shared families, not one-to-one with a single feature).All facts were verified directly against
~/pkuifrontend/backend source (route builders, module registrations, exact UI copy) and closed product-decision issues (prokube/pkui#2115, #2266) for the LLM Serving / AgentOps placement question, rather than assumed.Two screenshot slots in API Keys use the existing text-placeholder convention (no image yet):
api-key-usage-tab.png,api-key-usage-by-key-table.png.Verification
npm run build— passes cleanly, including cross-page anchor links (verified against rendered HTML output).