--- title: "About Agent Community" description: "About Agent Community — the open community of the companies, researchers, and developers building the agentic web, and why the work is organized as a community." lastUpdated: "2026-07" --- The open community of the people building the agentic web. We are the companies, labs, and independent builders who develop, research, deploy, or operate agents. We convene builders, run open work streams, map who is building what, and publish open specifications anyone can implement. We are also the applicant for the proposed .agent top-level domain, which is pending ICANN approval. - **Why** — The agentic web is being built right now, and its defaults are being set by whoever shows up. We would rather that were a community than a single company. - **What** — A place for the people building agents to find each other, agree on how things should work, and publish the results in the open for anyone to use. - **How** — Events and work streams anyone can join, a public map of member organizations, open specifications, and governance written down rather than assumed. ## The agentic web The agentic web is already here. Now we keep it open. We are moving from human clicks to a mesh of human-agent and agent-agent interactions. Agents will weigh options, make decisions, and coordinate across systems — calendars, services, robots, and autonomous teams operating with agents, many without a human in the loop at every step. That only works when the infrastructure they rely on is open, trustworthy, and community-governed. Agent-to-agent conversations are becoming the nervous system of the web. Open standards and community governance stop any single platform from dictating the terms. ### Agents everywhere Calendars, services, robots, and autonomous teams will all operate with agents. Many will act without humans in the loop, so we need shared rules and discoverability. ### Open coordination Agent-to-agent conversations become the nervous system of the web. Open standards and community governance stop any single platform from dictating the terms. ### Trust at scale For billions of agents to interact safely, they must carry recognizable names, reputations, and policies wherever they go. If approved, .agent would be the naming layer that enables it. ## Why community Why do this as a community. Shared infrastructure works when nobody owns it outright. That is the lesson of every layer of the internet that lasted: the people who depend on it have a say in how it runs, and the rules are written down where anyone can read them. Any single owner is fine right up until its incentives change, and then there is no mechanism left to appeal to. So this is built as a community. Membership is free and open to anyone who builds. Work streams are public and their archives stay readable. Members are listed on a map if they want to be, and the people running it are named. The longer version of this argument is in [what Agent Community is](/blog/what-agent-community-is). IDs connect machines. Names create relationships and accountability. The agentic web repeats the same pattern we have seen on every platform shift: handles make identity usable and durable. Just as IP addresses connected machines while DNS gave humans a usable naming layer, agents need human-meaningful handles so reputation, policy, and ownership can travel with them. Names persist through infrastructure migrations so agents remain recognizable and auditable even as hosts change. That is also why we are applying to ICANN for .agent as a community rather than as a business. The application, where it stands, and what happens if it is not approved are all on the [.agent page](/agent). ## Names in practice What a name like this makes possible. Picture an internet where agents carry clear, recognizable names that work in email, APIs, logs, and contracts — names that tell you who built them and who is accountable. This would only be possible if the naming layer is open. ### Personal roots lastname.agent with role-based handles that families and professionals actually use day to day. ### Company surfaces company.agent with support, status, and partnership touchpoints customers remember and trust. ### Community and cohort hubs Shared namespaces for alumni, accelerators, clubs, and civic networks that outlast the demo day. ### Project and campaign agents Launch, iterate, and retire agents with names that travel across providers and frameworks. ### Cloud and robotic fleets Coordinated agents managing warehouses, mobility, and robotics with clear, inspectable identities. ### Distributed surnames High-demand roots that distribute trustworthy sub-names so reputation scales instead of fragments. ## Team The people behind it. Engineers, researchers, and operators from across the agentic web, plus advisers who have been building the internet's naming layer since before there was much of one. Community governance is only credible if the community is real and named. Meet the team: [/team](/team). ## The network A planet of agents, already at work. Member organizations across many countries are building the agentic web, and growing. Explore the current organization count and country coverage on the [map](/map?view=globe). ## If you develop, research, deploy, or operate agents, this is your community Membership is free, and it stays open to anyone who builds, wherever they are. [Join us](/join) · [Read the charter](/docs/governance) *Last updated: July 2026*