What is the endpoint for [AI66-8]FTO Search - Claim Chart Analysis (Internal ID)?

The [AI66-8]FTO Search - Claim Chart Analysis (Internal ID) endpoint is POST https://connect.patsnap.com/fto_steps/cc_analysis.

Where can I find the OpenAPI schema for [AI66-8]FTO Search - Claim Chart Analysis (Internal ID)?

The OpenAPI schema is available at /openapi.json#/paths/~1fto_steps~1cc_analysis/post. You can also browse the full specification at /openapi.json.

[AI66-8]FTO Search - Claim Chart Analysis (Internal ID)

Q: What data can [AI66-8]FTO Search - Claim Chart Analysis (Internal ID) return?

[AI66-8]FTO Search - Claim Chart Analysis (Internal ID) Runs claim chart comparison on the screened patents. patent_ids are internal library IDs; when omitted, the patents kept by screening are used. At most 200 per call; exceeding it returns 422 requiring batching. Observed pro-mode timing: analysing all 150 patents successfully in about 239 seconds. POST returns running immediately; poll GET /fto_steps/cc_analysis/{task_id} for the result. See the Response Schema and Success Response Example on this page for the full structure.

post

https://connect.patsnap.com/fto_steps/cc_analysis

Try in Sandbox

Runs claim chart comparison on the screened patents. patent_ids are internal library IDs; when omitted, the patents kept by screening are used. At most 200 per call; exceeding it returns 422 requiring batching. Observed pro-mode timing: analysing all 150 patents successfully in about 239 seconds. POST returns running immediately; poll GET /fto_steps/cc_analysis/{task_id} for the result.

Request Parameters

List of parameters supported by this API endpoint

Name	Type	Example	Description
`task_id`	`string`	`fto-20260928-a1b2c3d4`	Task ID. Auto-generated as fto-{yyyymmdd}-{8-hex} on first call when omitted (same format as resolve_task_id in app/fto_mcp/context.py). Later steps must reuse the same task_id to read upstream artifacts.
`input_lang`	`string`	`cn`	Input language: cn / en / tw / jp. This step does not currently use this field (kept for compatibility, safe to ignore).
`technical_proposal`	`string`	`一种折叠屏电子设备的转轴结构，包括壳体、同步旋转机构与快拆锁定件……`	Technical proposal description. When omitted, it is read back by task_id from a prior artifact (usually the refined result of proposal_refine, or an earlier raw proposal already persisted). Returns 422 when neither is available.
`patent_ids`	`array`	`[ "57821030-e8f0-4cd3-8c28-1b1c485133e6" ]`	Internal patent IDs (UUIDs) to analyse, taken from retained_patent_ids of patent_screening. When omitted, it is read back from this task's screening result; returns 422 if the retained count exceeds 200, requiring explicit batching (reuse the same task_id across batches; each batch upserts by task_id+patent_id without overwriting others). At most 200 per call (unlike the MCP side's 10-per-batch cap).
`mode`	`string`	`pro`	Execution depth: pro for the full pipeline (default); lite for a quick screening. Internally sets top_k=min(count, 300) explicitly based on the actual patent count, to avoid the agent's default truncation (only 150 kept by default under pro) silently dropping patents.

{
  "mode": "pro",
  "task_id": "fto-20260928-a1b2c3d4",
  "input_lang": "cn",
  "patent_ids": [
    "57821030-e8f0-4cd3-8c28-1b1c485133e6"
  ],
  "technical_proposal": "一种折叠屏电子设备的转轴结构，包括壳体、同步旋转机构与快拆锁定件……"
}

Response Schema

Structure of the API response data

Field Name	Type	Example	Description
`status` Required	`string`	`running`	Status right after submission, always running; the actual execution happens in the background, poll with GET for the terminal state.
`task_id` Required	`string`	`fto-20260928-a1b2c3d4`	Task ID; when the request body omits it, this is the value generated for this call. Later steps must carry it to continue the chain.
`step_name` Required	`string`	`proposal_refine`	The submitted step name, matching the URL path.

Success Response Example

Example of a successful API response

JSON

{
  "status": true,
  "task_id": "fto-20260928-a1b2c3d4",
  "step_name": "proposal_refine",
  "error_code": 0
}

Error Codes

List of possible error codes returned by this endpoint

Business Errors

Error Code	Description
`68300004`	Invalid parameter!
`68300005`	Search api failure!
`68300006`	Analytic basic access error!
`68300007`	Bad request!
`68300008`	Service error, please try again later!
`68300010`	The file does not comply with upload specifications!

Platform Errors

Error Code	Description
`67200000`	API call exceeds the total limit set by the platform!
`67200001`	API call exceeds the total limit set by the platform!
`67200002`	The current call rate is too fast, exceeding the current configuration limit QPS!
`67200003`	The key and secret parameters for applying for the token are incorrect or the client has been disabled!
`67200004`	The requested api does not have permission. Please contact our support personnel!
`67200005`	Insufficient account balance/number of calls!
`67200006`	The client has exceeded the activation validity period!
`67200007`	The current call exceeds the configured usage limit of the day!
`67200008`	Please check if the required apikey in the query parameter has been transmitted!
`67200009`	The apikey does not match the passed bearerToken. Please check if a valid token is being used!
`67200012`	The request is illegal!
`67200100`	The current server status is busy, request response timeout!
`67200101`	The API requested currently does not exist. Please check the request path!

HTTP Status Codes

Status Code	Description
`0`	Success
`422`	Validation Error
`409`	同一 task_id 已有步骤正在运行