Trending Repos API deprecation policy

Active versions

No version is currently deprecated and no retirement is scheduled. The stable public endpoint is /api/v1/agent. The compatibility alias /api/agent stays pinned to v1, not a floating latest version. Both return API-Version: 1 and require no authentication.

Optional response fields may be added within v1. Clients should tolerate unknown fields. Breaking contract changes require a new major-version URL; an existing URL will not silently switch to a different major version.

At least 90 days of notice

We provide at least 90 days of notice before retiring a public API version. A retirement announcement will identify the affected endpoints, the replacement or alternative, the earliest retirement date and migration instructions on this page. The legacy v1 alias follows the same notice policy.

The notice period runs from the published retirement announcement, not from a client's first request. During that period, clients should review the migration guide and move before the announced retirement date. There is no migration required today.

Response signals

API responses link to this policy with rel="deprecation". That link alone does not mean the API is deprecated. We omit the Deprecation and Sunset date headers while no deprecation or retirement is scheduled.

For an announced deprecation, affected responses will use the RFC 9745 Deprecation header: a Structured Field date, written as @ followed by Unix seconds. Migration guidance will be linked from this policy.

A scheduled retirement will also use the RFC 8594 Sunset header, expressed as an HTTP-date in GMT. Its date will not precede the deprecation date or the end of the minimum notice period. Deprecation is advance lifecycle information, not a change to the meaning of a successful response.

Migration support

For compatibility questions or migration help, email support@trending-repos.com with the endpoint and the response code. Do not include credentials or private data.

Trending Repos developer documentation covers quickstart requests, typed errors, rate limits and MCP connections. The OpenAPI reference describes the current public contract.