Commmune Commune API

Name: Commune API
Brand: Commune API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingbearer7 EndpointsREST

For Agents

List communities, members, and events on Commune, and create new posts in a community via one bearer token.

Install Jentic One Beta

Connect the Commune API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Commune API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Commune API.

List every community accessible to the authenticated token via GET /communities

Fetch a single community record by id via GET /communities/{id}

List members across a community via GET /members

Read posts published in a community via GET /posts

GET STARTED

Start building with Commune API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Commune API, keeping it validated and agent-ready. Commune is a Japanese community management and engagement platform; the v2 API exposes a small core surface for listing communities, fetching community detail, listing members, reading and creating posts, and listing events. The post creation endpoint is the only write operation in the spec — everything else is read access. Use it to mirror community activity, drive notification systems, or let an agent post announcements on your behalf.

Use Cases

Patterns agents use Commune API for, with concrete tasks.

★ Cross-Post Announcements from a CMS

When an editorial CMS publishes an article, mirror the headline and link into Commune by calling POST /posts. The community manager sets the destination community id once, and every published article fans out automatically. Useful for keeping members informed without manual reposting.

POST a new post to /posts with title 'New Article Live' and body containing the article URL

Member Directory Sync

Pull GET /members on a schedule and reconcile against an internal source-of-truth (HRIS or CRM) to detect new joiners and leavers. Combined with GET /communities, this gives a current map of who belongs to which community for downstream segmentation.

List members via /members and join with an internal CRM email list to find members who have not been contacted this month

Event Calendar Aggregation

Surface Commune events alongside other calendar sources (Google Calendar, Eventbrite) in an internal portal. GET /events returns the event list which can be normalised into a unified schedule view, so members see one calendar instead of several tabs.

Fetch all events from /events and normalise them into a calendar JSON with title, start_at, and url fields

AI Community Manager via Jentic

An AI agent connected to Jentic can draft an announcement, post it to Commune, and confirm members can see it — all without raw key exposure. Jentic stores the bearer token in MAXsystem and returns only execution results to the agent context.

Use Jentic to search 'create a post in commune', load POST /posts, and execute with a draft announcement

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for commune api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/communities

List communities

GET

/communities/{id}

Get a single community

GET

/members

List members

GET

/posts

List posts

POST

/posts

Create a post

GET

/posts/{id}

Get a single post

GET

/events

List events

GET

/communities

List communities

GET

/communities/{id}

Get a single community

GET

/members

List members

GET

/posts

List posts

POST

/posts

Create a post

GET

/posts/{id}

Get a single post

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Commune bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents call operations via Jentic and the raw token never appears in the agent's context window or logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create a post in commune') and Jentic returns the matching operation with its full input schema, so the agent calls the right endpoint without browsing Commune docs.

Time to first call

Direct Commune integration: half a day to wire up the bearer token and post creation. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Commune API through Jentic.

Why is there no official OpenAPI spec for Commune API?

Commune does not publish an OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Commune via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Commune API use?

Commune uses a bearer token in the Authorization header. Through Jentic, the token is stored encrypted in the MAXsystem vault and never enters the agent's context — the agent only receives the response of the operation it called.

Can I create posts in a Commune community?

Yes. POST /posts creates a new post in a target community; the request body includes the community reference, post title, and body content. This is the only write endpoint in the v2 spec.

What are the rate limits for the Commune API?

Commune does not document a public rate limit. In practice, modest paginated reads work reliably; if 429 responses appear, back off and retry. Avoid posting in tight loops to prevent member-facing spam.

How do I create a Commune post through Jentic?

Search Jentic for 'create a post in commune', load the schema for POST /posts, and execute with the title and body. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).

Does the Commune API support listing events?

Yes. GET /events returns events scheduled in the community, including upcoming and past entries. Combine with /communities to scope events to a specific community.

Commmune Commune API

Connect the Commune API to your agent

Capabilities

Start building with Commune API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs