SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-ruiguan-text-trademark-detection

linkfox-ruiguan-text-trademark-detection

Marketing & growth

View repository

Updated 10-16 00:00

About this skill

Ruiguan Text Trademark Detection

This skill guides you on how to perform text-based trademark detection against product titles and other product text, helping e-commerce sellers identify potential trademark infringement risks before publishing listings.

Core Concepts

Text Trademark Detection scans product text (titles, descriptions, bullet points) against registered trademark databases across 15 countries/regions. It returns matched trademarks along with risk scores, registration details, and holder information so sellers can avoid intellectual property violations.

Risk score logic: The highestModeScore field ranges from 0 to 5 -- a higher value indicates greater infringement risk. The textTrademarkRadar field classifies overall product risk into three levels: 0 (low risk), 1 (needs manual review), 2 (high risk).

Blacklist and whitelist: The response may include blacklistTrademarks (known dangerous trademarks to always avoid) and whitelistTrademarks (safe trademarks that can be ignored). Always surface blacklist matches prominently to the user.

Parameters

Parameter Type Required Description Example
productTitle string Yes Product title to scan (max 1000 chars) Wireless Bluetooth Headphones Noise Cancelling
regions string No Country/region codes, comma-separated. Supported: US, EM, GB, DE, FR, IT, ES, AU, CA, MX, JP, CN, WO, TR, BX US,EM,GB
limit integer Yes Max number of results to return (default 100, max 500) 100
productText string No Additional product text such as bullet points, description (max 1000 chars) Ergonomic design with premium sound quality

Supported Regions

Code Region
US United States
EM European Union
GB United Kingdom
DE Germany
FR France
IT Italy
ES Spain
AU Australia
CA Canada
MX Mexico
JP Japan
CN China
WO WIPO (World Intellectual Property Organization)
TR Turkey
BX Bolivia

When the user does not specify a region, default to US.

How to call

  • API endpoint：POST /ruiguan/textTrademarkDetection(for full parameters/responses/error codes, see references/api.md）
  • Python script：python scripts/ruiguan_text_trademark_detection.py '<JSON 参数>' [--inline]
  • Cost constraints: This tool consumes compute; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the zip code to probe repeatedly; if further retrieval is needed, first explain to the user that it will incur additional consumption.

Output strategy (default script behavior)：

  • Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-ruiguan-text-trademark-detection-<timestamp>.json（<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and if the current directory is not writable, report an error)
  • Response body ≤ 8 KB: after saving to disk, print the full JSON to stdout
  • Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also saved to disk)

Data reading suggestions: first look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

  • API Key not configured: the environment variable is not configured LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

How to Build Requests

Principles

  1. Include the full product title: Always pass the complete product title in productTitle -- partial text may miss trademark matches.
  2. Choose target regions: Select regions matching the marketplaces where the product will be sold. Use comma-separated codes for multi-region checks.
  3. Provide additional text when available: If the user has bullet points, descriptions, or backend keywords, include them in productText for a more thorough scan.
  4. Set an appropriate limit: Use the default of 100 for standard checks. Increase up to 500 when scanning titles with many potential matches.

Usage Examples

1. Basic US Trademark Check for a Product Title

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

2. Multi-Region Check (US + EU + UK)

productTitle: "Portable USB-C Charger Fast Charging Power Bank"
regions: "US,EM,GB"
limit: 100

3. Full Listing Scan with Additional Text

productTitle: "Stainless Steel Vacuum Insulated Water Bottle"
productText: "BPA-free, double-wall insulation, keeps drinks cold 24 hours, fits standard cup holders"
regions: "US,JP"
limit: 200

4. Broad Global Check

productTitle: "LED Ring Light with Tripod Stand for Streaming"
regions: "US,EM,GB,DE,FR,IT,ES,AU,CA,MX,JP,CN"
limit: 500

5. China Domestic Market Check

productTitle: "智能蓝牙耳机降噪头戴式"
regions: "CN"
limit: 100

Display Rules

  1. Risk-first presentation: Always highlight the overall risk level (textTrademarkRadar) at the top of results. Use clear language: "Low Risk", "Needs Manual Review", or "High Risk".
  2. Blacklist prominence: If blacklistTrademarks is non-empty, display them first with a clear warning.
  3. Table format: Present trademark matches in a table with columns: Trademark Name, Region, Risk Score, Status, Holder, Application Number, Famous, Amazon Brand, Active Holder.
  4. Score explanation: Remind users that highestModeScore ranges from 0 (safe) to 5 (highest risk).
  5. Whitelist reassurance: If whitelistTrademarks contains entries, note them as safe/exempted trademarks.
  6. Error handling: When a request fails, explain the issue and suggest the user check their product title or adjust regions.
  7. No legal advice: Always remind users that results are for reference only and do not constitute legal advice. Recommend consulting an IP attorney for definitive trademark clearance.

Important Limitations

  • Text-only detection: This tool detects trademarks in text. It does not analyze logos, images, or design marks.
  • Result cap: Maximum 500 results per request.
  • Character limit: Both productTitle and productText are limited to 1000 characters each.
  • Database coverage: Covers 15 countries/regions. Trademarks registered in other jurisdictions may not be detected.

User Expression & Scenario Quick Reference

Applicable -- Trademark risk analysis for product text:

User Says Scenario
"Check my title for trademark issues" Basic trademark scan
"Is this product name safe to use" Infringement risk check
"Scan my listing for brand violations" Full listing scan
"Any trademark risks in this title" Risk assessment
"Check trademarks in US and EU" Multi-region check
"Is XX a registered trademark" Specific term lookup
"Will my listing get taken down for IP" Compliance screening
"Check if this keyword infringes any brand" Keyword safety check

Not applicable -- Needs beyond text trademark detection:

  • Logo or image-based trademark analysis
  • Patent infringement checks
  • Copyright detection
  • Legal opinions or litigation strategy
  • Trademark registration or filing assistance

Compute consumption rules

Consumes 31 compute.

Important: This skill consumes a large amount of compute. If the number of calls exceeds 5, you must useAskUserQuestion to confirm again with the user, and clearly inform the user of the compute already consumed and the estimated compute consumption if continuing to call, letting the user decide whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.