Skip to content

nexscope-ai/nexscope-ecommerce-skills / ecommerce-ruiguan-detection-patent-design

ecommerce.ruiguan-detection-patent-design

Verified

Detect design patent infringement risks by comparing a product image against a global design patent database across 25+ jurisdictions. Triggered when users mention design patent detection, patent infringement check, patent risk analysis, TRO case lookup, design patent search, product design patent screen, or visual patent similarity. Even if the user does not explicitly say "design patent," this skill should be triggered whenever the need involves checking whether a product image may infringe existing design patents.

FileKindSize
SKILL.mdskill md10.4 KB
manifest.jsonconfig519 B
references/api.mdmarkdown8.8 KB
scripts/ruiguan_detection_patent_design.pyscript6.2 KB
scripts/upload_image.pyscript9.6 KB

references/api.md

View on GitHub
# Ruiguan Design Patent Detection API Reference

## Request Specification

- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ruiguan/detectionPatentDesign`
- **Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`; read api_key from `nexscope_AGENT_API_KEY` or `nexscopeAGENT_API_KEY`. If neither is configured, follow the authentication and credits guidance in SKILL.md.

## Request Parameters

POST Body (JSON):

| Parameter | Type | Required | Default | Description |
|------|------|------|--------|------|
| imageUrl | string | Yes | - | Product image file URL for comparison with the patent database (maximum 1000 characters) |
| queryMode | string | Yes | hybrid | Search mode: `physical` (physical image search), `line` (line drawing search), or `hybrid` (combined search). Maximum 1000 characters |
| topNumber | integer | Yes | 100 | Number of patents to retrieve (maximum 100) |
| regions | string | No | US | Country/region codes where the product is sold, separated by commas (e.g., `US,EU,CN`). Supported: US, EU, CN, JP, KR, DE, GB, FR, IT, AU, CA, BR, MX, IN, TH, SE, CH, IE, IL, DK, NZ, AT, BX, FI, WO. Maximum 1000 characters |
| productTitle | string | No | - | Product title providing additional search context (maximum 1000 characters) |
| productDescription | string | No | - | Product description providing additional search context (maximum 1000 characters) |
| patentStatus | string | No | 1 | Patent validity filter: `1` (valid patents), `0` (expired or invalid patents), or `1,0` (all). Maximum 1000 characters |
| enableRadar | boolean | No | true | Whether to enable radar analysis (AI infringement assessment) |
| topLoc | string | No | - | First-level LOC scope to search (e.g., `06,07`). Format: `^(0[1-9]\|1[0-9]\|2[0-9]\|3[0-2]\|ALL)(,(0[1-9]\|1[0-9]\|2[0-9]\|3[0-2]\|ALL))*$`. If omitted, use the results of the model LOC prediction service |
| sourceLanguage | string | No | - | Source language code for translation into English (e.g., `zh-CN`). Leave empty for English text. Maximum 1000 characters |


## Nexscope response envelope

These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.

`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.

Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.

```json
{"code":0,"msg":null,"data":{}}
```

Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.

## Response Structure

| Field | Type | Description |
|------|------|------|
| total | integer | Total number of patent records returned |
| data | array | List of patents (see patent objects below) |
| columns | array | Rendering column definitions |
| costToken | integer | Tokens consumed |
| type | string | Rendering style |

### Patent Objects (Each Element of the `data` Array)

| Field | Type | Description |
|------|------|------|
| applicationNumber | string | Patent application number |
| publicationNumber | string | Patent publication number |
| patentProd | string | Patent title (English) |
| patentProdCn | string | Patent title (Chinese) |
| similarity | string | Similarity between the patent and product image (0-1) |
| patentImageUrl | string | URL of the patent drawing most similar to the product image |
| images | array | List of patent images |
| abstracts | string | Patent abstract |
| specification | string | Patent specification |
| inventors | array | List of inventors |
| applicants | array | List of applicants |
| applicantAddresses | array | Applicant addresses |
| troCase | boolean | Whether there is a history of TRO enforcement |
| troHolder | boolean | Whether the patent belongs to a TRO rights holder |
| radarResult | object | AI radar analysis result |
| radarResult.same | boolean | Whether infringement is suspected |
| radarResult.exp | string | Expected description (explanation of the radar assessment) |
| patentLoc | string | Patent LOC classifications (comma-separated) |
| locOneInfo | string | First-level LOC details |
| locTwoInfo | string | Second-level LOC details |
| patentValidity | string | Patent validity |
| applicationDate | string | Patent application date |
| publicationDate | string | Patent publication date |
| grantDate | string | Patent grant date |
| estimatedDueDate | string | Estimated expiration date |
| registrationOfficeCode | string | Patent registration office |
| patentFamily | array | List of patent family members |
| globalPatentId | string | Global patent ID |
| globalImageId | string | Patent image ID |
| isSketchText | string | Whether the image is a line drawing |

## Error Codes

HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.

### Recovery guidance

| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: follow the authentication and credits guidance in SKILL.md. |
| Insufficient credits or balance | HTTP 402: follow the authentication and credits guidance in SKILL.md. |

## curl Examples

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ruiguan/detectionPatentDesign \
  -H "Authorization: $nexscopeAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "imageUrl": "https://example.com/product.jpg",
    "queryMode": "hybrid",
    "topNumber": 50,
    "regions": "US",
    "enableRadar": true
  }'
```

## Multi-region Search Example

```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ruiguan/detectionPatentDesign \
  -H "Authorization: $nexscopeAGENT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "imageUrl": "https://example.com/product.jpg",
    "queryMode": "physical",
    "topNumber": 100,
    "regions": "US,EU,CN",
    "productTitle": "Portable wireless charging stand",
    "productDescription": "A foldable wireless charging stand for smartphones",
    "patentStatus": "1",
    "enableRadar": true
  }'
```

---

## Feedback API

> This endpoint is **separate** from the tool API above. Do not mix the two base URLs.

- **POST** `https://skill-api.nexscope.com/api/v1/public/feedback`
- **Content-Type:** `application/json`

```json
{
  "skillName": "nexscope-xxx-xxx",
  "sentiment": "POSITIVE",
  "category": "OTHER",
  "content": "Results were accurate, user was satisfied."
}
```

**Field rules:**
- `skillName`: Use this skill's `name` from the YAML frontmatter
- `sentiment`: Choose ONE — `POSITIVE` (praise), `NEUTRAL` (suggestion without emotion), `NEGATIVE` (complaint or error)
- `category`: Choose ONE — `BUG` (malfunction or wrong data), `COMPLAINT` (user dissatisfaction), `SUGGESTION` (improvement idea), `OTHER`
- `content`: Include what the user said or intended, what actually happened, and why it is a problem or praise

## API Key request rate and retries

All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.

HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall