Project websites are generally intended as a way for project teams to communicate with their communities. Project websites tend to be a bit of a grey area with regard to intellectual property tracking requirements. In general, CQs are not required to track content that is used in a project website. As Kai stated, however, it is imperative that the terms of the license be respected.
The reason why we allow this flexibility with websites is that we do not generally expect that folks will build products based on the content of a project website.
A Swagger-based API feels like something different. I believe that it is reasonable to expect that an individual or organization might incorporate your Swagger-based content into a product, which effectively makes your Swagger-based content "project code" (core content) that must be taken through the process.
According to IPzilla, we have multiple versions of Swagger approved, so getting that through as "license certified" third party content should be pretty quick.
Wayne