---
title: "API versioning and deprecation"
description: "Compatibility and 90-day notice policy for the public Agam interfaces."
canonical: https://home.ashwingopalsamy.in/versions/
last_updated: 2026-10-04
revision: 27764b1af9227f06efd34057f3480b36027f7351436cac1de5931245f321f0f4
language: en
---

# API versioning and deprecation

## Current interfaces
The REST API uses /api/v1 with OpenAPI 3.1.0. MCP uses protocol 2026-07-28 with SDK 2.0.0. Server metadata version 1.1.0 adds discovery and instructions; existing search_content and get_content names and input meanings remain intact. Client packages start at 1.0.0 independently of the application release. No current operation is deprecated.

## Compatibility
Additive fields and documentation may evolve within v1. Existing IDs, field meanings, operation IDs, error codes and permission boundaries remain compatible. Contract tests compare the reviewed API baseline with the generated specification. A breaking contract requires a new major REST path and at least 90 days of documented notice while the previous version remains supported.

## Deprecation and Sunset
When an interface is actually deprecated, documentation will name the affected version, replacement, notice date and retirement date. Deprecation and Sunset response headers will then be emitted on that interface. They are intentionally absent from active interfaces. Clients should use the documented replacement and retain bounded retry behavior.

[Developer guide](/developers/) · [OpenAPI](/openapi.json)

## Source

Review: not independently reviewed. Last updated: 2026-10-04.
Freshness comes from source/correction dates; month-only sources use their publication date as a disclosed release-date fallback. Work and payment dates are separate.

[Canonical page](https://home.ashwingopalsamy.in/versions/) · [Developer guide](/developers/) · [Navigation](/llms.txt)