# Commune **Canonical:** https://apis.io/providers/usecommune/ **Website:** https://usecommune.com **APIs profiled:** 2 Commune turns newsletters into communities: each newsletter has an archive of articles and every article carries a threaded chat, with engagement insights, subscriber analytics, growth tracking and superfan identification on top. The Commune API (63 operations, 23 webhook topics, contract version 2026-08-26) exposes newsletters, articles, threads, messages, subscribers, tags, senders, domains, metrics, sends and event delivery over a cursor-paginated REST surface at api.usecommune.com, authenticated with bearer API keys or OAuth 2.1 (PKCE, dynamic client registration, RFC 9728 protected-resource metadata), versioned by a Commune-Version date header, with a required Idempotency-Key on every write and a hosted MCP server at api.usecommune.com/mcp. ## Kin Score — 63.7 / 100 (strong) Scored 2026-10-09 under rubric 0.23.0. | Facet | Score | |---|---| | Discoverability | 65.0 | | Contract Quality | 74.2 | | Contract Governance | 22.0 | | Operational Transparency | 55.3 | | Developer Ergonomics | 56.5 | | Access Clarity | 76.3 | Regulatory layer — **Telecommunications**: 35.0 (matched via tags). ## Agent readiness — 59.0 (agent-native) | Dimension | Value | |---|---| | Spec Presence | yes | | Agentic Access | derived | | Reversibility Documented | no | | MCP Server | documented | | Auth Clarity | served | | Idempotency | verified | | Error Semantics | documented | | OpenAPI Examples | partial | | Rate Limit Signal | verified | | Event Surface Described | yes | | Agent Skills | derived | | Well Known Catalog | no | | Consent Identity | no | | Agent Card | no | | Dry Run Mode | no | | Delegated Identity | served | | Protected Resource Metadata | verified | | Dynamic Client Registration | yes | | Agentic Commerce | no | ## APIs (18) - **Commune Articles API** — An article is one thing a newsletter published: written in Commune and sent, or imported from the newsletter's provider. Two rules gate every article read and are described on e... - **Commune Engagement API** — What Commune knows about one subscriber that a newsletter's email provider cannot answer: engagement scored across the inbox and the community together, and the raw event stream... - **Commune Event delivery API** — Where a newsletter's events go, and how a creator changes it. Commune hands every event it publishes to a delivery service that owns fan out, retries, signing and the delivery l... - **Commune Highlights API** — A highlight is a passage of an article a reader marked. It anchors a comment to the exact sentence that prompted it. - **Commune Messages API** — A message is a reply inside a thread, up to two levels deep. Reactions hang off a message. - **Commune Metrics API** — The rolled up numbers for a newsletter and for one article: headline stats for a period, acquisition attribution, bucketed series for charting, and one article's email performan... - **Commune Newsletters API** — A newsletter is the top level object in Commune. It owns its articles, its chat, its subscribers and its team. Everything else in this API hangs off one. - **Commune Platform API** — The API's own machinery rather than any newsletter's data: the readiness probe, what a credential has left of its rate limit budgets, what its newsletter's plan allows, and the ... - **Commune Search API** — One query across newsletters, articles, people and chat. Where a reader starts who does not yet have an identifier for any of them. - **Commune Senders API** — The addresses a newsletter sends from, and the state of the DNS that has to be in place for them to work. The sending half of the pair; Website domains is the other. Needs `send... - **Commune Sends API** — A send is one dispatch of one article to a newsletter's list: when it started, when it finished, and the three numbers it finished on. Not to be confused with Senders, one headi... - **Commune Subscriber tags API** — A tag segments a newsletter's audience. Sending an article to a tag stamps that article with an audience, which is what makes it invisible to everyone outside it. Named for the ... - **Commune Subscribers API** — Who receives a newsletter. Needs `audience`, and never a public surface: a newsletter's list belongs to its creator. `GET /subscriptions` is that edge read from the other end, t... - **Commune Team API** — Who may act on behalf of a newsletter: its owner, plus the members the owner added as admins, editors or guests. Both sides of that edge are here. A newsletter's roster answers ... - **Commune Threads API** — A thread is a conversation inside a newsletter's community. Commune has no separate posts or comments stack: a creator's broadcast, a reader's question and the discussion under ... - **Commune Users API** — A person with a Commune account: the readers who join a community and the writers who are credited on an article. Looked up by identifier or by username, and only ever as a publ... - **Commune Webhooks API** — The events Commune pushes to a consumer, rather than the resources a consumer pulls. Commune publishes state changes on 23 topics, each delivered as one HTTPS POST to an endpoin... - **Commune Website domains API** — A creator's own domain pointed at their Commune site, so their community lives at their address rather than at ours. The same prove you own this hostname flow as Senders, pointe... ## MCP servers (1) - **Commune MCP Server** — Commune ships a hosted, remote MCP server at https://api.usecommune.com/mcp (Streamable HTTP). The guide describes job-shaped tools (for example 'which readers am I about to los... ## Agentic access (1) - **Usecommune Agentic Access** — 63 operations · 19 acting · 1 human-in-the-loop ## Security (2) - **Usecommune Authentication** — http/oauth2 · 2 schemes - **Usecommune Domain Security** — TLSv1.3 · DMARC ## Plans (1) - **Usecommune Plans Pricing** ## Tags Newsletters, Email, Community, Publishing, Creator Economy, Subscribers, Webhooks, MCP, Analytics, Content --- Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/usecommune/). Scores are computed from the provider's own public artifacts under a published rubric.