Prove GateKit in one real integration.

Beta success target

Reach the first Wallet Allowlist verification in under 3 minutes without direct support, then complete one real backend integration. GateKit is testing developer time-to-value before adding more product surface.

Create one project

Sign in, create a workspace and one project, then open the project Console.

Start with Wallet Allowlist

Create one enabled Wallet Allowlist policy with a wallet you control or a public test address. Give it a simple entitlement such as member.

Do not create duplicate policies just to test another wallet. Reuse the same policy so an allowlisted wallet can pass and another wallet can fail.

Create one Test API key

Copy the full gk_test_... value when it is shown. GateKit stores only its hash and cannot display the full secret again.

Never send the key in feedback, screenshots, chat messages, or browser client code.

Prove both policy outcomes

In Playground, run the allowlisted wallet and confirm allowed. Then use a wallet not present in the same allowlist and confirm denied.

Move the same policy into real server code

The Playground proves policy behavior; a real backend integration proves product value. Use the Next.js/server SDK path or the package-independent REST path for generic Node.js applications.

Optional: test a real onchain rule

Try Base or Ethereum ERC-20, ERC-721, or ERC-1155 after the allowlist flow works. ERC-20 minimum values use raw smallest units returned by balanceOf; ERC-721/1155 minimums are integer token balances.

GateKit validates that a configured token/NFT address has runtime contract bytecode before trusting the decoded balance response. Infrastructure or contract-read failures return an error decision rather than an accidental allow.

Send integration evidence and friction

□ Account confirmed and Console opens
□ Workspace + project created
□ Wallet allowlist policy created
□ Test API key created and stored safely
□ One allowed verification completed
□ One denied verification completed
□ Result appears in Recent verifications
□ One real server/backend integration completed
□ Optional: one Base/Ethereum token rule tested

Framework/backend: __
Access rule/use case: __
Time to first verification: __ minutes
Needed direct help? yes / no
Most confusing step: __
Real server integration completed? yes / no
Denied vs error semantics clear? yes / no
Code/infrastructure GateKit replaced: __
Rule/chain/integration needed next: __
Would you keep GateKit instead of maintaining this yourself? yes / maybe / no

The key metrics are time to first verification, support required, real server integration, repeat usage, and whether GateKit replaces code the developer would otherwise maintain themselves.