# dak.dev API Versioning and Deprecation Policy

This policy applies to the public HTTP and Model Context Protocol surfaces documented in the [dak.dev OpenAPI document](https://dak.dev/.well-known/openapi.json). The current stable contract is version 1. Clients may send `X-Dak-API-Version: 1`, and versioned responses echo the selected version.

## Stability

Compatible additions may ship within version 1. Dak.dev will not remove documented fields, change their meaning, or make a previously optional field required without publishing a new major contract version. A new major version will run alongside the version it replaces for at least 90 days.

## Deprecation notice

No version is currently deprecated. When retirement is scheduled, affected responses will include a `Deprecation` header using the date format defined by RFC 9745 and a `Link` header with `rel="deprecation"` pointing to migration instructions. The notice will be published here and in the OpenAPI document at least 90 days before removal.

## Sunset notice

If an endpoint is expected to become unavailable, affected responses will also include a `Sunset` header as defined by RFC 8594. Its date will never precede the deprecation date. Clients should migrate before that date and must not interpret the absence of a Sunset header as an active retirement notice.

## Support

Review the [OpenAPI document](https://dak.dev/.well-known/openapi.json) and [authentication guide](https://dak.dev/auth.md) before integrating. Send migration questions to hey@dak.dev and include the endpoint, current version, and problem response code.