Pick a gate condition. Connect your wallet. The hidden message either appears, or it doesn't. Same engine that powers the WordPress plugin, running right here in your browser.
The site never sees your wallet's raw balances or holdings — InsumerAPI returns a signed yes-or-no on whether the condition is met, and nothing more.
Demo presets only. On your site, you set your own conditions — any contract, chain, threshold, EAS template, or Farcaster check, with up to 10 stacked rules (Pro).
Connect a wallet that meets the condition above to see it.
Most token-gating plugins hide content with CSS — the gated text is in the page source, just invisible. Anyone can View Source and read it. SkyeGate doesn't.
To verify on this page (do this before clicking Connect Wallet):
Cmd+Opt+I on Mac, F12 on Windows)./api/verify return a signed result. If you pass, a second request to /api/skyegate-demo-content fetches the unlock message. The text only enters the page after that response.So yes — once you've unlocked it, "Inspect Element" will show the message in the live DOM (it's been added by JavaScript). But it was never in the HTML the server first sent you, never in the JavaScript file, and never came down the wire until a JWT signed by InsumerAPI proved your wallet qualified. That's the difference: most token-gating plugins put gated content in the page source and hide it with CSS. SkyeGate doesn't.
You just saw a single condition unlock content. Now imagine combining ten of them.
Stack up to 10 conditions in a single gate, mixing all four verification types. The combinations are practically endless:
All 4 condition types (Token, NFT, EAS, Farcaster) · 32 chains · Multi-wallet · Unlimited verifications · Cryptographically signed · Server-side delivery
Just want to try it? Start free with a single-condition gate.
Install SkyeGate Lite — Free on WordPress.org1 condition per gate · 31 chains · 3 condition types (Token, NFT, EAS) · Unlimited verifications