Section · Get started
Build against Munin.
Three surfaces, one install. The REST API for HTTP integrators, MCP for the agents you operate, and Skills for the procedures those agents read at runtime. Pick the door that matches what you’re building.
The three surfaces read these in order
01
REST API
When you’re integrating Munin from another HTTP service — a backoffice, a webhook receiver, a sync job.
- 131 endpoints across conversations, CRM, KB, CMS, outreach, admin
- Bearer tokens, session cookies, or delegated end-user tokens
- OpenAPI 3.1 spec at
/api/v1/openapi.json
02
MCP Tools
When you’re wiring an LLM agent to act on Munin — read articles, reply in conversations, look up people.
- 108 Model Context Protocol tools served at
/mcp - Audiences gate visibility: admin keys see everything, end-user tokens see only self-service
- Each tool ships with its JSON Schema and a scope list
03
Skills Library
When you want your agent to do things well, not just call tools — the runbooks humans write to encode how Munin should be operated.
- 25 markdown procedures bundled with Munin
- Read at runtime via
skill://module/name - Cover triage, bulk imports, escalations, locale rollouts, more
Authentication three ways in
All three surfaces share the same auth model. Pick the credential that matches who’s calling.
Admin API keyServer-to-server. Full access to the org. Generated in Settings → Tokens.
Authorization: Bearer mun_admin_…Delegated user tokenActing on behalf of one end-user. Self-service tools only. Issued by your auth server.
Authorization: Bearer mun_user_…Session cookieBrowser-side calls from a logged-in operator. Same scopes as the operator.
Cookie: munin_session=…Your first call
A friendly endpoint that confirms your token works and tells you who Munin thinks you are.
cURL · GET /api/v1/whoamicopy & run
curl 'https://api.getmunin.com/api/v1/whoami' \ -H 'Authorization: Bearer $MUNIN_API_KEY'