Text Trademark Detector API

Text trademark detection and infringement risk analysis for e-commerce product listings.

All APIs · Official documentation

Category: Patent & IP Risk · Data API

Text trademark detection and infringement risk analysis for e-commerce product listings.

Endpoint

POST https://api.nexscope.ai/api/skill-api/v1/skills/text-trademark-detector/run

Headers: Authorization: Bearer YOUR_API_KEY and Content-Type: application/json.

Execution: synchronous; inspect the direct API-specific response body.

Request parameters

Name	Type	Required	Description	Constraints
`productTitle`	string	Yes	Product title, used for trademark detection (max 1000 characters)	{}
`regions`	string	No	Country/region codes, multiple separated by commas. Supported values: US, EM, GB, DE, FR, IT, ES, AU, CA, MX, JP, CN, WO, TR, BX	{}
`limit`	integer	Yes	Limit on the number of returned results (default 100, max 500)	{}
`productText`	string	No	Other product text information, such as bullet points or product description (max 1000 characters)	{}

The table summarizes the published fields. Consult the full request definition for nested objects, alternatives, and conditional requirements.

Call this API

Run these commands from the repository root after setting your API key. Copy the sample to a separate file and replace illustrative URLs, IDs, search terms, and required values before submitting. Sample responses are documentation fixtures, not live results.

cp payloads/text-trademark-detector.json request.json
# Edit request.json for your inputs.
bash examples/curl/run.sh text-trademark-detector request.json
# Or: node examples/javascript/run.mjs text-trademark-detector request.json
# Or: python3 examples/python/run.py text-trademark-detector request.json

Published request example

{
  "regions": "US",
  "productTitle": "MagSafe Phone Case for iPhone",
  "limit": 10,
  "productText": "Protective magnetic phone case with shockproof corners."
}

Response

The run endpoint returns its API-specific payload directly. Do not assume a data or result wrapper. For asynchronous APIs, the run response is a task receipt, not the final generated asset.

Published response example

{
  "total": 1,
  "data": [
    {
      "region": "US",
      "score": 1,
      "highestModeScore": 1,
      "isFamous": false,
      "isAmazonBrand": false,
      "isActiveHolder": false,
      "isCompatibility": false,
      "isCommonSense": false,
      "niceClass": [],
      "originalTextMatches": []
    }
  ],
  "detectId": "example-id",
  "columns": [],
  "blacklistTrademarks": [],
  "whitelistTrademarks": [],
  "costToken": 1,
  "blacklisttrademarks": [
    {
      "region": "US"
    }
  ]
}

Full definitions

Some source definitions use field descriptors rather than JSON Schema; these are preserved and labeled rather than presented as strict validation schemas.

MCP

Tool name: nexscope_text_trademark_detector. See MCP integration.

Source retrieved: 2026-09-10. See source and validation notes.

FilesExpand file tree

text-trademark-detector.md

Latest commit

History