Changelog

​

Messages now default to feed semantics

• Changed GET /api/v1/messages and list_messages to return eligible messages even when they have no linked extracted events.
• Kept assetIds, directions, and eventTypes as compatibility filters that narrow messages through linked events when supplied.

​

Documentation and MCP guidance

• Clarified the new message-feed behavior in the public docs, generated API reference, and MCP filter guidance resource.
• Kept the response shape and pagination contract unchanged.

​

Broader read surface

• Expanded the documented and generated REST surface beyond events to cover messages, positions, and stats under /api/v1.
• Expanded the documented MCP surface to cover the same read-only trading data families across events, messages, positions, discovery, and stats.

​

Query and pagination updates

• Removed allTime from the public date-range contract. Time-bounded reads now use startTime and endTime.
• Standardized list-style reads on forward-only cursor pagination and documented the applied time bounds echoed back in relevant responses.

​

Access and authentication behavior

• Clarified that returned data can reflect current access and eligibility rules, so visible rows and available history can vary by caller context.
• Hardened event pagination so paging remains stable even as the currently visible result set changes.
• Added MCP support for ?api_key= as a compatibility fallback when a client cannot send authorization headers.

​

Documentation and client guidance

• Reframed the docs around a broader read-only trading data surface instead of an events-only product view.
• Added a data-reads guide, aligned public skill guidance, and refreshed client setup docs to match the expanded REST and MCP surface.

​

Task-first onboarding

• Reworked the homepage around access, path selection, and quickstarts for both REST and MCP.
• Added concrete MCP setup guides for Claude Code, Cursor, and Codex.

​

API reference improvements

• Strengthened the generated OpenAPI-backed reference with richer examples and schema descriptions.
• Kept Swagger available as a secondary technical artifact rather than the primary docs surface.

​

Information architecture

• Kept the top-level Documentation, API reference, and Changelog tabs.
• Moved public skills into a more clearly supplemental role within the docs.