KocakZ brings your access key, loader, and account information together in one place. This guide explains what to expect when claiming a key for the first time.
Connect your Discord account
Start by selecting Get Key on the website or in our Discord server. Sign in with the Discord account you want to use for your access.
You must belong to the KocakZ Discord server before continuing. If you haven't joined yet, follow the invitation shown during the claim process, then return and try again.
Complete your checkpoint
Free access requires completing the verification and checkpoint steps shown on your claim page.
If the checkpoint takes you to a blog article, wait until the Continue button becomes available, then select it to return to your claim. You do not need to click advertisements to complete this step.
Premium access skips the article checkpoint.
Copy your key and loader
When your claim is complete, the page shows your key and loader snippet. Use the copy buttons to avoid missing characters when transferring them.
Keep your key private. Sharing it could let someone else use your available device or session slots.
Understand your access limits
Free keys last 24 hours and support one HWID with up to five active sessions. Premium keys last 30 days and support up to five HWIDs with 50 active sessions.
Your key is not bound to a device when you generate it. Device binding happens when you first use it through the loader.
If you already have a valid key, reuse it. Once a free key expires, you can complete the claim process again to receive a new one.
Need help?
If something fails, note the step you reached and the error message you received before asking for help in our Discord server.
Never post your full key in a public channel. A screenshot with the key hidden is enough to explain most problems.
Know which page answers which question
The homepage gives you a public starting point. A claim flow handles the account and verification steps needed to obtain access. A completed result provides the key and loader, while a blog article explains a topic or, when assigned to an active claim, hosts its checkpoint panel.
These pages can look connected because they belong to the same site, but they are not interchangeable. Opening a public article does not by itself create a claim. Reopening a completed flow does not make it unused again. Keep the purpose of the page in mind when choosing your next action.
If you become unsure where you are, identify the last successful stage. Did Discord return you to the site? Did verification finish? Did the final page display a key? Answering those questions is more useful than starting another flow whenever a screen looks unfamiliar.
Prepare a first attempt without collecting duplicate copies
Use the Discord account you intend to keep associated with your access. Confirm the account shown during browser authorization, especially if you also use a different account in the desktop app. The browser identity is the one the website receives from the sign-in process.
Keep one current claim available while completing its prompts. Several nearly identical tabs can make it difficult to tell which attempt is active or which account owns it. If an old flow has expired, begin a fresh claim deliberately rather than cycling through saved links.
When the result appears, copy the requested value using the available control and paste it into the intended destination. The key and loader are related outputs, but a key field does not expect an entire script. Read the label before copying so you know which item is currently on the clipboard.
Understand the first loader run
The website issues a credential; accepted loader use supplies the device identifier and starts a session. This is why opening the claim page on a phone does not itself bind the phone as the device used by the script.
Use the loader and instructions supplied by the current result. Do not combine fragments from old snippets or edit a key to make it resemble another value. If copying is uncertain, replace the whole value from the source instead of trying to reconstruct missing characters manually.
On the first attempt, observe the exact result before making changes. A syntax message, expired-key rejection, and session-limit message point to different questions. Keep the non-secret wording so you can choose the relevant help rather than repeat the entire claim process.
Distinguish the account from the device and session
The Discord account owns the stored access. An HWID represents a device identifier accepted during loader use. A session represents an active run. One account can therefore have a valid key while encountering a device or session capacity limit.
For a hypothetical example, several runs on one accepted device consume session capacity without necessarily adding new device bindings. Trying a different device can reach the HWID allowance even when session slots remain. Treat the two limits separately when describing the issue.
The fuller explanation is in keys, device limits, and sessions. Read it if the numbers in the access comparison seem to contradict what you are seeing. The distinction often explains why requesting the same valid key again does not change the available capacity.
Return to existing access before starting over
If you already have a valid stored key, retrieve it using the same owning account. Requesting it again does not extend its lifetime. Check the current expiry instead of relying on an old screenshot or a copy saved from an earlier period.
When a free key expires, use a new claim for renewed free access. An old completed claim is a record of a finished attempt, not a reusable way to reset the period. Premium expiry follows the account's paid entitlement rather than the time you happen to retrieve the key.
If the site shows a different account or unexpected status, resolve that identity question first. Creating more claims under the wrong account can make the history more confusing without restoring the access you expected to see.
Keep your first support report small and useful
Write the action you attempted, the last stage that worked, and the exact non-secret error. Include the approximate time and whether one controlled retry produced the same result. These details let support begin with a specific failure instead of reconstructing your entire session.
Remove credentials from screenshots and code before sharing. The same key may appear in both a visible field and the loader snippet, so inspect the whole outgoing image. You can explain where the error occurred without giving another person the credential needed to use your access.
Ready to try your first claim? Keep the Discord account you intend to use available, then open the KocakZ homepage. Work through the prompts in one browser session so you can follow your progress from sign-in to the completed result.
For a walkthrough of the individual stages, follow how to claim your first KocakZ key. If a screen behaves differently from what you expect, record its message and the stage you reached before trying again.