feat(messages)!: add Anthropic Message Batches API

[cdoern]

Summary

Adds all 5 Anthropic Message Batches API endpoints under /v1/messages:

• POST /v1/messages/batches — create a batch of message requests
• GET /v1/messages/batches — list batches with pagination
• GET /v1/messages/batches/{id} — retrieve batch status
• POST /v1/messages/batches/{id}/cancel — cancel an in-progress batch
• GET /v1/messages/batches/{id}/results — stream results as JSONL

The implementation follows the same architecture as the existing OpenAI Batches provider: KVStore persistence, background asyncio tasks with semaphore-based concurrency control, and reuse of the existing create_message() flow for processing individual batch requests.

Breaking change

MessagesConfig now requires a kvstore backend (KVStoreReference). Existing distributions are updated via codegen; out-of-tree configs will need to add this field.

Test plan

• Integration tests added at tests/integration/messages/test_message_batches.py covering create / retrieve / list / cancel / results / duplicate-custom_id / 404, running under the messages-openai suite (already wired into tests/integration/ci_matrix.json)
• Recordings committed against openai/gpt-4o so replay-mode CI works without an API key
• Pre-commit checks pass (ruff, mypy, API spec, Anthropic coverage)
• Unit tests pass
• OpenAPI spec auto-regenerated with new endpoints
• Distribution configs (ci-tests, starter) updated via codegen

Locally verified:

./scripts/integration-tests.sh \
  --stack-config server:ci-tests --setup gpt \
  --file tests/integration/messages/test_message_batches.py
# 6 passed in 1.76s

🤖 Generated with Claude Code

[github-actions]

✱ Stainless preview builds

This PR will update the llama-stack-client SDKs with the following commit message.

feat(messages): add Anthropic Message Batches API

Edit this comment to update it. It will appear in the SDK's changelogs.

✅ llama-stack-client-go studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (5 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches/{message_batch_id}/cancel`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}/results`

✅ llama-stack-client-node studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (5 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches/{message_batch_id}/cancel`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}/results`

✅ llama-stack-client-python studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (5 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches/{message_batch_id}/cancel`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}/results`

✅ llama-stack-client-openapi studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️

New diagnostics (5 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `post /v1/messages/batches/{message_batch_id}/cancel`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/messages/batches/{message_batch_id}/results`

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-04-22 19:29:36 UTC

[cdoern]

not sure why backwards compatibility test is failing, I added ! in.