Nexscope

Advertiser Search

Find advertisers in the Google ads directory and see roughly how many ads they run. Call the Advertiser Search API via REST or MCP to automate SEO research.

CostRecent 10 credits / call
Try online
POST · https://api.nexscope.ai/seo/advertiserSearchMCP · nexscope_seo_advertiser_search

Choose an integration method

Ad Intelligence

What this API does

Find advertisers in the Google ads directory and see roughly how many ads they run. The request accepts limit, query. Its documented result includes advertisers.advertiserId, advertisers.approxAdsCount, advertisers.location, advertisers.name, advertisers.rankAbsolute, advertisers.rankGroup, advertisers.verified, query.

Advertiser Search API use cases

Find products matching a sourcing brief

To find products matching a sourcing brief, a search marketer submits limit and query to Advertiser Search. The returned advertisers.advertiserId, advertisers.approxAdsCount, advertisers.location help identify products matching the requested search criteria.

Compare a product search shortlist

A search marketer uses Advertiser Search with limit and query to compare a product search shortlist. The returned advertisers.advertiserId, advertisers.approxAdsCount, advertisers.location help compare candidates before requesting individual product details.

Collect candidates for a market review

For this workflow, a search marketer calls Advertiser Search with limit and query to collect candidates for a market review. The result helps choose products for a supplier or competitor review.

Advertiser Search API FAQ

What does the Advertiser Search API return?

Find advertisers in the Google ads directory and see roughly how many ads they run. The documented output includes advertisers.advertiserId, advertisers.approxAdsCount, advertisers.location, advertisers.name, advertisers.rankAbsolute, advertisers.rankGroup, advertisers.verified, query. It corresponds to the supplied limit, query. 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 Advertiser Search API cost?

The current documented cost is Recent 10 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 Advertiser Search API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/seo/advertiserSearch 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_advertiser_search. 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/advertiserSearch
MCP method
nexscope_seo_advertiser_search

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/advertiserSearch

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/advertiserSearch' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "limit": 20,
  "query": "nexscope"
}'

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/ Ad Intelligence

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_advertiser_search",
    "arguments": {
      "limit": 20,
      "query": "nexscope"
    }
  }
}

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 Advertiser Search

Find advertisers in the Google ads directory and see roughly how many ads they run. Call the Advertiser Search API via REST or MCP to automate SEO research.

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

1–20

*
Value sent as the “query” request parameter.

Up to 200 characters

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 10 credits / callAPI usage records

Try it

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

Endpoint
/seo/advertiserSearch
Processing result endpoint
https://api.nexscope.ai/seo/advertiserSearch/calls/{resultId}
MCP method
nexscope_seo_advertiser_search
cURL
curl -X POST \
  https://api.nexscope.ai/seo/advertiserSearch \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 20, "query": "nexscope" }'
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