API docs

One body of content, two ways in: REST for scripts, MCP for agents. Public articles need no key; subscriber guides need an API key from an account with access.

Overview

Every path below is relative to this base URL. Responses are JSON.

https://api.modernengineer.dev

Authentication

Create an API key in API key management, then send it in an Authorization: Bearer <key> header. The key is shown once, when you create it. Public verbs (catalog, articles) need no key.

Limits & errors

Every error comes back in the same JSON shape, with a requestId to quote when reporting it:

{
  "error": {
    "code": "not_found",
    "message": "Content item was not found",
    "requestId": "…"
  }
}

MCP setup

Declare it once in an MCP client and replace <API key> with the key you created (JSON config does not expand environment variables; use your client's own variable syntax if it has one). It uses the same API key as REST.

{
  "mcpServers": {
    "modernengineer": {
      "type": "http",
      "url": "https://api.modernengineer.dev/mcp",
      "headers": {
        "Authorization": "Bearer <API key>"
      }
    }
  }
}

Tool list

The verbs agents use to read content. Each has a REST path and an MCP tool with the same parameters. tools/list also returns a few account tools (API keys, billing) not covered here.