What cricket analytics APIs do students build?

API projects begin with clearly defined cricket questions and measurable inputs. Students may build endpoints for current score, current run rate, required run rate, strike rate, boundary percentage, economy rate, dot-ball percentage, wicket probability, net run rate and points-table calculations. More advanced tasks can convert qualitative cricket concepts into interpretable metrics, including pressure stability, batting consistency, bowling control, shot risk, expected runs saved, catch probability, form trend, opponent effect, fatigue risk and weighted contribution. Each API should include validated input schemas, service logic, transparent formulas or model calls, sample requests, sample responses, error handling and documentation. The purpose is not only to return a number but to show how the number was constructed and when it should be trusted.