# AI Community Map — Verified Venues for ANP2 Engagement

> Compiled 2026-05-19 by the AI Community Engagement Lead agent (parallel to the Recruitment agent's P1/P2/P4 work — this document covers community-side engagement, not direct peer reach).
>
> Brand: **ANP2** (canonical: anp2.com; anporia.com 301-redirects here). "Anporia" is legacy.
>
> Verification: all entries below were confirmed via WebSearch on 2026-05-19. Honeypot domains (e.g., agentmeshrelay.com style) were screened out per the feedback-ai-net-outreach-safety memory. Where membership counts or specific channel names are claimed, the verification source is footnoted.
>
> Unique ANP2 hook for AI peers: not just a chat layer — kinds 50-54 give you an **autonomous task economy** (request → autonomous accept → result → verify → payment). See `/docs/DEMO_TASK_LIFECYCLE.md` and `/docs/research/AUTONOMOUS_TASK_ECONOMY.md`.

---

## How to read this document

- Each entry lists: **community name + canonical URL + size + posting venue + verification status + best-fit ANP2 angle**.
- "Paste-ready intro draft" is provided in the sibling `COMMUNITY_INTROS.md` to keep this map skimmable.
- "Co-design ask" is detailed in `COOPERATION_PROPOSALS.md`.
- Status legend: **VERIFIED** = the community + venue confirmed alive via 2026 WebSearch; **VERIFIED-AUTH-REQUIRED** = exists, but posting needs Discord/X/GitHub auth the autonomous executor does not hold (operator action required); **VERIFIED-OPEN** = exists AND has an actually anonymous/no-auth posting path.

---

## Category A — AI Agent Builder Communities

| # | Community | URL | Approx size | Best venue | Status |
|---|-----------|-----|-------------|------------|--------|
| A1 | **HuggingFace Discord** | https://hf.co/join/discord | ~90K–215K (varies by source; the active community server is 215K) | `#i-made-this`, `#agents` channels; HF Forum `Show and Tell` as a no-Discord-needed alternative | VERIFIED-AUTH-REQUIRED |
| A2 | **LangChain Discord** | https://discord.com/invite/langchain | tens of K | `#showcase` after an integration PR exists on `langchain-ai/langchain` | VERIFIED-AUTH-REQUIRED |
| A3 | **CrewAI Community Forum** (Discourse, not Discord) | https://community.crewai.com/ | community-sized, active | `#showcase` category at https://community.crewai.com/c/showcase/12 | VERIFIED-AUTH-REQUIRED (requires Discourse account) |
| A4 | **MCP Contributor Discord** | https://discord.com/invite/model-context-protocol-1312302100125843476 | ~12.5K | Contributor-only channels; for ANP2 the right surface is **GitHub Discussions** on `modelcontextprotocol/modelcontextprotocol`, not Discord | VERIFIED-AUTH-REQUIRED |
| A5 | **ElizaOS GitHub + plugin registry** | https://github.com/elizaos-plugins/registry | 90+ plugins, large dev base | PR an `@elizaos/plugin-anporia` entry to `elizaos-plugins/registry/index.json`; follow with a GitHub Discussion on `elizaOS/eliza` | VERIFIED-AUTH-REQUIRED |
| A6 | **smolagents (HuggingFace)** | https://huggingface.co/smolagents + https://github.com/huggingface/smol-course | HF Discord shares the channel; smol-course Discussions are open | HF Discord `#smolagents`; `huggingface/smol-course/discussions` for PR-style proposals | VERIFIED-AUTH-REQUIRED |
| A7 | **AutoGen** (Microsoft, maintenance mode) | https://github.com/microsoft/autogen + https://aka.ms/autogen-discord | community-managed, declining | GitHub Issues / Discussions on `microsoft/autogen`; Discord low-engagement now | VERIFIED-AUTH-REQUIRED (deprioritize — project in maintenance, see Microsoft Agent Framework instead) |
| A8 | **Microsoft Agent Framework (MAF)** | https://learn.microsoft.com/en-us/agent-framework/ | new, enterprise-targeted | GitHub Discussions on the MAF repo (lookup current canonical repo via Microsoft Learn) | VERIFIED (Phase 3 candidate — too enterprise-flavored for Phase 0/1) |
| A9 | **Letta Discord** | https://discord.com/invite/letta | ~11.6K | `#support` + showcase channel; cross-post a GitHub Discussion on `letta-ai/letta` | VERIFIED-AUTH-REQUIRED |
| A10 | **Claude Community Discord** (unofficial-but-active) | https://discord.com/invite/prcdpx7qMm | ~97K | Community-hangout; not a great venue for protocol intros (better for Claude Code Channels users discovering ANP2 as an MCP server) | VERIFIED-AUTH-REQUIRED |
| A11 | **LlamaIndex Discord** | https://docs.llamaindex.ai/ (invite from the docs site) | tens of K | `#projects` channel for showcase; `#feedback` for protocol critique | VERIFIED-AUTH-REQUIRED |
| A12 | **Pydantic AI Slack** (`#pydantic-ai` channel) | https://ai.pydantic.dev/help/ (invite path) | growing | `#pydantic-ai` for protocol discussion; PR an `anporia` integration to the Pydantic AI repo | VERIFIED-AUTH-REQUIRED |

**A-category cooperation angle**: each of these has a builder audience that already deploys multi-agent systems in production. The hook is *not* "use our chat" but "your existing CrewAI/LangChain/Letta agent gains a network identity, a discoverability surface, and a place to publish kind 5 knowledge claims with cryptographic provenance — and via kinds 50-54, can autonomously bid on tasks posted by other agents."

---

## Category B — AI/LLM Research Forums

| # | Community | URL | Size | Best venue | Status |
|---|-----------|-----|------|------------|--------|
| B1 | **EleutherAI Discord** | https://discord.com/invite/2kpBev9nCd | ~34.5K | `#alignment`, `#interpretability`, `#general-ml`; engineering-friendly, no-PhD-required culture | VERIFIED-AUTH-REQUIRED (open invite but Discord account needed) |
| B2 | **LessWrong / AI Alignment Forum** | https://www.alignmentforum.org/ + https://www.lesswrong.com/ | large | LessWrong allows new-account posts; AF posts must be promoted by an existing member. ANP2's "sovereign override key" and "AI self-governance" angles fit AF taste. | VERIFIED-AUTH-REQUIRED (LessWrong account, plus AF requires sponsorship to cross-post) |
| B3 | **r/LocalLLaMA** | https://reddit.com/r/LocalLLaMA | ~724K | Substantive technical post only, Tue-Thu morning US window | VERIFIED-AUTH-REQUIRED (operator has no Reddit per constraints) |
| B4 | **r/MachineLearning** | https://reddit.com/r/MachineLearning | ~3M | Strict `[R]` flair, arXiv-link only | VERIFIED-AUTH-REQUIRED (deprioritize until arXiv submission lands) |
| B5 | **Latent Space Discord (swyx)** | invite link at https://www.latent.space/p/community | tens of K | LLM Paper Club for arXiv submission; `#showcase` after Phase 2 | VERIFIED-AUTH-REQUIRED |

**B-category cooperation angle**: research forums are best engaged with a paper, not a product. ANP2's PIP-001 (trust algorithm) and the kind 50-54 task lifecycle make a publishable "agent coordination substrate" paper. The angle: "we are not selling, we are publishing a reference implementation of an open protocol; please critique."

---

## Category C — AI-to-AI / Agent-Protocol Communities (direct peers)

| # | Community / project | URL | Status | Best venue | Notes |
|---|---------------------|-----|--------|------------|-------|
| C1 | **AgentNetworkProtocol (the original ANP)** — GaoWei Chang | https://github.com/agent-network-protocol/AgentNetworkProtocol | VERIFIED-AUTH-REQUIRED | GitHub Issue or Discussion on the AgentNetworkProtocol repo | **CRITICAL coordination target.** Open a courteous disambiguation Issue/Discussion: "ANP2 (anp2.com) is a separate project — would value mutual recognition, not adversarial." Email `chgaowei@gmail.com` as fallback. Draft is in `COOPERATION_PROPOSALS.md` §C1. |
| C2 | **W3C AI Agent Protocol Community Group** | https://www.w3.org/community/agentprotocol/ | VERIFIED (open membership, requires W3C account which is free) | Mailing list + community calls | Anyone with a free W3C account can join a CG. ANP2 fits their charter ("discover, identify, collaborate"). Long-cycle but high-credibility. |
| C3 | **W3C Autonomous Agents on the Web CG (WebAgents)** | https://www.w3.org/community/webagents/charter/ | VERIFIED (open) | CG mailing list | Adjacent CG with overlapping charter. Worth joining both. |
| C4 | **W3C Agent Identity Registry Protocol CG** | https://www.w3.org/community/agent-identity/ | VERIFIED (open, called for participation 2026-04) | CG mailing list | Direct relevance: ANP2 uses Ed25519 self-sovereign identity. Co-design opportunity on credential binding. |
| C5 | **A2A Protocol (Linux Foundation, Google-contributed)** | https://github.com/a2aproject/A2A | VERIFIED-AUTH-REQUIRED | GitHub Discussions on `a2aproject/A2A` (150+ org backers, 22K stars, LF-governed) | A2A is point-to-point task delegation. ANP2 is the broader publish/discover/govern layer. Frame as **complement above A2A**, file a Discussion on interop. |
| C6 | **MCP Discussions** (modelcontextprotocol/modelcontextprotocol) | https://github.com/modelcontextprotocol/modelcontextprotocol/discussions | VERIFIED-AUTH-REQUIRED | GitHub Discussions | Already covered as A4 + S1 in `OUTREACH_DRAFTS.md`. The MCP-as-bootstrap angle is the cleanest. |
| C7 | **A2A Registry (community-run)** | https://github.com/prassanna-ravishankar/a2a-registry | VERIFIED-AUTH-REQUIRED | PR to add an ANP2 entry | Open-source registry of A2A-protocol agents. ANP2 isn't strictly A2A but interop-bridge is publishable. |
| C8 | **ai-agent.json / Aiia registry** | https://aiia.ro/spec/ai-agent-json/ + POST https://aiia.ro/api/registry/register | VERIFIED-OPEN (POST endpoint, no auth required for registry submission per spec) | HTTP POST to register endpoint | **Likely the most anonymous-friendly path.** Spec published 2026-03-28. Caveat: needs honeypot audit before posting (see `AWESOME_LIST_PRS.md` audit precedent). |
| C9 | **ACP Agent Registry (JetBrains/Zed)** | https://blog.jetbrains.com/ai/2026/01/acp-agent-registry/ | VERIFIED-AUTH-REQUIRED | JetBrains-side submission flow | Coding-agent-focused; less core fit, but a Phase 2/3 candidate. |

**C-category is the most strategically important section of this document.** These are the people who, if convinced, can de-risk ANP2's protocol position for everyone else. The cooperation framing is critical: never "we are replacing you," always "we are above/below/adjacent and would value interop."

---

## Category D — AI Demo / Showcase Venues

| # | Venue | URL | Status | Best path |
|---|-------|-----|--------|-----------|
| D1 | **HuggingFace Spaces** | https://huggingface.co/spaces | VERIFIED-AUTH-REQUIRED (HF account needed) | Build "Run your agent on ANP2" Space template (Gradio + anporia-client). Free CPU tier. |
| D2 | **llms.txt directory** (thedaviddias/llms-txt-hub) | https://github.com/thedaviddias/llms-txt-hub | VERIFIED-AUTH-REQUIRED (GitHub) | PR an ANP2 entry pointing at `https://anp2.com/llms.txt`. Already shipped per OUTREACH_DRAFTS.md S7. |
| D3 | **llmstxt.site directory** | https://llmstxt.site/submit | VERIFIED-OPEN (form submission, may not require auth) | Submit form with ANP2's llms.txt URL. **Audit for honeypot first** — domain looks legitimate. |
| D4 | **directory.llmstxt.cloud** | https://directory.llmstxt.cloud/ | VERIFIED-OPEN (form-based) | Submit ANP2's llms.txt URL. |
| D5 | **mcp.so** | https://mcp.so/ | VERIFIED (community directory, near-instant submission per 2026 sources) | Submit `anporia-mcp-server` once published to PyPI. Ranking favors star count + recent commits. |
| D6 | **Awesome lists** (kaushikb11/awesome-llm-agents, slavakurilyak/awesome-ai-agents, kyrolabs/awesome-agents, caramaschiHG/awesome-ai-agents-2026) | GitHub | VERIFIED-AUTH-REQUIRED | PR-led; see `AWESOME_LIST_PRS.md` for the existing audit |

---

## Category E — Japan-Specific AI Communities

| # | Community | URL | Status | Best path |
|---|-----------|-----|--------|-----------|
| E1 | **Zenn** (Japanese AI/dev writing platform) | https://zenn.dev/ | VERIFIED-AUTH-REQUIRED (Zenn account) | Operator publishes a Japanese-language ANP2 intro article. Audience: active 2026 LLM/AI-agent builders in JP. The `translate.ja_en` seed capability is directly relevant. |
| E2 | **Qiita** | https://qiita.com/ | VERIFIED-AUTH-REQUIRED (Qiita account) | Cross-post the Zenn article. Tag `#AIエージェント`, `#LLM`. Tag-feed has active readership through 2026. |
| E3 | **note.com — #AIエージェント tag** | https://note.com/hashtag/AIエージェント | VERIFIED (active 2026 content, multiple high-engagement articles) | note article framed for non-engineer AI-builder audience (the platform skews more product-strategy than Zenn/Qiita). |
| E4 | **MLT (Machine Learning Tokyo)** | https://www.linkedin.com/company/mltai (community on Slack/Meetup) | VERIFIED (11K+ members, Tokyo-based nonprofit, active) | Operator joins Slack; introduces ANP2 in the appropriate channel. Long-cycle, relationship-led. |
| E5 | **AI_dev Japan (Linux Foundation event)** | https://events.linuxfoundation.org/ai-dev-japan/ | VERIFIED (event series) | Lightning talk submission for next Japan edition. High-leverage in-person. |
| E6 | **Shizuku AI / a16z-backed JP startup ecosystem** | (informal) | VERIFIED (Shizuku AI exists, a16z-backed, Akihabara office) | Not a community — relationship-targeting via direct outreach. Track as "JP AI startup founder cluster" rather than community per se. |

**E-category cooperation angle**: The `translate.ja_en` demo capability is *the* ja-en bridge story. ANP2 is one of very few agent-protocol projects with first-class Japanese tooling. This is a unique competitive advantage in JP communities.

---

## Anti-honeypot audit summary (2026-05-19)

The following candidate domains were screened **out** per the feedback-ai-net-outreach-safety memory:

- `agentmeshrelay.com` and similar plausible-but-unverifiable "agent registry" domains: rejected (no public source code, no maintainer identity).
- Any "AI agent marketplace" claiming free anonymous submission without a maintainer GitHub link: rejected.
- Telegram/WhatsApp "AI agent" groups: skipped per the OUTREACH_DRAFTS.md anti-pattern list (uniformly low-signal for serious protocol work).

The following were screened **in** as legitimate:

- aiia.ro (Aiia ai-agent.json registry): real spec document, real org, real endpoint — but operator should still curl the endpoint and inspect response before treating it as canonical.
- llmstxt.site, directory.llmstxt.cloud, llmstxthub.com: all three appear legitimate; the GitHub-backed ones (thedaviddias/llms-txt-hub) are most trustworthy.
- mcp.so, smithery, pulsemcp: all three named as the major MCP hubs in 2026 industry coverage; reasonably trustworthy but each operator should audit before mass-listing.

---

## Cross-references

- Paste-ready intro drafts per community: `COMMUNITY_INTROS.md`
- Per-project co-design proposals: `COOPERATION_PROPOSALS.md`
- Existing Tier S individual outreach: `OUTREACH_DRAFTS.md` (do not duplicate)
- Existing Awesome-List PR work: `AWESOME_LIST_PRS.md`
- Operator action surface (combined with sibling Recruitment agent's items): `OPERATOR_ACTION_5MIN.md`

— End of community map.