# Moz API > 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. - Canonical: https://www.anchorterminal.com/tools/moz-api - Markdown: https://www.anchorterminal.com/tools/moz-api.md (~7,950 tokens) - Slim: https://www.anchorterminal.com/tools/moz-api.min.md (~2,030 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/moz-api.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade E · 45.3/100 · rank #571 of 629 · #6 in SEO & search visibility · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | SEOmoz, Inc. (https://moz.com) | | Kind | HTTP API | | Category | SEO & search visibility (https://www.anchorterminal.com/categories/seo) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://api.moz.com/jsonrpc` | | Auth | API key · 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 ($20 / mo) · 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). | | x402 | No · No x402, MPP or L402 in the API docs, the pricing page or the product page (checked 2026-10-08). | | 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 | | Docs | https://moz.com/api/docs | | llms.txt | not found | | Last release | 2026-08-14 | | API | JSON-RPC 2.0 over POST at https://api.moz.com/jsonrpc, single and batch requests, gzip in both directions, request bodies up to 100 KB after decompression | | Methods | 73 documented. 33 `data` methods (site metrics, Brand Authority, links, linking domains, anchor text, link intersect, link status, final redirect, top pages, competitors, ranking keywords, keyword metrics, search intent, related keywords, SERP fetch and generate, global top domains and pages), 35 `local` methods for Moz Local, plus quota, index, async and test calls | | MCP server | Beta since 14 August 2026. https://api.moz.com/mcp/v1/data (needs a Moz API subscription) and https://api.moz.com/mcp/v1/local (needs Moz Local). OAuth or a Bearer token. Account owners only. Tool list not readable without an account | | Credentials | Up to five deletable tokens per account, sent as `x-moz-token`. No scopes found. MCP OAuth metadata lists authorisation code, PKCE S256, dynamic client registration and the scope `mcp` | | Rate limits | Free plan one request every ten seconds. Edge limits of 2,000 requests in 60 seconds, 20 client errors in 60 seconds, and a 30-minute block after ten 401 or 403 responses in five minutes. `data.keyword.serp.generate` shares 2,000 requests an hour across all callers | | Errors | Thirteen documented codes from -32700 to -32650 with HTTP status, `data.issue`, `data.key` and `data.explanation`. Per-method 429 (-32658) carries `Retry-After`, edge 429 (-32650) does not | | Quota | Counted in rows. `data.site.metrics.fetch` costs one row a call, list methods one row per result, `data.keyword.serp.generate` up to 21 rows. `quota.lookup`, `metadata.index.fetch` and the test methods are free | | Paging | `offset.limit` (1 to 50 on link lists, default 25) and an opaque `offset.token` returned with each page | | Async | Some methods return an `async_call` with `pending`, `processing` or `complete` status and a `ttl` in seconds, polled with `async.call.lookup` | | SERP coverage | `engine` is google, bing or yahoo, `device` is desktop, mobile_android or mobile_ios, and `locale` is a Google hl-gl pair such as en-US. Ranking keywords cover the top 50 Google results | | Versioning | Not versioned. The docs expect no breaking changes outside beta methods. Some link and site methods are still documented only in the legacy docs at https://moz.com/help/links-api | | Terms | API General Conditions effective 12 August 2026 (new subscribers) and 11 September 2026 (existing). Availability on commercially reasonable efforts, fees non-refundable, no AI training on the data, attribution required for external display | | Status | No working public status page found. moz.statuspage.io redirects to a page saying Moz Status is inactive | | Capabilities | seo.keywords, seo.backlinks, seo.serp, seo.rankings | | Tags | hosted, json-rpc, api-key, freemium, mcp, oauth, backlinks, keywords, closed-source | | JSON | https://www.anchorterminal.com/api/v1/tools/moz-api.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 42 | 8.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 50 | 8.1 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 38 | 6.7 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 28 | 2.5 | | Transparency & trust (editorial 39, provenance 79) | 7% | 8.8 | 59 | 5.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **45.3 → E** | ### Why each score - Reliability 42: Graded on the public JSON-RPC API with the hosted lines. No working public status page was found. moz.statuspage.io redirects to a page saying Moz Status is inactive, the docs and help hub link none, and status.moz.com and health.moz.com did not connect from our network (0). No readable incident history (5). Edge limits are published with numbers, 2,000 requests in 60 seconds, 20 client errors in 60 seconds and a 30-minute block after ten 401 or 403 responses in five minutes, plus one request every ten seconds on the free plan (15). Per-method 429 responses carry `Retry-After` and the docs say to honour it, edge 429 responses carry none and the docs ask for exponential backoff, and no idempotency guidance was found for the Local write methods (12). The General Conditions promise commercially reasonable efforts at availability with no SLA or credits (0). The JSON-RPC API is generally available, and the MCP server is beta (10). 0 + 5 + 15 + 12 + 0 + 10 = 42. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 50: No downloadable OpenAPI or OpenRPC file was found, and api.moz.com/openrpc.json and /openapi.json return 404. Each method page is generated from JSON Schema definitions for payload, result and quota, which we count as a partial contract (8). moz.com/llms.txt returns 404 and no Markdown docs for agents were found (0). Method descriptions state the purpose and the row cost, and the guides explain async calls and errors, but few say when not to use a method (10). Inputs are typed with enums for scope, sort, filters, engine and device, numeric ranges and required fields (13). Request and response examples appear on each method page and in cURL, Python and JavaScript, and the error guide lists 13 codes with sample bodies (14). The docs say the API is not versioned, and the product updates archive holds one dated Moz API entry in the last 90 days (5). 8 + 0 + 10 + 13 + 14 + 5 = 50. - Agent ergonomics 74: List methods take `limit` (1 to 50 on link lists) and separate methods return a single keyword metric, but no field selection was found, and a site metrics object carries about 60 fields (15). Paging by opaque token, sort keys and named filters such as external, follow and gained_last_60_days (20). Errors carry a stable code, HTTP status, `data.issue`, `data.key` and an explanation, though the status field is named `status` in some bodies and `httpStatus` in others (19). The Data methods are reads, validation and quota checks run before any rows are used, and async calls can be polled again, but no idempotency keys were found for the Local write methods (13). `site_query` is the only required input on most site methods, the request `id` must be at least 24 characters, and no official SDK was found in the reviewed documentation (7). 15 + 20 + 19 + 13 + 7 = 74. - Security & auth 38: Plain revocable tokens, up to five per account, sent in the `x-moz-token` header and never in a URL. No scopes were found. The beta MCP server adds OAuth with PKCE and dynamic client registration, with a single scope named `mcp` (20). The Data methods only read, but there's no read-only or per-product token, and the same token works on the Local endpoint, whose methods create, update, cancel and close locations (8). Results carry page titles, anchor text and search result snippets from the open web, and no prompt-injection guidance was found (0). Each response reports the quota used and the dashboard has a usage page, which sits behind a login we couldn't read. No audit log was found in the docs (5). security.txt gives a contact address, but it expired about three hours before our check and its policy, acknowledgements and PGP key links return 404. No SOC 2 or ISO 27001 statement and no bug bounty were found on the pages reviewed (5). 20 + 8 + 0 + 5 + 5 = 38. - Payments & pricing 20: No x402, MPP or L402 (0). Plan prices, monthly rows and per-row overage prices are public without a login, and each method page states its row cost (20). The free plan of 50 rows a month requires a valid credit card, so it doesn't count (0). A person has to sign up and check out in a browser before a token exists. The MCP server's OAuth has dynamic client registration but still needs the account owner to sign in (0). 0 + 20 + 0 + 0 = 20. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 28: The newest dated Moz API entry in the product updates archive is the MCP server beta of 14 August 2026, 55 days before the check (20). That is the only Moz API entry in the last 90 days, the other nine dated since 15 June are Moz Pro and Moz Local (0). A dated archive exists, and support is by api@moz.com and the help team contact form, with 24/7 online support claimed on the product page. We could not test response times, and the contact page returned 403 to our reader (8). No official SDK was found (0). No packages to assess (0). The API General Conditions were revised with effect from 12 August 2026, and API responses report service version 2.28.2, which has no public release notes. 20 + 0 + 8 + 0 + 0 = 28. - Transparency & trust 59: Editorial half only. Closed service with clear terms, the API General Conditions (effective 12 August 2026) and an API legal page with attribution rules (15). The privacy policy (effective 8 April 2025) has a table of retention periods by data category and describes transfers under the EU-U.S. Data Privacy Framework, but covers the whole Moz site. No data processing agreement and no statement on retention of API queries were found on the pages reviewed (15). The docs say no breaking changes are expected outside beta methods, while the terms let Moz change or discontinue the service without notice, and the note that some methods are documented only in the legacy docs carries no dates (5). No list of subprocessors or data locations was found. The privacy policy says data is shared with other Ziff Davis companies (4). 15 + 15 + 5 + 4 = 39. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/moz-api.md (JSON https://www.anchorterminal.com/fixes/moz-api.json) ### What we couldn't check - unchecked: status.moz.com and health.moz.com did not connect from our network, so we can't say whether either hosts a live status page. moz.statuspage.io reports the page as inactive. - unchecked: the MCP server's tool list, schemas and annotations. Both endpoints return 401 without an account. - unchecked: the API dashboard and its usage page, which sit behind a login. - unchecked: moz.com/help/contact returned 403 to our reader, so support routes are taken from the product page and docs. - The founder's note said Moz's site could not be fetched earlier. On 8 October 2026 moz.com and api.moz.com answered curl with a plain user agent, and the docs were read from the page payload. WebFetch was refused for moz.com. - security.txt carried an expiry of 2026-10-07T22:45:48-07:00, about three hours before the check. It may be regenerated on a schedule, so the expired reading could be short-lived. - No data processing agreement, subprocessor list, SOC 2 or ISO 27001 statement was found on the pages reviewed. We tried moz.com/dpa, /subprocessors, /security and /trust, which return 404, and did not search further. - The welcome page says the API is moving between versions and some link and site methods are documented only in the legacy docs, although current method pages exist for most of those named. Which methods remain legacy-only was not established. - Whether an official SDK exists outside the docs was not established. None is named in the docs or on the product page. ### Sources - product page (data sets, vendor claims, MCP mention): (seen 2026-10-08) - pricing (plans, rows, overage, free plan limit, beta rows): (seen 2026-10-08) - docs index and method list (73 methods): (seen 2026-10-08) - getting started (endpoint, quota, compression, beta methods, versioning): (seen 2026-10-08) - authentication (tokens, five per account, card for free plan): (seen 2026-10-08) - error handling and rate limiting: (seen 2026-10-08) - MCP server guide (endpoints, OAuth, beta, Claude Code command): (seen 2026-10-08) - asynchronous calls guide: (seen 2026-10-08) - method page, List Links (schema, paging, filters, quota): (seen 2026-10-08) - method page, Generate SERP (async, engines, shared rate limit, row cost): (seen 2026-10-08) - MCP OAuth metadata (PKCE, dynamic registration, scope): (seen 2026-10-08) - API General Conditions (entity, availability, AI training clause, refunds): (seen 2026-10-08) - API legal page (attribution, suspension, beta terms): (seen 2026-10-08) - terms of use (effective 22 April 2023): (seen 2026-10-08) - privacy policy (effective 8 April 2025): (seen 2026-10-08) - product updates archive (MCP beta, 14 August 2026): (seen 2026-10-08) - security.txt (expiry, contact, broken links): (seen 2026-10-08) - Statuspage page reported inactive: (seen 2026-10-08) - RDAP registration date for moz.com: (seen 2026-10-08) ## Who's behind it (provenance 79/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | SEOmoz, Inc. | 20/20 | | Domain age | moz.com, registered 1998-04-29 (28 years) | 15/15 | | Endpoint on the vendor's domain | api.moz.com | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 2 clauses that cost points | 4.3/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | published but past its Expires date | 5/10 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://moz.com/api-general-conditions), read 2026-10-08, dated 2026-08-12, states 5 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "Subscriber will not use or access the Service for purposes of benchmarking or otherwise comparing the availability, performance or functionality of any Moz Services with similar third party software or API services." - To know. Says the terms or the service can change without notice (costs points). "Notwithstanding the foregoing, Moz USA retains the right to revise and update these General Conditions at any time for any reason in its sole and absolute discretion, effective immediately on posting the same to www.moz.com or www.mozcast.com (the “Sites”)." - To know. Requires arbitration or waives class actions. "The parties to this Agreement will submit all disputes arising under this Agreement to arbitration in New York City, New York, before a single arbitrator of the American Arbitration Association (“AAA”)." - Gives the date it was last updated. Last updated 2026-08-12. - Names the governing law or courts. The law of the State of New York. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Subscribers may not use data obtained through the Services to develop, train, fine-tune or improve any artificial intelligence system, model or algorithm, or permit a third party to do so. "use any data obtained through the Services to develop, train, fine-tune, refine, or improve any artificial intelligence system, model, or algorithm (including, without limitation, large language models, machine learning, or generative artificial intelligence), or permit any third party to do so" - Also in the text (2026-10-08). Moz may use the subscriber's name and logo on the client identification part of its website, and the subscriber grants a licence for that use. "You acknowledge and agree that We shall have the right to use Your name and/or logo on the client identification portion of Our website, and You hereby grant Us a license to all rights required for the lawful reproduction of Your name and/or logo on such page." - Also in the text (2026-10-08). Moz may change service fees for any renewal term, provided it gives notice of the new fees at least 30 days before that renewal term starts. "We reserve the right to change Service Fees for any Renewal Term; provided, however, that such change will not take effect unless We provide You notice of different Service Fees at least thirty (30) days prior to the start of the applicable Renewal Term." **Privacy policy** (https://moz.com/privacy-policy), read 2026-10-08, dated 2025-04-08, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Under some circumstances we may sell or share the personal data you provide to us to provide ads to you that align with your interests." - Gives the date it was last updated. Last updated 2025-04-08. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@moz.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. ## Live (updated 2026-10-08 19:08 UTC) - Right now: up, HTTP 404, 137 ms, checked 2026-10-08 19:08 UTC (get on `https://api.moz.com/jsonrpc`) - Uptime 24h 100.0% (42 probes) · 30 days 100.0% (42 probes) · p50 153 ms · p95 351 ms - security.txt: valid - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/moz-api.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Free plan | free | per month (plan) | 50 rows a month, one request every ten seconds, credit card required | | Starter Medium | $20 | per month (plan) | 3,000 rows, no overage, plus 150 beta rows | | Starter Large | $75 | per month (plan) | 15,000 rows, plus 750 beta rows | | Growth Small | $125 | per month (plan) | 50,000 rows, plus 3,500 beta rows | | Growth Medium | $250 | per month (plan) | 120,000 rows, plus 8,400 beta rows | | Growth Large | $500 | per month (plan) | 500,000 rows, plus 35,000 beta rows | | Overage row, Starter Large | $0.005 | per record | $5 per 1,000 rows | | Overage row, Growth Small | $0.0025 | per record | $25 per 10,000 rows | | Overage row, Growth Medium | $0.002 | per record | $20 per 10,000 rows | | Overage row, Growth Large | $0.001 | per record | $10 per 10,000 rows | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. Send a request `id` of at least 24 characters (letters, numbers and hyphens). A UUID works. Shorter ids are rejected with -32654. 2. Stop on a 401. Ten 401 or 403 responses in five minutes block the caller for 30 minutes. 3. On 429 with code -32658 wait the `Retry-After` seconds. On code -32650 no wait time is given, so back off exponentially. 4. Call `quota.lookup` (free) before large pulls. List methods charge one row per result, and `limit` is capped at 50 on link lists. 5. Poll `async.call.lookup` for `data.keyword.serp.generate`, and collect the result within 20 seconds of first seeing it complete. ## Connect First request: ```bash 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"}}}' ``` Claude Code: ```bash claude mcp add moz-mcp-v1-data https://api.moz.com/mcp/v1/data --transport http --header "Authorization: Bearer $YOUR_MOZ_TOKEN" --scope user ``` Through letme (picks today, calling later): https://letme.dev/moz-api. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | DataForSEO | B | 64.9 | 244 | seo.keywords, seo.backlinks, seo.serp, seo.rankings | no | https://www.anchorterminal.com/tools/dataforseo.md | | Manifold | C | 56.2 | 438 | seo.keywords, seo.backlinks, seo.serp, seo.rankings | no | https://www.anchorterminal.com/tools/manifold-mcp.md | | Semrush API + MCP | D | 53.1 | 487 | seo.keywords, seo.backlinks, seo.rankings, seo.serp | no | https://www.anchorterminal.com/tools/semrush.md | | Ahrefs | D | 49.8 | 526 | seo.keywords, seo.backlinks, seo.serp, seo.rankings | no | https://www.anchorterminal.com/tools/ahrefs.md | | Similarweb | D | 46 | 566 | seo.keywords, seo.serp, seo.rankings | no | https://www.anchorterminal.com/tools/similarweb.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - One URL, https://api.moz.com/jsonrpc, takes every call as a JSON-RPC 2.0 POST. The docs list 73 methods, 33 under `data` for links, sites and keywords, 35 under `local` for Moz Local, and five for quota, index, async and test calls (source: ) - Quota is counted in rows, and each method page states its cost. Validation runs before the quota check, and a call that would exceed the balance is refused without using any rows (source: ) - Edge limits are published. Ten 401 or 403 responses in five minutes block the caller for 30 minutes, 20 client errors in 60 seconds throttle it, and so do 2,000 requests in 60 seconds (source: ) - The MCP server went to beta on 14 August 2026 with two endpoints, https://api.moz.com/mcp/v1/data and https://api.moz.com/mcp/v1/local, and is included in every paid plan as beta access (source: ) - The General Conditions forbid using data from the service to develop, train or fine-tune any AI system or model, while allowing AI software to analyse the data for internal business purposes (source: ) - The docs say the API is not versioned and that no breaking changes are expected outside beta methods, which can change or be removed without notice (source: ) - Moz says its link index covers 45.5 trillion links across 1 billion domains, with 1.25 billion monthly keyword volumes (source: ) ## Compare - [Ahrefs vs Moz API](https://www.anchorterminal.com/compare/ahrefs-vs-moz-api.md): D 49.8 vs E 45.3 - [DataForSEO vs Moz API](https://www.anchorterminal.com/compare/dataforseo-vs-moz-api.md): B 64.9 vs E 45.3 - [Manifold vs Moz API](https://www.anchorterminal.com/compare/manifold-mcp-vs-moz-api.md): C 56.2 vs E 45.3 - [Moz API vs Semrush API + MCP](https://www.anchorterminal.com/compare/moz-api-vs-semrush.md): E 45.3 vs D 53.1 - [Moz API vs Similarweb](https://www.anchorterminal.com/compare/moz-api-vs-similarweb.md): E 45.3 vs D 46 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on moz.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "moz-api", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Moz API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Moz API on Anchor Terminal](https://www.anchorterminal.com/badges/moz-api.svg)](https://www.anchorterminal.com/tools/moz-api) ``` Plain link: ```html Moz API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Moz API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/moz-api-dark.png - Light: https://www.anchorterminal.com/assets/share/moz-api-light.png