OpenAPI Spec Quality and Endpoint Inventory
Pricing
$5.00 / 1,000 processed specifications
OpenAPI Spec Quality and Endpoint Inventory
Review public OpenAPI 3.0 and 3.1 JSON specifications. Export endpoint inventory, security requirements, operation IDs, response coverage, missing path parameters and unresolved local references.
Pricing
$5.00 / 1,000 processed specifications
Rating
0.0
(0)
Developer
Muntasir Salim
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Review public OpenAPI 3.0 and 3.1 JSON specifications. Export endpoint inventory, security requirements, operation IDs, response coverage, missing path parameters and unresolved local references.
Who is it for?
API documentation QA, integration planning and endpoint discovery. This Actor runs automatically on Apify; use schedules, API calls or integrations to repeat a workflow.
Quick start
- Enter public URLs in the input form.
- Set a maximum output record limit and spending cap.
- Run the Actor and export the dataset as JSON, CSV or Excel. A CSV file and run summary are also saved in the key-value store.
Example input:
Output
Each successfully processed source emits one summary record followed by its data records. Records include source URL and recordType. Failed sources are listed in REPORT.errors and do not produce a paid result. A valid source with no matching records still produces a clear summary, rather than an ambiguous empty run.
Pricing
$0.005 per specification processed ($5.00 per 1,000), including platform usage. Each successfully processed URL is charged once, including its summary and all data rows within your output limit. A valid source with no matching data still counts as processed. Failed or robots-blocked sources are not charged. Set a maximum cost per run to control spending; requests stop when the remaining processing budget is exhausted.
What it does not do
OpenAPI 3.0/3.1 JSON only. No YAML, Swagger 2.0 or external $ref fetching. Does not call documented API endpoints. A documentation quality review, not full OpenAPI conformance validation or penetration testing.
Responsible operation
Public URLs only. No logins, private networks, CAPTCHA bypass, stealth proxies or LLM API keys. DNS is checked and connections are pinned to a public address. Robots.txt is respected, including each redirect target. Requests and decompressed responses are bounded. At most 50 sources, 1,000 records, and 5 MB per response. No external $ref or arbitrary URL discovered inside a document is fetched. UTF-8 input only. Respect data licenses and source terms.
Maintenance and data
Outputs remain in the calling Apify account under its retention settings. Source content is untrusted and treated as data. Monitoring results can change when websites change; check important decisions against the source. No warranty of continued source availability, customer demand or revenue.
