Skip navigation
Getting started › Overview

API docs

One API, two ways in: REST for scripts, MCP for agents. The catalog, prices and home page highlights need no key; reading subscriber guides, placing bank-transfer orders and checking your account's access need an API key.

Overview

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

base URL
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.list, pack-versions, spotlight, prices) need no key. POST and PATCH verbs take their parameters in a JSON body, sent with a Content-Type: application/json header.

Limits & errors

Applies toLimit
Paid guide reads (content.get)1,000 in 24 hours, per account
File pack and visual links (packs.download, visuals.issueUrl)50 links in 24 hours, per account
Bank-transfer orders (orders.create)20 orders per hour, per account
Discount code quotes (orders.quote)30 per hour, per account
Facebook claim codes (claims.redeem)10 attempts per hour, per account
The /mcp endpoint300 per minute, per IP

Every error comes back in the same JSON shape, with a requestId to quote when reporting it. Some add details: invalid_input lists the rejected fields in details.issues, and unprocessable gives the reason in details.reason.

application/json
{
  "error": {
    "code": "not_found",
    "message": "Content item was not found",
    "requestId": "…"
  }
}
StatusError
400invalid_input
401unauthenticated
403forbidden
403insufficient_scope
404not_found
405method_not_allowed
409conflict
422unprocessable
429too_many_requests
500internal_error
503service_unavailable

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.

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

Tool list

Every verb an API key can call. Each has a REST path and an MCP tool with the same parameters. Managing API keys, connected apps and card billing belongs to the account pages on the web: an API key's tools/list leaves those tools out, so they are not covered here.

VerbRESTMCP toolAccess
catalog.listGET /catalogcatalog_listNo key
catalog.getGET /catalog/{locale}/{slug}catalog_getNo key
articles.listGET /articlesarticles_listNo key
articles.getGET /articles/{locale}/{slug}articles_getKey required
content.listGET /contentcontent_listKey required
content.searchGET /content/searchcontent_searchNo key
content.getGET /content/{locale}/{slug}content_getKey required
packs.downloadPOST /packs/{slug}/downloadpacks_downloadKey required
pack-versions.getGET /pack-versions/{slug}pack-versions_getNo key
visuals.issueUrlPOST /visuals/{locale}/{slug}/urlvisuals_issueUrlKey required
visuals.issueFlowUrlPOST /visuals/{locale}/{slug}/flow/urlvisuals_issueFlowUrlKey required
visuals.issueMotionUrlPOST /visuals/{locale}/{slug}/motion/urlvisuals_issueMotionUrlKey required
spotlight.listGET /spotlightspotlight_listNo key
prices.listGET /pricesprices_listNo key
orders.quotePOST /orders/quoteorders_quoteKey required
orders.createPOST /ordersorders_createKey required
orders.listGET /ordersorders_listKey required
orders.getGET /orders/{code}orders_getKey required
claims.redeemPOST /claims/facebookclaims_redeemKey required
entitlements.statusGET /entitlements/statusentitlements_statusKey required
preferences.getGET /preferencespreferences_getKey required
preferences.updatePATCH /preferencespreferences_updateKey required