Nexscope

Backlink Domain Intersection

Compare several domains to find the websites that link to all of them. Call the Backlink Domain Intersection API via REST or MCP to automate SEO research.

CostRecent 37 credits / call
Try online
POST · https://api.nexscope.ai/seo/backlinkDomainIntersectionMCP · nexscope_seo_backlink_domain_intersection

Choose an integration method

Backlinks & Authority

What this API does

Compare several domains to find the websites that link to all of them. The request accepts limit, target1.kind, target1.target, target2.kind, target2.target. Its documented result includes inputTarget1.kind, inputTarget1.target, inputTarget2.kind, inputTarget2.target, first.backlinks, first.rank, referringDomain, second.backlinks.

Backlink Domain Intersection API use cases

Review link acquisition evidence

To review link acquisition evidence, a search marketer submits limit and target1.kind to Backlink Domain Intersection. The returned inputTarget1.kind, inputTarget1.target, inputTarget2.kind help identify referring sources that merit closer inspection.

Compare competitor link profiles

A search marketer uses Backlink Domain Intersection with limit and target1.kind to compare competitor link profiles. The returned inputTarget1.kind, inputTarget1.target, inputTarget2.kind help compare link evidence for competing websites.

Prioritize links for manual review

For this workflow, a search marketer calls Backlink Domain Intersection with limit and target1.kind to prioritize links for manual review. The result helps choose suspicious or valuable links for manual assessment.

Backlink Domain Intersection API FAQ

What does the Backlink Domain Intersection API return?

Compare several domains to find the websites that link to all of them. The documented output includes inputTarget1.kind, inputTarget1.target, inputTarget2.kind, inputTarget2.target, first.backlinks, first.rank, referringDomain, second.backlinks. It corresponds to the supplied limit, target1.kind, target1.target, target2.kind, target2.target. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Backlink Domain Intersection API cost?

The current documented cost is Recent 37 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Backlink Domain Intersection API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/backlinkDomainIntersection with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_seo_backlink_domain_intersection. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/seo/backlinkDomainIntersection
MCP method
nexscope_seo_backlink_domain_intersection

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/seo/backlinkDomainIntersection

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/seo/backlinkDomainIntersection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "limit": 10,
  "target1": {
    "kind": "DOMAIN",
    "target": "nexscope.ai"
  },
  "target2": {
    "kind": "DOMAIN",
    "target": "nexscope.ai"
  }
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
All categories/ Backlinks & Authority

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json
Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_seo_backlink_domain_intersection",
    "arguments": {
      "limit": 10,
      "target1": {
        "kind": "DOMAIN",
        "target": "nexscope.ai"
      },
      "target2": {
        "kind": "DOMAIN",
        "target": "nexscope.ai"
      }
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Uses your signed-in Nexscope session
SEO API Lab

SEO Backlink Domain Intersection

Compare several domains to find the websites that link to all of them. Call the Backlink Domain Intersection API via REST or MCP to automate SEO research.

Live request
Estimated 37 credits / callAPI usage records
Value sent as the “limit” request parameter.

1–20

*
Value sent as the “target1” request parameter.
*
Value sent as the “target2” request parameter.

Live calls may use Data credits.

Processing result

If a request is still processing, use the returned identifier to retrieve its stored result. The tester recognizes the identifier automatically, and result queries do not spend credits.

Live response

Results

Your live result will appear here.

Complete the request fields above and run the API. No sample response is substituted.

Test with an API key or MCP
Estimated 37 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint
/seo/backlinkDomainIntersection
Processing result endpoint
https://api.nexscope.ai/seo/backlinkDomainIntersection/calls/{resultId}
MCP method
nexscope_seo_backlink_domain_intersection
cURL
curl -X POST \
  https://api.nexscope.ai/seo/backlinkDomainIntersection \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 10, "target1": { "kind": "DOMAIN", "target": "nexscope.ai" }, "target2": { "kind": "DOMAIN", "target": "nexscope.ai" } }'
Response
No response yet. Run the request to see the response here.
Processing result

Use the identifier returned by Run request. The tester selects the correct result query automatically, and result queries do not spend credits.

Result response
No task result yet. Query the task to see the generated output here.

Related APIs