# Majestic API vs SpyFu API (slim)

> SpyFu scores 48.1 (D) to Majestic's 33.5 (F) for keyword data. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/majestic-vs-spyfu.md (~4,500 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/majestic-vs-spyfu.json · canonical https://www.anchorterminal.com/compare/majestic-vs-spyfu
- 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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

SpyFu API scores 48.1 (D) on agent readiness against Majestic API's 33.5 (F), and leads in 5 of 7 scored categories. Majestic API leads on maintenance & community and transparency & trust. Both do keyword data.

- Majestic API: F 33.5, rank #1382 of 1486 · https://www.anchorterminal.com/tools/majestic.min.md
- SpyFu API: D 48.1, rank #1123 of 1486 · https://www.anchorterminal.com/tools/spyfu.min.md
- Majestic API, good for An agent that needs backlink, referring domain, anchor text and Trust Flow data in volume for an owner who already pays for the API plan. Ahead on Maintenance & community, 22 against 16; Transparency & trust, 54 against 38.
- SpyFu API, good for Competitor keyword, ad history and ranking history research, with a long paid-search archive. Ahead on Reliability, 45 against 17; Schema & documentation, 75 against 44; Agent ergonomics, 65 against 54; Security & auth, 52 against 32; Payments & pricing, 20 against 15.

| Category | Majestic API | SpyFu API |
| --- | --- | --- |
| Reliability (16%) | 17 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 44 | 75 |
| Agent ergonomics (13%) | 54 | 65 |
| Security & auth (14%) | 32 | 52 |
| Payments & pricing (10%) | 15 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 22 | 16 |
| Transparency & trust (7%) | 54 | 38 |

| Fact (where they differ) | Majestic API | SpyFu API |
| --- | --- | --- |
| Vendor | Majestic (Majestic-12 Limited) | SpyFu, Inc. |
| Hosted endpoint | `https://api.majestic.com` | `https://api.spyfu.com/apis` |
| Licence | Proprietary service under Majestic's Terms and Conditions. The Python 3 connector on GitHub carries a BSD-style licence file | Proprietary, under SpyFu, Inc.'s terms and conditions |
| Tools exposed | none | 0 |
| Last release | none | 2026-07-13 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-04-01 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 3 stars | none |
| Agent reviews | 2.5/5 (4) | none |

Why the edge:
- Schema & documentation, SpyFu API +31: Majestic API 44 (No OpenAPI file or other machine-readable contract was found (0 of 25). Both majestic.com and developer-support.majestic.com serve an llms.txt, and the developer one links an llms-full.txt of its 39 pages (10). Each command page states its purpose, its status, its unit cost and whether it may be queued, and the overview says which command suits large domains (14 of 20). Parameter tables give defaults, maxima and allowed values, and `SortBy1` and `FilteringDepth` list their options. `Filters` is a string expression language of its own (9 of 15). Every command page read has XML and JSON samples, dated 2017. The errors page lists two universal codes and four OpenApps codes, and other codes appear only in passing (9 of 15). The API has no version in its path, no changelog was found, and the deprecated commands table gives replacements without dates (2 of 15). Total 44.); 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.)
- Reliability, SpyFu API +28: Majestic API 17 (Graded on the hosted lines. No status page was found. None is linked from the site footer, the developer docs or either llms.txt (0 of 20), so there is no incident record to read (0 of 30). The docs publish monthly unit allowances, batch sizes (100 items, 1,000 keywords, 50,000 rows) and one concurrency limit, 5 requests at once when sorting or filtering. No requests-per-second figure was found, and clause 13 of the supply terms lets Majestic throttle access at its discretion (6 of 15). No 429 or overload guidance and no Retry-After were found. Nearly every command is a read, and `SkipIfAnalysisCostGreaterThan` stops an oversized download (2 of 15). No SLA was found, and the terms disclaim liability for unavailability (0). The API carries no preview label, with one command, GetRelatedSites, marked Beta (9 of 10). Total 17.); SpyFu API 45 (Hosted lines. No status page found; status.spyfu.com did not resolve and the docs link none (0). No incident history to read (5). Per-endpoint limits published, 10 to 1,000 requests a second over a rolling second (15). 429 with `Retry-After: 1` and a JSON error body, and every endpoint is a read (15). No SLA found (0). Generally available (10). 0+5+15+15+0+10 = 45.)
- Security & auth, SpyFu API +20: Majestic API 32 (An account can hold several API keys, each of which can be disabled and limited to IP addresses or CIDR ranges. OpenApps gives each user a revocable access token paired with the app's private key. Keys have no scopes (22 of 30). The docs show the key as an `app_api_key` URL parameter on GET, advise POST or a cookie instead, and say plain HTTP is still accepted (minus 10, leaving 12). The API is close to read-only, with AddToBucket, SubmitURLsToCrawl and DeleteDownloads the writes found, and the IP allow-list narrows a key. No read-only key or approval step exists (8 of 20). Responses carry third-party anchor text and page titles, and no prompt-injection guidance was found (0 of 15). An IP activity page shows usage by key and address, and GetSubscriptionInfo returns allowance used (9 of 15). The developer security page gives key-handling advice. No security.txt (404), certification, bug bounty or disclosure policy was found (3 of 20). Total 32.); 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.)
- Transparency & trust, Majestic API +16: Majestic API 54 (Closed service with public Terms and Conditions released on 13 April 2026. They are subscription terms with no API section, they still name Silver, Gold and Platinum levels, and they limit use to research. The connectors carry a BSD-style licence (13 of 30). The privacy policy (updated April 2026) names the controller, gives a seven-year retention period for basic customer records and names its outside processors. It still cites the EU-US Privacy Shield as a transfer mechanism, and no DPA or retention period for API request logs was found. A separate GDPR statement covers personal data met in crawling (16 of 30). The command overview marks four commands deprecated with their replacements and no dates, and the terms let Majestic withdraw or amend the service without notice (6 of 20). The privacy policy names Cybersource, PayPal, Zendesk, Infusionsoft, Zapier, Dropbox and Acuity, with no hosting provider or data location stated (8 of 20). Total 43.); 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: Majestic API 54 (`Count`, `From`, `MaxSourceURLsPerRefDomain` and `MaxSameSourceURLs` size a GetBackLinkData response. There is no field selection, and a GetIndexItemInfo row in the sample carries more than 70 columns (12 of 25). `Count` up to 50,000 with `From` for paging, two sort keys and up to 25 filters a query, at an extra 5,000 to 15,000 analysis units (17 of 20). Every response has `Code`, `ErrorMessage` and `FullError`, though few codes are documented (9 of 20). Commands are reads and can be repeated, but each call spends units and the docs don't say whether a failed call is charged. A sandbox host costs nothing (8 of 20). Most commands need only `cmd` and an item, with stated defaults. Connectors exist in eight languages as source on GitHub, last updated between 2016 and 2021 and not on a package registry (8 of 15). Total 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, Majestic API +6: Majestic API 22 (No API changelog or release list was found, and the site updates page is behind the account login. The newest dated product change found is a blog post of 30 July 2026 on a Site Explorer chart, 71 days before the check. The newest dated change to the developer docs is the llms.txt of 26 January 2026, 256 days before. We scored between the two (10 of 30). No three dated API or product releases in the last 90 days (0 of 20). Support is a contact form and an email address, with no public developer forum or issue tracker in use (5 of 15 on the closed-service line). The connectors on GitHub were last updated between March 2016 and September 2021 (5 of 15). They have no CI and no package registry entry (2 of 10). The Fresh Index itself was updated 40 minutes before our read, per the site footer. Total 22.); 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.)