OpenPaths is an open source model router and AI gateway. One API key and one base URL (https://openpaths.io/v1) reach language, image, video, speech, music, embedding and 3D models from many providers.

Is OpenPaths compatible with the OpenAI and Anthropic SDKs?

Yes. POST /v1/chat/completions follows the OpenAI schema and POST /v1/messages follows the Anthropic schema. Change the base URL and keep your existing code.

How does OpenPaths pricing work?

Pay as you go at the provider price with near-zero markup. Requests on your own provider keys (BYOK) are recorded at $0. See https://openpaths.io/pricing.

What does openpaths/auto do?

openpaths/auto routes each request to a suitable model automatically, with automatic fallbacks when a provider fails or rate-limits.

Is there an OpenAPI spec or MCP server?

Yes. The OpenAPI 3.1 spec is at https://openpaths.io/openapi.json, the MCP endpoint is https://openpaths.io/mcp, and llms.txt plus llms-full.txt list every model id.

Speech-to-Text API (Transcription)

Upload an audio file and get text back using the same multipart request shape as the OpenAI transcription API, billed per audio hour.

Speech to Text models and pricing

Model	Provider	Context	Price
xAI Speech to Text `xai-stt`	xAI	500 MB	$0.10 / hour
Muse Voice Transcribe 1.0 `muse-voice-transcribe-1.0`	Meta	N/A	$0.18 / hour

FAQ

Is it compatible with the OpenAI SDK?

Yes. Set base_url to https://openpaths.io/v1 and use your OpenPaths API key; request and response shapes follow the OpenAI API.

Which formats are accepted?

Common audio containers such as mp3, wav, m4a, webm and ogg, up to the gateway request size limit.

How is it priced?

Prepaid, pay-as-you-go credits at close to provider list price with no subscription. The tables on this page are generated from the live OpenPaths model catalog.

Text to Speech Chat Completions Embeddings