FlareKey Docs

Appearance

Integrations ​

Integrations gate a free, short-lived license key behind one or more Linkvertise / LootLabs / work.ink links, chained into a checkpoint sequence called a reward. Visitors complete the checkpoints to unlock the key. The ad revenue from those services goes to your own publisher account on that service, not FlareKey. This feature is split across two dashboard pages: Integrations (linking accounts) and Rewards (building the actual gate).

  • Integration: the connection details for one external account (Linkvertise Publisher ID, LootLabs API token, or a work.ink link). Create it once from Integrations and reuse it across rewards.
  • Reward: the shareable gate link, built from your linked integrations on the Rewards page. Name, key validity, and the checkpoint sequence all live here.
  • Checkpoint: one step in a reward, built from an integration. A reward chains any number of checkpoints, and the same integration can be added twice (e.g. two Linkvertise checkpoints back to back).
  • By default checkpoints run strictly in order. A visitor cannot skip ahead or replay a finished one. Turning on User Select Mode instead shows every checkpoint as an alternative and lets the visitor pick any ONE to unlock the key.
  • The key is only generated after the reward's checkpoint requirement is met.
  • Supported rewards can use B.Y.P.A.S.S. protection for an additional anti-bypass layer alongside FlareKey's normal provider-completion checks.
  • Reward settings: Expiry on first use (the key's countdown starts on its first real verify instead of at issuance), One-time use keys (blocks HWID resets once bound), HWID Limit (max devices per key), Salt (a random per-reward string with a generate button), Theme (a cosmetic accent color for the public checkpoint/reveal pages).
  • Streak System: turns the one-time reveal page into a standing keys page instead. Visitors can hold multiple keys (up to a limit you set), renew an expired key for free, and claim a time bonus on a cooldown.

B.Y.P.A.S.S. Protection ​

Supported FlareKey reward gates can use B.Y.P.A.S.S. protection to add an additional anti-bypass layer to the normal provider-completion checks. A protected reward only grants access after the required monetization step is genuinely completed.

  • Protected flows combine provider completion verification with VPN/proxy blocking, CAPTCHA enforcement, ad-block and private-mode checks where supported, minimum-completion-time checks, and additional automated and manual bypass detection.
  • Userscript activity, spoofed-completion attempts, suspiciously fast completion, and other supported bypass signals are checked before a protected reward is released.
  • Direct attempts to skip the protected completion flow are rejected. Attempting to redeem a reward without completing its required step is treated as a bypass attempt.
  • Confirmed bypass attempts result in a 24-hour block from every FlareKey ad/reward gate, not only the reward that was targeted. Multiple visitor signals are used so changing one browser or session value does not immediately remove the block.
  • Closing a gate, abandoning a reward, letting a link expire, or encountering a temporary service failure is not treated as a bypass attempt. Access is simply not granted until verification can complete.

Providers ​

ProviderWhat it is
LinkvertiseMonetized checkpoints with provider completion verification.
Work.inkWork.ink links used as reward checkpoints.
LootLabsContent Locker checkpoints with provider completion verification.
ShrinkearnShortened-link checkpoints.
Cuty.ioShortened-link checkpoints.
ShrtFlyShortened-link checkpoints.
SafelinkuShortened-link checkpoints with completion confirmation.
Exe.io / Clk.sh / Short-jambo / GPLinksShortened-link checkpoints with the same setup flow.
Ouo.ioShortened-link checkpoints.

Linkvertise ​

Linkvertise checkpoints send visitors through a monetized link before FlareKey verifies completion.

  1. Sign in at linkvertise.com and open your Creator dashboard.
  2. Go to the "FullScript API" section. Your Publisher ID is shown there, a numeric ID, e.g. 123456.
  3. In FlareKey, open Integrations, click + New Integration, choose Linkvertise, paste the Publisher ID, then Create.
  4. Optional, for stronger verification: in the Linkvertise dashboard go to Settings, enable "Anti-Bypassing", and copy the token shown into the connection's Anti-Bypass token field.
  5. Add the integration as a checkpoint on a reward from the Rewards page. Keep the Linkvertise Anti-Bypass token configured so completion can be verified before access is granted.
  • If completion cannot be confirmed, the checkpoint stays locked until the provider can verify it.

Work.ink ​

Create the Work.ink link in Work.ink's dashboard, then connect it to FlareKey as a reward checkpoint.

  1. In FlareKey, open Integrations, click + New Integration, choose Work.ink, give it a label only (leave the link field blank), then Create.
  2. Open the new connection's card and copy its Return URL. It looks like this: https://flarekey.xyz/api/lockers/workink-return/<connectionId>?token={TOKEN}
  3. In your work.ink dashboard, create a Key System / Custom Redirect link and set its redirect URL to the exact Return URL you copied, keeping {TOKEN} in place literally, since work.ink substitutes the real token into that placeholder itself.
  4. Copy the work.ink link work.ink gives you back (e.g. https://work.ink/abc/xyz), paste it into the "Your work.ink link" field on the connection's card, then Save link.
  5. Add the integration as a checkpoint on a reward from the Rewards page. Completion is verified before access is granted.
  • Work.ink completion is confirmed through a single-use return flow.

LootLabs ​

LootLabs checkpoints use a Content Locker flow before FlareKey verifies completion.

  1. Sign in at lootlabs.gg and open your panel.
  2. Go to API and generate/copy your API token.
  3. In FlareKey, open Integrations, click + New Integration, choose LootLabs, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. FlareKey verifies the selected Ad tasks (1-5) before issuing access - the more tasks, the more the visitor has to complete and the more you earn.
  5. Optional, for stronger verification: in the LootLabs panel go to Advanced and set your postback URL to https://flarekey.xyz/api/lockers/webhook/lootlabs/<connectionId&gt; (shown on the connection's card). LootLabs will notify FlareKey the moment a visitor completes it.
  • Completion is verified before access is granted, so changing return details does not skip the required tasks.
  • The Ad tasks (1-5) setting controls how many steps the visitor completes and, correspondingly, how much you earn per unlock.

Shrinkearn ​

Shrinkearn provides shortened-link checkpoints.

  1. Sign in at shrinkearn.com and go to Tools -> Developers API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose Shrinkearn, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. No further setup needed.
  • Shrinkearn is a link shortener, so each checkpoint is one shortened hop the visitor passes through before the key is unlocked.

Cuty.io ​

Cuty.io provides shortened-link checkpoints.

  1. Sign in at cuty.io and go to Tools -> Developer API.
  2. Copy your API token shown there, the "Legacy" Developer API. Cuty also offers a newer Full API / Quick API, not used here.
  3. In FlareKey, open Integrations, click + New Integration, choose Cuty.io, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. No further setup needed.
  • Use the Legacy Developer API token, not the newer Full/Quick API. The newer API options are not supported for this integration.
  • Each checkpoint is one cuty.io hop; chain more checkpoints for more revenue per unlock.

ShrtFly ​

ShrtFly provides shortened-link checkpoints.

  1. Sign in at shrtfly.com and go to your Developer API tools section.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose ShrtFly, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. No further setup needed.

Safelinku ​

Safelinku provides shortened-link checkpoints with completion confirmation.

  1. Sign in at safelinku.com and go to Tools -> Api -> Rest API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose Safelinku, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. No further setup needed.
  • Completion is confirmed on the return trip, so the key only issues after the visitor actually passes through the link.

Exe.io, Clk.sh, Short-jambo, and GPLinks use the same setup flow for shortened-link checkpoints.

  1. Sign in at the provider's site (exe.io, clk.sh, short-jambo.com, or gplinks.com) and go to Tools -> Developer(s) API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose the matching provider, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward. No further setup needed.
  • Pick the provider whose payout and audience fit your region; the checkpoint behavior is the same across all four.

Ouo.io ​

Ouo.io provides shortened-link checkpoints.

  1. Sign in at ouo.io and go to Tools -> Quick Link.
  2. Copy the key shown in the example URL there, the part right after /api/, before the ?. For example, in http://ouo.io/api/14dVpIgS?s=..., the key is 14dVpIgS.
  3. In FlareKey, open Integrations, click + New Integration, choose Ouo.io, paste that key, then Create.
  4. Add the integration as a checkpoint on a reward.

FlareKey documentation

2026 FlareKey