World (@worldnetwork): A Private, Sybil Resistant, Free Agentic Web

A Private, Sybil Resistant, Free Agentic Web With World ID, verify that an agent is backed by a real human. As agents become ubiquitous, websites need a way to distinguish one person running a thousand agents from a thousand different people each running one. Solutions today include pay-per-request, which uses economic cost to disincentivize spam, but come with the tradeoffs of price discovery and privacy. World ID solves this, allowing users to prove an agent is tied to a unique human without exposing any personal information or activity. Use cases today include: Your agent books tickets for an upcoming concert Blocking humans who use agents to misbehave on platforms, such as a human spinning up multiple agents to promote memecoins on Moltbook Provisioning phone numbers or browser usage, but limiting to per human rather than per agent To make it easy for developers, we're introducing AgentKit. Launching in beta, AgentKit extends the x402 protocol created by @coinbase and @Cloudflare . This means your x402 endpoints can be private and free while still being protected from spam. See the documentation at: https://docs.world.org/agents/agent-kit. Registration An agent can register itself on-chain in the AgentBook by calling the register function, providing a valid World ID proof with its address and a nonce in its signal. The external nullifier for the World ID proof is used as an "anonymous human identifier." To look up this "human identifier" from an agent's address, you can call the lookupHuman function, checking whether it returns 0x0 (meaning the address has not been registered in the AgentBook). x402 SDK Extension Websites that want to open up traffic to agents can install the x402 extension @worldcoin/x402-agentkit and configure access modes per route. When an agent sends a request, the server responds with 402 Payment Required, including the AgentKit extension with a CAIP-122 challenge (nonce, domain, supported chains, mode). The agent will sign the challenge with their wallet and send it via the agentkit HTTP header. The server then validates the signature and looks to see there is a wallet address corresponding to a human identifier in the AgentBook. If the agent is registered under a human, access is granted or a discount is applied. Otherwise, the server will fall back to the standard payment flow. Future Work The identity functionality in the AgentKit extension is similar to the one in the existing SIWX (Sign-In-With-X) extension. As the x402 standard evolves and more extensions emerge that have a use for stateful agent sessions, it might make sense to make SIWX a core part of the protocol. Additionally, AgentKit will look to expand in the future to support other open protocol use cases such as human in the loop payment verifications.