RouteMux Docs
Api referenceAudio

语音转文本(OpenAI 兼容)

POST
/v1/audio/transcriptions

以 multipart/form-data 提交,音频放在 file 字段。

计费单位取决于模型:通常按输入音频的秒数计,但也存在按 token 计的模型。先看该模型的定价。

Authorization

bearerAuth
AuthorizationBearer <token>

Authorization: Bearer <your RouteMux API key>.

Create keys at https://routemux.com/console/keys. New keys use the sk- prefix; the legacy rmx_live_ prefix is still accepted.

The Anthropic SDK's x-api-key and the Google SDK's x-goog-api-key are accepted too. Sending several key headers with different values returns 400 AUTH_AMBIGUOUS_API_KEY.

In: header

Request Body

multipart/form-data

TypeScript Definitions

Use the request body type in TypeScript.

Request and response bodies match the upstream provider's official format verbatim — RouteMux passes them through untouched. See the provider's own docs for field definitions; the gateway itself only reads model and stream.

Response Body

application/json

application/json

application/json

curl -X POST "https://example.com/v1/audio/transcriptions"
{  "model": "string",  "stream": true}