交易所 API Key 权限范围披露雷达
已验证事实边界
1. Binance documentation includes fields that expose API key permissions and IP restriction state. 2. Coinbase developer documentation says Advanced Trade portfolios can use dedicated CDP API keys scoped to a specific portfolio. 3. Coinbase Help describes portfolio, permission, passphrase and IP address whitelist fields in API key creation. 4. Kraken Support publishes an API key creation help surface for account API access. 5. An API key inventory is not complete if it records only key name and exchange without permission, portfolio and network restriction fields. 6. Public exchange documentation cannot prove private key storage, bot-vendor custody, breach response, region-specific restrictions or future permission changes.
收起完整分析
决策矩阵
文章表格：可横向滑动，或聚焦表格区域后使用方向键。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Permission fields | read, trade, transfer and withdrawal permissions have different failure and loss modes | record each permission as a separate inventory column | venue-specific naming, hidden dependency permissions and future permission schema changes |
| Portfolio boundary | portfolio-scoped keys can reduce blast radius when the venue supports them | link every key to the exact portfolio, account, subaccount or organization boundary | legacy key compatibility, OAuth access differences and private account structure |
| Network restriction | IP whitelisting or restriction is a control only when the runtime host is stable | record IPs, host owner, NAT path and change procedure | dynamic IP churn, cloud failover and emergency access exceptions |
| Secret handling | one-time display and passphrase rules make recovery different from ordinary passwords | store secrets outside chat and record only non-secret evidence | vendor logging, browser extension leakage and local machine compromise |
| Rotation trigger | keys need a revocation and replacement rule before an incident happens | define rotation after role change, vendor change, host migration or suspected exposure | exchange support delays, stale bot configs and untracked copies |
来源地图
- Binance Developer Docs：Get API Key Permission（binance-api-restrictions）
- Coinbase Developer Documentation：Advanced Trade Portfolios（coinbase-advanced-portfolios）
- Coinbase Help：How to create an API key（coinbase-api-key-help）
- Kraken Support：How to create an API key（kraken-create-api-key）
控制说明
1. Permission fields
这一项要求读者把公开来源翻译成操作规则。这里的含义是：read, trade, transfer and withdrawal permissions have different failure and loss modes。可执行动作是：record each permission as a separate inventory column。仍然未知的是：venue-specific naming, hidden dependency permissions and future permission schema changes。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、安全保证、恢复保证、平台排名或价格暗示。
2. Portfolio boundary
这里的含义是：portfolio-scoped keys can reduce blast radius when the venue supports them。可执行动作是：link every key to the exact portfolio, account, subaccount or organization boundary。仍然未知的是：legacy key compatibility, OAuth access differences and private account structure。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
3. Network restriction
这里的含义是：IP whitelisting or restriction is a control only when the runtime host is stable。可执行动作是：record IPs, host owner, NAT path and change procedure。仍然未知的是：dynamic IP churn, cloud failover and emergency access exceptions。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
4. Secret handling
这里的含义是：one-time display and passphrase rules make recovery different from ordinary passwords。可执行动作是：store secrets outside chat and record only non-secret evidence。仍然未知的是：vendor logging, browser extension leakage and local machine compromise。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
5. Rotation trigger
这里的含义是：keys need a revocation and replacement rule before an incident happens。可执行动作是：define rotation after role change, vendor change, host migration or suspected exposure。仍然未知的是：exchange support delays, stale bot configs and untracked copies。
操作测试也必须很窄。这就是本文坚持以清单形式呈现的原因。
仍需明确的未知项
- venue-specific naming, hidden dependency permissions and future permission schema changes
- legacy key compatibility, OAuth access differences and private account structure
- dynamic IP churn, cloud failover and emergency access exceptions
- vendor logging, browser extension leakage and local machine compromise
- exchange support delays, stale bot configs and untracked copies
实用结论
NexuAlpha radar signal 是：交易所 API-key 安全取决于可见 permission scope、portfolio/account boundary、IP controls 与 secret-handling rules。Binance 发布了 permission readback endpoint；Coinbase 文档说明 portfolio-scoped API keys 与 permission categories；Kraken 文档把 API key creation 作为带权限的账户表面。实用结论是：连接任何自动化前，先建立包含 read、trade、transfer、withdrawal、portfolio、IP 与 rotation 字段的 key inventory。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、API key、池子路径、稳定币余额、代币化资产或政策框架在任何未来条件下都能成功的承诺。
相关专题与工具:交易所 API 与行情数据核查
来源与证据
04- Get API Key Permission · developers.binance.com
- Advanced Trade Portfolios
- How to create an API key
- How to create an API key · support.kraken.com