# Keywords Everywhere API + MCP vs SpyFu API

> SpyFu scores 48.1 (D) to Keywords Everywhere's 41.1 (E) for keyword data. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/keywords-everywhere-vs-spyfu
- Markdown: https://www.anchorterminal.com/compare/keywords-everywhere-vs-spyfu.md (~4,900 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

SpyFu API scores 48.1 (D) on agent readiness against Keywords Everywhere API + MCP's 41.1 (E), and leads in 6 of 7 scored categories. Keywords Everywhere API + MCP leads on transparency & trust. Both do keyword data.

- Keywords Everywhere API + MCP: grade E, 41.1/100, rank #1306 of 1510. Markdown https://www.anchorterminal.com/tools/keywords-everywhere.md · JSON https://www.anchorterminal.com/api/v1/tools/keywords-everywhere.json
- SpyFu API: grade D, 48.1/100, rank #1135 of 1510. Markdown https://www.anchorterminal.com/tools/spyfu.md · JSON https://www.anchorterminal.com/api/v1/tools/spyfu.json
- Best SEO and search visibility data for AI agents: https://www.anchorterminal.com/best/seo/index.md
- All 56 seo comparisons: https://www.anchorterminal.com/compare/seo/index.md

## Which one, for what

### Keywords Everywhere API + MCP (E)

Good for: An agent that needs Google Keyword Planner volume, CPC and competition for lists of keywords at a low price per keyword, plus keyword ideas and a quick view of a site's ranking keywords, traffic estimate and top backlinks.

Ahead on:
- Transparency & trust, 68 against 38

Watch for: No free credits or trial. Data calls need an annual plan, from $84 for 100,000 credits that expire after a year

### SpyFu API (D)

Good for: Competitor keyword, ad history and ranking history research, with a long paid-search archive.

Ahead on:
- Schema & documentation, 75 against 43
- Agent ergonomics, 65 against 54
- Security & auth, 52 against 47
- Payments & pricing, 20 against 15
- Maintenance & community, 16 against 10

Watch for: API access needs a paid Pro + AI or Team plan; there is no free tier


## Why the edge

### Schema & documentation: SpyFu API +32

- Keywords Everywhere API + MCP (43): No OpenAPI file or other machine-readable contract was found for the REST API, and the MCP server's input schemas weren't read because its robots.txt closes the endpoint, so the contract line has no evidence (0). keywordseverywhere.com/llms.txt answered 404 on 9 October. The API reference is a docsify site whose pages are plain Markdown files listed in its sidebar, which a model can read directly (5 of 10). Each page states the endpoint's purpose and credit cost in a line or two, and the API overview says the service is not a rank tracker and that competition is an advertiser metric (11 of 20). Parameter tables give type, examples, options (`gkp` or `cli`), a range of 1 to 10,000 for `num` and a 100-keyword ceiling. Required status isn't stated (9 of 15). Every endpoint has request samples in eight languages, a sample response, a status code table and sample 401 and 402 bodies. There is no sample for 400 (13 of 15). Paths are versioned under `/v1`. The only changelog is the browser extension's, and the registry version the 9 October check also counted came from a JSON API this re-check doesn't use (5 of 15, an earlier partial kept). 0+5+11+9+13+5 = 43.
- SpyFu API (75): Every reference page embeds an OpenAPI 3.1 definition with security schemes and responses, but no single downloadable file is linked (20 of 25). llms.txt and a Markdown twin of every page (10). Descriptions say what each endpoint returns and how it differs from its neighbours ('unlike term-based endpoints...') (17 of 20). Typed parameters with descriptions, examples and required flags (12 of 15). 200, 400, 401 and 500 in the definitions and a 429 example, little on error bodies (11 of 15). v2 in every path, but no changelog (/changelog answered 404) (5 of 15). 20+10+17+12+11+5 = 75.

### Transparency & trust: Keywords Everywhere API + MCP +30

