Current Savi API and MCP versions, release notes, and deprecation policy.
Use with an AI agent
Export this page as Markdown or copy a task prompt with links to the hosted docs.
Try a task
Preview the prompt that will be copied
# Savi developer task ## Task [Describe the integration or change you want to make.] ## Instructions Use only documented methods, fields, authentication, scopes, and effects. Read the current page and Authentication guide as the source of truth before implementing. ## Documentation - Current page: https://financesavi.com/developers/changelog.md - Authentication guide: https://financesavi.com/developers/authentication.md
Versions and compatibility
JSON-RPC API
v2
https://api-v2.financesavi.com/rpcThe endpoint host identifies the API contract generation. JSON-RPC 2.0 is the message protocol, not the Savi API release version.
MCP server
0.1.0
https://mcp.financesavi.com/mcpReported as serverInfo.version. The MCP protocol version is negotiated during initialize; clients do not select a server release by URL.
Changelog
- Public version baseline: Recorded the current JSON-RPC API and MCP server versions and published the compatibility policy. This documentation entry does not change any endpoint, method, or tool contract.
This public changelog starts at the baseline above; earlier releases are not reconstructed.
Deprecation policy
- Additive methods, optional fields, and backward-compatible fixes stay in the current JSON-RPC major version.
- Breaking JSON-RPC changes ship under a new major endpoint host. The previous major remains available for at least 180 days after its replacement launches.
- Breaking MCP tool changes and removals receive at least 180 days of notice. The MCP endpoint is not version-selectable.
- A deprecation notice appears in this changelog and on the affected method or tool reference, with a replacement and planned removal date.
- Security or legal requirements may require shorter notice; publish notice as soon as practical.