Move your inference API to HIPS

Keep the client patterns you know. For supported OpenAI-style integrations, the intended starting point is three settings: your HIPS API key, base URL, and model.

Our migration guide will help you choose a model, check the features your application uses, and compare results before moving traffic.

Review the endpoints, parameters, response fields, streaming behavior, structured outputs, and tool calls your application depends on. A shared client format does not mean every provider feature or model behavior is identical.

For image, audio, video, and specialist tasks, follow the relevant task guide. Some workflows may require asynchronous jobs or a different request shape.

Start with a small representative set of inputs. Compare output usefulness, errors, latency, and measured cost. Confirm the applicable data-use policy and execution requirements.

Add streaming, concurrency, and failure handling after the simplest request works. Follow the documented rate limits and retry rules, including how charges are handled. Do not assume that every failed or retried attempt has the same billing outcome.

The rules are on Retries and billing outcomes and Data handling.

Keep your existing configuration recoverable. Begin with limited traffic and use the Console to understand results and usage. Expand after the integration and selected models meet your requirements.

Three settings move; three things do not behave as a drop-in. Nothing is silently dropped: a field that would change the output or the bill and that the named model cannot honor is a 400, never ignored. Nothing is silently substituted: the model served is the model named. A requirement is never weakened to make a request succeed.