When building a Solver, you can register actions to the MAOTO Marketplace. These actions define specific capabilities that a Solver can execute when handling tasks.
In a ride-hailing scenario, the cost of an action (e.g., booking a ride) is highly case-specific.
Factors such as distance, traffic conditions, surge pricing, and availability of drivers dynamically affect the cost.
The Solver adapts pricing in real-time before placing a bid.
Different ride-hailing providers (e.g., Uber, Lyft, etc.) may have different pricing structures, which the Solver can factor in before setting its final bid.