Examples
Examples
Try the starting example
- JSON Required item keys; compound keys use explicit user-defined identifiers
- ["A","B","C"]
- JSON Present valid item keys
- ["A","B","D"]
- Missing required keys
- ["C"]
- Additional keys
- ["D"]
- Required coverage (%)
- 66.666667
Try another scenario
- JSON Required item keys; compound keys use explicit user-defined identifiers
- ["A","B","C"]
- JSON Present valid item keys
- ["A","B","C"]
- Missing required keys
- []
- Additional keys
- []
- Required coverage (%)
- 100
Calculation method
Calculation method
Missing required keys
Sorted required set minus valid-present set.
Additional keys
Sorted valid-present set minus required set.
Required coverage (%)
100 × cardinality(intersection) / cardinality(required); empty requirement set returns 100.
Symbols and units
- a
- JSON Required item keys; compound keys use explicit user-defined identifiers
- b
- JSON Present valid item keys
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions & limits
Assumptions & limits
- Required account/contact/instruction compound keys versus present validated documentation keys. No credentials collected, no access granted and no legal succession claim. Supported limits: Up to 1000 keys per list. Duplicate keys are rejected. Presence is not a legal, security, scientific, or quality certification.
Are these inputs private?
These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.