Integrators

Versioning and changes

Where to read the API, MCP server and method versions, what is stable (fields are added, never renamed or removed without notice here), and the dated list of changes.

Last reviewed 1 Nov 2026

Reading the version

What	Version	Where to read it
REST API	`0.1.0`	`info.version` of `https://coastal-intelligence.triskelionaisystems.com/api/openapi.json`
MCP server	`1.0.0`	The `serverInfo.version` of the `initialize` response (server name `coastal-intelligence-agency`)
Risk index method	`risk-index/2`	The `method` field of every risk index row and result

There is one version of the partner API at a time; no version prefix in the paths, no version header. A client that wants to notice a change compares info.version of the OpenAPI document with the value it last saw.

What is stable

The paths on the REST API page, the tool names and argument names on the MCP server page, and the five provenance fields of every row.
Fields are added, never renamed or removed, without a dated entry on this page first. New optional query parameters and new tool arguments may appear; existing ones keep their meaning.
The meaning of the status codes and of the tool-error shape (Authentication and keys).
A change of method for a derived value (the risk index, a signal) changes its method version string, which travels in the rows, so a figure can always be matched to the method that produced it.

Not covered by this promise: the routes the web app uses (tags other than the partner tags), the exact wording of error texts and notices, and the dataset registry, which follows the providers.

Where changes are announced

Here, on this page, with the date. Newest first:

Date	Change
2026-11-01	Developer documentation published: REST API, MCP server, risk index and signed exports, observations webhook, data model and licences. No API change.

Integrators, data engineers

REST API

The base URL of this deployment, every partner endpoint with its parameters, the date rules, the response envelope field by field, examples in curl, Python and JavaScript, and the live OpenAPI reference.

Last reviewed 1 Nov 2026 Data engineers, legal and compliance

Data model and licences

The five provenance fields on every row, the three scales, what lead_hours means, the public dataset registry, the licence ids and the attribution line each one requires, and the product catalogue.