Enterprise Patent List API

Retrieve patent records for an enterprise using its enterprise ID or unified social credit code with the Yuandian API. Results are paginated, with 30 records per page by default. Screen company records for intellectual property research. The GET request schema also lists tyshxydm, pageNo.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Enterprise ID
Unified social credit code
Page number; defaults to 1

Sample response

"code": 200
data {}
"hasMore": true
"id": "a80a4cc8-9954-4dd3-bcaf-aebb99487b14"
list [1]
[0] {}
"专利名称": "大模型的训练方法、问答方法、装置、设备以及存储介质"
代理人JSON string · parsed preview
data.list[0]["代理人"]
[
  "阎敏",
  "陈晓欣"
]
"代理机构": "北京易光知识产权代理有限公司"
分类号JSON string · parsed preview
data.list[0]["分类号"]
[
  "G06F18/214",
  "G06F18/2415",
  "G06N5/04",
  "G06N3/0895",
  "G06N3/091"
]
发明人JSON string · parsed preview
data.list[0]["发明人"]
[
  "文祎琳",
  "陈沐晗",
  "吕中厚",
  "包沉浮",
  "王国秋",
  "田伟娟",
  "侯金昌",
  "韩淼"
]
"地址": "北京市海淀区上地十街10号百度大厦2层"
"摘要": "本公开提供了大模型的训练方法、问答方法、装置、设备以及存储介质,涉及计算机技术领域,尤其涉及深度学习、大模型、智能问答、安全检测等技术领域。具体实现方案为:确定训练样本集合,该训练样本集合包含正样本和负样本;该正样本包括第一提示信息、与该第一提示信息对应的第一答案信息、第一思维链和第一标签中的至少之一;该负样本包括第二提示信息、与该第二提示信息对应的第二答案信息和第二标签中的至少之一;根据训练提示,利用该正样本和该负样本,确定目标损失函数;利用该目标损失函数,对待训练的第一大模型进行训练,以得到训练完成的第二大模型。本公开能够提升大模型对生成内容进行安全检测的准确性。"
"申请人": [
  "北京百度网讯科技有限公司"
]
"申请公布号": "CN121743868A"
"申请公布日期": "2026-03-27"
"申请号": "CN202511864451.4"
"申请日期": "2025-12-10"
"name": "北京百度网讯科技有限公司"
"pageNo": 1
"pageSize": 30
"total": 23163
"message": "请求成功"
"status": "success"

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • hasMoreboolean
    • idstring
    • listobject[]
      • 专利名称string
      • 代理人string
      • 代理机构string
      • 分类号string
      • 发明人string
      • 地址string
      • 摘要string
      • 申请人string[]
      • 申请公布号string
      • 申请公布日期string
      • 申请号string
      • 申请日期string
    • namestring
    • pageNointeger
    • pageSizeinteger
    • totalinteger
  • messagestring
  • statusstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Enterprise Patent List API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.