Changelog
Changes to the partner interface land here, newest first, once there are any.
apiVersion v1 · schemaRevision 1
How the interface evolves
- Additive-only within v1
- New optional fields and entirely new tools are added at any time with no breaking change. An existing field never changes type, never becomes required, and never disappears. An existing tool never changes its output incompatibly and is never removed without the deprecation window below. A breaking change always gets a new version (/api/mcp/v2/) alongside v1, never an in-place break.
- 90-day deprecation window
- A tool or field slated for removal is first announced here as a dated entry, marked the same day with a deprecation note in its own description in tools/list, and then stays callable for at least 90 days. Removing it before the window expires is a contract violation; the window may only ever be extended.
- Version stamp cannot drift
- tools/list carries apiVersion and the same number the newest entry here declares. The Website build fails if the two disagree, so the tool reference and the changelog can never silently fall out of sync.
No entries yet. The current API version is v1.
Trust and live status
Machine-readable service facts and the current operational status of the partner interface are publicly available at all times, no login needed.