Documentation

Everything you need to run Changelog Observer from a coding agent, a script or your own code. The API lives at https://api.changelog.observer; the MCP server at https://api.changelog.observer/mcp. Both take the same key.

QuickstartFrom sign-in to the first event in about ten minutes, with Claude Code or with curl.ConceptsWorkspaces, projects, dependencies, sources, events, incidents, rules and destinations, in plain words.REST APIEvery endpoint with its scope, what it does and what it takes.MCP serverConnect any MCP client; every tool, generated from the server's own definitions.WebhooksThe payload, the headers, how to verify the signature, and how retries work.Email and the inboxInbound addresses, verified senders, quarantine, confirmations and sender rules.Incidents and ticketsThe two lifecycles, what you may claim, summaries, and pushing to Jira, Linear, GitHub or Statuspage.Rules, digests and quiet hoursWhat alerts at once, what waits, and what is never sent.Agent guideHow a coding agent should set up, keep in sync, triage and report, and what it must never do.SkillsThe four published skills and how to give them to your agent.

Two things to know before anything else

The platform never reads your repository. Your agent does, with the access it already has, and sends the dependency list. Setup is a sentence to the agent, not a form.

Severity is not impact. Every incident carries the vendor’s status and yours separately. The API refuses a claim that your customers are affected unless a note names the evidence. Keep that in mind when you build on top of it.

Where the words come from

The REST reference is kept next to the worker’s routes and its tests. The MCP reference is generated from the tool definitions at build time, so it cannot drift. The agent guide and the skills are the same files the repository ships for agents to read.