---
title: "Developer changelog"
source: "https://ottom.io/developers/changelog"
summary: "The Ottom developer changelog lists every change to what a developer builds against: the HTTP API and its OpenAPI document, the MCP server, how Ottom’s agent identifies itself, and the developer documentation. Each entry is dated, says what changed and links the page that describes it, and the same entries are published as an Atom feed."
---

# Developer changelog

The Ottom developer changelog lists every change to what a developer builds against: the HTTP API and its OpenAPI document, the MCP server, how Ottom’s agent identifies itself, and the developer documentation. Each entry is dated, says what changed and links the page that describes it, and the same entries are published as an Atom feed.

Atom feed: https://ottom.io/developers/changelog.atom

## Agent identity guides, and this changelog

12 November 2026. Developer docs.

Two guides for the developer whose firewall, CDN or bot manager turned a scan away: recognising Ottom’s agent and letting it through, and blocking it or opting a store out. And this changelog, with an Atom feed.

Documented at https://ottom.io/developers/letting-ottoms-agent-through-your-firewall

## Guides for developers

12 November 2026. Developer docs.

Written guides on the developer hub, grouped by who they are for: reading a report, fixing and verifying each kind of finding, release gates in CI, and setting up an enterprise workspace, its alerts and its Order Form. Every guide has a markdown copy and is listed in llms.txt.

Documented at https://ottom.io/developers

## A public MCP server

12 November 2026. MCP server.

Check a store’s readiness for AI agents from any AI assistant over the Model Context Protocol, authenticated with a free key from your account. The reference lists its tools, their inputs, the limits and every error code.

Documented at https://ottom.io/developers/mcp

## API reference and OpenAPI document

12 November 2026. HTTP API.

A reference for the HTTP API that starts a scan from CI and reads its result, and the same contract as an OpenAPI 3.0 document at `/developers/openapi.json`, generated from the schemas the API validates requests and responses with.

Documented at https://ottom.io/developers/api

## API version 2: the release gate result

26 October 2026. HTTP API.

A scan’s result carries `gate`, the release gate result, with the reason and the checks that tripped, and `apiVersion` is 2. Every version 1 field is unchanged and means what it meant, so a version 1 client keeps working.

Documented at https://ottom.io/developers/api#read-a-scan

## Published addresses as JSON

17 October 2026. Agent identity.

The agent’s egress addresses, user agent and From mailbox are published as JSON at `/agent/ips.json`, in the shape crawler operators use for their address lists, so a script can keep a firewall rule current.

Documented at https://ottom.io/agent#addresses

## Questions

### How do I follow changes?

Subscribe to the Atom feed linked on this page in any feed reader. It carries the same entries as the page.

### Which date does an entry carry?

The day the change was made. An entry is published in the same release as the change it describes, so nothing is listed here before you can use it.

### Will a change break my integration?

A change that removes a field or changes its meaning moves the API version, and is listed here with the new version. New fields are added without a version change, so parse responses in a way that ignores fields you do not know.