Shodan exposes several values called “credits,” but they are not interchangeable. Query Credits cover searches and data retrieval, while Scan Credits cover requests to scan IP addresses.
Core distinction
Query Credits retrieve data; Scan Credits request scanning
Used for filtered queries, later result pages, and API or CLI data retrieval.
Used for on-demand scanning. Official guidance generally counts one Scan Credit per IP.
Query Credits: search and retrieval quota
Shodan documentation describes one Query Credit as enabling download of 100 results. API or CLI requests that use filters or request page two and beyond commonly consume Query Credits.
Scan Credits: on-demand scanning quota
Scan Credits ask Shodan to crawl a specified IP or range. Official on-demand scanning guidance uses the baseline of one Scan Credit per IP.
Only scan assets you own or are explicitly authorized to assess, and follow applicable law and Shodan terms.
Why both numbers matter
- Search and data analysis primarily depend on Query Credits.
- Refreshing a specific authorized asset depends on Scan Credits.
- Continuous monitoring also depends on monitored IP capacity and plan permissions.
- Examples and screenshots do not replace a live api-info response.
Refresh and usage recommendations
Both credit types refresh monthly under current official guidance. In practice:
- Call api-info after delivery and record the initial state.
- Test bulk jobs at small scale to observe consumption.
- Add rate limits, bounded retries, and quota alerts.
- Avoid unnecessary repeated paging or scanning.
References
This article supports product understanding, development learning, and lawful authorized use. Third-party documentation, software versions, and platform rules may change.
Frequently asked questions
Can Query Credits and Scan Credits be exchanged?
No. Query/data retrieval and on-demand scanning use separate quotas.
When do credits refresh?
Shodan documentation says query and scan credits refresh at the start of each month; the amount depends on the account plan.
Does every search consume Query Credits?
Not necessarily. Filters and pages after the first are examples that can consume credits through the API or CLI. Confirm current rules for the endpoint you use.