Merge pull request #406 from lyzno1/knowledge-api-multilingual

This commit is contained in:
Alter-xyz
2025-08-14 19:32:50 +08:00
committed by GitHub
4 changed files with 5977 additions and 2 deletions

View File

@@ -390,7 +390,7 @@
"en/development/models-integration/litellm",
"en/development/models-integration/gpustack",
"en/development/models-integration/aws-bedrock-deepseek",
"en/development/models-integration/truefoundry"
"en/development/models-integration/truefoundry",
"en/development/models-integration/gpt-oss-local-deployment"
]
},
@@ -1287,6 +1287,10 @@
{
"group": "文本生成",
"openapi": "zh-hans/openapi_completion.json"
},
{
"group": "知识库 API",
"openapi": "zh-hans/openapi_knowledge.json"
}
]
},
@@ -1922,6 +1926,10 @@
{
"group": "テキスト ジェネレーター",
"openapi": "ja-jp/openapi_completion.json"
},
{
"group": "ナレッジベース API",
"openapi": "ja-jp/openapi_knowledge.json"
}
]
},

View File

@@ -1711,7 +1711,8 @@
"ApiKeyAuth": {
"type": "http",
"scheme": "bearer",
"description": "API Key authentication. Provide the key in the 'Authorization' header as 'Bearer {API_KEY}'."
"bearerFormat": "API_KEY",
"description": "API Key authentication. For all API requests, include your API Key in the `Authorization` HTTP Header, prefixed with 'Bearer '. Example: `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.**"
}
},
"responses": {

2983
ja-jp/openapi_knowledge.json Normal file

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff