{ "data": { "a": { "slug": "pulsedive", "name": "Pulsedive", "vendor": "Pulsedive LLC", "vendorUrl": "https://pulsedive.com", "kind": "http-api", "category": "security-intelligence", "summary": "Pulsedive is a threat intelligence platform from Pulsedive LLC in New Jersey. Its API looks up domains, IP addresses and URLs for risk scores, linked threats and feeds, scans new indicators on demand and exports STIX over TAXII 2.1.", "url": "https://www.anchorterminal.com/tools/pulsedive", "markdownUrl": "https://www.anchorterminal.com/tools/pulsedive.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pulsedive.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pulsedive.json", "dns": "pulsedive.grade.anchorterminal.com", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key from the account page after a free browser signup, sent only as a `key` query parameter. Requests without a key are accepted at a much lower limit (10 a day and 100 a month per the March 2024 plan post). No scopes, rotation or header option was found. The TAXII server takes the key by HTTP Basic or query parameter.", "pricing": "freemium", "pricingNotes": "Free registered account, no card, 50 API requests a day and 500 a month per the March 2024 plan post. Pro $29 a month (250 a day, 2,500 a month) per the site menu and that post, which also gave Team API $300 a month for 25,000 requests and Business API $900 a month for 100,000 with soft limits, Custom by contact, and feed subscriptions from $1,500 to $3,000 a month. The current pricing pages render by script, so the 2024 figures for Team and Business are the latest read.", "priceSummary": "$29 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI files, the terms or the plan posts (checked 2026-11-03). A spent quota answers 429 with an error string that points to the plan page.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.pulsedive.com/", "llmsTxt": "https://docs.pulsedive.com/llms.txt", "openapi": "https://docs.pulsedive.com/api/indicator/indicator-by-value.yaml", "capabilities": [ "secintel.indicators", "secintel.reputation", "secintel.dns", "secintel.ip-enrichment" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "no-auth", "api-key", "llms-txt", "openapi", "async-jobs", "closed-source", "no-status-page" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 47.9, "grade": "D", "agentReady": false, "rank": 1047, "ranked": true, "rankOf": 1349, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 40, "payments": 50, "reliability": 31, "schema": 77, "security": 23, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Lookups work with no key at all, a free account allows 50 requests a day, and the docs ship llms.txt, per-endpoint OpenAPI files and timestamps for every scan. The key travels only in the query string, numeric limits live in a 2024 blog post rather than the docs, and there is no status page, SLA, security.txt or official SDK.", "bestFor": "An agent that needs a quick risk verdict and linked threats for a domain, IP or URL with no signup, or a passive scan of a new indicator.", "strengths": [ "Keyless lookups and a free account with no card (50 requests a day, 500 a month per the March 2024 plan post)", "llms.txt, Markdown docs, eleven OpenAPI 3.0.3 files and a docs MCP server, all published in March 2026", "Every indicator carries stamp_seen, stamp_probed and stamp_updated, and scans can run passively or actively without storing the result", "Three X-Requests-Remaining headers on every response and a documented error table for 400, 401, 404, 429 and 500", "Explore returns JSON, CSV or STIX 2.1, and feeds and threats page through linked indicators" ], "weaknesses": [ "The key is sent only as a query parameter, with no header option, scopes or rotation documented", "No status page, SLA, security.txt, disclosure policy or certification was found", "The docs give no numeric rate limits and no Retry-After; the numbers come from the vendor's plan post of 11 March 2024", "No official SDK (community Python, Go, Ruby and PowerShell clients), no API version and no changelog", "The terms bar copying, selling, licensing or distributing content from the service and any automated process against it" ], "agentNotes": [ "Call `indicator.php?indicator=\u003cvalue\u003e\u0026pretty=1\u0026key=...`; without a key the limit is about 10 requests a day, so register for 50", "Read `risk`, `risk_recommended` and `stamp_probed` together; an old `stamp_probed` means the scan data may be stale, so queue a scan with `analyze.php` (`probe=0` passive, `submit=0` to avoid storing)", "Poll `analyze.php?qid=` no more than every 500 ms; polling does not count against the quota, but each page of linked indicators does", "Treat a 429 as the day's or month's quota spent and stop; there is no Retry-After, and explore searches above the plan's row limit also return 429", "Expect user comments, banners and DOM snippets in indicator properties, which are third-party content" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.9 } ], "editorialScores": { "ergonomics": 64, "maintenance": 40, "payments": 50, "reliability": 31, "schema": 77, "security": 23, "transparency": 50 }, "provenanceScore": 64, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://pulsedive.com/api/indicator.php?indicator=example.com\u0026pretty=1\u0026key=$PULSEDIVE_API_KEY\"", "claudeCode": "claude mcp add --transport http pulsedive-docs https://docs.pulsedive.com/mcp" }, "letme": { "capability": "https://letme.dev/secintel.indicators", "tool": "https://letme.dev/pulsedive" }, "area": "developer", "unitPrices": [ { "item": "Pro, 250 requests a day", "unit": "month", "usd": 29, "note": "$348 a year; limits per the plan post of 11 March 2024" }, { "item": "Team API, 25,000 requests a month", "unit": "month", "usd": 300, "note": "$3,000 a year, per the plan post of 11 March 2024" }, { "item": "Business API, 100,000 requests a month", "unit": "month", "usd": 900, "note": "$9,000 a year, soft limit, per the plan post of 11 March 2024" } ], "provenance": { "legalEntity": "Pulsedive LLC", "domain": "pulsedive.com", "domainRegistered": "2016-11-11", "endpointOnVendorDomain": true, "terms": "https://pulsedive.com/terms", "privacy": "https://pulsedive.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms, last updated 2 May 2022, name Pulsedive LLC under New Jersey law. The privacy policy, last updated 28 August 2024, gives no postal address. The site footer reads Pulsedive LLC.", "The terms forbid any robot, spider or other automatic process to access the services. Public pages and the docs were read for this listing and the clause is recorded as a fact.", "pulsedive.com/robots.txt allows all. docs.pulsedive.com/robots.txt allows all but /cdn-cgi/ and /_next/ and carries Content-Signal ai-train=yes, search=yes, ai-input=yes.", "No status page was found on the site, the docs, the support page or in search. No changelog was found; the blog carries product posts and the footer a version number.", "pulsedive.com/.well-known/security.txt returns 404. RDAP at Verisign gives a registration date of 11 November 2016." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pulsedive.json", "live": { "slug": "pulsedive", "securityTxt": { "url": "https://pulsedive.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:46.13864767Z" }, "updatedAt": "2026-11-04T15:54:46.13864767Z" } }, "answer": "WhoisXML API scores 56.8 (C) on agent readiness against Pulsedive's 47.9 (D), and leads in 5 of 7 scored categories. Pulsedive leads on schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "whoisxml-api", "name": "WhoisXML API", "vendor": "Whois API, Inc.", "vendorUrl": "https://www.whoisxmlapi.com", "kind": "http-api", "category": "security-intelligence", "summary": "WhoisXML API is a set of domain, DNS, IP and threat intelligence APIs from Whois API, Inc. Its WHOIS API returns parsed registration records for a domain or address, and a hosted MCP server bundles 35 tools on one balance.", "url": "https://www.anchorterminal.com/tools/whoisxml-api", "markdownUrl": "https://www.anchorterminal.com/tools/whoisxml-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/whoisxml-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json", "dns": "whoisxml-api.grade.anchorterminal.com", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp-hosted.whoisxmlapi.com/mcp", "packages": [ { "registry": "npm", "name": "@whoisxmlapidotcom/mcp-whoisxmlapi" } ], "auth": "mixed", "authNotes": "API key from the account after a browser signup, sent as an `apiKey` query parameter (which takes priority) or as `Authorization: Bearer`, which also accepts a server-to-server OAuth token. An IP allowlist can be set (403 AUTHENTICATE_10). The hosted MCP server uses OAuth, taking the API key once in the connect flow; local installs take the key as an environment variable.", "pricing": "freemium", "pricingNotes": "500 free WHOIS API credits on signup with no card. A WHOIS lookup costs 1 credit, 5 with a forced real-time refresh. WXA.ONE universal credit pools, one balance across the APIs and the MCP server, start from $129 a month, monthly or yearly; per-credit rates sit behind a calculator and were not read. Enterprise packages and premium support by sales. Credits expire after 12 months and orders are non-refundable under the terms.", "priceSummary": "$129 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the WHOIS API docs, the pricing pages, the terms or the MCP server docs (checked 2026-11-03). An exhausted balance answers 401 AUTHENTICATE_05.", "endpoints": [] }, "toolCount": 35, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://whois.whoisxmlapi.com/documentation/making-requests", "llmsTxt": "https://www.whoisxmlapi.com/llms.txt", "registryName": "io.github.whois-api-llc/mcp-whoisxmlapi", "capabilities": [ "secintel.dns", "secintel.reputation", "secintel.ip-enrichment", "secintel.indicators" ], "tags": [ "hosted", "freemium", "no-card", "free-tier", "api-key", "oauth", "mcp", "remote-mcp", "official", "mcp-registry", "llms-txt", "status-page", "prepaid", "typescript", "python", "go", "docker", "closed-source" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 56.8, "grade": "C", "agentReady": false, "rank": 731, "ranked": true, "rankOf": 1349, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 76, "payments": 25, "reliability": 65, "schema": 70, "security": 39, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string.", "bestFor": "An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.", "strengths": [ "500 free WHOIS credits on signup with no card, and 1 credit a lookup from cache or 5 for a forced refresh", "JSON Schema and XSD documents for the record, availability and error responses, with an error code table and Retry-After on 429", "Each record carries audit.createdDate and audit.updatedDate, so an agent can tell when the copy was collected", "Official MCP server with 35 tools, hosted with OAuth, in the official MCP registry with 21 versions since May 2026", "llms.txt on whoisxmlapi.com lists the APIs, feeds and databases" ], "weaknesses": [ "Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable", "The terms license data for one site, bar sharing it with third parties and forbid AI model training on it without written authorisation", "The docs say 200 requests a second while the terms say 50, 20 concurrent and 5 concurrent bulk", "The key is accepted as a query parameter that overrides the header, no scopes were found, and security.txt returns 404", "The privacy policy was last modified on 6 April 2020, cites Privacy Shield, and names no processors, locations or retention periods", "No OpenAPI document, no API version, and the MCP server's source was not found" ], "agentNotes": [ "Send the key as `Authorization: Bearer` and `outputFormat=JSON`; the default output is XML and an `apiKey` query parameter overrides the header", "Leave the cache flags alone for 1 credit a lookup; `_hardRefresh=1` costs 5 credits, and `_dbOnly=1` returns WHOIS_03 when nothing is cached", "Read `audit.updatedDate` before trusting a record, and check `dataError` for MASKED_WHOIS_DATA or PARTIAL_DATA", "Watch `X-RateLimit-Remaining` and on 429 AUTHENTICATE_06 wait for `Retry-After`; a 401 AUTHENTICATE_05 means the balance is spent, so stop", "Keep results inside the customer's own systems; the terms forbid passing data to third parties or using it to train models" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.8 } ], "editorialScores": { "ergonomics": 65, "maintenance": 76, "payments": 25, "reliability": 65, "schema": 70, "security": 39, "transparency": 31 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx @whoisxmlapidotcom/mcp-whoisxmlapi --help", "http": "curl -H \"Authorization: Bearer $WHOISXML_API_KEY\" \"https://www.whoisxmlapi.com/whoisserver/WhoisService?domainName=example.com\u0026outputFormat=JSON\"", "claudeCode": "claude mcp add --transport http whoisxmlapi https://mcp-hosted.whoisxmlapi.com/mcp", "config": { "mcpServers": { "whoisxmlapi": { "url": "https://mcp-hosted.whoisxmlapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/secintel.dns", "tool": "https://letme.dev/whoisxml-api" }, "area": "developer", "unitPrices": [ { "item": "WXA.ONE universal credit pool, smallest plan", "unit": "month", "usd": 129, "note": "from $129 a month; credits included and per-credit rates were not read" } ], "provenance": { "legalEntity": "Whois API, Inc.", "domain": "whoisxmlapi.com", "domainRegistered": "2009-03-20", "endpointOnVendorDomain": true, "terms": "https://main.whoisxmlapi.com/terms-of-service", "privacy": "https://main.whoisxmlapi.com/privacy-policy", "statusPage": "https://main.whoisxmlapi.com/api-status", "changelog": "https://main.whoisxmlapi.com/press-release", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms of service, last updated 3 March 2025 and effective 3 May 2025, name Whois API, Inc. under California law with AAA arbitration. The company page's copyright line reads 2010 to 2026 Whois API, Inc. No postal address was found on the terms, privacy policy or company page.", "The terms forbid unauthorised data mining and obtaining materials through means not intentionally made available, and set a rate limit of 50 requests a second. Public pages were read for this listing and the clauses are recorded as facts.", "whois.whoisxmlapi.com/robots.txt allows all paths for general crawlers and blocks five named bots. www.whoisxmlapi.com/robots.txt disallows blog admin paths and /BulkWhoisLookup/, none fetched. www.whoisxmlapi.com/terms-of-service redirects to a 404; the terms live at main.whoisxmlapi.com.", "The status page is the vendor's own Service Status and Data Releases page, which describes a JSON status file and feeds but lists no incidents.", "The changelog link is the press release page, whose newest product update is dated 9 May 2025. MCP server versions are dated in the official MCP registry.", "main.whoisxmlapi.com/.well-known/security.txt returns 404. RDAP at Verisign gives a registration date of 20 March 2009." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/whoisxml-api.json", "live": { "slug": "whoisxml-api", "probe": { "target": "https://mcp-hosted.whoisxmlapi.com/mcp", "method": "get", "lastAt": "2026-11-04T21:28:20.437933986Z", "lastOk": true, "lastStatus": 401, "lastMs": 391, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 413, "p95ms24h": 537, "samples24h": 62, "samples30d": 62, "days": [ { "date": "2026-11-04", "probes": 62, "ok": 62 } ] }, "vendorStatus": { "page": "https://main.whoisxmlapi.com/api-status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:26:59.259669881Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.whois-api-llc/mcp-whoisxmlapi", "version": "1.15.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@whoisxmlapidotcom/mcp-whoisxmlapi", "version": "1.15.0", "seenAt": "2026-11-04T21:06:02.286471255Z" } ], "npmWeekly": 1559, "securityTxt": { "url": "https://whoisxmlapi.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:49.350283946Z" }, "updatedAt": "2026-11-04T21:28:20.437933986Z" } }, "edges": [ { "by": 36, "category": "maintenance", "leads": "whoisxml-api", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The site footer shows version 6.3.18 dated 27 October, seven days before the check, and the newest blog post is 29 September 2026 (30). No changelog lists releases, so three dated changes in 90 days could not be shown (0 of 20). A Discord, support@pulsedive.com, a contact form and a docs troubleshooting section; the GitHub feedback repository is archived since 2020 (10 of 15). No entry in the official MCP registry (the docs MCP server is not listed and the registry's pulsedive entries are third-party) and no official SDK (0 of 15). No official packages to assess (0 of 10). 30 + 0 + 10 + 0 + 0 = 40.", "b": "Read as a closed service with an official MCP server. MCP server 1.13.0 was published in the official registry on 3 November 2026 and the ProfessionalServices and ipgeo-community repositories were pushed the same day (30). 1.8.6 on 8 September through 1.13.0 on 3 November 2026 is nine registry versions in 90 days (20). Product updates are summarised in yearly press releases, the newest 9 May 2025, support is a contact form with tiered response times sold separately, and the client library repositories were last pushed in 2023 (8 of 15). The MCP server is in the official registry under io.github.whois-api-llc, and official Python and Go clients exist (15). The MCP server's source was not found on GitHub, and the SDK repositories show no activity since 2023 (3 of 10). 30 + 20 + 8 + 15 + 3 = 76." }, "scores": { "a": 40, "b": 76 } }, { "by": 34, "category": "reliability", "leads": "whoisxml-api", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. No status page was found on the site, the docs, the support page or in search (0). No readable history (5). The limits page names Free, Pro, Commercial and Enterprise tiers and three remaining-request headers but gives no numbers, pointing to the account page; the vendor's plan post of 11 March 2024 gives 50 a day on Free and 250 on Pro (8 of 15). A 429 returns a JSON error naming the limit and the headers show what remains, with no Retry-After or backoff guidance; scans are safe to repeat and polling is free (8 of 15). No SLA; the terms supply the services as is and as available (0). The API is generally available (10). 0 + 5 + 8 + 8 + 0 + 10 = 31.", "b": "Read with the hosted lines. The vendor's own Service Status and Data Releases page is linked from the docs and describes a per-API JSON status file with four levels (20). It shows no incident history and the status file's live values could not be read, so no 90-day record (5). The docs give 200 requests a second with rejection until the next second; the terms give 50 a second, 20 concurrent and 5 concurrent bulk requests, so numbers are published even though they disagree (15). A 429 AUTHENTICATE_06 carries Retry-After and every response X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, with guidance to slow before zero; all calls are reads (15). No SLA; the terms guarantee no minimum uptime and cite a historical 99.9 per cent, with enterprise SLAs by separate agreement (0). The API is generally available (10). 20 + 5 + 15 + 15 + 0 + 10 = 65." }, "scores": { "a": 31, "b": 65 } }, { "by": 25, "category": "payments", "leads": "pulsedive", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Pro $29 a month is on the site menu and the Team and Business API prices are in the vendor's plan post of 11 March 2024, sold as monthly quotas rather than per call (10). A free account needs no card (20). Requests without a key are accepted, so an agent can look up an indicator with no signup at about 10 a day (20). 0 + 10 + 20 + 20 = 50.", "b": "No x402, MPP or L402 (0). The only public price is from $129 a month for a universal credit pool; per-credit rates are behind a calculator whose output was not read and enterprise packages are by sales (5 of 20). 500 free WHOIS credits on signup with no card (20). The key comes from the account after a browser signup and no key API was found (0). 0 + 5 + 20 + 0 = 25." }, "scores": { "a": 50, "b": 25 } }, { "by": 16, "category": "security", "leads": "whoisxml-api", "name": "Security \u0026 auth", "reasons": { "a": "One key per account sent only as a query parameter, with no scopes, header option or rotation documented (10 for one all-powerful key less 10 for the query string, so 0). Lookups read, submit=1 writes to the public dataset and keyless use is read-only in practice, but there is no read-only key (10 of 20). Responses include community comments, banners and DOM snippets from scans with no guidance on treating them as untrusted (3 of 15). The privacy policy says web and API logs are available from the account page (10 of 15). security.txt returns 404 and no disclosure policy, bug bounty or certification was found (0 of 20). 0 + 10 + 3 + 10 + 0 = 23.", "b": "An API key with no scopes found, accepted as an apiKey query parameter that overrides the Authorization header, or as a Bearer token including a server-to-server OAuth token; an IP allowlist can be set on the account (20 less 10 for the query string, plus 4 for OAuth and the allowlist, so 14). Every call is a read and the MCP server has no write tools, but there is no read-only or restricted key (12 of 20). Records include raw registrar text from third parties with no guidance on treating it as untrusted (5 of 15). The MCP server's account_balance tool reports credits per product and the account page shows usage, with no per-call log documented (5 of 15). security.txt returns 404, no disclosure policy, bug bounty or certification was found, and the payment page names only a PCI-compliant card processor (3 of 20). 14 + 12 + 5 + 5 + 3 = 39." }, "scores": { "a": 23, "b": 39 } }, { "by": 7, "category": "schema", "leads": "pulsedive", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.0.3 documents for every endpoint, eleven YAML files under Apache 2.0, with typed parameters and response schemas, though split per endpoint and without a securitySchemes block in the scan and explore file (22 of 25). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). Each endpoint states its purpose, probe and submit are explained with their side effects, and the collection page says what each timestamp means, with little on when not to call (15 of 20). Enumerated 0 or 1 flags, required parameters marked, risk and type enums, but key is optional while 401 describes it missing, and explore summaries allow types the indicator schema does not (11 of 15). curl examples on every page and an error table for 400, 401, 404, 429 and 500 with an example body (12 of 15). No API version or changelog; the docs launch post of 30 March 2026 and a footer version number are the only dated changes, and the spec marks the recent field deprecated with no date (7 of 15). 22 + 10 + 15 + 11 + 12 + 7 = 77.", "b": "The surface graded is the WHOIS API, with the hosted MCP server noted. No OpenAPI document. JSON Schema draft-07 and XSD files define the WHOIS record, the DomainInfo response and the error body, and a Postman collection is published (15 of 25). llms.txt on www.whoisxmlapi.com lists the APIs, databases and feeds (10). The making-requests page states each parameter's purpose, default and credit cost, lists deprecated parameters that are still accepted, and says when RDAP applies, with little on when not to call (15 of 20). rdap, outputFormat and the cache flags have enumerated values and the record schema is typed, but unknown parameters are ignored silently and the output page gives no types in prose (11 of 15). Request examples, example records and an error table with HTTP status, errorCode and message (12 of 15). No API version and no changelog for the API; press releases summarise product updates yearly, the newest dated 9 May 2025, and the MCP server's versions are dated in the registry (7 of 15). 15 + 10 + 15 + 11 + 12 + 7 = 70." }, "scores": { "a": 77, "b": 70 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Pulsedive LLC", "b": "Whois API, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp-hosted.whoisxmlapi.com/mcp", "name": "Hosted endpoint" }, { "a": "", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "0", "b": "35", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.whois-api-llc/mcp-whoisxmlapi", "name": "MCP registry" }, { "a": "2026-10-27", "b": "2026-11-03", "name": "Last release" }, { "a": "2022-05-02", "b": "2025-03-03", "name": "Terms last updated" }, { "a": "2024-08-28", "b": "2020-04-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "WhoisXML API scores 56.8 (C) on agent readiness against Pulsedive's 47.9 (D), and leads in 5 of 7 scored categories. Pulsedive leads on schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, Pulsedive or WhoisXML API?" }, { "answer": "Pulsedive needs an API key. WhoisXML API takes an API key or an OAuth sign-in.", "question": "Do Pulsedive and WhoisXML API need an API key?" }, { "answer": "No hosted endpoint is listed for Pulsedive. WhoisXML API has a hosted endpoint at https://mcp-hosted.whoisxmlapi.com/mcp.", "question": "Can an agent call Pulsedive and WhoisXML API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 77 against 70", "Payments \u0026 pricing, 50 against 25" ], "also": null, "goodFor": "An agent that needs a quick risk verdict and linked threats for a domain, IP or URL with no signup, or a passive scan of a new indicator.", "slug": "pulsedive", "watchFor": "The key is sent only as a query parameter, with no header option, scopes or rotation documented" }, { "aheadOn": [ "Reliability, 65 against 31", "Security \u0026 auth, 39 against 23", "Maintenance \u0026 community, 76 against 40" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.", "slug": "whoisxml-api", "watchFor": "Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable" } ], "history": null, "job": { "capability": "secintel.indicators", "name": "Secintel indicators" }, "others": [ { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive.json", "title": "AbuseIPDB vs Pulsedive", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive" }, { "json": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.json", "title": "AbuseIPDB vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/greynoise-vs-pulsedive.json", "title": "GreyNoise vs Pulsedive", "url": "https://www.anchorterminal.com/compare/greynoise-vs-pulsedive" }, { "json": "https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api.json", "title": "GreyNoise vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api.json", "title": "VirusTotal vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/ipinfo-vs-pulsedive.json", "title": "IPinfo vs Pulsedive", "url": "https://www.anchorterminal.com/compare/ipinfo-vs-pulsedive" }, { "json": "https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api.json", "title": "IPinfo vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/censys-vs-whoisxml-api.json", "title": "Censys vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/censys-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/pulsedive-vs-securitytrails.json", "title": "Pulsedive vs SecurityTrails", "url": "https://www.anchorterminal.com/compare/pulsedive-vs-securitytrails" }, { "json": "https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.json", "title": "SecurityTrails vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api.json", "title": "Shodan vs WhoisXML API", "url": "https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api" }, { "json": "https://www.anchorterminal.com/compare/censys-vs-pulsedive.json", "title": "Censys vs Pulsedive", "url": "https://www.anchorterminal.com/compare/censys-vs-pulsedive" }, { "json": "https://www.anchorterminal.com/compare/pulsedive-vs-shodan.json", "title": "Pulsedive vs Shodan", "url": "https://www.anchorterminal.com/compare/pulsedive-vs-shodan" }, { "json": "https://www.anchorterminal.com/compare/pulsedive-vs-virustotal.json", "title": "Pulsedive vs VirusTotal", "url": "https://www.anchorterminal.com/compare/pulsedive-vs-virustotal" } ], "panel": null, "scores": [ { "by": 34, "edge": "whoisxml-api", "key": "reliability", "name": "Reliability", "pulsedive": 31, "weight": 16, "whoisxml-api": 65 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "edge": "pulsedive", "key": "schema", "name": "Schema \u0026 documentation", "pulsedive": 77, "weight": 13, "whoisxml-api": 70 }, { "by": 1, "edge": "whoisxml-api", "key": "ergonomics", "name": "Agent ergonomics", "pulsedive": 64, "weight": 13, "whoisxml-api": 65 }, { "by": 16, "edge": "whoisxml-api", "key": "security", "name": "Security \u0026 auth", "pulsedive": 23, "weight": 14, "whoisxml-api": 39 }, { "by": 25, "edge": "pulsedive", "key": "payments", "name": "Payments \u0026 pricing", "pulsedive": 50, "weight": 10, "whoisxml-api": 25 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "edge": "whoisxml-api", "key": "maintenance", "name": "Maintenance \u0026 community", "pulsedive": 40, "weight": 7, "whoisxml-api": 76 }, { "by": 3, "edge": "whoisxml-api", "key": "transparency", "name": "Transparency \u0026 trust", "pulsedive": 57, "weight": 7, "whoisxml-api": 60 } ], "summary": "WhoisXML API scores 56.8 (C) on agent readiness against Pulsedive's 47.9 (D), and leads in 5 of 7 scored categories. Pulsedive leads on schema \u0026 documentation and payments \u0026 pricing. Both do secintel indicators.", "tasks": null, "tutorials": [], "verdicts": { "pulsedive": "Lookups work with no key at all, a free account allows 50 requests a day, and the docs ship llms.txt, per-endpoint OpenAPI files and timestamps for every scan. The key travels only in the query string, numeric limits live in a 2024 blog post rather than the docs, and there is no status page, SLA, security.txt or official SDK.", "whoisxml-api": "500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api", "json": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.min.md" }, "markdown": "WhoisXML API scores 56.8 (C) on agent readiness against Pulsedive's 47.9 (D), and leads in 5 of 7 scored categories. Pulsedive leads on schema \u0026 documentation and payments \u0026 pricing. Both do secintel indicators.\n\n- Pulsedive: grade D, 47.9/100, rank #1047 of 1349. Markdown https://www.anchorterminal.com/tools/pulsedive.md · JSON https://www.anchorterminal.com/api/v1/tools/pulsedive.json\n- WhoisXML API: grade C, 56.8/100, rank #731 of 1349. Markdown https://www.anchorterminal.com/tools/whoisxml-api.md · JSON https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json\n- Best threat and security intelligence APIs for AI agents: https://www.anchorterminal.com/best/security-intelligence/index.md\n- All 33 security intel comparisons: https://www.anchorterminal.com/compare/security-intelligence/index.md\n\n## Which one, for what\n\n### Pulsedive (D)\n\nGood for: An agent that needs a quick risk verdict and linked threats for a domain, IP or URL with no signup, or a passive scan of a new indicator.\n\nAhead on:\n- Schema \u0026 documentation, 77 against 70\n- Payments \u0026 pricing, 50 against 25\n\nWatch for: The key is sent only as a query parameter, with no header option, scopes or rotation documented\n\n### WhoisXML API (C)\n\nGood for: An agent investigating a domain's registration, history, DNS, certificates or related domains at scale, on a prepaid credit pool.\n\nAhead on:\n- Reliability, 65 against 31\n- Security \u0026 auth, 39 against 23\n- Maintenance \u0026 community, 76 against 40\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Per-credit prices are not published outside a calculator; the only public figure is from $129 a month, and orders are non-refundable\n\n\n## Why the edge\n\n### Maintenance \u0026 community: WhoisXML API +36\n\n- Pulsedive (40): Read as a closed service. The site footer shows version 6.3.18 dated 27 October, seven days before the check, and the newest blog post is 29 September 2026 (30). No changelog lists releases, so three dated changes in 90 days could not be shown (0 of 20). A Discord, support@pulsedive.com, a contact form and a docs troubleshooting section; the GitHub feedback repository is archived since 2020 (10 of 15). No entry in the official MCP registry (the docs MCP server is not listed and the registry's pulsedive entries are third-party) and no official SDK (0 of 15). No official packages to assess (0 of 10). 30 + 0 + 10 + 0 + 0 = 40.\n- WhoisXML API (76): Read as a closed service with an official MCP server. MCP server 1.13.0 was published in the official registry on 3 November 2026 and the ProfessionalServices and ipgeo-community repositories were pushed the same day (30). 1.8.6 on 8 September through 1.13.0 on 3 November 2026 is nine registry versions in 90 days (20). Product updates are summarised in yearly press releases, the newest 9 May 2025, support is a contact form with tiered response times sold separately, and the client library repositories were last pushed in 2023 (8 of 15). The MCP server is in the official registry under io.github.whois-api-llc, and official Python and Go clients exist (15). The MCP server's source was not found on GitHub, and the SDK repositories show no activity since 2023 (3 of 10). 30 + 20 + 8 + 15 + 3 = 76.\n\n### Reliability: WhoisXML API +34\n\n- Pulsedive (31): Read with the hosted lines. No status page was found on the site, the docs, the support page or in search (0). No readable history (5). The limits page names Free, Pro, Commercial and Enterprise tiers and three remaining-request headers but gives no numbers, pointing to the account page; the vendor's plan post of 11 March 2024 gives 50 a day on Free and 250 on Pro (8 of 15). A 429 returns a JSON error naming the limit and the headers show what remains, with no Retry-After or backoff guidance; scans are safe to repeat and polling is free (8 of 15). No SLA; the terms supply the services as is and as available (0). The API is generally available (10). 0 + 5 + 8 + 8 + 0 + 10 = 31.\n- WhoisXML API (65): Read with the hosted lines. The vendor's own Service Status and Data Releases page is linked from the docs and describes a per-API JSON status file with four levels (20). It shows no incident history and the status file's live values could not be read, so no 90-day record (5). The docs give 200 requests a second with rejection until the next second; the terms give 50 a second, 20 concurrent and 5 concurrent bulk requests, so numbers are published even though they disagree (15). A 429 AUTHENTICATE_06 carries Retry-After and every response X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, with guidance to slow before zero; all calls are reads (15). No SLA; the terms guarantee no minimum uptime and cite a historical 99.9 per cent, with enterprise SLAs by separate agreement (0). The API is generally available (10). 20 + 5 + 15 + 15 + 0 + 10 = 65.\n\n### Payments \u0026 pricing: Pulsedive +25\n\n- Pulsedive (50): No x402, MPP or L402 (0). Pro $29 a month is on the site menu and the Team and Business API prices are in the vendor's plan post of 11 March 2024, sold as monthly quotas rather than per call (10). A free account needs no card (20). Requests without a key are accepted, so an agent can look up an indicator with no signup at about 10 a day (20). 0 + 10 + 20 + 20 = 50.\n- WhoisXML API (25): No x402, MPP or L402 (0). The only public price is from $129 a month for a universal credit pool; per-credit rates are behind a calculator whose output was not read and enterprise packages are by sales (5 of 20). 500 free WHOIS credits on signup with no card (20). The key comes from the account after a browser signup and no key API was found (0). 0 + 5 + 20 + 0 = 25.\n\n### Security \u0026 auth: WhoisXML API +16\n\n- Pulsedive (23): One key per account sent only as a query parameter, with no scopes, header option or rotation documented (10 for one all-powerful key less 10 for the query string, so 0). Lookups read, submit=1 writes to the public dataset and keyless use is read-only in practice, but there is no read-only key (10 of 20). Responses include community comments, banners and DOM snippets from scans with no guidance on treating them as untrusted (3 of 15). The privacy policy says web and API logs are available from the account page (10 of 15). security.txt returns 404 and no disclosure policy, bug bounty or certification was found (0 of 20). 0 + 10 + 3 + 10 + 0 = 23.\n- WhoisXML API (39): An API key with no scopes found, accepted as an apiKey query parameter that overrides the Authorization header, or as a Bearer token including a server-to-server OAuth token; an IP allowlist can be set on the account (20 less 10 for the query string, plus 4 for OAuth and the allowlist, so 14). Every call is a read and the MCP server has no write tools, but there is no read-only or restricted key (12 of 20). Records include raw registrar text from third parties with no guidance on treating it as untrusted (5 of 15). The MCP server's account_balance tool reports credits per product and the account page shows usage, with no per-call log documented (5 of 15). security.txt returns 404, no disclosure policy, bug bounty or certification was found, and the payment page names only a PCI-compliant card processor (3 of 20). 14 + 12 + 5 + 5 + 3 = 39.\n\n### Schema \u0026 documentation: Pulsedive +7\n\n- Pulsedive (77): OpenAPI 3.0.3 documents for every endpoint, eleven YAML files under Apache 2.0, with typed parameters and response schemas, though split per endpoint and without a securitySchemes block in the scan and explore file (22 of 25). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). Each endpoint states its purpose, probe and submit are explained with their side effects, and the collection page says what each timestamp means, with little on when not to call (15 of 20). Enumerated 0 or 1 flags, required parameters marked, risk and type enums, but key is optional while 401 describes it missing, and explore summaries allow types the indicator schema does not (11 of 15). curl examples on every page and an error table for 400, 401, 404, 429 and 500 with an example body (12 of 15). No API version or changelog; the docs launch post of 30 March 2026 and a footer version number are the only dated changes, and the spec marks the recent field deprecated with no date (7 of 15). 22 + 10 + 15 + 11 + 12 + 7 = 77.\n- WhoisXML API (70): The surface graded is the WHOIS API, with the hosted MCP server noted. No OpenAPI document. JSON Schema draft-07 and XSD files define the WHOIS record, the DomainInfo response and the error body, and a Postman collection is published (15 of 25). llms.txt on www.whoisxmlapi.com lists the APIs, databases and feeds (10). The making-requests page states each parameter's purpose, default and credit cost, lists deprecated parameters that are still accepted, and says when RDAP applies, with little on when not to call (15 of 20). rdap, outputFormat and the cache flags have enumerated values and the record schema is typed, but unknown parameters are ignored silently and the output page gives no types in prose (11 of 15). Request examples, example records and an error table with HTTP status, errorCode and message (12 of 15). No API version and no changelog for the API; press releases summarise product updates yearly, the newest dated 9 May 2025, and the MCP server's versions are dated in the registry (7 of 15). 15 + 10 + 15 + 11 + 12 + 7 = 70.\n\n## Score by category\n\n| Category | Weight | Pulsedive | WhoisXML API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 31 | 65 | WhoisXML API +34 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 70 | Pulsedive +7 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 65 | WhoisXML API +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 23 | 39 | WhoisXML API +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 25 | Pulsedive +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 40 | 76 | WhoisXML API +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 57 | 60 | WhoisXML API +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47.9 · D** | **56.8 · C** | |\n\n## Facts side by side\n\n| Fact | Pulsedive | WhoisXML API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Pulsedive LLC | Whois API, Inc. |\n| Hosted endpoint | no (local only) | `https://mcp-hosted.whoisxmlapi.com/mcp` |\n| Transports | | Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 0 | 35 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.whois-api-llc/mcp-whoisxmlapi` |\n| Last release | 2026-10-27 | 2026-11-03 |\n| Terms last updated | 2022-05-02 | 2025-03-03 |\n| Privacy policy last updated | 2024-08-28 | 2020-04-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n\n## Verdicts\n\n**Pulsedive.** Lookups work with no key at all, a free account allows 50 requests a day, and the docs ship llms.txt, per-endpoint OpenAPI files and timestamps for every scan. The key travels only in the query string, numeric limits live in a 2024 blog post rather than the docs, and there is no status page, SLA, security.txt or official SDK.\n\n**WhoisXML API.** 500 free credits with no card, JSON Schema and XSD for every response, 429s with Retry-After, cache controls that set the price per lookup, and a 35-tool hosted MCP server with OAuth. Per-credit prices sit behind a calculator, the terms confine data to one site and forbid AI training on it, and the key is accepted in the query string.\n\n## Before you call either\n\n### Pulsedive\n\n1. Call `indicator.php?indicator=\u003cvalue\u003e\u0026pretty=1\u0026key=...`; without a key the limit is about 10 requests a day, so register for 50\n2. Read `risk`, `risk_recommended` and `stamp_probed` together; an old `stamp_probed` means the scan data may be stale, so queue a scan with `analyze.php` (`probe=0` passive, `submit=0` to avoid storing)\n3. Poll `analyze.php?qid=` no more than every 500 ms; polling does not count against the quota, but each page of linked indicators does\n4. Treat a 429 as the day's or month's quota spent and stop; there is no Retry-After, and explore searches above the plan's row limit also return 429\n5. Expect user comments, banners and DOM snippets in indicator properties, which are third-party content\n\n### WhoisXML API\n\n1. Send the key as `Authorization: Bearer` and `outputFormat=JSON`; the default output is XML and an `apiKey` query parameter overrides the header\n2. Leave the cache flags alone for 1 credit a lookup; `_hardRefresh=1` costs 5 credits, and `_dbOnly=1` returns WHOIS_03 when nothing is cached\n3. Read `audit.updatedDate` before trusting a record, and check `dataError` for MASKED_WHOIS_DATA or PARTIAL_DATA\n4. Watch `X-RateLimit-Remaining` and on 429 AUTHENTICATE_06 wait for `Retry-After`; a 401 AUTHENTICATE_05 means the balance is spent, so stop\n5. Keep results inside the customer's own systems; the terms forbid passing data to third parties or using it to train models\n\n## Questions\n\n### Which is better for AI agents, Pulsedive or WhoisXML API?\n\nWhoisXML API scores 56.8 (C) on agent readiness against Pulsedive's 47.9 (D), and leads in 5 of 7 scored categories. Pulsedive leads on schema \u0026 documentation and payments \u0026 pricing.\n\n### Do Pulsedive and WhoisXML API need an API key?\n\nPulsedive needs an API key. WhoisXML API takes an API key or an OAuth sign-in.\n\n### Can an agent call Pulsedive and WhoisXML API without installing anything?\n\nNo hosted endpoint is listed for Pulsedive. WhoisXML API has a hosted endpoint at https://mcp-hosted.whoisxmlapi.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"pulsedive\", \"b\": \"whoisxml-api\"}`. From a terminal: `anchor compare pulsedive whoisxml-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/pulsedive.json and https://www.anchorterminal.com/api/v1/tools/whoisxml-api.json\n\n## Other comparisons with Pulsedive or WhoisXML API\n\n- [AbuseIPDB vs Pulsedive](https://www.anchorterminal.com/compare/abuseipdb-vs-pulsedive.md)\n- [AbuseIPDB vs WhoisXML API](https://www.anchorterminal.com/compare/abuseipdb-vs-whoisxml-api.md)\n- [GreyNoise vs Pulsedive](https://www.anchorterminal.com/compare/greynoise-vs-pulsedive.md)\n- [GreyNoise vs WhoisXML API](https://www.anchorterminal.com/compare/greynoise-vs-whoisxml-api.md)\n- [VirusTotal vs WhoisXML API](https://www.anchorterminal.com/compare/virustotal-vs-whoisxml-api.md)\n- [IPinfo vs Pulsedive](https://www.anchorterminal.com/compare/ipinfo-vs-pulsedive.md)\n- [IPinfo vs WhoisXML API](https://www.anchorterminal.com/compare/ipinfo-vs-whoisxml-api.md)\n- [Censys vs WhoisXML API](https://www.anchorterminal.com/compare/censys-vs-whoisxml-api.md)\n- [Pulsedive vs SecurityTrails](https://www.anchorterminal.com/compare/pulsedive-vs-securitytrails.md)\n- [SecurityTrails vs WhoisXML API](https://www.anchorterminal.com/compare/securitytrails-vs-whoisxml-api.md)\n- [Shodan vs WhoisXML API](https://www.anchorterminal.com/compare/shodan-vs-whoisxml-api.md)\n- [Censys vs Pulsedive](https://www.anchorterminal.com/compare/censys-vs-pulsedive.md)\n- [Pulsedive vs Shodan](https://www.anchorterminal.com/compare/pulsedive-vs-shodan.md)\n- [Pulsedive vs VirusTotal](https://www.anchorterminal.com/compare/pulsedive-vs-virustotal.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Pulsedive vs WhoisXML API", "url": "" } ], "description": "WhoisXML scores 56.8 (C) to Pulsedive's 47.9 (D) for secintel indicators. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Pulsedive D 47.9", "WhoisXML API C 56.8", "scores" ], "h1": "Pulsedive vs WhoisXML API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/pulsedive-vs-whoisxml-api", "published": "2026-10-01", "section": "tools", "title": "Pulsedive vs WhoisXML for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/pulsedive-vs-whoisxml-api" }, "tokens": { "markdown": 4200, "slim": 2580 }, "version": 1 }