# Censys vs Shodan (slim)

> Censys scores 64.1 (B) to Shodan's 39.5 (E) for secintel exposure. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/censys-vs-shodan.md (~5,100 tokens) · this version ~3,480 tokens · JSON https://www.anchorterminal.com/compare/censys-vs-shodan.json · canonical https://www.anchorterminal.com/compare/censys-vs-shodan
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Censys scores 64.1 (B) on agent readiness against Shodan's 39.5 (E), and leads in 6 of 7 scored categories. Shodan leads on payments & pricing. Both do secintel exposure.

- Censys: B 64.1, rank #420 of 1349 · https://www.anchorterminal.com/tools/censys.min.md
- Shodan: E 39.5, rank #1221 of 1349 · https://www.anchorterminal.com/tools/shodan.min.md
- Censys, good for An agent that needs to know what a host, web property or certificate exposes right now and how that changed, with DNS resolution and enrichment on paid plans. Ahead on Reliability, 55 against 40; Schema & documentation, 82 against 46; Agent ergonomics, 79 against 64; Security & auth, 55 against 19; Maintenance & community, 84 against 16; Transparency & trust, 64 against 44.
- Shodan, good for An agent that needs to know what is exposed on an IP or a range, which ports, products and CVEs, and to watch a network for change. Ahead on Payments & pricing, 40 against 35.

| Category | Censys | Shodan |
| --- | --- | --- |
| Reliability (16%) | 55 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 46 |
| Agent ergonomics (13%) | 79 | 64 |
| Security & auth (14%) | 55 | 19 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 84 | 16 |
| Transparency & trust (7%) | 64 | 44 |

| Fact (where they differ) | Censys | Shodan |
| --- | --- | --- |
| Vendor | Censys, Inc. | Shodan |
| Hosted endpoint | `https://api.platform.censys.io/v3/` | `https://api.shodan.io` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Licence | Proprietary service under Censys's Terms of Service. The Platform SDKs are MIT and the cencli command line tool is Apache-2.0 | Proprietary service. The official Python library and CLI in achillean/shodan-python are MIT |
| Tools exposed | 12 | none |
| llms.txt | yes | no |
| Last release | 2026-11-02 | 2023-12-17 |
| Terms restrict benchmarking | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 11 stars | 3.5k stars |

