百度千帆 · 中国站
How an agent gets a 百度千帆 · 中国站 key through KeyKeeper, what to choose on console.bce.baidu.com, and how KeyKeeper verifies it.
| Template id | baidu-qianfan-cn (also Baidu Qianfan, Qianfan CN) |
|---|---|
| Field | qianfan-api-key → QIANFAN_API_KEY · secret |
| Also | qianfan-appid → QIANFAN_APPID · plain, confirmed by you, optional |
| Key looks like | whether it can be viewed again is unconfirmed |
| Created at | console.bce.baidu.com |
| Verified by KeyKeeper | not verified |
| Template checked | 2026-09-15 |
What the agent does
keykeeper providers show baidu-qianfan-cn
keykeeper save --provider baidu-qianfan-cn --from-clipboard --create --purpose "what this task does"
keykeeper run -c baidu-qianfan-cn -- <your command>--provider baidu-qianfan-cn fills in the credential id and the fields. The environment
variables are the ones 百度千帆's own tools read, so nothing has to be mapped.
What only you can do
登录百度智能云
在安全认证的 API Key 页面创建 key
仅添加实际调用的服务或 appid 权限
Copy the key, then approve the save in KeyKeeper's window.
What to choose
只添加实际使用的千帆服务范围;若将 key 限定到 appid,调用时必须同时传入该 appid。
The agent is told the same thing. It opens the page for you and says what to pick; it never logs in, passes 2FA or pays on your behalf.
What KeyKeeper checks
- Before writing: the value must look like a 百度千帆 · 中国站 key (whether it can be viewed again is unconfirmed). A wrong paste is refused before anything is stored, and the agent is told why — without the value.
- After saving: 百度千帆 · 中国站 offers no read-only endpoint KeyKeeper can use, so the first real call is the test.
Endpoints
The key is a bearer token for these endpoints. keykeeper run sets only the variables above;
point your client at the base URL yourself.
- OpenAI compatible —
https://qianfan.baidubce.com/v2
Rotation and expiry
千帆 V2 认证文档称控制台创建的普通 API Key 永久有效,直至用户撤销或更换。 Rotate or revoke at console.bce.baidu.com.