Input is processed only in the active browser tab's memory and is not sent to a ByteQuant server.
OpenAPI Endpoint Inventory
Scans the paths object of an OpenAPI 3.x JSON document and turns methods, operationId, tags, security, and deprecated status into an inventory without making network requests.
Input and output are not stored. The optional usage counter keeps only tool identity and count, never content.
Output comes from disclosed rules or browser APIs and needs independent review before high-impact use.
A result in three steps
- 01
Load an OpenAPI JSON document.
- 02
Generate the endpoint inventory.
- 03
Verify missing security and operationId fields in source code.
When is this tool useful?
- ✓ API scope inventory
- ✓ Finding deprecated endpoints
- ✓ Pre-checking security declarations
Automated output is a preliminary assessment. Do not use it alone for legal, financial, medical, or security-critical decisions.
Guides for this tool
An API Delivery Review with NDJSON, OpenAPI, and SemVer
Validate streaming data, inventory endpoints, and verify release precedence before delivery with explainable steps.
Read guide →Frequently asked questions
Does this tool send input to a server?+
No. Processing runs in this browser tab. Data leaves the page only when you choose to copy or download the result.
Is the result definitive?+
The tool produces consistent output from disclosed rules and browser APIs, but context, data quality, and method limitations can affect it. Verify high-impact decisions.
Is input saved?+
No. Tool input is not persisted. With consent, only tool identity and usage count may be kept on this device for personal shortcuts.