📄 When Should a Provider Be Retired
A provider should be considered for retirement when the partnership no longer meets the operational or contractual standards required to reliably serve dAPI feeds. Retirement decisions should be discussed internally and relayed to BD.
Business & Contractual Issues
- Payment disagreement — The provider disputes or refuses agreed-upon payment terms and the issue cannot be resolved.
- Deployment non-compliance — The provider refuses to perform deployments as instructed or consistently fails to follow the agreed deployment process.
- Deployment non-participation — The provider repeatedly fails to attend or engage in scheduled deployment windows.
Technical Quality Issues
- Degraded API quality — The provider's API shows a sustained decline in reliability, accuracy, or uptime that does not improve after feedback is shared.
- Degraded data feed quality — The data feeds served through the provider no longer meet the quality thresholds required for dAPI operation.
Operational Issues
- Unresponsiveness — The provider consistently fails to respond to communications within a reasonable timeframe, blocking operational or technical coordination.
- Failure to meet updated criteria — If new provider requirements are established and the provider cannot or will not meet them within an agreed timeline.
Retirement Process
- Document the specific issue(s) and any prior feedback shared with the provider.
- Raise the situation with BD and relevant stakeholders.
- If the issue is remediable, give the provider a defined window to address it before proceeding.
- Once the decision is made, coordinate with the team to remove the provider's feeds from active dAPIs and
api-integrations
Owner: Mertcan