Weights

Any request to Pulze will result in the selection of a particular model, based on the most suitable model matching your criteria.

This criteria is a combination of several factors (including which models are enabled, or how creative you want the response to be) but it’s also strongly veered by the interaction between three key forces: quality, cost, and latency, which can be pre-configured in the App’s settings.

• quality (higher is better)
• cost (higher is cheaper)
• latency (higher is faster)

As a quick example, quality = 0.7 and cost = 0.3 (same as quality = 7, cost = 3) will favour quality of the response, but taking into consideration that the model isn’t expensive.

​

Example

The above example will modify the weights for that request only — which might result in a different model being chosen.

If you send Pulze-Labels header, the weights will be stored as part of the Labels in this format:

{
  "weights_cost": "0.2",
  "weights_quality": "0.8",
  "weights_latency": "0",
  ...
  "other-pulze-labels": "below",
  "foo": "bar",
  "my_obj": "{\"key\": \"value\"}"
}