Compliance with API Specifications; Nonconforming API Clause Samples
This clause requires that any use or implementation of the API must strictly adhere to the provided technical specifications. In practice, this means that developers or licensees must ensure their applications interact with the API as documented, and any deviations or nonconforming uses—such as unsupported calls or modifications—are not permitted. The core function of this clause is to maintain system integrity and interoperability by preventing errors or security issues that could arise from improper API usage.
Compliance with API Specifications; Nonconforming API. GSK shall manufacture, have manufactured, store, maintain, test and release all finished API in accordance with the applicable Specifications. GSK shall provide Prometheus with a Certificate of Analysis for each batch of API shipped to Prometheus. In the event that API delivered to Prometheus pursuant to Sections 2.6(a), 4.6(b)(i), and 4.4(b)(ii) above is found to have a Nonconformity caused by GSK, then Sections 6.1, 6.2. 6.3, 6.8 and 6.9(b) shall be deemed applicable. Upon confirmation of a Nonconformity, the Parties shall meet to discuss the situation and mutually agree in good faith that there is a compelling need to replace all or a portion of such Nonconforming API after taking into account all relevant facts and circumstances, including the remaining period in the Term, the status of API manufacturing transfer activities, the nature of the Nonconformity and ability to rework, current Product inventories, Product sales and anticipated changes in Product demand. To the extent the Parties agree such Nonconforming API will be replaced, then any replacement schedule shall take into account GSK's manufacturing schedules, availability of materials to produce API, Product sales levels, Product inventories, and similar relevant considerations.