Please describe your proposed solution.
MuesliSwap is already providing an API endpoint that is used by different providers like Discord price bots etc. Our goal is to optimize our API endpoints and consult with other DApps to propose an API endpoint standard. Moreover, we are planning on providing detailed documentation for this API endpoint such that new projects can easily adopt the endpoint and profit from a set of rich documented endpoints. Creating this standard API structure involves consultation with other Cardano protocols, creating documentation and implementing a reference endpoint for MuesliSwap.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
Our endpoint structure, if adopted, will make it possible for Cardano DApps to be easily integrated into new applications. Moreover, users that want to connect DApps to their portfolio trackers can more easily profit from an easy, well-documented API standard. Other DApps are also not required to put additional effort and money into creating their own structure for API endpoints. Also, new developers building applications on top of available DeFi DApps can profit from a unified API standard to aggregate information.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
As we already have a general idea of how the API endpoints could look, we don’t see any risk that the project can’t be finished. Also, we will not encounter any budget problems as any extra costs will be covered by the MuesliSwap team.