dynamo-protocols

Request/response types for OpenAI- and Anthropic-compatible inference servers. Built on async-openai v0.34, with selective overrides where inference engines need behaviors upstream doesn't support.

What's included

• Chat Completions — multimodal content, reasoning content (DeepSeek-R1 / QwQ), continuous usage stats, tool-calling.
• Batch API — re-exported from upstream.
• Files API — re-exported from upstream.
• Responses API — input chain owned (relaxed for Codex / Agents SDK); output chain re-exported from upstream.
• Completions — re-exported.
• Anthropic Messages — fully owned (no upstream equivalent).
• Embeddings, Images — re-exported.

Locally-defined extensions

A few fields extend the upstream async-openai schema:

• reasoning_content on assistant messages
• mm_processor_kwargs on chat-completion requests (vLLM multimodal)
• continuous_usage_stats on chat stream options
• FunctionCall.arguments accepts both string and object forms

Request compatibility and serving policy

CreateResponse accepts "text":{"verbosity":"low"} without a format. The upstream ResponseTextParam defaults the format to text. An explicit text, json_object, or json_schema format is preserved independently of verbosity. A serving adapter that cannot honor verbosity should ignore that hint while retaining the output-format constraint. Map supported fields to the engine request instead of forwarding the Responses text object.

CreateChatCompletionRequest and CreateCompletionRequest accept and preserve stream_options when stream is absent, null, false, or true. These types do not enforce cross-field streaming policy. A serving adapter that chooses permissive compatibility should clear stream_options when request.stream != Some(true) before backend validation or forwarding. Keep the options when streaming, and keep normal non-streaming response usage. This normalization belongs in the serving adapter because protocol types also serve callers that need to preserve the original request.

Run the wire-level regressions for #299 with cargo test -p dynamo-protocols --test request_compatibility.