01 · Records and state owned
URL and domain link metrics, linking roots, inbound links, anchor text, top pages, and related Moz index data.
Moz
Moz Pro / Moz API
Curated major addition platform in seo intelligence with material relevance to the Marcom operating stack and a first-party developer surface.
Analytics, SEO & experimentationSystem of intelligenceExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Query supported link-index metrics and link relationships for URLs, domains, and subdomains.
03 · Actions and write paths
The core Links API is analysis-oriented; no broad campaign-management write surface is represented in this profile.
04 · Authentication and permissions
Moz API credentials and subscription quotas apply.
05 · Monitoring, approval, and recovery
Expose metric definitions, index freshness, queried scope, and quota/cost context with every derived recommendation.
06 · Gaps and implementation limits
No first-party provider MCP was verified. Link metrics reflect Moz’s index and are not equivalent to search-engine ground truth.
First-party access
Documented surfaces
Agent access
MCP and adjacent posture
No first-party provider MCP verified in this snapshotNo first-party provider MCP foundNo first-party provider verified
Role: none_verified
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation2
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Moz ships these experiences.
Single-platform patterns
- Domain authority and link-opportunity workbench
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Moz Pro / Moz API + warehouse or semantic layer: executive insight brief
- Moz Pro / Moz API + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
2 recorded sources
APIRepresentative source
https://moz.com/help/links-api ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Sep 9, 2025
- BYO-UI reviewed
- Jul 10, 2026
Recorded first-party developer source; summary not endpoint-exhaustive
HomepageSource inventory
https://moz.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jul 10, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.