출처 검증 리서치: Kraken Account Verification API

Decision Matrix

Source Map

• Kraken Support: Updating account information (kraken-update-account-info)
• Kraken Support: Verification levels explained (kraken-verification-levels)
• Kraken Developers: Get API Key Info (kraken-api-key-info)

Control Notes

1. Verification level

Verification level is the decision point where public documentation must become an operating rule. In this package, it means account capabilities depend on verification rather than login alone. The practical action is to record the required level before planning funding or API use. The unresolved edge is private jurisdiction limits not listed in the public article, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Profile-change state

Profile-change state is the decision point where public documentation must become an operating rule. In this package, it means account information updates can alter review or support paths. The practical action is to separate identity-data changes from API troubleshooting. The unresolved edge is whether a private support request is already pending, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Permission scope

Permission scope is the decision point where public documentation must become an operating rule. In this package, it means API key permissions decide what the key can do. The practical action is to use least privilege and record only permission names. The unresolved edge is internal organization policy for shared keys, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Restriction fields

Restriction fields is the decision point where public documentation must become an operating rule. In this package, it means IP, nonce or validity restrictions can block otherwise correct calls. The practical action is to check restrictions before assuming endpoint failure. The unresolved edge is private network egress changes, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Last-used evidence

Last-used evidence is the decision point where public documentation must become an operating rule. In this package, it means last-used fields can support incident triage without exposing secrets. The practical action is to record timestamp and endpoint class, not signatures. The unresolved edge is whether the caller was an automated job or a human, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Account-vs-key boundary

Account-vs-key boundary is the decision point where public documentation must become an operating rule. In this package, it means a verified account can still have an unsafe or overbroad key. The practical action is to review account state and key state separately. The unresolved edge is legacy keys created before the current policy, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

7. Stop rule

Stop rule is the decision point where public documentation must become an operating rule. In this package, it means pause when verification, profile state or key permission cannot be explained. The practical action is to rotate or disable questionable keys before deeper automation. The unresolved edge is support-only remediation timing, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• private jurisdiction limits not listed in the public article
• whether a private support request is already pending
• internal organization policy for shared keys
• private network egress changes
• whether the caller was an automated job or a human
• legacy keys created before the current policy
• support-only remediation timing

Practical Takeaway

Kraken account readiness is not a single login state. Kraken support documentation separates account information updates from verification levels, while Kraken API documentation exposes API key permissions, restrictions, validity, nonce window and last-used fields through Get API Key Info. The decision outcome is to verify identity level, profile-change state, key permission scope, restriction fields and last-used timestamp before using an API key for funding, trading, Earn or reporting workflows. 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, callback, policy framework, settlement route or liquidity position will work under every future condition.