Governance that scales: API Score as the pipeline gate in Gravitee
API standards written as API Score rules can score every API's configuration in seconds and gate a CI/CD deployment, naming the failing rules back to the developer
Pre-release buildInternal only
Say while it plays
The ruleset is Spectral underneath, with JavaScript functions for custom checks, and it is just a file, so the standards can live in Git and go through review like any other change.
Scoring reads the API definition and its documentation, not traffic: an evaluation came back in seconds and named each failing rule in the standard's own words, with no meeting or pull request.
A score is a snapshot until something evaluates again, and API Review adds an accept or reject step against your own checklist for the design calls a ruleset cannot make.
Don't claim
Don't claim only the pipeline deploys: at 9:16 Sam deploys by hand before the gated run, so the recording does not show a pipeline-only sequence where a failed run left no deployment.
Don't claim the anonymous call went from 200 to 401: the recording says so at 14:14 but never shows it.
Don't claim Promote sits in the gateway or that a promotion was shown: it is in the console and none is shown. Also unverified: that you cannot review your own APIs (12:01) and that the box runs APIM 4.13 (1:02).