API Docs and OpenAPI Discovery - Developer Portal Intelligence
Pricing
from $5.00 / 1,000 api documentation reports
API Docs and OpenAPI Discovery - Developer Portal Intelligence
Discover public API documentation, OpenAPI or Swagger files, REST and GraphQL signals, auth schemes, SDKs, rate limits, and webhook evidence.
Pricing
from $5.00 / 1,000 api documentation reports
Rating
0.0
(0)
Developer
Sean J
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 hours ago
Last modified
Categories
Share
What does API Docs and OpenAPI Discovery do?
Find public developer-resource evidence before scoping an integration. This Actor collects documentation links and API-related strings, including OpenAPI, Swagger, GraphQL, auth and webhook references from bounded public-page checks. Open the Actor to inspect its input and pricing.
Start with one website
- Paste one public URL into the Input tab, preferably the relevant policy or resource page.
- Keep evidence enabled and set a run spending limit that covers both event fees below.
- Run the check, then inspect its sources and errors before expanding the list.
Example input with one public source URL checked on 27 October 2026. Current responses and coverage may differ:
Read the evidence
Start with the returned resource URLs and inspect each source yourself. An OpenAPI-like link or versioned endpoint string is a discovery candidate, not proof that a specification was downloaded, validated or successfully called.
| Field | How to use it |
|---|---|
status, confidence | Signal-detection status and a heuristic score, not a probability of correctness. |
extracted.apiArtifacts | API-related links and endpoint-like text for manual verification. |
findings | Short source snippets when includeEvidence is enabled. |
coverage, errors | Request/download limits and problems affecting what was checked. |
Export JSON or CSV with retrievedAt and your source notes so a later comparison retains its original context.
Scope and limits
The Actor does not authenticate, validate an API contract or test endpoint operations. Documentation hosted outside the submitted host’s allowed domain may not be followed.
Checks use static public responses, without browser execution or login. Each site is bounded by 20 seconds, 1 MiB downloaded and 4 MiB decoded text; redirects and failed requests consume maxPagesPerSite attempts. Submit at most 100 combined URL/domain entries, including duplicates. An undetected signal is not proof of absence.
Pricing and spending control
Event fees are $0.002 per attempt (website-processed) plus $0.005 per useful report (api-docs-report): $0.007 when both apply. Check the Pricing tab for the current rates. The report fee requires FOUND or PARTIAL with useful detected signals or extracted evidence. Failed or empty resource probes do not qualify; ordinary NO_SIGNAL/FETCH_FAILED output incurs only the attempt fee.
Budget for both fees before starting a website, and check the Pricing tab for platform terms and plan charges. Review RUN_SUMMARY before repeating billing/output uncertainty, because a retry is a new chargeable check.
Responsible use and support
Use permitted public targets and review their terms. Send a sanitized input through the Issues tab for support or a scope discussion.
