Case Semantic Search API

Search for case Semantic with the Yuandian API. Supply a search query. Sample fields include answers and titles. Use it to surface relevant records in a search or discovery tool. The POST request schema also lists rewrite_flag, wenshu_filter. Use the results to organize a research workflow and cross-check the relevant source records.

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
Question or query text to search for
Whether to rewrite the query; defaults to `false`
wenshu_filterobject

wenshu_filter

Case search filters; see the field descriptions for details
Number of cases to return (default 45; cannot exceed the total number retrieved)

Sample response

{
  "answer": "",
  "code": 201,
  "extra": {
    "wenshu": [
      {
        "ah": "(2019)京01刑终629号",
        "ajlb": "刑事案件",
        "anyou": [
          "盗窃罪"
        ],
        "authority": "",
        "ay": [
          "201"
        ],
        "cj": "中级",
        "content": "本案的案件基本事实为:被告人吕江波在湖北省黄石市三江共和城铜锣湾广场售楼部更衣室内,通过脚踩方式使被害人杨某掉落的信用卡等物品未被发现,随后非法占有并使用这些信用卡进行了取款,共计取款人民币8000元。吕江波的家属后来代其赔偿了被害人14000元,得到了被害人的谅解。吕江波的行为最终被认定为盗窃信用卡并使用,构成盗窃罪。本案争议焦点在于原审被告人吕江波的行为是否构成信用卡诈骗罪以及是否应当对其盗窃行为进行重新定罪量刑。法院认为,吕江波实施了窃取他人财物的行为,数额较大,其行为符合盗窃罪的构成要件,而非信用卡诈骗罪。一审判决将吕江波的行为错误地定性为信用卡诈骗罪,并据此作出数罪并罚的判决,属于法律适用错误,应予以纠正。同时,考虑到吕江波到案后能如实供述自己的罪行,自愿签署认罪认罚具结书,并在案发后通过家属帮助退赔全部涉案赃款,获得被害人谅解,依法可以从轻处罚。然而,鉴于吕江波多次实施盗窃,包括入户盗窃,这一情节在量刑时必须予以充分考虑。综合考量吕江波犯罪的事实、性质、情节及其行为对社会的危害程度,法院依法改判其构成盗窃罪,并根据相关法律规定调整了刑罚,确保判决公正合理。被告人以非法占有为目的,实施盗窃行为,数额较大,构成盗窃罪,应予惩处。若被告人到案后如实供述罪行,签署认罪认罚具结书,并在亲属协助下退赔全部赃款且获得被害人谅解,可依法从宽处罚;但多次盗窃或入户盗窃的情节应在量刑时予以考量。争议焦点1:原审被告人吕江波的行为是否构成盗窃罪而非信用卡诈骗罪。",
        "db": "精选案例库",
        "jaDate": 20191223,
        "jand": 2019,
        "jbdw": "北京市第一中级人民法院",
        "para_name": "总结",
        "scid": "b5c63a4ec01df9495b6b9024bf0a2bee",
        "score": 1.0098828125000001,
        "spcx": "二审案件",
        "title": "吕江波盗窃二审刑事判决书",
        "type": 2,
        "wszl": "判决书",
        "xzqh_c": "一中院",
        "xzqh_p": "北京"
      },
      {
        "ah": "(2019)京01刑终124号",
        "ajlb": "刑事案件",
        "anyou": [
          "盗窃罪"
        ],
        "authority": "",
        "ay": [
          "201"
        ],
        "cj": "中级",
        "content": "本案的案件基本事实为:2018年6月29日凌晨,汪传国在北京石景山区模式口村28号院内先后窃取了张某1的苹果牌Iphone6SPLUS手机一部及少量现金,以及郭某的两部手机(白色华为牌NOVA青春型手机一部,价值780元;苹果牌黑色Iphone8PLUS手机一部,价值4400元)和现金22100元。同年7月12日,汪传国被抓获,但赃款赃物未能追回。汪传国家属事后分别向张某1和郭某进行了部分经济补偿并获得了谅解。二审期间,汪传国未能提供新证据支持其未盗窃郭某现金的主张,相关证据足以证实其盗窃金额。本案争议焦点在于上诉人汪传国是否构成盗窃罪以及其刑事责任的确定。法院认为,汪传国以非法占有为目的,实施了入户盗窃他人财物的行为,且涉案金额较大,其行为符合盗窃罪的构成要件,依法应予惩处。此外,汪传国曾因盗窃罪被判刑,刑满释放后五年内再次实施盗窃行为,属于累犯,依法应从重处罚。然而,考虑到汪传国到案后如实供述了部分犯罪事实,积极退赔被害人部分损失并获得谅解,依法可以从轻处罚。综上所述,一审法院认定汪传国犯盗窃罪的事实清楚,证据确凿,定罪准确,量刑适当,审判程序合法,但未依法责令汪传国退赔全部违法所得,存在不当之处,需予以纠正。以非法占有为目的实施入户盗窃,数额较大的,构成盗窃罪,依法应予惩处。若行为人系累犯,即曾因盗窃罪被判处有期徒刑,刑罚执行完毕后五年内再犯应判处有期徒刑以上刑罚之罪的,依法应从重处罚。同时,行为人如实供述犯罪事实,积极退赔被害人损失并获得谅解的,依法可以从轻处罚。法院在判决时需考虑犯罪事实、性质、情节及对社会的危害程度,确保量刑适当。",
        "db": "精选案例库",
        "jaDate": 20190322,
        "jand": 2019,
        "jbdw": "北京市第一中级人民法院",
        "para_name": "总结",
        "scid": "3f186a2590ab411f2fedcd003caf9c1e",
        "score": 0.9608060420000001,
        "spcx": "二审案件",
        "title": "汪传国盗窃二审刑事判决书",
        "type": 2,
        "wszl": "判决书",
        "xzqh_c": "一中院",
        "xzqh_p": "北京"
      }
    ]
  },
  "messageId": "",
  "msg": "成功(返回结构化数据)",
  "request_id": "",
  "style": ""
}

Response result

Response structure

Inferred from examples
  • answerstring
  • codeinteger
  • extraobject
    • wenshuobject[]
      • ahstring
      • ajlbstring
      • anyoustring[]
      • authoritystring
      • aystring[]
      • cjstring
      • contentstring
      • dbstring
      • jaDateinteger
      • jandinteger
      • jbdwstring
      • para_namestring
      • scidstring
      • scorenumber
      • spcxstring
      • titlestring
      • typeinteger
      • wszlstring
      • xzqh_cstring
      • xzqh_pstring
  • messageIdstring
  • msgstring
  • request_idstring
  • stylestring

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 Case Semantic Search API with your agent

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