Prove AccessVerdict 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.

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.

Create one Test API key

Copy the full av_test_... value when it is shown. AccessVerdict 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

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.

Optional: test a real onchain rule

Try Base or Ethereum ERC-20, ERC-721 or ERC-1155 after the allowlist flow works. AccessVerdict validates configured contracts before trusting decoded token balances.

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 AccessVerdict replaced: __
Rule/chain/integration needed next: __
Would you keep AccessVerdict instead of maintaining this yourself? yes / maybe / no