Pricing Configuration

Tasks can be priced in a wide range of strategies using the pricing_config attribute. All Pricing Configuration settings must have a config_type value which controls the other attributes that must be provided in the object.

Regardless of what Pricing Configuration is used, all forms of user payouts are decided based off when a user enters the Task. If the payout changes when the user is attempting the Task, it does not change the compensation of the user's current attempt. This goes "both ways", regardless if the payout was increased or decreased.

Simple

The most simple pricing configuration looks like:

{
  "config_type": "simple",
  "cpi": 1000
}

This represents a Task that will pay $1.00.

Auto-Adjust

A simple auto-adjust pricing algorithm is available for a WXET Task. The example below represents that a Task will pay somewhere between $.75 – $2.00 and will initially be available at $1.00. The Auto-Adjust pricing strategy attempts to decrease the pay as low as possible that ensures the Task will get completed by the end_date.

{
  "config_type": "auto-adjust",
  "starting_cpi": 1000,
  "maximum_cpi": 2000,
  "minimum_cpi": 750,
  "end_date": "2024-10-04T12:28:33.242411Z"
}

Additional examples are coming soon that demonstrate dynamic pricing strategies which will allow more sophisticated pricing strategies giving real-time WXET Supply Network traffic conditions beyond the Auto-Adjust strategy.

Last modified: 01 October 2024