Skip to main content
After deploying model and routing traffic to it, you can send requests to the endpoint using the same inference APIs as serverless models. Features available on the underlying model work the same way on DMI, including: Dedicated model inference is served at https://api-inference.together.ai. There’s no CLI for inference, so send requests with curl or the SDK, pointing the base URL at https://api-inference.together.ai/v1. Pass the endpoint string as the model parameter, and use the same request shape you’d use against a serverless model. The endpoint string has the form your-project-slug/endpoint-name:

Prompt caching

Prompt caching stores the result of previously processed prompt prefixes so the model can reuse them instead of recomputing. It reduces redundant compute for repeated prefixes, such as a system prompt that’s shared across many requests. Prompt caching is enabled by default for dedicated model inference. No configuration is required.

Decoding optimizations

Decoding optimizations such as speculative decoding are set by the config your deployment runs on. To change them, deploy a different config.

Next steps

Create a deployment

Set the traffic split that drives routing.

Route traffic

See how the endpoint resolves each request to a deployment.