API changelog
Every change to the Havoptic REST API and MCP server: new endpoints, fields and parameters, with the Havoptic-Version they shipped in.
Also available as JSON or markdown from GET /v1/changelog (Accept: text/markdown). Breaking changes are announced here at least 12 months before they take effect.
2026-10-19: Bulk exports: releases json/ndjson/csv/parquet, changes.ndjson, daily deltas
New GET /api/v1/export/* downloads, pre-built by the pipeline whenever the dataset changes, with a manifest of row counts and sha256 hashes. CC BY 4.0, not gated. Havoptic-Version 2026-11-01.
- Added GET /api/v1/export/releases.{json,ndjson,csv,parquet}: the full release snapshot (json/ndjson rows are the Release object; csv/parquet use the flat columns listed in the manifest).
- Added GET /api/v1/export/changes.ndjson: every typed change item, one per line.
- Added GET /api/v1/export/deltas/{date}.ndjson: releases whose record changed that UTC day, as {op, id, changed_at, record} lines.
- Added GET /api/v1/export/manifest.json (also /api/v1/export): files, rows, bytes, sha256, columns, license and the delta file list.
- Exports stream with a strong ETag, Content-Disposition: attachment and Link rel="license" (CC BY 4.0). Unsupported formats and malformed delta dates return 400 problem+json.
- New JSON Schemas: export_manifest, export_delta.
References: issue #1952
2026-10-19: Complete REST catalog: tool detail, versions, features, trends, compare for 2–4 tools
New tool detail, per-tool releases and version lookup, feature catalog and trend endpoints; /tools, /releases, /compare and /tools/{id}/cadence gain additive filters and fields. Havoptic-Version 2026-11-01.
- Added GET /api/v1/tools/{id} (metadata, latest stable and prerelease, cadence summary, source health; registry aliases accepted).
- Added GET /api/v1/tools/{id}/releases (shortcut for /releases?tool={id}) and GET /api/v1/tools/{id}/versions/{version} (latest, v prefix and codex rust-v forms; 404 problem+json when unknown).
- GET /api/v1/tools accepts vendor, category, status (default active; all) and q; items add vendor, category, status, latest_release, release_count and health.
- GET /api/v1/releases accepts vendor, category, breaking, security, updated_since, sort (-published_at|published_at|product) and expand (changes|notes|product).
- GET /api/v1/compare accepts 2–4 tools plus aspects (cadence, features, recent_changes, verdict) and since; two-tool requests keep the legacy comparison object.
- GET /api/v1/tools/{id}/cadence accepts window=7d|30d|90d.
- Added GET /api/v1/features, GET /api/v1/features/{id}, GET /api/v1/trends/cadence, GET /api/v1/trends/feature-adoption and GET /api/v1/trends/mechanics.
- Unknown enum values on the new parameters return 400 application/problem+json naming the parameter. New JSON Schemas: cadence, comparison, feature, cadence_trend, feature_adoption, mechanics.
References: issue #1949
2026-10-19: API changelog, source status, and complete JSON Schemas
New GET /api/v1/changelog and GET /api/v1/status, and every response object now has a JSON Schema generated from the same source as OpenAPI. Havoptic-Version 2026-11-01.
- Added GET /api/v1/changelog (this document; Accept: text/markdown for markdown).
- Added GET /api/v1/status: dataset_updated_at, intelligence_since, last ingest, and per-source freshness (last_success_at, last_error, last_release_at).
- GET /api/v1/schemas/{name}.json now serves release, release_summary, change, product, vendor, upgrade_report, digest, search_results, list, problem, meta, changelog and status.
- OpenAPI components.schemas is generated from packages/core/api-schemas.mjs; /vendors, /tools/{id}/latest and /tools/{id}/upgrade are documented.
- infographicUrl9x16 and infographicUrl9x16Display are now absolute URLs, like the other infographic fields.
References: issue #1942, issue #1943, issue #1944
2026-10-18: MCP v2 tools, JSON Schema exports, breaking/security feeds
MCP v2 tools with markdown and structuredContent (the original 8 tool names keep working), GET /api/v1/schemas/{name}.json, and filtered breaking/security feeds. Havoptic-Version 2026-11-01.
- MCP server (https://mcp.havoptic.com/mcp) registers v2 tools alongside the legacy tool names.
- Added GET /api/v1/schemas/{name}.json (JSON Schema 2020-12) for release and change.
- Added breaking-change and security RSS/JSON feeds built from typed change items.
References: PR #1930
2026-10-18: Release intelligence REST endpoints
Typed change items, digests, search, vendors, latest-release and upgrade reports; cursor pagination and sparse fieldsets on /releases. Havoptic-Version 2026-11-01.
- Added GET /api/v1/changes (kind, tool, breaking, security, since, until, cursor).
- Added GET /api/v1/digest and GET /api/v1/tools/{id}/upgrade, both with Accept: text/markdown.
- Added GET /api/v1/search over change items and legacy notes.
- Added GET /api/v1/vendors, GET /api/v1/vendors/{id} and GET /api/v1/tools/{id}/latest.
- GET /api/v1/releases accepts cursor= (object: list with has_more/next_cursor) and fields=; offset= now sends Deprecation and Sunset headers.
- Release objects carry changes_available; legacy (pre-intelligence_since) releases report false with null has_breaking/has_security.
References: PR #1929
2026-10-18: Forward-only typed change extraction
Releases first detected after intelligence_since get evidence-checked typed changes, a neutral abstract, and detected_at; older releases are never backfilled automatically. Havoptic-Version 2026-11-01.
- New release fields on enriched releases: abstract, highlights, counts, has_breaking, has_security, changes, notes, ai, quality, detected_at.
- Added the data/changes.json projection of typed change items.
References: PR #1928
2026-10-18: Single tool and vendor registry
packages/core/registry.json became the one source for tool ids, display names, vendors, the intelligence_since cutover and the Havoptic-Version date. Havoptic-Version 2026-11-01.
- Tool id enums across the API, OpenAPI, llms.txt and agents.json come from the registry.
- meta.api_version reports the registry api_version.
References: PR #1927
2026-10-18: Contract and data-quality fixes
Validated query parameters with RFC 9457 errors, absolute URLs, date precision, ETag/304, and usage metering. Havoptic-Version 2026-11-01.
- Invalid filters (e.g. type=patch) return 400 application/problem+json with a param field.
- Added the computed bump filter and channel alias on GET /api/v1/releases.
- Infographic and source URLs are absolute; datePrecision is reported per release.
- Responses carry weak ETags and Last-Modified; If-None-Match / If-Modified-Since return 304.
- llms.txt and agents.json are generated from the tool registry.
References: PR #1926