Why the edge:
- Maintenance & community, Censys +68: Censys 84 (Newest changelog entry 2 November 2026 and censys-platform 0.16.7 on 29 October (30). Ten dated changelog entries between 8 September and 2 November and eight PyPI releases since 4 August (20). A closed service with a weekly changelog, a Gainsight community forum with Platform Q and A sections, an in-app feedback portal and support@censys.com. GitHub issue replies weren't read (12 of 15). Official SDKs in three languages regenerated from the spec, the Go and TypeScript repositories pushed on 3 November and PyPI on 29 October (15). The SDKs are 0.x and generated, with a stated grace period for dropping Python versions. CI wasn't read (7 of 10). 30 + 20 + 12 + 15 + 7 = 84.); Shodan 16 (No dated API change found. The blog's newest post is 7 August 2024, and the official Python library `shodan` 1.31.0 was published on 17 December 2023 with the repository's last push on 5 August 2024 (0 of 30). No releases or dated changelog entries in the last 90 days (0 of 20). 63 open issues on the Python repository with no push since August 2024; a support email and a help centre exist (5 of 25). The official Python SDK still installs but is two years old, and the other clients are community work (8 of 15). The repository has no CI configuration and no CHANGELOG entry since 1.28.0 of July 2022 (3 of 10). 0 + 0 + 5 + 8 + 3 = 16.)
- Schema & documentation, Censys +36: Censys 82 (OpenAPI 3.1.0, titled Censys Platform API, version 1.0.161, served inside each reference page and the source of the three Speakeasy SDKs. No standalone download was found, and the censys-sdk-openapi repository holds only a README (22 of 25). llms.txt at docs.censys.com with a Markdown twin of every page (10). Endpoint descriptions state purpose and a use case ('Run a search query across Censys data', a SOC hunting for a C2 banner, JARM or favicon hash), MCP tools say what each does, with little on when not to use a call (14 of 20). Typed path, query and body fields, `page_size` default and maximum 100, required `query`, an Accept header for schema versions. The query itself is a CenQL string with its own language docs (11 of 15). Code samples in shell, Python, Go, JavaScript and Java, a status code table and problem+json ErrorModel bodies, but the search operation's usage example block is empty and 429 isn't among its responses (10 of 15). Versioned paths and Accept header, a dated changelog every week from 8 September to 2 November 2026 (15). 22 + 10 + 14 + 11 + 10 + 15 = 82.); Shodan 46 (The surface graded is the REST API at api.shodan.io. An OpenAPI 3.0.0 document at developer.shodan.io/api/openapi.json covers 37 paths and 44 operations, but declares no securitySchemes, no enums and a non-200 response on one operation only (15 of 25). No llms.txt on developer.shodan.io or www.shodan.io, both 404, and no Markdown docs served for agents (0 of 10). Every operation carries a description, and the reference says which calls cost credits and which plans can scan, with little on when not to use a call (12 of 20). Required flags on the key and path parameters, with `facets`, `query` and `fields` as free strings and no enums or constraints (7 of 15). Example requests and responses for every endpoint in the reference, and errors documented only as a non-200 status with an `error` field (9 of 15). No version in the path, the OpenAPI document says 1.0.0, and the only dated record of changes is the blog, whose newest post is 7 August 2024 (3 of 15). 15 + 0 + 12 + 7 + 9 + 3 = 46.)
- Security & auth, Censys +36: Censys 55 (Personal access tokens as a Bearer header, several per user, named, shown once and deletable, with no scopes or expiry stated. Service accounts on Search and Core plans use OAuth 2 client credentials with module roles and a rotatable secret, and the MCP server takes OAuth with a consent page. Only the organisation id, not a secret, may travel in the query string (26 of 30). Module roles (Analyst, Manager), an API Access role and the advice to grant service accounts only the roles they need, but no read-only token and no confirmation step for deleting a collection (12 of 20). Results carry banners, HTML titles and certificate subjects from scanned hosts, and no guidance on treating them as untrusted was found in the API, MCP or skills docs (3 of 15). A platform audit log for admins that records service account activity, credit usage per member through the API and `X-Request-ID` on every response, with no documented per-call log for token holders (10 of 15). security@censys.com on the contact page. security.txt 404, no bug bounty, and the compliance page says Censys helps customers with SOC 2, ISO 27001 and FedRAMP without claiming any for itself (4 of 20). 26 + 12 + 3 + 10 + 4 = 55.); Shodan 19 (One key per account with no scopes, sent as `key=` in the query string on every documented call and in the OpenAPI document, with no header option. Read as a plain key, the way the Alpha Vantage listing was read, less 10 for the query string (10 of 30). No read-only key or least-privilege mode; the free plan's limits are quotas, not scopes, and alerts, notifiers and org members can be deleted with the same key and no confirmation (3 of 20). Results carry banners, HTTP titles and page bodies collected from arbitrary hosts, and no guidance on treating them as untrusted was found (3 of 15). `/api-info` reports the plan and credits, and no call log for the key holder was found (3 of 15). security.txt returns 404 on www.shodan.io, and no bug bounty, disclosure policy, SOC 2 or ISO 27001 was found on the pages read (0 of 20). 10 + 3 + 3 + 3 + 0 = 19.)
- Transparency & trust, Censys +20: Censys 64 (A closed service under terms effective 1 October 2018 that are clear on who may use the data for what, with MIT SDKs and an Apache-2.0 CLI (15 of 30). Privacy policy of 1 April 2025 keeps data 'for as long as necessary' with no periods, while the retention policy revised 11 July 2023 gives seven days for queries before anonymisation and up to three years for ASM seed data after an account expires, and still names the retired Censys Search. Two GDPR representatives are named. No public DPA found, and the privacy page's mailto points to censys.io while its text says censys.com (16 of 30). The transition guide gives the Legacy Search API no sunset date, the Accept header allows schema versions but no lifecycle is published, and credit packs were discontinued on 2 November with no notice period stated (5 of 20). Hosted in the United States, Stripe and Google named, unnamed analytics, advertising and session replay vendors, no subprocessor list (8 of 20). 15 + 16 + 5 + 8 = 44.); Shodan 44 (Editorial half. A closed service whose terms at static.shodan.io/legal/terms.html were not read, because that host answers 403 to robots.txt, so their clarity can't be assessed; the Python library is MIT (5 of 30). The privacy policy at account.shodan.io/privacy carries no date, names no legal entity, retention period, data location or subprocessor, and says Shodan may share information with advertisers, business partners, sponsors and other third parties (5 of 30). The help centre says export credits are deprecated and no longer sold, with no date; no deprecation policy found (3 of 20). No subprocessors or data locations disclosed (0 of 20). 5 + 5 + 3 + 0 = 13.)
- Reliability, Censys +15: Censys 55 (Graded as a hosted service on the Platform API. Atlassian Statuspage at status.censys.com with Platform API, Authentication, Credit Management and three MCP server components (20). Its feed lists 12 entries from 24 August to 2 November 2026. Two were maintenance on ASM. The rest include intermittent 500s on the Platform from 13:52 on 24 August to 09:52 the next day, periodic query failures from 20 to 22 September, historical data calls timing out for about an hour on 18 September, an internal networking outage of the Platform and ASM from 00:35 to 13:46 EDT on 30 September, and failing searches from 14:26 EST on 2 November still in monitoring at 19:08. One full outage of about 13 hours and two multi-hour periods of failing core queries, read as more than one major (5). Limits are published with numbers, concurrency 1 or 25 per organisation and 25 requests a second per IP with a burst of 125 (15). Overruns return 429 or 503, but no Retry-After, backoff guidance or idempotency keys were found, and the SDKs say only that they follow the API's default retry strategy (5 of 15). No SLA found. The terms disclaim any warranty that the service will meet requirements, and the pricing page names none (0). The v3 API is generally available (10). 20 + 5 + 15 + 5 + 0 + 10 = 55.); Shodan 40 (Read with the hosted lines. A public status page exists at status.shodan.io (UptimeRobot), but on 3 November 2026 its component list failed to load and it showed only that there were no updates in the last 7 days, so no component history was readable (10 of 20). No readable incident record for the 90 days (5). The billing page states that all API plans are limited to 1 request a second, and credits per plan are published with numbers (15). No 429, Retry-After or backoff guidance was found in the reference or the OpenAPI document; the only error statement is that a non-200 status carries an error message, and no idempotency keys exist for alert, notifier or scan writes. The official Python client throttles itself to 1 request a second and retries a timed-out search cursor, which is client behaviour, not an API contract (0). No SLA found on the billing, enterprise or developer pages (0). The REST API is generally available (10). 10 + 5 + 15 + 0 + 0 + 10 = 40.)
- Agent ergonomics, Censys +15: Censys 79 (`fields` limits a search response to named fields and `page_size` caps it at 100, with raw and full variants of lookups chosen by endpoint (22 of 25). `page_token` with `next_page_token` and `previous_page_token`, `total_hits`, aggregate endpoints and a bulk lookup (20). A status code table that separates 401, 403, 422, 429 and 503, problem+json bodies and `X-Request-ID` on responses, but no catalogue of error codes beyond status (14 of 20). Lookups and search are safe to retry, but collections, tags, comments and member endpoints write with no idempotency key, and no tool annotations are documented for the MCP server (8 of 20). One required field on search, SDKs in Python, Go and TypeScript, a CLI and Claude Code skills, though every paid-tier call also needs the organisation id (15). 22 + 20 + 14 + 8 + 15 = 79.); Shodan 64 (`minify` on host lookups drops banners and returns ports and host facts, `minify` on search (on by default) truncates large fields and `fields` selects which fields come back, so an agent can size a response (20 of 25). `page` with 100 results a page, `facets` for summaries, `count` for a free total, and the whole filter language of the search engine (18 of 20). Errors are a non-200 status and a short message such as Invalid IP, with no code list to branch on (8 of 20). Most calls are GET reads. Alerts, notifiers, scans and org members are written with POST, PUT and DELETE and no idempotency key, and nothing marks a destructive call (10 of 20). Few required parameters and sensible defaults, but only one official SDK, the Python library, with the other twelve languages community work (8 of 15). 20 + 18 + 8 + 10 + 8 = 64.)