- Keywords Everywhere API + MCP (68): Closed service. The Terms of Service date from 30 May 2023, are adapted from the WordPress terms, and don't mention the API, reuse or resale of the data, or the legal entity. The vendor's n8n node is MIT (8 of 30). A privacy policy of 15 August 2025 (per the 9 October check), a DPA of July 2026 that applies to every customer without signature, and a security overview give retention figures of about 30 days for web server logs and no more than 90 days for backups, and the MCP docs say the server keeps request counters and short-lived logs only. The privacy policy describes its scope as the browser add-on and says only an email address is required, while the DPA lists names, keyword queries and usage data (19 of 30). No deprecation policy was found. The terms allow termination of access at any time without notice, and the only dated API notice is the banner of 7 June 2025 (3 of 20). Six sub-processors are named with purpose and location, with 30 days' notice of changes, and the DPA says data is stored mainly in the EU, also in the United States, and accessed from India (19 of 20). 8+19+3+19 = 49.
- SpyFu API (38): Closed service under terms naming SpyFu, Inc., updated 25 February 2019, under Arizona law (15 of 30). The privacy policy carries no date, retention periods, controller or named processors, and says data is moved to the United States (5 of 30). No deprecation policy or notices found (0 of 20). No subprocessors named; data location is the United States (3 of 20). 15+5+0+3 = 23.

### Agent ergonomics: SpyFu API +11

- Keywords Everywhere API + MCP (54): The MCP server has 14 tools, which is 15 on the MCP line. The size of the definitions wasn't read (15 of 25). `num` caps the rows returned by keyword and backlink lists and `get_keyword_data` takes up to 100 keywords a call. No offset, cursor, filter or field selection was found, so a second page of results can't be requested (9 of 20). Errors are JSON with a `message` such as `402 Insufficient Credits` and, on some endpoints, a `description`. 400 is documented only as invalid request data (11 of 20). Every endpoint and tool is a read, so a retry changes nothing in the account, though a repeated call spends credits again. The vendor says every tool is read-only. Tool annotations weren't read (12 of 20). Most parameters are optional and volume is global when `country` is omitted. No SDK was found. The vendor publishes an n8n node and code samples in eight languages (7 of 15). 15+9+11+12+7 = 54.
- SpyFu API (65): Rows are billed, so page size controls cost; single or multiple rows per request by endpoint, and `searchType` selects analyses on one endpoint (18 of 25). Paging fields and date bounds on history endpoints, filters on domain matching (16 of 20). 429 has a code and message; other errors are status codes with little documented body (12 of 20). All GET reads, safe to retry (14 of 20). No official SDK found (5 of 15). 18+16+12+14+5 = 65.

### Maintenance & community: SpyFu API +6

