What authentication does the Commune API use?

Commune uses a bearer token in the Authorization header. Through Jentic, the token is stored encrypted in your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Commune API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Commune operations the agent may call and which credentials it may use. You can allow only reads such as GET /communities, GET /members, GET /posts, and GET /events, and grant POST /posts for creating announcements while leaving every other operation out. Because Commune puts community and post ids in the URL path (/communities/{id}, /posts/{id}), a rule can also pin the agent to a single community or post.