API Reference

Start with the Moonage MCP

The programmatic surface for agent work is the Moonage MCP server. It projects your organization's agents, memory, tasks, and capabilities as governed MCP tools, so an MCP-compatible client can drive the same work a person drives in the app — under the same policies, human gates, and audit log.

The connection recipe — authorization server, scopes, and dynamic client registration — is published as machine-readable markdown at https://moonage.ai/auth.md. The server card is at https://moonage.ai/.well-known/mcp/server-card.json.

If you are building an integration with Moonage, this is the surface to build on.

The REST API

https://api.moonage.ai is the application's own backend — the API the Moonage desktop app calls. It covers account and organization management.

• Paths are versioned under /v2. There is no /v1.
• Requests authenticate with a Bearer session JWT, issued by the sign-in flow. There are no API keys.
• An interactive reference lives at https://api.moonage.ai/docs, and the OpenAPI spec at https://api.moonage.ai/openapi.json.

The header shape:

curl -H "Authorization: Bearer <session-jwt>" \
  https://api.moonage.ai/v2/spaces

Without a valid token, that request returns 401.

What to expect from it

This is an internal backend that we happen to publish, not a supported customer integration surface. It moves with the application, and parts of the published spec have already drifted from what is live — some documented paths return 404. Read the spec as a description of the app's own traffic rather than as a contract, and expect anything built directly against it to break without notice.

For work you intend to keep running, use the Moonage MCP above.

A second, unrelated MCP server

The Content MCP at https://content.moonage.ai/mcp publishes website content only — blog, changelog, and roadmap. It has no access to your organization, its agents, or its memory. Do not confuse the two.

See MCP Server for that one, and Content API for its REST equivalent.