Moz is a Seattle-based search-marketing software company, founded in 2004 as SEOmoz and part of Ziff Davis since 2021, whose products include Moz Pro, Moz Local, STAT and Moz Data. Its developer surface is the Moz API, a JSON-RPC 2.0 API served from a single universal endpoint at https://api.moz.com/jsonrpc, exposing 62 public methods across five namespaces: site metrics (Domain Authority, Page Authority, Brand Authority, Spam Score), the Moz Link Index (links, linking root domains, anchor text, link intersect, link status, final redirect), keyword metrics (volume, difficulty, opportunity, priority, search intent, related keywords), ranking and top-page data, and Moz Local location, group, account, listing-network and Google Business Profile insight management. Requests are authenticated with a Moz API token in an x-moz-token header, billed against a row-based monthly quota, and Moz additionally runs two beta remote MCP servers - Moz Data and Moz Local - at https://api.moz.com/mcp/v1/data and https://api.moz.com/mcp/v1/local, protected by OAuth 2.1 with PKCE and RFC 9728 protected-resource metadata.
Moz is listed with 3 APIs on the APIs.io network. Tagged areas include SEO, Search, Marketing, Analytics, and Keywords.
Moz’s developer surface includes documentation, API reference, getting-started guide, pricing, support, engineering blog, authentication, and 26 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/moz/"><img src="https://apis.io/badge/moz/card.svg" alt="Moz on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
4 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
The Moz API is a JSON-RPC 2.0 API accessed through HTTP POST requests to a single universal endpoint, https://api.moz.com/jsonrpc. The method name in the request body selects th...
Beta remote Model Context Protocol server exposing Moz Data API tools (site metrics, links, keywords, rankings) to LLM hosts such as Claude Desktop, ChatGPT Desktop and Claude C...
Beta remote Model Context Protocol server exposing Moz Local tools for managing and reporting on business locations and listings. Streamable HTTP transport; OAuth 2.1 sign-in in...
Moz operates two first-party remote MCP servers, split by product. Both are documented on the Moz API docs site and both answered a live tools/list probe with an RFC 9728 OAuth ...
aid: moz
name: Moz
description: 'Moz is a Seattle-based search-marketing software company, founded in 2004 as SEOmoz and part of Ziff Davis since
2021, whose products include Moz Pro, Moz Local, STAT and Moz Data. Its developer surface is the Moz API, a JSON-RPC 2.0
API served from a single universal endpoint at https://api.moz.com/jsonrpc, exposing 62 public methods across five namespaces:
site metrics (Domain Authority, Page Authority, Brand Authority, Spam Score), the Moz Link Index (links, linking root domains,
anchor text, link intersect, link status, final redirect), keyword metrics (volume, difficulty, opportunity, priority, search
intent, related keywords), ranking and top-page data, and Moz Local location, group, account, listing-network and Google
Business Profile insight management. Requests are authenticated with a Moz API token in an x-moz-token header, billed against
a row-based monthly quota, and Moz additionally runs two beta remote MCP servers - Moz Data and Moz Local - at https://api.moz.com/mcp/v1/data
and https://api.moz.com/mcp/v1/local, protected by OAuth 2.1 with PKCE and RFC 9728 protected-resource metadata.'
url: https://raw.githubusercontent.com/api-evangelist/moz/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: freemium
onboarding: self-serve
trial: false
try_now: true
public: false
gated: none
gated_source:
- onboarding
label: Freemium · Self-serve signup
confidence: high
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://moz.com/images/cms/Moz-OG-Image-2024.jpg
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- SEO
- Search
- Marketing
- Analytics
- Keywords
- Backlinks
- Local Marketing
- Domain Authority
- Link Index
- JSON-RPC
- MCP
- Company
apis:
- name: Moz API
description: The Moz API is a JSON-RPC 2.0 API accessed through HTTP POST requests to a single universal endpoint, https://api.moz.com/jsonrpc.
The method name in the request body selects the operation. 62 public methods cover site metrics, the Moz Link Index, keyword
metrics, ranking keywords, top pages, global top domains/pages, Moz Local location and listing management, index metadata
and quota lookup. Authentication is a secret Moz API token supplied in the custom x-moz-token header.
humanURL: https://moz.com/products/api
baseURL: https://api.moz.com/jsonrpc
tags:
- SEO
- Links
- Keywords
- Site Metrics
- Local
properties:
- type: Documentation
url: https://moz.com/api/docs
- type: APIReference
url: https://moz.com/api/docs/welcome
- type: GettingStarted
url: https://moz.com/api/docs/guides/getting-started
- type: Authentication
url: authentication/moz-authentication.yml
- type: JSONSchema
url: json-schema/moz-api-schema.json
- type: ErrorCatalog
url: errors/moz-problem-types.yml
- type: Conventions
url: conventions/moz-conventions.yml
- type: DataModel
url: data-model/moz-data-model.yml
- type: RateLimits
url: rate-limits/moz-rate-limits.yml
- name: Moz MCP Server - Data
description: Beta remote Model Context Protocol server exposing Moz Data API tools (site metrics, links, keywords, rankings)
to LLM hosts such as Claude Desktop, ChatGPT Desktop and Claude Code. Streamable HTTP transport; OAuth 2.1 sign-in inside
the client, or an Authorization Bearer header carrying a Moz API key. Requires a Moz Data API subscription; access is
limited to account owners during beta.
humanURL: https://moz.com/api/docs/guides/mcp-servers
baseURL: https://api.moz.com/mcp/v1/data
tags:
- MCP
- Agents
- SEO
properties:
- type: MCPServer
url: mcp/moz-mcp.yml
- type: Documentation
url: https://moz.com/api/docs/guides/mcp-servers
- type: OAuthScopes
url: scopes/moz-scopes.yml
- name: Moz MCP Server - Local
description: Beta remote Model Context Protocol server exposing Moz Local tools for managing and reporting on business locations
and listings. Streamable HTTP transport; OAuth 2.1 sign-in inside the client, or an Authorization Bearer header carrying
a Moz API key. Requires a Moz Local subscription; access is limited to account owners during beta.
humanURL: https://moz.com/api/docs/guides/mcp-servers
baseURL: https://api.moz.com/mcp/v1/local
tags:
- MCP
- Agents
- Local Marketing
properties:
- type: MCPServer
url: mcp/moz-mcp.yml
- type: Documentation
url: https://moz.com/api/docs/guides/mcp-servers
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/moz-domain-security.yml
- type: Website
url: https://moz.com/
- type: DeveloperPortal
url: https://moz.com/products/api
- type: Documentation
url: https://moz.com/api/docs
- type: APIReference
url: https://moz.com/api/docs/welcome
- type: GettingStarted
url: https://moz.com/api/docs/guides/getting-started
- type: Pricing
url: https://moz.com/products/api/pricing
- type: Login
url: https://moz.com/api/dashboard
- type: TermsOfService
url: https://moz.com/terms-of-use
- type: PrivacyPolicy
url: https://moz.com/privacy-policy
- type: Support
url: https://moz.com/help
- type: Community
url: https://moz.com/community
- type: Blog
url: https://moz.com/blog
- type: GitHubOrganization
url: https://github.com/seomoz
- type: MCPServer
url: mcp/moz-mcp.yml
- type: JSONSchema
url: json-schema/moz-api-schema.json
- type: Authentication
url: authentication/moz-authentication.yml
- type: OAuthScopes
url: scopes/moz-scopes.yml
- type: ErrorCatalog
url: errors/moz-problem-types.yml
- type: Conventions
url: conventions/moz-conventions.yml
- type: DataModel
url: data-model/moz-data-model.yml
- type: Lifecycle
url: lifecycle/moz-lifecycle.yml
- type: Conformance
url: conformance/moz-conformance.yml
- type: RateLimits
url: rate-limits/moz-rate-limits.yml
- type: Plans
url: plans/moz-plans-pricing.yml
- type: Packages
url: packages/moz-packages.yml
- type: WellKnown
url: well-known/moz-well-known.yml
- type: SecurityTxt
url: well-known/moz-security.txt
- type: Security
url: security/moz-vulnerability-disclosure.yml
- type: LLMsTxt
url: llms/moz-llms.txt
- type: AgentSkill
url: skills/_index.yml
- type: Examples
url: examples/moz-examples.yml
- type: VulnerabilityDisclosure
url: security/moz-vulnerability-disclosure.yml
x-enrichment:
date: '2026-08-26'
status: enriched
artifacts_added: 27
pass: local-v1
Moz API — frequently asked questions
Does Moz have an API?
Yes. APIs.io lists 3 APIs from Moz, including Moz API, Moz MCP Server - Data and Moz MCP Server - Local.
How do I authenticate with the Moz API?
Moz documents its authentication (3 schemes). The details are profiled on APIs.io as Moz Authentication.
How much does the Moz API cost?
Moz publishes its prices; its Free plan is $0 as of 2026-10-28. APIs.io lists 7 pricing plans for Moz, with each plan's price, limits and inclusions under Pricing on this page.
Does Moz have an MCP server?
Yes. APIs.io lists 1 MCP server for Moz: Moz operates two first-party remote MCP servers, split by product. Both are documented on the Moz API docs site and both answered a live tools/list probe with an RFC 9728 OAuth challenge, which confir
Is the Moz API ready for AI agents?
Moz has a Kin Score of 48.5 out of 100 (developing) and an Agent Readiness score of 34.9 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.