Hosted API
Understand when to use the versioned Mogplex API for repositories, agents, models, sandboxes, automations, runs, and MCP.
The hosted API is the versioned external control-plane surface at
/api/v1/mogplex/*.
Use it when another system needs to inspect or drive Mogplex state directly: repositories, agents, models, sandboxes, automations, runs, events, logs, and MCP server definitions.
Unversioned /api/* routes are private web-app implementation surfaces. Do
not build external integrations against them.
Use the API when
- a CI job or internal tool needs to start or inspect runs
- a dashboard needs repository, run, model, sandbox, or automation state
- a local agent needs the Mogplex MCP tools
- the CLI needs versioned hosted account state
- an adjacent service needs a supported external contract
Prefer the app when a human is configuring account setup, GitHub coverage, agents, routing, or sandboxes interactively.
Public resource model
The public API exposes product resources without exposing the browser app's private route tree:
| Family | Examples |
|---|---|
| Discovery | /repos, /agents, /models |
| Runtime | /sandboxes, /runs, run events and logs |
| Automations | /automations, publish, model override, trigger, and run logs |
| MCP | /mcp/servers and the OAuth-enabled /mcp transport |
The API endpoint index lists every method and scope.
Auth model
Direct REST integrations use personal access tokens. Supported local MCP clients use OAuth 2.1 authorization code with PKCE.
Start with:
- API Authentication for PATs, OAuth, scopes, idempotency, and rate limits
- API Errors for envelope shape and status behavior
- API Quickstart for copyable requests
Good first calls
GET /api/v1/mogplex/reposto discover repository and installation idsGET /api/v1/mogplex/modelsto inspect available modelsGET /api/v1/mogplex/automationsto list bounded automation summariesGET /api/v1/mogplex/mcp/serversto export CLI-ready MCP definitionsPOST /api/v1/mogplex/runsto start headless agent work