POST /v1/messages serves the Anthropic Messages shape over the same memory wrapper as
Chat, so an application built on the Anthropic SDK gets memory by
changing its base URL.
x-api-key (what the Anthropic SDK does) or as
Authorization: Bearer, the same Anona key either way.
The shape is a wire format, not a provider: an Anthropic-shaped request does not mean
Anthropic inference, and you never supply a provider key.
model chooses from what
this deployment serves. Omit it for the default, or name one from
model selection; a model this deployment does not
serve returns 400 unsupported_model.Request
All memory tunables apply here, in the body or as
X-Anona-* headers.
Response
memories_injected and space_id are the Anona additions, and also arrive as the
X-Anona-Memories-Injected and X-Anona-Space-Id response headers.
Streaming
"stream": true emits the Anthropic named-event sequence: