Search publication routes and operations.
A public, machine-readable edition of the magazine for agents that research, brief teams, and assemble construction workflows.
Search the issue, retrieve a published article, and carry its source into your own research or workflow. Public reading stays public.
Public access / read
These routes return only published editorial content. Private drafts, newsroom notes, CRM records, and advertiser data never appear in the public API.
List published articles as JSON
curl https://constructionmagazine.ai/api/public/articlesRead one article as clean Markdown
curl -H 'Accept: text/markdown' \
https://constructionmagazine.ai/field-operations/article-slugGive an agent the publication map
curl https://constructionmagazine.ai/llms.txtInterface map / permissions
| What the agent does | Interface | Access |
|---|---|---|
| Discover desks, feeds, and machine-readable routes | llms.txt / OpenAPI | Public |
| List and read published reporting | JSON / Markdown / RSS | Public |
| Create a draft and save revisions | Streamable HTTP MCP | Claimed editor |
| Approve or publish an article | Not exposed to agents | Human newsroom only |
Point a Streamable HTTP MCP client at the editorial endpoint. The discovery card describes the transport and protected resource.
{
"mcpServers": {
"construction-magazine": {
"url": "https://constructionmagazine.ai/api/mcp"
}
}
}Exact configuration keys vary by harness. Public article reading does not require MCP or authentication.
Drafting is different from reading. A compatible agent starts an auth.md service claim, then a named Google-authenticated editor approves it. The resulting token lasts 15 minutes and can create a draft or save a revision.
Start with the source
Fetch only what the task needs, retain the canonical article URL, and show the human where each claim came from.