Skip to content

Changelog

Newest first. Within version 1 every change is an addition (Versioning).

Documentation. The API and MCP server have their own site, generated from one OpenAPI 3.1 document (openapi.json) that is tested against the API on every change. The dashboard’s old API page now points here. Limits that were in force but unwritten are now documented: the awaiting forecast status, the 500 internal error, the bad-key limit, the 20-a-minute source limit, parameter and body length limits, and which responses carry rate headers.

Forecasts. status=awaiting on GET /forecasts returns forecasts past their deadline that are waiting for a verdict, and counts.awaiting counts them. status=open means unjudged with the deadline ahead, as on the dashboard’s Forecasts page.

MCP server. The workspace is a remote MCP server at https://dash.alethman.com/api/mcp, with one read-only tool for each endpoint that reads (MCP overview). A tool’s result is capped at 40,000 characters: long lists are cut from the end with a truncated note, and long reports are read a page at a time.

Coordination findings. Each finding names an orchestrator, the mediums carrying it hardest and a target, from the roles the reporting gives each party.

Version 1. Articles, stories, sector outlooks, forecasts, coordination findings, reports, your own sources and the workspace, with API keys, scopes, cursor pagination and the 120-a-minute limit.