출처 검증 리서치: Crypto Private API Error

Decision Matrix

Source Map

• Bybit API Documentation: Error Codes (bybit-v5-error)
• Bybit API Documentation: Rate Limit Rules (bybit-v5-rate-limit)
• Coinbase Developer Documentation: List Accounts (coinbase-list-accounts)
• Coinbase Developer Documentation: Advanced Trade WebSockets (coinbase-ws-auth)
• OKX API Documentation: OKX API Guide (okx-api-docs)

Control Notes

1. Error taxonomy

Error taxonomy is the point where public documentation must become an operating rule. In this package, it means a code is useful only when mapped to documented meaning. The practical action is to record public source, exact code label and endpoint class. The unresolved edge is whether the same code has product-specific meanings, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

2. Retry class

Retry class is the point where public documentation must become an operating rule. In this package, it means rate-limit and permission failures require different recovery paths. The practical action is to separate backoff, credential review, permission review and hard stop cases. The unresolved edge is whether the original request already changed account state, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

3. Permission scope

Permission scope is the point where public documentation must become an operating rule. In this package, it means private endpoints can fail because the key, account or product scope is wrong. The practical action is to map key permission and account surface before retrying. The unresolved edge is whether support-side status changes the diagnosis, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

4. Non-secret evidence

Non-secret evidence is the point where public documentation must become an operating rule. In this package, it means incident records must not leak credentials or account balances. The practical action is to store endpoint name, non-secret code, timestamp, source URL and stop rule. The unresolved edge is whether a screenshot contains private account data, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

5. Radar output

Radar output is the point where public documentation must become an operating rule. In this package, it means the goal is disclosure completeness, not a universal safety score. The practical action is to mark missing source, ambiguous code and unsafe retry as separate blanks. The unresolved edge is whether future docs revise the label or behavior, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, safety guarantee, recovery promise, platform ranking or price implication.

The operating test is narrow.

Known Unknowns

• whether the same code has product-specific meanings
• whether the original request already changed account state
• whether support-side status changes the diagnosis
• whether a screenshot contains private account data
• whether future docs revise the label or behavior

Practical Takeaway

NexuAlpha Radar treats private API error codes as disclosure evidence only when the code can be mapped to a public source without exposing credentials. Bybit documents permission, expiry and rate-limit labels; Coinbase documents authenticated account and WebSocket surfaces; OKX API documentation exposes WebSocket login and subscription controls. The useful radar output is not a venue ranking. It is a checklist for whether an operator can record non-secret endpoint, source URL, error label, retry class, permission scope and stop condition before a private connector continues. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, API key, pool route, stablecoin balance, tokenized asset or policy framework will work under every future condition.