📄 When Should a dAPI Be Retired

A dAPI should be considered for retirement when it can no longer be maintained to a sufficient quality standard, poses an unacceptable risk, or has no active or anticipated usage. Retirement decisions should be discussed internally before action is taken.

Security Issues

• Exploit or compromise — The underlying asset or protocol has been exploited or otherwise compromised in a way that makes continued operation unsafe or misleading.

Usage & Demand

• No active usage and no anticipated demand — The dAPI has no current consumers and there is no indication that it will be needed in the foreseeable future. Keeping unused dAPIs active wastes operational resources.

Data Quality Issues

• Unsustainable data quality — The data quality for the feed cannot be maintained to acceptable standards, resulting in persistent and uncontrollable alerts or unreliable values that cannot be resolved through normal operational means.

---

Owner: Mertcan