What changed in the APIs you use, since a date, breaking changes first.
reef reads the changelogs of the API providers your code depends on and answers your AI agent over MCP: every change with the provider's own words, a link to the source page, the affected endpoints or scopes, and the announced, effective, and sunset dates. The agent reads it in the same session it fixes the code.
Providers reef tracks
2 providers, 19 breaking changes announced in the last 90 days. Read nightly from each provider's public changelog.
Connect your agent
- Add reef as an MCP server. Claude Code: claude mcp add --transport http reef https://reef.pkslabs.com/mcp
- Sign in when the browser opens and create your organisation. That is your tenant.
- Ask the agent to subscribe to the APIs you use, then ask what changed since a date. The answer comes back breaking first, with sources.
You publish an API? Create a publisher account: after approval by hand, your changes appear beside the ingested ones, attributed to you.
How reef reads a change
- The provider's words, not ours. The summary and body are the provider's text; every change links to the provider's source page.
- Severity is reef's and says so. Breaking, notable, or info, set by a named rule per provider; a staff override carries a note.
- Dates are never invented. Announced, effective, and sunset dates come from what the provider wrote; when the text names no date, the field is empty.