Data-only OpenAI-compatible provider alias specs.

These providers share the OpenAI chat-completions wire shape. Adapter code
may still apply provider quirks from the profile, but the registry should
not need one hand-written register-provider call per alias.

OpenAI audio provider family namespace.

OpenAI Chat Completions transport adapter.
Covers OpenAI, OpenRouter, DeepSeek, and other OpenAI-compatible providers.

OpenAI embeddings adapter — POST {base}/embeddings.

Same auth and base-url plumbing as the chat adapter; we share the
profile, just register an additional :profile/embed-transport-
constructor on it. Other OpenAI-compat hosts that offer embeddings
(Mistral, Together, Voyage, Jina, etc.) can reuse this transport by
attaching the same constructor.

OpenAI image generation adapter.

POST {base}/images/generations. A model is required because the former
implicit DALL-E models were retired on 2026-05-12. Explicit caller-selected
DALL-E 2/3 requests retain their documented wire contracts; GPT Image
requests use the current GPT-specific contract.

OpenAI Moderations adapter.

POST {base}/moderations. omni-moderation-latest (the default since
Nov 2024) accepts multi-modal input — a vector of {:type :text|:image_url}
maps as well as plain strings. text-moderation-* models are
text-only.

Response shape per the OpenAI Moderations API:
  {:id :model
   :results [{:flagged bool
              :categories {category-name bool}
              :category_scores {category-name float}
              :category_applied_input_types {category-name ["text"|"image"]}}]}

OpenAI /audio/speech adapter — POST {model, voice, input, response_format}
returns raw audio bytes.

OpenAI and Groq /audio/transcriptions adapters. The endpoints share
multipart mechanics, but provider-specific request policies are enforced
before fields are serialized.