API changelog tools, compared
Spec-diff generators, docs platforms with a changelog built in, generic release-notes widgets, and git-native automation: a researched map of what actually produces an API changelog, and where each one falls short.
33 stories
Spec-diff generators, docs platforms with a changelog built in, generic release-notes widgets, and git-native automation: a researched map of what actually produces an API changelog, and where each one falls short.
A researched map of what actually governs an enterprise MCP server: SDKs that write server code, gateways that add auth and rate limits in front of one, and platforms that generate and host a governed server directly.
Board and committee minutes have to be defensible. The software job is the record: a full transcript with named speakers, decisions, and owners. A checklist, and where an iPhone fits.
A researched map of the real tools behind "agent permissions": policy engines, non-human identity platforms, MCP's own OAuth flow, and cloud IAM for agents, four different layers people keep treating as one.
A precise map of the tools people reach for to keep an API contract true without hand-writing one: schema-first frameworks, code-reading generators, contract testing, and drift detection, and where each one actually stops.
URL versions, headers, dates, or no versions at all: how the four common strategies handle a breaking change, and the discipline that matters more.
Twelve checks that make API governance real: catalog, contracts, breaking change gates, auth, observability, and agent access, all enforced in CI.
An update on the Model Context Protocol roadmap and focus areas for upcoming specification releases.
A vendor-agnostic evaluation checklist for AI agent platforms: pilot-failure data, six evaluation criteria, governance pressure, and a scorecard you can reuse.
Partners, internal teams, the public, and agents all need different views of the same endpoints. Contracts make that explicit.
The updated Model Context Protocol roadmap for 2026: transport scalability, agent communication, governance maturation, and enterprise readiness, plus guidance on SEP prioritization and how to get involved.
The Transport Working Group's plan to evolve MCP beyond Streamable HTTP for enterprise-scale remote deployments.
Anthropic is donating MCP to the newly formed Agentic AI Foundation under the Linux Foundation, ensuring vendor-neutral governance for the protocol's future.
SEPs are moving from GitHub Issues to pull requests against the seps/ directory — why, and what changes for contributors.
Introducing MCP's formal governance model: Specification Enhancement Proposals (SEPs), a maintainer structure, and a community-driven process for evolving the protocol.
Showing 33 of 33 stories
You're all caught up.
Get the top AI news and tools straight to your inbox every week.
Weekly · AI news
Join 15,000+ AI enthusiasts