Skip to main content
PipeLLM exposes two kinds of public routes:
  • Native public routes on https://api.pipellm.ai
  • Converter routes under /openai, /anthropic, and /gemini
Use a native route only when your request already matches the target protocol. Use a converter route when you want to keep one SDK format and call models from another protocol family.

Route Matrix

Protocol Guard Rules

  • /v1/chat/completions and /v1/responses accept OpenAI-compatible request bodies and route only to OpenAI-compatible platforms.
  • /v1/messages accepts Anthropic Messages request bodies and routes only to Anthropic-compatible platforms.
  • Gemini native endpoints accept Gemini request bodies and route only to Gemini platforms.
  • Converter-prefixed routes such as /openai/..., /anthropic/..., and /gemini/... are not affected by the native-route protocol guard.

Common Patterns

Error Behavior

Protocol mismatches return a consistent JSON body:
The error message tells developers:
  • which request format was detected
  • why the native route is incompatible
  • which converter route or native route to use instead
  • which docs page to read next

API Reference Overview

Public routes and endpoint families

Converters Overview

Keep your SDK format and route across providers

OpenAI Responses

/v1/responses on PipeLLM