Nexscope

IP Risk Detection RG: text Trademark Detection API

Use IP Risk Detection RG: text Trademark Detection API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 74 · Range 64–74 credits / call
Try online
POST · https://api.nexscope.ai/rg/textTrademarkDetectionMCP · nexscope_data_rg_text_trademark_detection
IP Risk Detection RG

What this API does

Use IP Risk Detection RG: text Trademark Detection API through Nexscope with documented parameters, structured results and API key authentication. The request accepts productTitle, regions, limit, productText. Its documented result includes detectId, blacklistTrademarks, whitelistTrademarks, textTrademarkRadar, trademarkName, region, score, highestModeScore.

IP Risk Detection RG: text Trademark Detection API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits productTitle and regions to IP Risk Detection RG: text Trademark Detection API. The returned detectId, blacklistTrademarks, whitelistTrademarks help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses IP Risk Detection RG: text Trademark Detection API with productTitle and regions to collect records for an ip review. The returned detectId, blacklistTrademarks, whitelistTrademarks help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

For this workflow, a compliance analyst calls IP Risk Detection RG: text Trademark Detection API with productTitle and regions to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

IP Risk Detection RG: text Trademark Detection API API FAQ

What does the IP Risk Detection RG: text Trademark Detection API API return?

Use IP Risk Detection RG: text Trademark Detection API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes detectId, blacklistTrademarks, whitelistTrademarks, textTrademarkRadar, trademarkName, region, score, highestModeScore. It corresponds to the supplied productTitle, regions, limit, productText. 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 IP Risk Detection RG: text Trademark Detection API API cost?

The current documented cost is Recent Avg. 74 · Range 64–74 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 IP Risk Detection RG: text Trademark Detection API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/rg/textTrademarkDetection 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_data_rg_text_trademark_detection. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/rg/textTrademarkDetection
MCP method
nexscope_data_rg_text_trademark_detection

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/rg/textTrademarkDetection

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/rg/textTrademarkDetection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "limit": 100,
  "productTitle": "Wireless Bluetooth Headphones Noise Cancelling Over Ear",
  "regions": "US"
}'

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/ IP Risk Detection RG
POSThttps://api.nexscope.ai/rg/textTrademarkDetection

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/rg/textTrademarkDetection
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
productTitlestringrequired
Product title, used for trademark detection, maximum 1000 characters
regionsstringoptional
Country/region codes, separate multiples with commas. support `US`, `EM`, `GB`, `DE`, `FR`, `IT`, `ES`, `AU`, `CA`, `MX`, `JP`, `CN`, `WO`, `TR`, `BX`
Example: US
limitintegerrequired
Limit on the number of returned results, maximum 500
Example: 100
productTextstringoptional
Other text information about the product, such as five-point description or product description, maximum 1000 characters

Code example

{
  "limit": 100,
  "productTitle": "Wireless Bluetooth Headphones Noise Cancelling Over Ear",
  "regions": "US"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (28 fields)

NameTypeRequiredDescription
totalintegeroptional
Number of matched trademark records
dataarrayoptional
Trademark list (flattened), each element contains the fields below
detectIdstringoptional
Interface call ID
columnsarrayoptional
Rendered column definitions
blacklistTrademarksarrayoptional
Blacklisted trademarks detected in text
whitelistTrademarksarrayoptional
Whitelisted (safe) trademarks detected in text
textTrademarkRadarstringoptional
Product risk level: `0` is low risk, `1` is pending manual verification, and `2` is high risk
costTokenintegeroptional
Consume token
typestringoptional
Rendering style
trademarkNamestringoptional
Trademark word
regionstringoptional
Country code
scoreintegeroptional
risk score
highestModeScoreintegeroptional
Maximum risk score, range 0-5
trademarksStatusstringoptional
Highest scoring trademark word status
regionStatusstringoptional
Trademark status in matching regions
holderstringoptional
rights holder
applicationNumberstringoptional
Application number
registrationNumberstringoptional
Registration number
isFamousbooleanoptional
Is it a famous trademark?
isAmazonBrandbooleanoptional
Is it an Amazon hot search brand?
isActiveHolderbooleanoptional
Are you an active rights defender?
isCompatibilitybooleanoptional
Compatibility
isCommonSensebooleanoptional
Is it a common word?
niceClassarrayoptional
Nice Classification
originalTextMatchesarrayoptional
The original word that triggered the match
trademarkstringoptional
Trade name
regionstringoptional
Country code
notestringoptional
Remarks

Responses

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.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

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_data_rg_text_trademark_detection",
    "arguments": {
      "limit": 100,
      "productTitle": "Wireless Bluetooth Headphones Noise Cancelling Over Ear",
      "regions": "US"
    }
  }
}

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.

81 credits / callAPI usage records

Try it

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

Endpoint
/rg/textTrademarkDetection
MCP method
nexscope_data_rg_text_trademark_detection
cURL
curl -X POST \
  https://api.nexscope.ai/rg/textTrademarkDetection \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 100, "productTitle": "Wireless Bluetooth Headphones Noise Cancelling Over Ear", "regions": "US" }'
Response
No response yet. Run the request to see the response here.

Related APIs