Docs/One-pager

One-pager

Plain public background on Agent Community, the accountability purpose behind the work, and the proposed .agent namespace it is applying for.


Draft date: July 1, 2026

Purpose: plain public one-pager for counsel, advisors, and ecosystem introductions. This is not fundraising copy.

What Agent Community Is

Agent Community is an organized community for the people and organizations building the agentic web: builders, companies, individuals, communities, researchers, and supporters of accountable agents. AI agents can also participate over time, but the core community is the accountable humans and organizations behind them.

The purpose is to make agents more accountable. As agents act on behalf of people, companies, and institutions, users need a simple way to ask: can I trust this agent, and is there an accountable operator behind it? The community convenes builders, runs open workstreams, maintains a public map of member organizations, and publishes open specifications for agent identity and discovery, all of which work on ordinary domains today.

Agent Community is also preparing an application to ICANN for .agent, the proposed top-level domain for the agentic web, so that .agent, if approved, can be governed as a community namespace rather than becoming a generic domain land grab. That is one part of the work rather than the whole of it.

Why .agent

Domain names are the native trust anchor of the web. A .agent name can become a visible, portable signal that an agent is tied to a verified entity and governed by published eligibility rules.

The goal is not to claim that a domain name makes an agent safe by itself. The goal is to create a namespace where public-facing agents can be connected to accountable legal entities, verified operators, and community-governed policy within ICANN requirements.

ICANN's 2026 new gTLD round includes a community-priority path. Agent Community is preparing for that path, with the application deadline on August 12, 2026.

What "Verified Agent" Means

A verified agent starts with the entity behind it.

Models, prompts, tools, hosting environments, and context can change. The durable question is whether there is an accountable person or organization operating the agent, and whether that operator can be checked.

The proposed verification model has three layers:

LayerMeaning
Verified entityThe legal person, organization, or institution responsible for the agent.
Verified namespaceThe domain and endpoint through which the agent presents itself.
Verified operating statusA public signal that the agent/operator is in good standing under the community's eligibility and accountability rules, subject to ICANN-approved allocation policies.

Over time, additional assurance mechanisms may be layered on top, including stronger technical checks, sector-specific requirements, independent audits, or insurance-backed guarantees. The first requirement is identity and accountability.

Governance

.agent should be governed, not owned by a single commercial actor. Governed means the people who build on it direct it, through binding registration policies, public records, and the standing ability to hold any operator to the charter.

The specific governance structure is still being designed. We will publish it when it is settled rather than describe a model that could still change.

Current Workstreams

Five public workstreams are forming. Each runs as an open mailing list with a public archive at agentcommunity.org/lists, where the threads and member counts are visible without joining.

WorkstreamFocus
IdentityWho or what is behind an agent, and how that link is expressed.
SecurityAbuse prevention, operational safety, and accountable infrastructure.
EvaluationsHow agents can be assessed, tested, and compared over time.
TrustVerification, reputation, assurance, and good-standing signals.
GovernanceCommunity rules, eligibility, appeals, and policy stewardship within ICANN requirements.

Current Community

As of the June 2026 public data brief, Agent Community had:

MetricCount
Registered members29,514
Organizations8,231
Individuals21,260
Agent accounts23
Countries represented122
Domain-interest records98,501

Agent Community has also collected 16,000+ signed endorsements for .agent — more than half the membership, individuals and organizations together.

The public member map is available at agentcommunity.org/map.

Advisors

Agent Community's advisor group includes:

  • Esther Dyson - long-time techy, founding chair of ICANN (1998-2000), and author of the forthcoming book Term Limits: Human time and AI scale (MIT Press).
  • Tim O'Reilly - founder, O'Reilly Media.
  • Illia Polosukhin - co-author, "Attention Is All You Need"; co-founder, NEAR Protocol.
  • Zsolt Nemeth - founder and CEO, R6 Security.
  • Ken Hansen - domain industry leader; led .biz, former GM of .nyc, and co-founder, co.com Registry.

The public team page is available at agentcommunity.org/team.

Shipped Work

Agent Community is not only a domain application effort. Current public work includes:

  • the public Agent Community site, profiles, map, and member directory;
  • events and public gatherings for the agent ecosystem, listed at agentcommunity.org/events;
  • AID, an open agent identity/discovery specification live at aid.agentcommunity.org;
  • Agent Brief, a news and context surface for the agent ecosystem;
  • DMV, the Department of Machine Verification, an experimental verification/onboarding surface;
  • public writing around trusted agents and accountable operators.

These projects support the same thesis: agents need names, identity, and accountability that can work across the open web.

Current Status

Agent Community is preparing the .agent ICANN application and the governance materials required to support it.

The application, the governance structure, and the exact .agent policies remain subject to counsel, ICANN rules, and the application process. Nothing in this document should be read as implying that .agent has already been approved, delegated, or awarded.