An API changelog your developers actually read
Your API changes live in commits and PRs. Changelore turns them into release notes your integrators can follow — without you re-typing anything.
API consumers do not read your dashboard; they read your docs and their inbox. When a breaking change ships without a clear, dated note, you pay for it in support tickets and broken integrations. And the person who knows what changed — the engineer who merged it — is the least likely to open a marketing tool to write it up.
Breaking changes drafted from the PR
Point your AI agent at the merge and it drafts the note — what changed, what breaks, what to migrate to. You review and publish.
Embed it in your docs
A public read API and an RSS feed mean the changelog can live inside your docs site, not only on a page nobody visits.
Tag by version
Tag entries (v2, deprecation, breaking) so integrators can filter to just the changes that affect them.
Notify the people who integrate
Email subscribers and webhooks to Slack or Discord fire the moment you publish — where your developer community already is.
> draft a changelog entry from PR #482
Agent → reads the diff, drafts:
## Breaking: /v1/users now paginates by cursor
`?page=` is removed. Use `?cursor=`.
Migration: read `next_cursor` from the response.
tags: v1, breakingQuestions
- Can I keep the changelog inside my documentation site?
- Yes. Every project exposes a public read API (X-API-KEY) and an RSS feed, so you can render entries inside your docs with your own components.
- Can I mark an entry as a breaking change?
- Use tags. Entries can be tagged (for example "breaking" or "v2") and the public page lets readers filter by tag.
Changelore is launching soon
The changelog written from your code. Join the waitlist for early access.
Join the waitlist