treg.to / Catalog / Moz
12 tools · your own account · never metered

Moz: connect your own account

Domain Authority, Page Authority, backlinks and link metrics. Connect your own Moz account once and your agent uses it from then on, through one treg.to token. Calls on your own connection are never metered.
Start freeSee all 12 toolsAPI docs ↗
$1.00 of free credit once per new verified account · no card · platform tools need no provider signup
12 of 12 tools on this page are live-verified against the provider.
works in
ChatGPTClaudeClaude CodeCodexCursorGrokGemini CLI
What your agent can now do

Moz, one prompt away

AGENT
ChatGPTClaudeClaude CodeCodexCursorGrokGemini CLI
authority metrics for a URL or domain✓
backlink profile of a domain or URL✓
list individual backlinks to a target✓
→
▚ treg
$ treg call moz.account.usage
✓ 200 · free
$ treg call moz.web.url.metrics
✓ 200 · $0.00667/call
$ treg call moz.web.anchors.list
✓ 200 · $0.00667/result
$ _
→
MozYOUR ACCOUNT
Domain Authority, Page Authority, backlinks and link metrics.
⚒ 12 TOOLS

SEO · https://lsapi.seomoz.com/v2

Set up

Set up Moz in Claude Code, Codex or any agent

1Give this to your agent
in your agent's chat
set up treg — https://treg.sciatafrica.com/llms.txt
2Or add the MCP server yourself
claude code
claude mcp add --transport http treg https://treg.sciatafrica.com/mcp

ChatGPT

Settings → Connectors → add https://treg.sciatafrica.com/mcp as a custom connector.

Grok bot

Add https://treg.sciatafrica.com/mcp as a remote MCP connector in its tool settings.

Claude Desktop

Settings → Connectors → Add custom connector → https://treg.sciatafrica.com/mcp.

Cursor, Codex, any MCP client

Point it at https://treg.sciatafrica.com/mcp (HTTP transport).

CLI

curl -fsSL https://treg.sciatafrica.com/install.sh | sh

Plain HTTP

LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.

Try it

What's the best way to ask?

the prompt
Using treg, authority metrics for a URL or domain. Show me the price first.

Run one directly

a live-verified call
treg call moz.account.usage --method POST --data '{}'
Why treg.to

Why call Moz through treg.to

Your account, held safely

Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.

Price before the call

The provider's own rate, $0.000 markup. How billing works.

Account billing

Calls through your own connection are not metered by treg.

Your own Moz key is free

Register it and those calls are never metered. Your key always wins.

Switch by changing a word

Another provider is a different word in the prompt, not a new integration.

One key, the whole catalog

The same token calls DataForSEO, Majestic, Semrush and 3,605 other tools.

The shelf

All 12 Moz tools

Open web & SEO data · 11 tools
  • Anchor texts in backlinks by domain or URL · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Anchor-text distribution of inbound links, with domain and page counts per phrase moz.web.anchors.list
    1 row per returned anchor-text phrase; `limit` (1-50) sets the ceiling OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Competitor link gaps · BYOK only · live-verified · No treg charge; upstream $0.0333+/result
    Sources that link to the given competitors but not to you — link-gap prospecting moz.web.backlinks.intersect
    weighted endpoint: 5 rows per RETURNED result (limit 1 = 5 rows, limit 50 = 250 rows). Fewer results than `limit` cost proportionally less. OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Backlinks by domain or URL — source and target metrics · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Individual inbound links, with full URL metrics for both source and target moz.web.backlinks.list
    1 row per returned link; `limit` (1-50) sets the ceiling OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Check referring sites · BYOK only · live-verified · No treg charge; upstream $0.0133+/source
    Check whether specific sources link to a target — returns one boolean per source moz.web.backlinks.status
    weighted endpoint: 2 rows per source (1 source = 2 rows, 50 sources = 100 rows) OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Backlinks summary by domain — authority, spam histograms · BYOK only · live-verified · No treg charge; upstream $0.0133/call
    Aggregate backlink profile plus histograms by DA, spam score and root domains moz.web.backlinks.summary
    1 row per target + 1 row for the distributions modifier OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Top linked domains · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Most-linked root domains on the web, with DA and spam score (index-wide, no target) moz.web.global.top_domains
    1 row per returned root domain; defaults to 25 rows when `limit` is omitted OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Top linked pages · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Most-linked pages on the web, with full URL metrics (index-wide, takes no target) moz.web.global.top_pages
    1 row per returned page; defaults to 25 rows when `limit` is omitted OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Moz link index version · BYOK only · live-verified · No treg charge; upstream $0.00667/call
    Which Moz link index is serving results — tells you if metrics moved on a refresh moz.web.index.metadata
    1 row per call. OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after; rows_consumed moved by exactly 1. This closes the previous `value: null, confidence: unknown`, which existed only because the test credential had been out of quota on 2026-07-28 — the endpoint gates on quota (403 insufficient-quota), so it was never free, just unmeasurable at the time.
  • Referring domains by domain or URL — authority, spam · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Root domains linking to a target, with each source's DA, spam score and link counts moz.web.linking_domains.list
    1 row per returned root domain; `limit` (1-50) sets the ceiling OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Highest-authority pages by domain, with URL metrics · BYOK only · live-verified · No treg charge; upstream $0.00667/result
    Highest-authority pages of a domain, with full URL metrics per page moz.web.site.top_pages
    1 row per returned page; history modifiers add rows as in url_metrics OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
  • Domain Authority, Page Authority and Spam Score by URL · BYOK only · live-verified · No treg charge; upstream $0.00667/call
    Domain Authority, Page Authority, Spam Score and link counts for up to 50 URLs moz.web.url.metrics
    1 row per target with no modifiers; each history list entry and `distributions: true` adds 1 row per target (weighted endpoint) OBSERVED 2026-07-31 — measured against POST /v2/usage_data (free) immediately before and after this exact test_request; rows_consumed moved by exactly this value.
The provider account itself — usage, quota, balance (not a content platform) · 1 tools
  • Account usage — quota rows consumed this period · BYOK only · account management · live-verified · No treg charge; upstream free
    Rows consumed this period — Moz's quota meter, covering both V1 and V2 usage moz.account.usage
    answers 200 even when the account's row quota is fully exhausted, so it costs nothing and is the right liveness probe for a Moz key

Reliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.

Used in

Jobs Moz does, compared with the other providers

Backlink API: the backlink profile of a domain from Moz, DataForSEO, Serpstat, SE Ranking, Majestic or Semrush, per call

Every provider that does this job, side by side: price per billing unit, measured success rate and speed.

Related

Same jobs, other providers

These providers answer some of the same capabilities as Moz. The platform pages show them on one row with rate and coverage; choosing is yours, treg.to does not route between providers automatically.

also on the catalog
DataForSEOMajesticSemrushSE RankingSerpstat
Questions

Before you start

Do I need a Moz account?

Yes. This is an own-account connection: you sign in to Moz once and your agent uses that connection through your treg.to token. Calls on it are never metered.

How do I add Moz to Claude Code?

Run: claude mcp add --transport http treg https://treg.sciatafrica.com/mcp. One MCP server carries Moz and the rest of the catalog.

Which frameworks does it work with?

Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).

Is this the official Moz MCP server?

No. treg.to serves Moz's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official Moz channels are linked above.