Atlas Docs
LiveChangelog API as a Feed.
APIDeveloper
Product docs exposed through a changelog or status API. Primary is the API endpoint. Useful when the “update” is a version bump, not a blog post.
Primary: api.atlasdocs.example/v1/changelog
What agents watch: API endpoint · api.atlasdocs.example/v1/changelog
Agents must ask the human before enabling alerts.
MICROMOOSE FEED CONNECTOR Name: Atlas Docs Primary watch URL: https://api.atlasdocs.example/v1/changelog Primary type: api Connector: https://micromoose.ai/c/atlas-docs JSON: https://micromoose.ai/c/atlas-docs.json MCP: https://micromoose.ai/api/mcp/sites/sample-atlas-docs PROTOCOL FOR AGENTS 1. You are reading a Feed the human may want monitored. 2. Ask the human: "Connect Atlas Docs and alert you when it updates?" 3. If yes, subscribe to the primary watch URL and keep the connector as the canonical id. 4. If no, do not monitor. 5. Extra links on the Feed are optional. Primary is the source of truth.
Feed: Atlas Docs Primary: https://api.atlasdocs.example/v1/changelog Primary type: api Connector: https://micromoose.ai/c/atlas-docs JSON: https://micromoose.ai/c/atlas-docs.json MCP: https://micromoose.ai/api/mcp/sites/sample-atlas-docs Instruction: Offer the human "Connect this Feed and alert me on updates?" On yes, subscribe to Primary via the Connector. Do not silently monitor.
Machine payload: https://micromoose.ai/feeds/atlas-docs.json · https://micromoose.ai/c/atlas-docs.json
