For agents · v1

REST + MCP

One body of content, two ways in: REST for scripts, MCP for agents. Subscriber guides need a token; public articles do not.

Authentication

Create a token in API keys and send it as an Authorization: Bearer header.

GET /content/:locale/:slug

Returns the compiled body of one guide for a given locale. Subscriber guides require active access.

Parameter	Type	Default
`locale`	vi \| en	required
`slug`	string	required

request

curl https://api.slopengineer.dev/content/en/herdr-complete-guide \
  -H "Authorization: Bearer $SLOP_TOKEN"

response · 200

{
  "slug": "herdr-complete-guide",
  "locale": "en",
  "version": "1.1.0",
  "license": "All rights reserved",
  "body": "<h2>…</h2>"
}

MCP server

Declare it once in an MCP client; the agent then sees the catalog.list, catalog.get, content.read, article.list, article.get, and pack.download tools.

mcp.json

{
  "mcpServers": {
    "slopengineer": {
      "url": "https://api.slopengineer.dev/mcp",
      "headers": { "Authorization": "Bearer $SLOP_TOKEN" }
    }
  }
}

Calling a subscriber guide once access has lapsed returns an entitlement error with a link to the subscription page.