Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
Python agent-contextagent-memoryagent-pluginsagentic-ragcontext-databasedsh-pluginknowledge-basememorymemory-managementself-evolvingvector-database
docs: update agent authentication wording (#3035)
ManAsWind23835289ecc3
diff --git a/docs/images/agents/en/hermes.md b/docs/images/agents/en/hermes.mdindex 7db632368..0d78d7ed4 100644--- a/docs/images/agents/en/hermes.md+++ b/docs/images/agents/en/hermes.md@@ -6,15 +6,15 @@hermes memory setup```-## Step 2: Copy the Base URL and API Key+## Step 2: Copy the Base URL and Authentication management-After running the setup command, Hermes prompts for the Base URL and API Key. Copy them and paste them into Hermes:+After running the setup command, Hermes prompts for the Base URL and Authentication management. Copy them and paste them into Hermes:- Base URL: Copy the following Base URL into Hermes:```texthttps://api.vikingdb.cn-beijing.volces.com/openviking```-- API Key: Copy the API Key shown on the page into your Hermes terminal+- Authentication management: Copy the Authentication management shown on the page into your Hermes terminal- Tenant account / user / agent ID: Used for multi-tenant deploymentsThe configuration is saved to Hermes `config.yaml` and `.env` files.diff --git a/docs/images/agents/en/trae.md b/docs/images/agents/en/trae.mdindex ff253c00c..283a88170 100644--- a/docs/images/agents/en/trae.md+++ b/docs/images/agents/en/trae.md@@ -90,7 +90,7 @@ ov health| `mcpServers` | Yes | Root node for MCP Server configuration || `ov-mcp-server` | Yes | Service alias. It can be customized, but keeping this name is recommended for contextual recognition || `url` | Yes | OpenViking MCP endpoint. For CN, use `https://api.vikingdb.cn-beijing.volces.com/openviking/mcp` |-| `headers.Authorization` | Yes | Format: `Bearer <API Key>`. Source: see chapter 2 |+| `headers.Authorization` | Yes | Format: `Bearer API Key`. Source: see chapter 2 |---diff --git a/docs/images/agents/zh/hermes.md b/docs/images/agents/zh/hermes.mdindex dd186c2e5..c1ec619b0 100644--- a/docs/images/agents/zh/hermes.md+++ b/docs/images/agents/zh/hermes.md@@ -7,14 +7,14 @@hermes memory setup```-## 步骤 2:复制 Base URL 和 API Key-执行 setup 命令后会依次提示输入 Base URL 和 API Key,可复制后粘贴到你的 Hermes:+## 步骤 2:复制 Base URL 和 鉴权管理+执行 setup 命令后会依次提示输入 Base URL 和 鉴权管理,可复制后粘贴到你的 Hermes:- Base URL: 复制以下 Base URL 到你的 Hermes:```texthttps://api.vikingdb.cn-beijing.volces.com/openviking```-- API Key: 复制页面中展示的 API Key 到你的 Hermes 终端+- 鉴权管理: 复制页面中展示的 鉴权管理 到你的 Hermes 终端- 租户 account / user / agent ID:多租户部署时使用配置保存在 Hermes 的 `config.yaml` 和 `.env` 文件中。diff --git a/docs/images/agents/zh/trae.md b/docs/images/agents/zh/trae.mdindex b380b59c8..fc62fb111 100644--- a/docs/images/agents/zh/trae.md+++ b/docs/images/agents/zh/trae.md@@ -92,7 +92,7 @@ ov health|`mcpServers`|是|MCP Server 配置根节点||`ov\-mcp\-server`|是|服务别名,可自定义;建议保持与上下文识别一致||`url`|是|OpenViking MCP 服务端点;CN 区固定为 `https://api\.vikingdb\.cn\-beijing\.volces\.com/openviking/mcp`|-|`headers\.Authorization`|是|格式 `Bearer \<API Key\>`,来源见第二章|+|`headers\.Authorization`|是|格式 `Bearer API Key`,来源见第二章|---