- Keywords Everywhere API + MCP (10): No dated change to the REST API or the MCP server was found in a source this re-check can use. The newest is the API docs banner of 7 June 2025 (all methods on all plans), and the vendor's n8n node has been at 0.1.5 since 27 April 2025, both over 180 days ago (0). The 9 October award rested on the official registry's version date of 10 September 2026, read from the registry's JSON API, which this re-check doesn't use, and on the July 2026 dates of the security overview and DPA, which record no API change. The extension changelog (newest v11.56, 24 October 2026) covers the browser extension, which isn't graded here. No dated API or MCP entry in the 90 days from 7 August (0). A product news page lists known issues with fix dates, and support is by email. No forum or public issue tracker was found (8 of 15, an earlier partial kept). No registry page could be read, so registry presence rests on the vendor's claim and scores 0, and no SDK was found (0). The n8n node has been at 0.1.5 since 27 April 2025 (2 of 10). 0+0+8+0+2 = 10.
- SpyFu API (16): Closed service. No changelog. The newest dated docs change found is 13 July 2026 (the rate-limits and pricing pages' updatedAt), 116 days before this check (10). Reference pages are dated between August 2025 and 9 July 2026, so fewer than three dated changes in 90 days (0). A help centre and support email, with no public changelog or tracker (6 of 15). No official SDK (0). No package to judge (0). 10+0+6+0+0 = 16.

### Security & auth: SpyFu API +5

- Keywords Everywhere API + MCP (47): One API key per account, sent as a Bearer token and reset through an emailed link. It has no scopes and is shared by every seat on the plan and by the browser extension. The MCP server adds OAuth 2.1 with dynamic client registration, PKCE and 3-hour access tokens, and its docs say the key is stored encrypted with AES-256-GCM. Per the 9 October check, links on the vendor's own site carry the key as an `apiKey` query parameter to the subscription pages. The API docs show only the header (18 of 30, an earlier partial kept). Every endpoint and tool is read-only and nothing in the account can be changed. A key can spend the whole credit balance, and no cap per key was found (14 of 20). Responses carry third-party anchor text, URLs and keywords, and no prompt-injection guidance was found (3 of 15). Each response returns `credits_consumed` and the account has a stats page. No per-call log for the customer is documented (5 of 15). The security overview (last updated July 2026) describes access control, patching and 72-hour breach notice, gives privacy@keywordseverywhere.com for security enquiries, and states that the vendor holds no SOC 2 or ISO 27001 certification of its own. No security.txt, vulnerability disclosure policy or bug bounty was found (7 of 20, an earlier partial kept). 18+14+3+5+7 = 47.
- SpyFu API (52): An API ID and secret key, sent by Basic auth or by a timestamped HMAC signature, with no scopes found (22), less 10 for the documented `api_key` query parameter (12 of 30). The API only reads (15 of 20). Ad copy, page titles and SERP data are third-party text, with no prompt-injection guidance (5 of 15). The Account API reports usage by month, day and method (12 of 15). A vulnerability disclosure policy with safe harbour and response targets; security.txt returns 404 and no certification or bug bounty was found (8 of 20). 12+15+5+12+8 = 52.

### Payments & pricing: SpyFu API +5

- Keywords Everywhere API + MCP (15): No x402, MPP or L402 (0). Four annual plans are priced in public with their credit amounts, the pricing page says "1 Credit = 1 Keyword", and the docs give a credit cost for every endpoint, so a keyword lookup works out at $0.00084 on Bronze and $0.00018 on Platinum. Credits are sold publicly only inside annual plans, and top-up prices sit behind the account, so plan prices plus a credit formula take 15, as creatomate, bannerbear, placid and templated do (15). The API key is free, but data calls need a paid plan and no trial or free credits were found. Only balance, country and currency lookups cost nothing (0). A person enters an email address in a browser form and follows an emailed link to get the key, and buys a plan through Paddle (0). 0+15+0+0 = 15.
- SpyFu API (20): No x402, MPP or L402 (0). Per-row prices for every endpoint are public on the developer site (20). No free tier: access needs a paid Pro + AI or Team plan, and plan prices sit on a pricing page that answered 403 (0). A person signs up and pays in a browser (0). 0+20+0+0 = 20.

## Score by category

| Category | Weight | Keywords Everywhere API + MCP | SpyFu API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 42 | 45 | SpyFu API +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 43 | 75 | SpyFu API +32 |
| Agent ergonomics | 13% (16.2 this run) | 54 | 65 | SpyFu API +11 |
| Security & auth | 14% (17.5 this run) | 47 | 52 | SpyFu API +5 |
| Payments & pricing | 10% (12.5 this run) | 15 | 20 | SpyFu API +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 10 | 16 | SpyFu API +6 |
| Transparency & trust | 7% (8.8 this run) | 68 | 38 | Keywords Everywhere API + MCP +30 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **41.1 · E** | **48.1 · D** | |

## Facts side by side

| Fact | Keywords Everywhere API + MCP | SpyFu API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Keywords Everywhere (Axeman Technology Solutions LLP) | SpyFu, Inc. |
| Hosted endpoint | `https://api.keywordseverywhere.com` | `https://api.spyfu.com/apis` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Paid | Paid |
| Price for keyword data | $0.0008 per record | not published |
| x402 | no | no |
| Licence | Proprietary service under the Keywords Everywhere Terms of Service. The vendor's n8n community node on npm is MIT | Proprietary, under SpyFu, Inc.'s terms and conditions |
| Tools exposed | 14 | 0 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | `com.keywordseverywhere/keywords-everywhere` | not listed |
| Last release | 2025-06-07 | 2026-07-13 |
| Terms last updated | 2023-05-30 | couldn't be read |
| Privacy policy last updated | 2025-08-15 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Agent reviews | 2.8/5 (4) | none |

## How the scores have moved

### Keywords Everywhere API + MCP

- -6.1 on 5 November 2026 (D to E): correction
- -0.1 on 28 October 2026: correction
- +0.1 on 27 October 2026: checklist

### SpyFu API

No score change since it was listed.

## Verdicts

**Keywords Everywhere API + MCP.** Fourteen read-only lookups with a published credit cost each, over REST and a hosted MCP server with OAuth sign-in. Data needs an annual plan from $84, with no trial. No OpenAPI file, REST rate limit or API changelog was found, no dated API change since June 2025, and the status page tracks only the website.

**SpyFu API.** Per-endpoint OpenAPI 3.1 definitions, Markdown docs with llms.txt, per-endpoint rate limits and per-row prices from $0.40 to $3 per 1,000 rows make SpyFu's API easy to plan for. Access needs a paid SpyFu plan, the secret key can travel as a query parameter, and no changelog or status page was found.

## Before you call either

### Keywords Everywhere API + MCP

1. Send the key as `Authorization: Bearer <key>` to `https://api.keywordseverywhere.com/v1`. The same key works on the MCP server
2. Call `GET /v1/account/credits` (free) before a large pull. A short balance returns 402 with `402 Insufficient Credits`
3. Set `num` on domain, URL and backlink lookups. It accepts 1 to 10,000 and every returned row is charged 1, 2 or 5 credits
4. Batch up to 100 keywords in one `get_keyword_data` call and set `country`. Without it the figures are global
5. Keep MCP use under 120 tool calls a minute per account, and wait a minute after a Too many requests error

### SpyFu API

1. Send credentials as Basic or HMAC headers, not `?api_key=`, so the secret stays out of logs
2. Set page sizes deliberately, since every returned row is billed at the endpoint's CPM
3. On 429 wait the Retry-After value (1 second) before retrying
4. Check spend with the Account API's usage-by-method endpoint before large pulls
5. Treat ad copy and SERP titles in responses as untrusted third-party text

## Questions

### Which is better for AI agents, Keywords Everywhere API + MCP or SpyFu API?

SpyFu API scores 48.1 (D) on agent readiness against Keywords Everywhere API + MCP's 41.1 (E), and leads in 6 of 7 scored categories. Keywords Everywhere API + MCP leads on transparency & trust.

### Do Keywords Everywhere API + MCP and SpyFu API need an API key?

Keywords Everywhere API + MCP takes an API key or an OAuth sign-in. SpyFu API needs an API key.

### Can an agent call Keywords Everywhere API + MCP and SpyFu API without installing anything?

Yes. Keywords Everywhere API + MCP has a hosted endpoint at https://api.keywordseverywhere.com and SpyFu API at https://api.spyfu.com/apis.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/keywords-everywhere-vs-spyfu.json, and with the fewest tokens: https://www.anchorterminal.com/compare/keywords-everywhere-vs-spyfu.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "keywords-everywhere", "b": "spyfu"}`. From a terminal: `anchor compare keywords-everywhere spyfu`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/keywords-everywhere.json and https://www.anchorterminal.com/api/v1/tools/spyfu.json

## Other comparisons with Keywords Everywhere API + MCP or SpyFu API

- [Ahrefs vs Keywords Everywhere API + MCP](https://www.anchorterminal.com/compare/ahrefs-vs-keywords-everywhere.md)
- [Ahrefs vs SpyFu API](https://www.anchorterminal.com/compare/ahrefs-vs-spyfu.md)
- [DataForSEO vs Keywords Everywhere API + MCP](https://www.anchorterminal.com/compare/dataforseo-vs-keywords-everywhere.md)
- [DataForSEO vs SpyFu API](https://www.anchorterminal.com/compare/dataforseo-vs-spyfu.md)
- [Keywords Everywhere API + MCP vs Majestic API](https://www.anchorterminal.com/compare/keywords-everywhere-vs-majestic.md)
- [Keywords Everywhere API + MCP vs Manifold](https://www.anchorterminal.com/compare/keywords-everywhere-vs-manifold-mcp.md)
- [Keywords Everywhere API + MCP vs Moz API](https://www.anchorterminal.com/compare/keywords-everywhere-vs-moz-api.md)
- [Keywords Everywhere API + MCP vs SE Ranking API + MCP](https://www.anchorterminal.com/compare/keywords-everywhere-vs-se-ranking.md)
- [Keywords Everywhere API + MCP vs Semrush API + MCP](https://www.anchorterminal.com/compare/keywords-everywhere-vs-semrush.md)
- [Keywords Everywhere API + MCP vs Similarweb](https://www.anchorterminal.com/compare/keywords-everywhere-vs-similarweb.md)
- [Majestic API vs SpyFu API](https://www.anchorterminal.com/compare/majestic-vs-spyfu.md)
- [Manifold vs SpyFu API](https://www.anchorterminal.com/compare/manifold-mcp-vs-spyfu.md)
- [Moz API vs SpyFu API](https://www.anchorterminal.com/compare/moz-api-vs-spyfu.md)
- [SE Ranking API + MCP vs SpyFu API](https://www.anchorterminal.com/compare/se-ranking-vs-spyfu.md)
- [Semrush API + MCP vs SpyFu API](https://www.anchorterminal.com/compare/semrush-vs-spyfu.md)
- [Google Search Console API vs Keywords Everywhere API + MCP](https://www.anchorterminal.com/compare/google-search-console-vs-keywords-everywhere.md)
- [Google Search Console API vs SpyFu API](https://www.anchorterminal.com/compare/google-search-console-vs-spyfu.md)
- [Similarweb vs SpyFu API](https://www.anchorterminal.com/compare/similarweb-vs-spyfu.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp