Example 1
- 4 public
- 3 PII
- 2 auth
- 3 deps
API exposure index: 50 / 100
The calculator uses the numbers you enter. With 4 public, 3 PII, 2 auth, 3 deps the result is API exposure index: 50 / 100. This is not a penetration test.
The calculator uses the numbers you enter. With 4 public, 3 PII, 2 auth, 3 deps the result is API exposure index: 50 / 100. This is not a penetration test.
This is not a penetration test. Fairness gap is on Fairness gap.
Enter data and click Calculate.
API exposure in this calculator is the mean of four 1 to 5 scores, then a 0 to 100 scale. With 4 public, 3 PII, 2 auth, 3 deps the result is API exposure index: 50 / 100.
score = mean(map15) × 100. map15 = (x − 1) / 4. The formula uses auth and PII.
API exposure index: 50 / 100 is not a penetration test. Another set of numbers gives API exposure index: 38 / 100, and a further set gives API exposure index: 69 / 100. Empty optional fields do not change the result.
Fairness gap answers a different question. Documentation does too. Here 4 public, 3 PII, 2 auth, 3 deps leave API exposure index: 50 / 100.
Type 4 public, 3 PII, 2 auth, 3 deps and click Calculate. Two more ready sets sit under the form: API exposure index: 38 / 100 and API exposure index: 69 / 100.
Other numbers on the same labels move the result. The first example gives API exposure index: 50 / 100.
score = mean(map15) × 100. map15 = (x − 1) / 4.
The calculator uses the numbers you enter. With 4 public, 3 PII, 2 auth, 3 deps the result is API exposure index: 50 / 100. This is not a penetration test.
API exposure index: 50 / 100
The calculator uses the numbers you enter. With 4 public, 3 PII, 2 auth, 3 deps the result is API exposure index: 50 / 100. This is not a penetration test.
API exposure index: 38 / 100
With 2 public, 2 PII, 4 auth, 2 deps the result is API exposure index: 38 / 100.
API exposure index: 69 / 100
With 5 public, 5 PII, 1 auth, 4 deps the result is API exposure index: 69 / 100.
API exposure index: 50 / 100. This is not a penetration test.
API exposure index: 38 / 100.
API exposure index: 69 / 100.
No. It is the result from the numbers you enter.
No. Empty optional fields do not change the result.
That calculator answers another question. Here API exposure stays at API exposure index: 50 / 100.
Yes. A comma and a dot mean the same in a number field.
No. The result comes from the numbers you enter. a penetration test sits outside this calculator.
Yes. That is the second example under the form.
The calculator takes the mean of four 1 to 5 scores: publicness, data, authentication, and dependencies. Each score is mapped to 0 to 1 with (score - 1) / 4, then the mean is multiplied by 100. In the first example the result is API exposure index: 50 / 100.
Each field is a score from 1 to 5. 1 is low and 5 is high. The fields are not percent weights; they enter the mean with equal weight.
No. The result is a heuristic from the scores you enter. The calculator is not a penetration test and does not scan an API.
Not separately. A high auth score and low publicness enter the same mean. No field multiplies the others.
The terms come from EU acts. The calculator result is a sketch index, not a regulator decision.
Page updated in 2026.