rout.my documentation

rout.my exposes a unified API for chat, embeddings, image generation, video generation, and compatibility formats used by popular clients. The docs are written around endpoint behavior instead of model preference: choose any model available to your account and pass its exact id from GET /v1/models.

Base URLs

Purpose	URL
OpenAI-compatible API	https://api.rout.my/v1
Gemini-compatible API	https://api.rout.my/compatible/v1beta
Anthropic-compatible API	https://api.rout.my/v1
Embed image URLs	https://api.rout.my/embed

Main endpoints

Endpoint	Method	What it does
/v1/models	GET	Lists model IDs visible to your account.
/v1/chat/completions	POST	OpenAI-style chat, tools, vision input, streaming, and image-capable chat models.
/v1/responses	POST	OpenAI Responses-style request shape for agents and Codex-like clients.
/v1/embeddings	POST	Text embeddings for search, retrieval, clustering, and similarity.
/v1/images/generations	POST	OpenAI-style image generation endpoint.
/v1/video/generations	POST	Synchronous video generation endpoint.
/embed/image:{model}	GET	Returns raw image bytes for direct use in HTML or Markdown.

Start here

• Quick Start shows the first request.
• Models explains model IDs and availability.
• API Explorer builds a request and can send it with your own key.
• Endpoint Matrix lists every main route in one table.
• Integrations covers common client setup.
• llms.txt gives agents a compact map of the docs.

Model IDs

The examples use neutral placeholders such as provider/model-id. Replace them with an exact id returned by GET /v1/models or copied from the dashboard.