Embeddings API

/v1/embeddings is not part of the public BotConnector hosted contract. A client pointed at https://api.botconnector.id/v1/embeddings will not get a vector back.

This is a boundary, not an outage: the route is listed with the other endpoints that are not yet public, and unsupported routes return an explicit error instead of being quietly routed to a different provider. That way a failure in your pipeline is never a surprise result.

Do not build on it yet

Do not make an external client, an index, or a stored migration depend on this hosted route. An endpoint that answers today under an unpublished contract can change without a deprecation cycle, and embeddings are expensive to re-derive once a corpus has been indexed.

What you can use today

For embeddings inside an application, the local path is documented and stable: Embedding models covers running an open embedding model on your own machine and calling it through BotConnector Local.

Text generation is unaffected — POST /v1/chat/completions is public and works with any model ID from GET /v1/models.

Checking the boundary yourself

The Hosted Developer API page lists the verified routes and, at the bottom, everything that is deliberately outside the contract: Embeddings, Files, Vector Stores, Rerank, Audio/Realtime, and fine-tuning. That table is the source of truth; if a route is not on it, treat it as unavailable.