> ## Documentation Index
> Fetch the complete documentation index at: https://developers.meshapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog: August 2026

> What changed in Mesh in August 2026.

**August 2026**

Dated API versions; Anthropic Messages API; Node.js SDK 2.0

## Pin the API contract to a date

Mesh now versions its public contract **by date**, in a request header. The current
version is `2026-08` (released 15 August):

```bash theme={null}
curl https://api.meshapi.ai/v1/models \
  -H "Authorization: Bearer rsk_..." \
  -H "X-Mesh-Version: 2026-08"
```

A pinned request states which response shapes your code can parse, so a future change to
those shapes cannot reach it. `/v1` stays exactly where it is — it is a namespace, not a
version, and there is no `/v2` planned.

**You do not have to do anything.** Sending no header gets you the *oldest* supported
version, so publishing a new one never moves existing traffic.

* `GET /v1/api-versions` lists every version served, with its `status`, release date,
  and which one is the `baseline` and which is `latest`.
* An API key can carry a pin, so code you do not control still gets a fixed contract —
  set it on the key's **API Version** field under **API Keys**. A header on the request
  wins over the key's pin.
* Every response echoes `X-Mesh-Version` with the version that served it.
* A version Mesh does not serve is rejected with `400 invalid_api_version` rather than
  silently downgraded, so a typo'd pin fails immediately instead of quietly serving you
  something else. The error body lists `supported_versions`.

When a version is eventually retired, its responses will carry standard `Deprecation` and
`Sunset` headers first, so monitoring can notice before anyone reads a page. Nothing is
deprecated today.

Full detail: [API versioning](https://developers.meshapi.ai/docs/reference/api-versioning.md).

## Anthropic Messages API

`POST /v1/messages` speaks Anthropic's Messages format, so a client built on Anthropic's
SDK, [Claude Code](https://developers.meshapi.ai/docs/capabilities/claude-code.md) included, can point at Mesh unchanged
and address any model Mesh serves, not only Claude. Streaming, tool use and vision are
supported. See [Messages API](https://developers.meshapi.ai/docs/capabilities/messages-api.md).

## Playground saves conversations

The dashboard's chat Playground saves each conversation as a thread, together with the
request configuration that produced it, so reopening a thread restores the run. Threads
are visible only to you.

## Node.js SDK 2.0.0 — the request id rides on what each call returns

**Breaking:** `MeshAPIConfig.onResponse` and the `ResponseInfo` type are gone. The hook
was configured once per client, so with several calls in flight it could not say which
response belonged to which call.

The id now lives on the value the call returned:

```typescript theme={null}
const completion = await client.chat.completions.create(params);
console.log(completion.requestId);

const stream = client.chat.completions.create({ ...params, stream: true });
console.log(await stream.requestId); // resolves when headers arrive, before the first chunk
for await (const chunk of stream) { /* ... */ }
```

* Every streaming method returns an `SSEStream<T>`, an `AsyncIterable` that also carries
  `requestId` as a promise. It stays readable after a mid-stream failure or an abort,
  which is when you most want it.
* `SSEStream.cancel()` releases the connection for a stream you read the id from but
  never iterated. It is also wired to `Symbol.asyncDispose` for `await using`.
* Breaking out of a `for await` over a stream now closes the connection; previously it
  leaked the socket.
* Iterating one stream object twice no longer issues, and bills, a second request.
* Errors raised from a mid-stream error frame no longer report an empty `requestId`.

Widening the return types is source-compatible: only code that set `onResponse` has to
change. See [Streaming](https://developers.meshapi.ai/sdk/streaming.md) and [Error handling](https://developers.meshapi.ai/sdk/error-handling.md).

## SDK releases

* **Node.js 2.0.0** — request id on every returned value; `onResponse` removed (above).
* **Node.js 1.0.4** — repaired Responses API streaming and the realtime ESM entry point;
  clearer error messages; `models.free()` / `models.paid()` now filter server-side via
  `?free=`; the SDK version header matches the package version again.
* **Node.js 0.1.2** — exposed `x-request-id` on successful responses via `onResponse`
  (superseded by 2.0.0 four days later). Tagged `v1.0.2` in the repository.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.