{"componentChunkName":"component---src-templates-acg-portal-new-template-tsx","path":"/Zmspw9ngv","result":{"data":{"markdownRemark":{"html":"<h2 id=\"场景一：企业-api-统一接入与治理\"><a href=\"#%E5%9C%BA%E6%99%AF%E4%B8%80%EF%BC%9A%E4%BC%81%E4%B8%9A-api-%E7%BB%9F%E4%B8%80%E6%8E%A5%E5%85%A5%E4%B8%8E%E6%B2%BB%E7%90%86\" aria-label=\"场景一：企业 api 统一接入与治理 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景一：企业 API 统一接入与治理</h2>\n<p><strong>业务痛点</strong>：企业内部服务与对外开放能力各自暴露入口，认证、限流、域名、审计等治理能力重复建设，缺乏统一的流量入口与管控平面。</p>\n<p><strong>解决方案</strong>：</p>\n<ol>\n<li>创建 API 网关专享版实例，作为企业南北向流量的统一入口，支持公网（EIP）与私网（VPC 服务网卡）双通道接入。</li>\n<li>通过 <strong>基础服务 + HTTP API</strong> 代理企业各后端服务（域名后端 / IP 后端），统一配置请求路径与方法。</li>\n<li>为不同调用方创建 <strong>消费者</strong>（API-KEY 或 AK/SK 凭证），按服务级别或 API 级别授权。</li>\n<li>通过 <strong>流量管控插件</strong> 设置限流策略，绑定 <strong>自定义域名</strong> 与 SSL 证书对外提供 HTTPS 服务。</li>\n<li>通过业务监控、日志分析实现统一审计与问题定位。</li>\n</ol>\n<h2 id=\"场景二：多模型统一接入\"><a href=\"#%E5%9C%BA%E6%99%AF%E4%BA%8C%EF%BC%9A%E5%A4%9A%E6%A8%A1%E5%9E%8B%E7%BB%9F%E4%B8%80%E6%8E%A5%E5%85%A5\" aria-label=\"场景二：多模型统一接入 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景二：多模型统一接入</h2>\n<p><strong>业务痛点</strong>：企业 AI 应用需要同时调用多家模型服务（如千帆平台模型、第三方模型 API、自建开源模型），各家接口格式、认证方式不同，业务代码耦合大量适配逻辑，切换模型成本高。</p>\n<p><strong>解决方案</strong>：</p>\n<ol>\n<li>为每个模型供应商创建 <strong>AI 模型后端</strong>，配置服务地址、模型协议（OpenAI 兼容 / Anthropic 兼容 / 原生协议）与 API-Key。</li>\n<li>创建 <strong>Model 服务</strong>，选择模型场景（文本生成、Embedding 等）与服务协议，网关自动生成标准的预置路由（如 <code>/v1/chat/completions</code>）。</li>\n<li>创建 <strong>Model API</strong>，选择多后端策略（按模型名称路由），将不同模型名称的请求分发到对应后端。</li>\n</ol>\n<p>业务方只需对接网关的统一 OpenAI 兼容接口，通过请求中的 <code>model</code> 字段即可访问任意已接入的模型服务。</p>\n<h2 id=\"场景三：新模型灰度发布\"><a href=\"#%E5%9C%BA%E6%99%AF%E4%B8%89%EF%BC%9A%E6%96%B0%E6%A8%A1%E5%9E%8B%E7%81%B0%E5%BA%A6%E5%8F%91%E5%B8%83\" aria-label=\"场景三：新模型灰度发布 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景三：新模型灰度发布</h2>\n<p><strong>业务痛点</strong>：需要将线上流量从旧模型平滑迁移到新模型，直接切换风险高，出现问题难以回滚。</p>\n<p><strong>解决方案</strong>：在 Model API 中使用 <strong>多后端（按比例）</strong> 策略，先将 5% 流量分配给新模型后端，结合业务监控（成功率、响应时间）与调用链分析验证效果，逐步调高比例直至全量。同时配置 <strong>Fallback</strong> 兜底后端，新模型异常时自动切换到稳定模型，保障业务连续性。</p>\n<h2 id=\"场景四：企业内部模型资源统一管控与成本分摊\"><a href=\"#%E5%9C%BA%E6%99%AF%E5%9B%9B%EF%BC%9A%E4%BC%81%E4%B8%9A%E5%86%85%E9%83%A8%E6%A8%A1%E5%9E%8B%E8%B5%84%E6%BA%90%E7%BB%9F%E4%B8%80%E7%AE%A1%E6%8E%A7%E4%B8%8E%E6%88%90%E6%9C%AC%E5%88%86%E6%91%8A\" aria-label=\"场景四：企业内部模型资源统一管控与成本分摊 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景四：企业内部模型资源统一管控与成本分摊</h2>\n<p><strong>业务痛点</strong>：企业内多个团队共用模型资源，API-Key 分散管理存在泄露风险，各团队用量不透明，成本无法分摊。</p>\n<p><strong>解决方案</strong>：</p>\n<ol>\n<li>模型 API-Key 统一托管在网关后端配置中，各团队不接触真实密钥。</li>\n<li>为每个团队创建 <strong>消费者</strong>，分发独立的 API-KEY 或 AK/SK 凭证。</li>\n<li>通过 <strong>授权管理</strong> 控制各团队可访问的服务与 API 范围。</li>\n<li>通过 <strong>配额管理</strong> 设置各团队的请求数与 Token 配额上限，按天自动重置，防止超用。</li>\n<li>为后端配置 <strong>Token 单价</strong>（区分输入、输出、命中缓存），在消费者 <strong>费用信息</strong> 中按时间段和后端维度查询各团队消费汇总，实现成本分摊。</li>\n</ol>\n<h2 id=\"场景五：agent-应用统一代理\"><a href=\"#%E5%9C%BA%E6%99%AF%E4%BA%94%EF%BC%9Aagent-%E5%BA%94%E7%94%A8%E7%BB%9F%E4%B8%80%E4%BB%A3%E7%90%86\" aria-label=\"场景五：agent 应用统一代理 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景五：Agent 应用统一代理</h2>\n<p><strong>业务痛点</strong>：企业构建的 Agent 应用形态多样（HTTP、WebSocket），接入方式缺乏统一标准，难以实现集中化治理。</p>\n<p><strong>解决方案</strong>：通过 <strong>Agent 服务 + Agent API</strong> 将 Agent 应用统一接入网关，支持 HTTP 与 WebSocket 协议代理，复用网关的消费者鉴权、授权、限流插件与全链路观测能力，实现 Agent 应用的统一入口与治理。</p>\n<h2 id=\"场景六：传统-api-与-ai-api-混合治理\"><a href=\"#%E5%9C%BA%E6%99%AF%E5%85%AD%EF%BC%9A%E4%BC%A0%E7%BB%9F-api-%E4%B8%8E-ai-api-%E6%B7%B7%E5%90%88%E6%B2%BB%E7%90%86\" aria-label=\"场景六：传统 api 与 ai api 混合治理 permalink\" class=\"anchor\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a>场景六：传统 API 与 AI API 混合治理</h2>\n<p><strong>业务痛点</strong>：企业同时存在传统 HTTP API 与 AI API，希望使用同一个网关统一管理。</p>\n<p><strong>解决方案</strong>：API 网关专享版的 <strong>基础服务（HTTP_SERVICE）</strong> 支持传统 HTTP API 代理，与 Model 服务、Agent 服务共存于同一实例，共享域名管理、消费者体系、插件体系与观测能力，避免多套网关并行维护。</p>","fields":{"slug":"Zmspw9ngv","title":"应用场景","date":"2026-08-28","extractedHeadings":[]},"headings":[{"value":"场景一：企业 API 统一接入与治理","depth":2},{"value":"场景二：多模型统一接入","depth":2},{"value":"场景三：新模型灰度发布","depth":2},{"value":"场景四：企业内部模型资源统一管控与成本分摊","depth":2},{"value":"场景五：Agent 应用统一代理","depth":2},{"value":"场景六：传统 API 与 AI API 混合治理","depth":2}]}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"Zmspw9ngv","prev":{"id":"dmspw9neq","name":"产品优势","path":"dmspw9neq","filePath":"API网关专享版/产品描述/产品优势.md","seo":null,"parentIds":["Omspw9n4x","emspw9n9t"],"parents":[{"id":"Omspw9n4x","documentId":"cbb7cda2-d4b2-4774-9c2f-c637554847d6","name":"API网关专享版","repoName":"APIGW","filePath":"API网关专享版","disabled":false,"path":"Omspw9n4x","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null},{"id":"emspw9n9t","documentId":"c0c14516-125c-422e-b7a5-c7776e460d08","name":"产品描述","repoName":"APIGW","filePath":"API网关专享版/产品描述","disabled":false,"path":"emspw9n9t","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null}]},"next":{"id":"xmspw9nad","name":"规格说明","path":"xmspw9nad","filePath":"API网关专享版/产品描述/规格说明.md","seo":null,"parentIds":["Omspw9n4x","emspw9n9t"],"parents":[{"id":"Omspw9n4x","documentId":"cbb7cda2-d4b2-4774-9c2f-c637554847d6","name":"API网关专享版","repoName":"APIGW","filePath":"API网关专享版","disabled":false,"path":"Omspw9n4x","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null},{"id":"emspw9n9t","documentId":"c0c14516-125c-422e-b7a5-c7776e460d08","name":"产品描述","repoName":"APIGW","filePath":"API网关专享版/产品描述","disabled":false,"path":"emspw9n9t","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null}]},"parents":[{"id":"Omspw9n4x","documentId":"cbb7cda2-d4b2-4774-9c2f-c637554847d6","name":"API网关专享版","repoName":"APIGW","filePath":"API网关专享版","disabled":false,"path":"Omspw9n4x","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null},{"id":"emspw9n9t","documentId":"c0c14516-125c-422e-b7a5-c7776e460d08","name":"产品描述","repoName":"APIGW","filePath":"API网关专享版/产品描述","disabled":false,"path":"emspw9n9t","lastMergeTime":null,"isApiDoc":null,"httpMethod":null,"seo":null,"sourceOrgName":null,"sourceRepoName":null,"sourceDocumentId":"","solutionTag":null,"solutionColor":null}],"specificSeo":null}}}