> For the complete documentation index, see [llms.txt](https://docs.ai.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.neevcloud.com/api-reference/model-routing.md).

# Model Routing API

The Model Routing API is NeevAI's **serverless, OpenAI-compatible inference gateway**. It routes your requests to a shared catalog of hosted models, so you can run chat completions, list available models, and generate speech without provisioning or managing any GPU infrastructure yourself. Because the API mirrors the OpenAI request and response format, most existing OpenAI SDKs and tools work by simply changing the base URL and API key.

## What you can do

* **Chat completions** — `POST /v1/chat/completions` for single-turn or multi-turn conversations, with support for both streamed and non-streamed responses, following OpenAI's request schema.
* **List models** — `GET /v1/models` to discover the models available for routing, returned in OpenAI-style list format.
* **Retrieve a model** — `GET /v1/models/{model_id}` to fetch a single model's descriptor.
* **Text to speech** — `POST /v1/audio/speech` to synthesize audio from text.

Use the interactive reference below to inspect the request and response schemas and to try each endpoint directly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ai.neevcloud.com/api-reference/model-routing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.