# Overview & Benefits *** Yecho's Enterprise API Service is designed for **dApps**, **protocols**, and **enterprises** that want to offload the heavy lifting of on-chain data reading, yield calculations, and storage. Instead of building and maintaining your own infrastructure for tracking user incomes/borrows, you can delegate it all to Yecho and simply query a single endpoint to get real-time, accurate data for your users. #### Key Benefits for Enterprises * **Complete Delegation**: Yecho handles all on-chain reads, calculations of daily incomes (e.g., yields from positions) and borrows (e.g., costs from loans), and secure data storage. No need for your team to manage RPC calls, indexing, or databases freeing you to focus on your core product. * **Seamless Integration**: Call one simple endpoint with a user's address to retrieve their full yield history. Integrate it directly into your frontend for a smooth user experience (e.g., show "You earned $X today from your Aave position"). * **Scalability & Reliability**: Supports high volumes of users and contracts without performance drops. Custom refresh rates mean data is always fresh, and we use battle-tested providers for RPCs. * **Cost Efficiency**: Pay only for what you use avoid building your own yield tracker. Plus, privacy-compliant: No unnecessary data exposure. * **Actionable Insights**: Users get granular data, boosting engagement in your dApp. For you: Potential add-ons like aggregated stats (total yields generated by all your users). This service is ideal for lending protocols, yield aggregators, or any dApp where users want to see their real daily earnings without you handling the backend complexity. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.yecho.app/integrations/enterprise-and-api/overview-and-benefits.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.