Developers

Changelog

Platform release notes and breaking-change notices.

Current version
v1 — specified, not yet served
Public releases
None yet
Deprecations scheduled
Two

Overview

What a changelog means here

Once /v1 serves traffic, it is never modified in place. A breaking change requires a new version, a deprecated endpoint announces itself in Deprecation and Sunset response headers, and migration documentation is published before removal rather than after. Those rules are in force now, while the surface is still a specification — which is why the first entries below exist at all.

Breaking changes are announced ahead of the release, not described after it.

Deprecations

Already scheduled, before first release

Two endpoints were superseded as the AI surface grew, and were deprecated rather than deleted. Both remain in the document and will keep working until their sunset date.

POST /ai/messages

Superseded by POST /ai/conversations/{id}/messages — a message belongs to its conversation. Sunset 2027-02-06.

Deprecated

POST /ai/search

Superseded by POST /ai/knowledge/search — a search over knowledge lives under knowledge. Sunset 2027-02-06.

Deprecated

History

How the specification grew

The surface was designed in phases, each building on the last. Most recent first.

Reference implementations

A TypeScript SDK client and an in-memory sandbox reference server now exist, with tests in which the client drives the server over real HTTP through the quick-start and game-economy loops — headers, envelope, idempotency, rate limits, double-entry ledger, reward evaluation, redemptions, transfers and signed webhook delivery, all to the specification. The SDK and the specification artifacts are open source at github.com/matinee-ai/sdk under MIT, with CI running; the sandbox server remains in the platform repository, and nothing is on npm or deployed.

Reference

Workflow automation surface

Workflows, versions, validation, simulation, executions and approvals. Published versions are immutable, every loop must be bounded, and a replay is a new linked execution. Eleven new permission codes and nine new error codes.

Specification

AI agent surface

Agents, runs, memory, prompts, evaluations and usage. An agent can never exceed its creator’s permissions, high-risk tools require approval before execution, and cost limits stop a run rather than degrading it silently.

Specification

Blockchain and treasury surface

Networks, deployments, transactions, treasury limits and approval policies. Deployment requires explicit confirmation with thirteen validation checks before a signature is requested, and self-approval is forbidden at the database as well as the API.

Specification

The v1 contract

Nineteen resource groups; six request headers; the { data, meta } envelope; cursor pagination everywhere; the error registry; OpenAPI 3.1 generation with Postman and TypeScript artefacts. The conventions every later surface inherits.

Specification

Data model and platform architecture

The multi-tenant schema underneath the API: double-entry ledger, idempotency records, the event outbox, append-only audit logs, and the worker architecture that processes events into rewards.

Specification

Brand, site and design system

The identity, information architecture and component system this site is built from — including the honesty rules that shape every page here.

Foundation

Announcements

How you will hear about changes

Release notes will be dated entries on this page covering what shipped, what changed and what is deprecated, with migration notes for anything breaking.

Deprecations also announce themselves in-band, through the Deprecation and Sunset headers on affected endpoints, and official SDKs report X-SDK-Version so a deprecation can be targeted at the versions actually affected.

Want release notes when they start?

Access is reviewed. Request access and we will let you know when the first deployment — and the first dated entry here — happens.