Use these terms consistently in docs, configuration, code comments, logs, and capture metadata. This page is a terminology map; exact values live in the corresponding reference pages.
request protocolThe inbound protocol detected from the local request path, such as openai_responses or anthropic_messages.
protocol, which controls outbound wire behavior.provider protocolThe outbound protocol configured on a provider; controls provider request serialization and upstream response handling.
protocol valueOne of openai_responses, openai_chat_completions, or anthropic_messages.
translation pairA directed conversion from inbound request protocol to provider protocol, for example openai_chat_completions -> anthropic_messages.
provider nameUser-defined label for a configured upstream provider.
anthropic does not automatically mean anthropic_messages.routeAn explicit model/protocol rule that selects a provider before default provider fallback.
request_protocol guardOptional route field that restricts a model match to one detected inbound protocol.
inbound_requestPipeline phase containing the local client request as ProxAI received it.
provider_request, which is after provider selection, translation, model rewrite, and serialization.provider_requestPipeline phase containing the selected, translated, serialized provider request.
upstream_responsePipeline phase containing upstream status, headers, and raw body bytes.
outbound_response, which is after response translation/reconstruction.outbound_responsePipeline phase containing the final response returned to the local client.
capture phaseNamed pipeline location where optional debugging artifacts can be written.
request hintsCompact protocol-aware log summaries that avoid private request bodies.
SSEServer-Sent Events; the streaming carrier used by OpenAI-compatible and Anthropic-style streaming responses.
terminal eventProtocol-specific event or sentinel that marks semantic stream completion, such as response.completed, [DONE], or message_stop.
semantic timeoutTimeout for a protocol-level condition, such as started-but-unfinished streamed tool-call arguments.
idle-read timeoutTransport-level timeout while waiting for upstream response bytes.
stop reasonProvider/protocol-specific reason for ending generation, such as Anthropic stop_reason.
finish_reason or Responses status; mappings are protocol-specific.client-facing error typeStable compact type value returned to clients, such as stream_translation_error.
TranslationError or SseError.