Authentication & Tenancy
Oct 26, 2026
6 min read
Every /api/v1/* and /v1/* endpoint in Mule requires authentication with an API key. This page covers how keys work, how the first admin is bootstrapped, development shortcuts, and how Mule isolates each user’s data in multi-user (fleet) deployments.
Overview
Mule implements multi-user tenancy (migration 0012_tenancy.sql):
- Each user’s agents, workflows, jobs, skills, and providers are invisible and inoperable to every other user.
- An admin role is available for fleet operators and sees all owners’ data.
- Tools, WASM modules, settings, and memory config are shared/global by design.
Authentication is enforced by middleware on the API server (internal/api/auth.go):