There is a specific gap most engineering teams have and cannot see. Here is how to find it.

Most teams that have invested in API test automation will tell you the same thing when you ask how their testing is going: "We have a pipeline. Tests run on every PR. Coverage looks solid."

Then they ship a bug that the pipeline should have caught. And when they dig into why, the answer is almost never "the tests didn't run." It is almost always "the tests didn't cover that."

This is the gap that a maturity model for API testing exists to name. And it turns out to be structured in a way that makes it invisible unless you are specifically looking for it.

The Two Axes Nobody Separates