Endpoint

Files

ModRouter registers OpenAI-compatible file routes under /openai. With base_url=f"{base_url}/openai", OpenAI SDK calls use the first route form below; clients configured with /openai/v1 use the second. Example:

Batches

ModRouter registers OpenAI-compatible batch routes under /openai: Example:

Containers

ModRouter also exposes OpenAI-compatible container and container-file routes under /openai/containers and /openai/v1/containers. Use these only with providers configured for container operations. Unsupported providers return a normal ModRouter provider error.

Cross-Provider Notes

OpenAI SDK routes can target other providers when ModRouter can translate the operation. Include provider information through the model name or operation-specific request fields supported by ModRouter. For provider-native batch or file semantics, use the matching provider integration:
  • Anthropic inline message batches: /anthropic
  • Google GenAI files and batches: /genai
  • Bedrock model invocation jobs and S3-compatible file routes: /bedrock