{ "data": { "a": { "slug": "moz-api", "name": "Moz API", "vendor": "SEOmoz, Inc.", "vendorUrl": "https://moz.com", "kind": "http-api", "category": "seo", "summary": "Moz API is a hosted JSON-RPC 2.0 service for SEO data from Moz's link and keyword indexes. It returns Domain Authority, backlinks, keyword metrics, ranking keywords and search results, with a beta MCP server for AI clients.", "url": "https://www.anchorterminal.com/tools/moz-api", "markdownUrl": "https://www.anchorterminal.com/tools/moz-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/moz-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/moz-api.json", "license": "Proprietary service under the Moz API General Conditions (effective 12 August 2026 for new subscribers). Displaying Moz data to others requires attribution under the API legal page", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.moz.com/jsonrpc", "packages": [], "auth": "api-key", "authNotes": "Self-serve. A person signs up at moz.com with a credit card, then creates a token in the API dashboard. Each account holds up to five tokens, which can be deleted, and every request sends one in the `x-moz-token` header. No scopes or read-only tokens were found in the reviewed documentation. The beta MCP server at https://api.moz.com/mcp/v1/data accepts OAuth (authorisation code with PKCE, dynamic client registration, one scope named `mcp`) or the same token as a Bearer header, and is limited to account owners.", "pricing": "freemium", "pricingNotes": "Free plan of 50 rows a month at one request every ten seconds, which needs a valid credit card. Paid plans run from $20 a month for 3,000 rows to $500 for 500,000, with overage from $5 per 1,000 rows down to $10 per 10,000. Over 4 million rows a month is quoted by sales. There is no sandbox, though `quota.lookup`, `test.ping` and `test.ping.async` cost no rows (checked 2026-10-08).", "priceSummary": "$20 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the pricing page or the product page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://moz.com/api/docs", "capabilities": [ "seo.keywords", "seo.backlinks", "seo.serp", "seo.rankings" ], "tags": [ "hosted", "json-rpc", "api-key", "freemium", "mcp", "oauth", "backlinks", "keywords", "closed-source" ], "lastRelease": "2026-08-14", "graded": true, "anchor": { "graded": true, "score": 45.3, "grade": "E", "agentReady": false, "rank": 770, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 28, "payments": 20, "reliability": 42, "schema": 50, "security": 38, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The JSON-RPC API documents every error code, its rate limits and the row cost of each method, and failed validation uses no quota. No working status page, SLA, machine-readable spec or official SDK was found. Tokens carry no scopes, and the free plan needs a credit card.", "bestFor": "Agents that need Domain Authority, backlink lists, link intersects, keyword volume and difficulty, search intent and ranking keywords at a low entry price, on a read-only data set.", "strengths": [ "Error reference lists 13 codes, each with HTTP status, a machine-readable `data.issue` and the parameter at fault", "Edge rate limits are published with numbers, and per-method 429 responses carry `Retry-After`", "Each method page states its row cost, and validation and quota checks run before any rows are used", "List methods take a `limit`, a paging token, sort keys and named filters", "Public plan prices from $20 a month for 3,000 rows, with per-row overage prices" ], "weaknesses": [ "No working public status page was found, and moz.statuspage.io reports the Moz Status page as inactive", "No downloadable OpenAPI or OpenRPC file, no llms.txt and no official SDK in the reviewed documentation", "Tokens have no scopes or read-only mode, and one token works on both the Data and Local MCP endpoints", "The free plan of 50 rows a month requires a valid credit card", "security.txt expired on 8 October 2026 (UTC), and its policy, acknowledgements and PGP key links return 404" ], "agentNotes": [ "Send a request `id` of at least 24 characters (letters, numbers and hyphens). A UUID works. Shorter ids are rejected with -32654.", "Stop on a 401. Ten 401 or 403 responses in five minutes block the caller for 30 minutes.", "On 429 with code -32658 wait the `Retry-After` seconds. On code -32650 no wait time is given, so back off exponentially.", "Call `quota.lookup` (free) before large pulls. List methods charge one row per result, and `limit` is capped at 50 on link lists.", "Poll `async.call.lookup` for `data.keyword.serp.generate`, and collect the result within 20 seconds of first seeing it complete." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.3 } ], "editorialScores": { "ergonomics": 74, "maintenance": 28, "payments": 20, "reliability": 42, "schema": 50, "security": 38, "transparency": 39 }, "provenanceScore": 79 }, "connect": { "http": "curl -X POST https://api.moz.com/jsonrpc -H \"x-moz-token: $MOZ_TOKEN\" -H \"Content-Type: application/json\" -d '{\"jsonrpc\":\"2.0\",\"id\":\"01a0458f-a14f-7254-aa11-7c6cb734e3f2\",\"method\":\"quota.lookup\",\"params\":{\"data\":{\"path\":\"api.limits.data.rows\"}}}'", "claudeCode": "claude mcp add moz-mcp-v1-data https://api.moz.com/mcp/v1/data --transport http --header \"Authorization: Bearer $YOUR_MOZ_TOKEN\" --scope user" }, "letme": { "capability": "https://letme.dev/seo.keywords", "tool": "https://letme.dev/moz-api" }, "area": "web-data", "unitPrices": [ { "item": "Free plan", "unit": "month", "usd": 0, "note": "50 rows a month, one request every ten seconds, credit card required" }, { "item": "Starter Medium", "unit": "month", "usd": 20, "note": "3,000 rows, no overage, plus 150 beta rows" }, { "item": "Starter Large", "unit": "month", "usd": 75, "note": "15,000 rows, plus 750 beta rows" }, { "item": "Growth Small", "unit": "month", "usd": 125, "note": "50,000 rows, plus 3,500 beta rows" }, { "item": "Growth Medium", "unit": "month", "usd": 250, "note": "120,000 rows, plus 8,400 beta rows" }, { "item": "Growth Large", "unit": "month", "usd": 500, "note": "500,000 rows, plus 35,000 beta rows" }, { "item": "Overage row, Starter Large", "unit": "record", "usd": 0.005, "note": "$5 per 1,000 rows" }, { "item": "Overage row, Growth Small", "unit": "record", "usd": 0.0025, "note": "$25 per 10,000 rows" }, { "item": "Overage row, Growth Medium", "unit": "record", "usd": 0.002, "note": "$20 per 10,000 rows" }, { "item": "Overage row, Growth Large", "unit": "record", "usd": 0.001, "note": "$10 per 10,000 rows" } ], "provenance": { "legalEntity": "SEOmoz, Inc.", "domain": "moz.com", "domainRegistered": "1998-04-29", "endpointOnVendorDomain": true, "terms": "https://moz.com/api-general-conditions", "privacy": "https://moz.com/privacy-policy", "statusPage": "", "changelog": "https://moz.com/whats-new/archive", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The API General Conditions name SEOMOZ, INC., a Delaware corporation, as the contracting party. The site footer reads SEOMoz, Inc., a Ziff Davis company, and the terms of use give 360 Park Ave. S., 17th Floor, New York, NY 10010 for notices.", "The API answers at https://api.moz.com/jsonrpc and the MCP server at https://api.moz.com/mcp/v1/data, both on moz.com.", "moz.com/.well-known/security.txt gives a contact address and `Expiration: 2026-10-07T22:45:48-07:00`, about three hours before our fetch at 08:42 UTC on 8 October 2026. Its Policy, Acknowledgements and Encryption links (moz.com/security-policy, /hall-of-fame, /pgp-key.txt) return 404.", "moz.statuspage.io redirects to a page saying the Moz Status page is inactive and visible only to team members. status.moz.com and health.moz.com did not connect from our network.", "The changelog is Moz's product updates archive, which covers all products. The newest Moz API entry is the MCP server beta of 14 August 2026.", "RDAP for moz.com gives a registration date of 1998-04-29 and expiry in 2029.", "The privacy policy is effective 8 April 2025 and says Moz is owned by Ziff Davis, Inc. and takes part in the EU-U.S. Data Privacy Framework." ], "score": 79 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/moz-api.json", "live": { "slug": "moz-api", "probe": { "target": "https://api.moz.com/jsonrpc", "method": "get", "lastAt": "2026-10-09T09:45:02.129708639Z", "lastOk": true, "lastStatus": 404, "lastMs": 181, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 136, "p95ms24h": 312, "samples24h": 197, "samples30d": 197, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 104, "ok": 104 } ] }, "securityTxt": { "url": "https://moz.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-08T15:38:29.983500854Z" }, "pages": [ { "url": "https://moz.com/whats-new/archive", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:22:15.827097105Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2df39f51de96" }, { "url": "https://moz.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:22:13.802124938Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef92cf739b3e" }, { "url": "https://moz.com/api-general-conditions", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:22:11.727645446Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "13b81cfc0ea8" } ], "updatedAt": "2026-10-09T09:45:02.129708639Z" } }, "answer": "SE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth.", "b": { "slug": "se-ranking", "name": "SE Ranking API + MCP", "vendor": "SE Ranking (SER Acquisition Inc.)", "vendorUrl": "https://seranking.com", "kind": "http-api", "category": "seo", "summary": "SE Ranking is an SEO platform whose Data API returns keyword, backlink, domain, site audit and AI search data for credits. A Project API manages rank tracking in the account, and a hosted MCP server exposes both to agents.", "url": "https://www.anchorterminal.com/tools/se-ranking", "markdownUrl": "https://www.anchorterminal.com/tools/se-ranking.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/se-ranking.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/se-ranking.json", "repo": "https://github.com/seranking/openapi", "license": "Proprietary service under the SE Ranking API Terms of Service. The OpenAPI file and the Claude skills on GitHub are MIT", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.seranking.com", "packages": [], "auth": "mixed", "authNotes": "REST calls take an API key as `Authorization: Token \u003ckey\u003e`, or as an `apikey` query parameter. One key covers the Data, Project, Local Marketing and SE Visible APIs, with no scopes. Keys are self-serve in the API dashboard of any plan or trial, with no app review. The MCP server signs in by OAuth 2.1 with dynamic client registration against the SE Ranking account, or takes the key in an `X-Api-Key` header. Sub-accounts have no keys of their own yet. Direct competitors, resale and embedding raw data in a paid product need written consent.", "pricing": "usage", "pricingNotes": "Data API calls spend credits, from $50 for 250,000 pay-as-you-go credits that don't expire. Each endpoint's credit cost is published and failed requests cost nothing. Subscription plans include 10,000 to 100,000 credits a month, an add-on starts at $540 a year for 3 million credits, and a standalone API plan at $2,148 a year for 12 million. Project API calls use the plan's limits instead of credits. A 14-day trial with 100,000 credits and MCP access needs no card and lets an agent start without a contract. Our request saw the pricing page in pounds.", "priceSummary": "$0.0002 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the MCP docs or the API pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 0, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://seranking.com/api.html", "openapi": "https://raw.githubusercontent.com/seranking/openapi/main/openapi/data-api.yaml", "registryName": "com.seranking/mcp", "capabilities": [ "seo.keywords", "seo.backlinks", "seo.rankings", "seo.traffic", "seo.serp" ], "tags": [ "official", "hosted", "mcp", "oauth", "api-key", "openapi", "closed-source", "usage-credits", "prepaid", "free-trial", "status-page", "ai-visibility" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 50.9, "grade": "D", "agentReady": false, "rank": 681, "ranked": true, "rankOf": 842, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 79, "payments": 40, "reliability": 51, "schema": 58, "security": 21, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Every Data API endpoint has a published credit cost, credits sell from $50 for 250,000 with no expiry, and a 14-day trial needs no card. Keys carry full account access with no scopes or read-only mode, the key may travel in the URL, and no security page, SLA or llms.txt was found.", "bestFor": "An agent that needs keyword, backlink, domain and AI search visibility data at a published price per call, or that manages rank tracking projects for an SE Ranking customer.", "strengths": [ "Credit cost is published per endpoint, failed requests aren't charged, and pay-as-you-go packs start at $50 for 250,000 credits that don't expire", "A 14-day trial with 100,000 credits covers the API and the MCP server, with no card, per the pricing page", "Hosted MCP server at `https://api.seranking.com/mcp`, listed in the official MCP registry as `com.seranking/mcp` with 15 versions since 22 May 2026", "Rate limits are stated as 10 requests a second for the Data API and 5 for the Project API, with backoff guidance for 429", "`limit`, `offset`, `cols` and bracketed `filter` parameters size Data API responses, and an OpenAPI 3.0 file covers its 86 operations" ], "weaknesses": [ "No scoped or read-only keys. The MCP docs say a key has the same access as the account, including Project API deletes", "The API key is accepted as an `apikey` query parameter, and the OpenAPI file and its README describe only that method", "No security page, certification statement, bug bounty or readable security.txt was found, and the API terms say there is no SLA without a separate agreement", "The MCP server advertises 180+ tools with no documented way to load a subset", "The API terms let SE Ranking remove deprecated functionality at any time, with up to 30 days' notice only where practicable" ], "agentNotes": [ "Send the key as `Authorization: Token \u003ckey\u003e`, not `Bearer` and not `?apikey=`, so it stays out of URLs and logs", "Call `GET /v1/account/subscription` (0 credits) and read `units_left` before a large pull. A short balance returns `Insufficient funds`", "Set `limit` and `cols` on per-record endpoints. Backlink summaries cost 100 credits a target and keyword rows 10 credits each", "Stay under 10 requests a second on the Data API and 5 on the Project API per key. Repeated overruns block the Project API for 10 minutes", "Ask the owner before any Project API or `PROJECT_*` create, update or delete call. The key has no read-only mode and nothing confirms a delete" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.9 } ], "editorialScores": { "ergonomics": 58, "maintenance": 79, "payments": 40, "reliability": 51, "schema": 58, "security": 21, "transparency": 59 }, "provenanceScore": 83 }, "connect": { "http": "curl -X GET 'https://api.seranking.com/v1/account/subscription' -H 'Authorization: Token YOUR_API_KEY'", "claudeCode": "claude mcp add --transport http se-ranking https://api.seranking.com/mcp", "config": { "mcpServers": { "se-ranking": { "url": "https://api.seranking.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/seo.keywords", "tool": "https://letme.dev/se-ranking" }, "area": "web-data", "unitPrices": [ { "item": "Data API credit, pay-as-you-go", "unit": "credit", "usd": 0.0002, "note": "$50 for 250,000 credits that don't expire" }, { "item": "Domain overview, per request", "unit": "call", "usd": 0.02, "note": "100 credits at the pay-as-you-go rate. Failed requests cost nothing" }, { "item": "Keyword row (related, similar or question keywords)", "unit": "record", "usd": 0.002, "note": "10 credits a record at the pay-as-you-go rate" }, { "item": "Backlink row", "unit": "record", "usd": 0.0002, "note": "1 credit a record at the pay-as-you-go rate. A backlink summary is 100 credits a target" }, { "item": "Standalone API plan, 12 million credits a year", "unit": "month", "usd": 179, "note": "billed annually at $2,148, Data API only" }, { "item": "API add-on, 3 million credits a year", "unit": "month", "usd": 45, "note": "billed annually at $540, on top of a subscription" } ], "provenance": { "legalEntity": "SER Acquisition Inc.", "domain": "seranking.com", "domainRegistered": "2010-09-16", "endpointOnVendorDomain": true, "terms": "https://seranking.com/legal/api-terms-of-service.html", "privacy": "https://seranking.com/legal/privacy-statement.html", "statusPage": "https://status.seranking.com", "changelog": "https://seranking.com/whats-new.html", "securityTxt": "unknown", "checked": "2026-10-08", "notes": [ "The API Terms of Service (3 March 2026) name SER Acquisition Inc., care of The Corporation Trust Company, 1209 Orange Street, Wilmington, Delaware, as the provider as a general rule, and Seranking Ltd., London, for some earlier customers paying in pounds.", "The privacy statement (last updated 25 June 2026) names Seranking Ltd and SER Acquisition Inc. as joint controllers and says the group shares some data with Planable Inc.", "The REST APIs and the MCP server answer at api.seranking.com.", "seranking.com/.well-known/security.txt answered 403 to our request, so we couldn't tell whether a file exists.", "status.seranking.com is a Pulsetic status page titled SE Ranking Online Status. It isn't linked from the pages we read and its content is drawn by script.", "The What's New page lists releases by year. The dates of its entries aren't in the page's HTML.", "RDAP for seranking.com gives a registration date of 2010-09-16.", "robots.txt allows the pages we read and carries no Content-Signal line." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/se-ranking.json", "live": { "slug": "se-ranking", "probe": { "target": "https://api.seranking.com", "method": "get", "lastAt": "2026-10-09T09:45:07.460554225Z", "lastOk": true, "lastStatus": 401, "lastMs": 103, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 96, "p95ms24h": 123, "samples24h": 23, "samples30d": 23, "days": [ { "date": "2026-10-09", "probes": 23, "ok": 23 } ] }, "vendorStatus": { "page": "https://status.seranking.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:31.020038985Z" }, "updatedAt": "2026-10-09T09:45:07.460554225Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "SEOmoz, Inc.", "b": "SE Ranking (SER Acquisition Inc.)", "name": "Vendor" }, { "a": "https://api.moz.com/jsonrpc", "b": "https://api.seranking.com", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "not published", "b": "$0.002 per record", "name": "Price for seo keywords" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Moz API General Conditions (effective 12 August 2026 for new subscribers). Displaying Moz data to others requires attribution under the API legal page", "b": "Proprietary service under the SE Ranking API Terms of Service. The OpenAPI file and the Claude skills on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "com.seranking/mcp", "name": "MCP registry" }, { "a": "2026-08-14", "b": "2026-09-28", "name": "Last release" }, { "a": "2026-08-12", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-04-08", "b": "2026-06-25", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "0 stars", "name": "Popularity" } ], "faq": [ { "answer": "SE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Moz API or SE Ranking API + MCP?" }, { "answer": "Moz API needs an API key. SE Ranking API + MCP takes an API key or an OAuth sign-in.", "question": "Do Moz API and SE Ranking API + MCP need an API key?" }, { "answer": "Yes. Moz API has a hosted endpoint at https://api.moz.com/jsonrpc and SE Ranking API + MCP at https://api.seranking.com.", "question": "Can an agent call Moz API and SE Ranking API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 74 against 58", "Security \u0026 auth, 38 against 21" ], "also": null, "goodFor": "Agents that need Domain Authority, backlink lists, link intersects, keyword volume and difficulty, search intent and ranking keywords at a low entry price, on a read-only data set.", "slug": "moz-api", "watchFor": "No working public status page was found, and moz.statuspage.io reports the Moz Status page as inactive" }, { "aheadOn": [ "Reliability, 51 against 42", "Schema \u0026 documentation, 58 against 50", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 79 against 28", "Transparency \u0026 trust, 71 against 59" ], "also": null, "goodFor": "An agent that needs keyword, backlink, domain and AI search visibility data at a published price per call, or that manages rank tracking projects for an SE Ranking customer.", "slug": "se-ranking", "watchFor": "No scoped or read-only keys. The MCP docs say a key has the same access as the account, including Project API deletes" } ], "job": { "capability": "seo.keywords", "name": "Seo keywords" }, "others": [ { "json": "https://www.anchorterminal.com/compare/ahrefs-vs-moz-api.json", "title": "Ahrefs vs Moz API", "url": "https://www.anchorterminal.com/compare/ahrefs-vs-moz-api" }, { "json": "https://www.anchorterminal.com/compare/ahrefs-vs-se-ranking.json", "title": "Ahrefs vs SE Ranking API + MCP", "url": "https://www.anchorterminal.com/compare/ahrefs-vs-se-ranking" }, { "json": "https://www.anchorterminal.com/compare/dataforseo-vs-moz-api.json", "title": "DataForSEO vs Moz API", "url": "https://www.anchorterminal.com/compare/dataforseo-vs-moz-api" }, { "json": "https://www.anchorterminal.com/compare/dataforseo-vs-se-ranking.json", "title": "DataForSEO vs SE Ranking API + MCP", "url": "https://www.anchorterminal.com/compare/dataforseo-vs-se-ranking" }, { "json": "https://www.anchorterminal.com/compare/manifold-mcp-vs-moz-api.json", "title": "Manifold vs Moz API", "url": "https://www.anchorterminal.com/compare/manifold-mcp-vs-moz-api" }, { "json": "https://www.anchorterminal.com/compare/manifold-mcp-vs-se-ranking.json", "title": "Manifold vs SE Ranking API + MCP", "url": "https://www.anchorterminal.com/compare/manifold-mcp-vs-se-ranking" }, { "json": "https://www.anchorterminal.com/compare/moz-api-vs-semrush.json", "title": "Moz API vs Semrush API + MCP", "url": "https://www.anchorterminal.com/compare/moz-api-vs-semrush" }, { "json": "https://www.anchorterminal.com/compare/moz-api-vs-similarweb.json", "title": "Moz API vs Similarweb", "url": "https://www.anchorterminal.com/compare/moz-api-vs-similarweb" }, { "json": "https://www.anchorterminal.com/compare/se-ranking-vs-semrush.json", "title": "SE Ranking API + MCP vs Semrush API + MCP", "url": "https://www.anchorterminal.com/compare/se-ranking-vs-semrush" }, { "json": "https://www.anchorterminal.com/compare/se-ranking-vs-similarweb.json", "title": "SE Ranking API + MCP vs Similarweb", "url": "https://www.anchorterminal.com/compare/se-ranking-vs-similarweb" }, { "json": "https://www.anchorterminal.com/compare/google-search-console-vs-moz-api.json", "title": "Google Search Console API vs Moz API", "url": "https://www.anchorterminal.com/compare/google-search-console-vs-moz-api" }, { "json": "https://www.anchorterminal.com/compare/google-search-console-vs-se-ranking.json", "title": "Google Search Console API vs SE Ranking API + MCP", "url": "https://www.anchorterminal.com/compare/google-search-console-vs-se-ranking" } ], "scores": [ { "by": 9, "edge": "se-ranking", "key": "reliability", "moz-api": 42, "name": "Reliability", "se-ranking": 51, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "se-ranking", "key": "schema", "moz-api": 50, "name": "Schema \u0026 documentation", "se-ranking": 58, "weight": 13 }, { "by": 16, "edge": "moz-api", "key": "ergonomics", "moz-api": 74, "name": "Agent ergonomics", "se-ranking": 58, "weight": 13 }, { "by": 17, "edge": "moz-api", "key": "security", "moz-api": 38, "name": "Security \u0026 auth", "se-ranking": 21, "weight": 14 }, { "by": 20, "edge": "se-ranking", "key": "payments", "moz-api": 20, "name": "Payments \u0026 pricing", "se-ranking": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 51, "edge": "se-ranking", "key": "maintenance", "moz-api": 28, "name": "Maintenance \u0026 community", "se-ranking": 79, "weight": 7 }, { "by": 12, "edge": "se-ranking", "key": "transparency", "moz-api": 59, "name": "Transparency \u0026 trust", "se-ranking": 71, "weight": 7 } ], "summary": "SE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth. Both do seo keywords.", "verdicts": { "moz-api": "The JSON-RPC API documents every error code, its rate limits and the row cost of each method, and failed validation uses no quota. No working status page, SLA, machine-readable spec or official SDK was found. Tokens carry no scopes, and the free plan needs a credit card.", "se-ranking": "Every Data API endpoint has a published credit cost, credits sell from $50 for 250,000 with no expiry, and a 14-day trial needs no card. Keys carry full account access with no scopes or read-only mode, the key may travel in the URL, and no security page, SLA or llms.txt was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/moz-api-vs-se-ranking", "json": "https://www.anchorterminal.com/compare/moz-api-vs-se-ranking.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/moz-api-vs-se-ranking.md", "slim": "https://www.anchorterminal.com/compare/moz-api-vs-se-ranking.min.md" }, "markdown": "SE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth. Both do seo keywords.\n\n- Moz API: grade E, 45.3/100, rank #770 of 842. Markdown https://www.anchorterminal.com/tools/moz-api.md · JSON https://www.anchorterminal.com/api/v1/tools/moz-api.json\n- SE Ranking API + MCP: grade D, 50.9/100, rank #681 of 842. Markdown https://www.anchorterminal.com/tools/se-ranking.md · JSON https://www.anchorterminal.com/api/v1/tools/se-ranking.json\n\n## Which one, for what\n\n### Moz API (E)\n\nGood for: Agents that need Domain Authority, backlink lists, link intersects, keyword volume and difficulty, search intent and ranking keywords at a low entry price, on a read-only data set.\n\nAhead on:\n- Agent ergonomics, 74 against 58\n- Security \u0026 auth, 38 against 21\n\nWatch for: No working public status page was found, and moz.statuspage.io reports the Moz Status page as inactive\n\n### SE Ranking API + MCP (D)\n\nGood for: An agent that needs keyword, backlink, domain and AI search visibility data at a published price per call, or that manages rank tracking projects for an SE Ranking customer.\n\nAhead on:\n- Reliability, 51 against 42\n- Schema \u0026 documentation, 58 against 50\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 79 against 28\n- Transparency \u0026 trust, 71 against 59\n\nWatch for: No scoped or read-only keys. The MCP docs say a key has the same access as the account, including Project API deletes\n\n\n## Score by category\n\n| Category | Weight | Moz API | SE Ranking API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 42 | 51 | SE Ranking API + MCP +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 58 | SE Ranking API + MCP +8 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 58 | Moz API +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 38 | 21 | Moz API +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | SE Ranking API + MCP +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 79 | SE Ranking API + MCP +51 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 71 | SE Ranking API + MCP +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.3 · E** | **50.9 · D** | |\n\n## Facts side by side\n\n| Fact | Moz API | SE Ranking API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | SEOmoz, Inc. | SE Ranking (SER Acquisition Inc.) |\n| Hosted endpoint | `https://api.moz.com/jsonrpc` | `https://api.seranking.com` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| Price for seo keywords | not published | $0.002 per record |\n| x402 | no | no |\n| Licence | Proprietary service under the Moz API General Conditions (effective 12 August 2026 for new subscribers). Displaying Moz data to others requires attribution under the API legal page | Proprietary service under the SE Ranking API Terms of Service. The OpenAPI file and the Claude skills on GitHub are MIT |\n| Read-only variant documented | no | yes |\n| llms.txt | no | no |\n| MCP registry | not listed | `com.seranking/mcp` |\n| Last release | 2026-08-14 | 2026-09-28 |\n| Terms last updated | 2026-08-12 | no date given |\n| Privacy policy last updated | 2025-04-08 | 2026-06-25 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | none | 0 stars |\n\n## Verdicts\n\n**Moz API.** The JSON-RPC API documents every error code, its rate limits and the row cost of each method, and failed validation uses no quota. No working status page, SLA, machine-readable spec or official SDK was found. Tokens carry no scopes, and the free plan needs a credit card.\n\n**SE Ranking API + MCP.** Every Data API endpoint has a published credit cost, credits sell from $50 for 250,000 with no expiry, and a 14-day trial needs no card. Keys carry full account access with no scopes or read-only mode, the key may travel in the URL, and no security page, SLA or llms.txt was found.\n\n## Before you call either\n\n### Moz API\n\n1. Send a request `id` of at least 24 characters (letters, numbers and hyphens). A UUID works. Shorter ids are rejected with -32654.\n2. Stop on a 401. Ten 401 or 403 responses in five minutes block the caller for 30 minutes.\n3. On 429 with code -32658 wait the `Retry-After` seconds. On code -32650 no wait time is given, so back off exponentially.\n4. Call `quota.lookup` (free) before large pulls. List methods charge one row per result, and `limit` is capped at 50 on link lists.\n5. Poll `async.call.lookup` for `data.keyword.serp.generate`, and collect the result within 20 seconds of first seeing it complete.\n\n### SE Ranking API + MCP\n\n1. Send the key as `Authorization: Token \u003ckey\u003e`, not `Bearer` and not `?apikey=`, so it stays out of URLs and logs\n2. Call `GET /v1/account/subscription` (0 credits) and read `units_left` before a large pull. A short balance returns `Insufficient funds`\n3. Set `limit` and `cols` on per-record endpoints. Backlink summaries cost 100 credits a target and keyword rows 10 credits each\n4. Stay under 10 requests a second on the Data API and 5 on the Project API per key. Repeated overruns block the Project API for 10 minutes\n5. Ask the owner before any Project API or `PROJECT_*` create, update or delete call. The key has no read-only mode and nothing confirms a delete\n\n## Questions\n\n### Which is better for AI agents, Moz API or SE Ranking API + MCP?\n\nSE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth.\n\n### Do Moz API and SE Ranking API + MCP need an API key?\n\nMoz API needs an API key. SE Ranking API + MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Moz API and SE Ranking API + MCP without installing anything?\n\nYes. Moz API has a hosted endpoint at https://api.moz.com/jsonrpc and SE Ranking API + MCP at https://api.seranking.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/moz-api-vs-se-ranking.json, and with the fewest tokens: https://www.anchorterminal.com/compare/moz-api-vs-se-ranking.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"moz-api\", \"b\": \"se-ranking\"}`. From a terminal: `anchor compare moz-api se-ranking`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/moz-api.json and https://www.anchorterminal.com/api/v1/tools/se-ranking.json\n\n## Other comparisons with Moz API or SE Ranking API + MCP\n\n- [Ahrefs vs Moz API](https://www.anchorterminal.com/compare/ahrefs-vs-moz-api.md)\n- [Ahrefs vs SE Ranking API + MCP](https://www.anchorterminal.com/compare/ahrefs-vs-se-ranking.md)\n- [DataForSEO vs Moz API](https://www.anchorterminal.com/compare/dataforseo-vs-moz-api.md)\n- [DataForSEO vs SE Ranking API + MCP](https://www.anchorterminal.com/compare/dataforseo-vs-se-ranking.md)\n- [Manifold vs Moz API](https://www.anchorterminal.com/compare/manifold-mcp-vs-moz-api.md)\n- [Manifold vs SE Ranking API + MCP](https://www.anchorterminal.com/compare/manifold-mcp-vs-se-ranking.md)\n- [Moz API vs Semrush API + MCP](https://www.anchorterminal.com/compare/moz-api-vs-semrush.md)\n- [Moz API vs Similarweb](https://www.anchorterminal.com/compare/moz-api-vs-similarweb.md)\n- [SE Ranking API + MCP vs Semrush API + MCP](https://www.anchorterminal.com/compare/se-ranking-vs-semrush.md)\n- [SE Ranking API + MCP vs Similarweb](https://www.anchorterminal.com/compare/se-ranking-vs-similarweb.md)\n- [Google Search Console API vs Moz API](https://www.anchorterminal.com/compare/google-search-console-vs-moz-api.md)\n- [Google Search Console API vs SE Ranking API + MCP](https://www.anchorterminal.com/compare/google-search-console-vs-se-ranking.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Moz API vs SE Ranking API + MCP", "url": "" } ], "description": "SE Ranking API + MCP scores 50.9 (D) on agent readiness against Moz API's 45.3 (E), and leads in 5 of 7 scored categories. Moz API leads on agent ergonomics and security \u0026 auth. Both do seo keywords. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Moz API E 45.3", "SE Ranking API + MCP D 50.9", "scores" ], "h1": "Moz API vs SE Ranking API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-moz-api-vs-se-ranking.png", "path": "/compare/moz-api-vs-se-ranking", "published": "2026-10-01", "section": "tools", "title": "Moz API vs SE Ranking API + MCP for AI agents, E 45.3 vs D 50.9", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/moz-api-vs-se-ranking" }, "tokens": { "markdown": 2250, "slim": 730 }, "version": 1 }