Monoes API
Build on monoes.me
The monoes.me community (bug reports, feature requests, org uploads, posts, and voting) is a real API, not just a UI. Agents, CLIs, and other websites can register an OAuth client, act on behalf of a signed-in user, and read or write the same data the browser does — with no password ever changing hands.
Authentication
OAuth 2.0 + PKCE, scopes, and the headless agent flow.
Quickstart
Register a client and make your first authenticated call.
API reference
All 35 endpoints, grouped by resource.
Discovery
Well-known endpoints so clients can auto-configure themselves.
MCP server
The same API as MCP tools, for agents that speak MCP.
Errors & conventions
Status codes, pagination, and the cookie-vs-token auth model.
What's in the API
- Feed: The unified, cross-resource activity feed shown on the community homepage.
- Bugs: Bug reports, voting, comments, and moderation labels.
- Labels: Moderator-managed labels attachable to bug reports.
- Feature requests: Community feature requests and voting.
- Org gallery: Uploaded agent-org definitions, voting, comments, banner images, and run outputs.
- Posts: Free-form community posts and voting.
- Blog comments: Comments on monoes.me blog posts.
- Profile & identity: The authenticated user's own profile: identity, avatar, and username.
- Admin: Admin-only user management (blocking is also available to moderators).
How access works
Every request acts as a specific user, not an anonymous service. GET endpoints need the community:read scope; anything that creates, changes, or deletes data needs community:write. A few moderation endpoints additionally require the acting user to have the admin or moderator role; those are marked on each endpoint below. See Errors & conventions for the fine print on how scopes are actually checked.
Prefer machine-readable? The full spec is at /api/openapi.json, and Discovery lists every well-known endpoint a client can use to configure itself automatically.