Serialization & Deserialization for Requests

Model Database Inference Endpount comes with a default serving container which is used for all supported Transformers and Sentence-Transformers tasks and for custom inference handler. The serving container takes care of serialization and deserialization of the request and response payloads based on the content-type and accept headers of the request. That means that when you send a request with a JSON body and a content-type: application/json header, the serving container will deserialize the JSON payload into a Python dictionary and pass it to the inference handler and if you send a request with a accept: image/png header, the serving container will seralize the response from the task/custom handler into a image.

Below is a list of supported content-types and the deserialized payload that is passed to the inference handler.

Below is a list of supported accept headers and the serialized payload is returned.