This is a static, simulated illustration. There are no real proofs, no real gate and no real wallet, and nothing can be edited or tested. The explainer page is linked from the top.
Access policy is an illustration of a site owner's access policy, drawn as a flow, that rewards visitors for declaring whether they are a person or a bot and rate-limits or blocks those that stay silent. A visitor that declares what it is gets more than one that stays silent, with access shaped to what it is. Each access point has exactly one requirement: free, payment or work. The illustration is static and simulated, with no real proofs, gate or wallet.
Bots and automation are increasingly treated as hostile, so an agent that declares what it is looks the same as one that doesn't, and site-holders end up blocking real visits or giving up discovery by services such as Google and ChatGPT.
Site-holders, and the people and agents who visit their sites, have this problem. Today a site can mostly allow traffic, block it, or challenge it. Bot-ness is inferred from behavior, not declared, and where bots are blocked, declaring is disincentivized. For site-holders, the drawbacks of allowing any bots, crawlers or other automation, such as declining real user visits, have begun to outweigh the benefits, such as discovery by services like Google or ChatGPT.
It matters because without a reason to declare, sites cannot tell who is visiting, and everyone, including honest agents, gets treated the same way. Even more, without a means to have granular user-friendly controls, site-holders are left with blunt, overly technical means to control traffic.
Incentivized declaration. A visitor that declares what it is, a person or a bot, gets more than one that stays silent. An undisclosed visitor is heavily rate-limited or blocked, which is cheap for the site to do, and a disclosed one gets access shaped to what it is. The owner sets this up as a simple flow, like a workflow builder, and the rules are enforced at the edge.
Each access point has exactly one requirement, free, payment or work, so each item can be configured, changed and counted on its own. People and bots are treated the same way. The wallet supplies the proof of personhood, humanity or liveness, so the visitor doesn't repeat it site by site.
Sites that reward declaring what a visitor is, with one clear requirement per access point, give people and agents a reason to declare.
If that holds, bot-ness no longer has to be inferred from behavior. Sites can shape access to what each visitor is, and honest agents are no longer treated like hostile ones.