# Compatibility and retirement

Build against released contracts and get at least 30 days of notice for planned stable retirement.

## Released contracts

The stable HTTP API lives under `/v1`. HTTP and MCP use the same published operation contracts. Draft app changes and internal fields do not automatically become part of that contract.

Compatible additions can ship within v1. Clients should accept additional response fields and use stable identifiers instead of display labels. Follow each schema's treatment of enum values; do not assume that a human-readable label is a permanent identifier.

Breaking replacements require a new major API contract. Existing operation behavior and webhook contracts remain available through their support period; preserving a name while changing its meaning is not a compatible replacement.

## Planned retirement

Brigg gives at least **30 days' notice** before a planned retirement of a stable public operation or webhook contract. A retirement notice identifies the affected contract, the shutdown date, and the replacement or migration guidance where available.

Deprecation recommends a replacement while the old contract remains available. A retirement date is the point at which the old contract stops working. Releasing a replacement does not immediately retire the original.

Read the [API changelog](https://developer.brigg.app/changelog) and inspect deprecation metadata in your authenticated operation schemas. Brigg captures operation use and webhook subscriptions to identify customers affected by planned changes.

## Experimental operations

Experimental capabilities have an explicit stability label and require opt-in. Their stated support policy can differ from stable v1. Do not rely on an experimental operation as a stable dependency without reviewing that policy.

## Existing MCP and webhooks

Existing launched MCP tools, personal grants, conversion permissions, and `meeting.completed` webhook contracts retain their supported behavior. New identity modes and operation discovery expand the API without silently widening old credentials.