GTM Index developer resources
GTM Index API versioning and deprecation
Agents should treat the public GTM Index HTTP surface as versioned. Breaking changes require a new major path. This page is the deprecation and sunset policy.
Current versions
- REST list APIs live under
/v1/on https://gtmindex.io and on the Gateway origin.GET /v1/peopleandGET /v1/jobsare the v1 contracts. - Open WebMCP is
POST /mcpJSON-RPC. Tool names are additive; renaming or removing a tool is a breaking change and will be announced here first. - Machine files (
/openapi.json,/llms.txt, RFC 9727 catalog) describe the current major version.
How deprecation is signaled
When a path or field is deprecated, responses include RFC 9745 Deprecation and, when a removal date is known, Sunset. They also include a Link header with rel="deprecation" pointing at this page. Until a sunset date is published, v1 remains the supported major version. There is no scheduled sunset for /v1/people, /v1/jobs, or POST /mcp.
What will not change without a new major
Error documents stay RFC 9457 application/problem+json with code, detail, and hint. Rate-limit responses keep IETF RateLimit / RateLimit-Policy and Retry-After on 429. Pagination stays limit/offset. We will not silently require an API key for public browse without a documented replacement version.