Regulation Keyword Search API

Search for regulation Keyword with the Yuandian API. The sample response includes titles. Use it to surface relevant records in a search or discovery tool. The POST request schema also lists search_mode, fgmc. 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
Optional parameters (12)
Keywords in regulation text; split on spaces and join with AND/OR according to `search_mode` to form a queryString
Keyword combination mode; defaults to `AND` and is converted to uppercase (for example, `AND`/`OR`)
Regulation name filter; split on spaces and require every term to match the regulation title
Validity status filter; split on spaces and match any term. Allowed literal values: 现行有效、失效、已被修改、部分失效、尚未生效
Region filter; split on spaces and match any term. Allowed literal values: 中央、北京、天津、河北、山西、内蒙古、辽宁、吉林、黑龙江、上海、江苏、浙江、安徽、福建、江西、山东、河南、湖北、湖南、广东、广西、海南、重庆、四川、贵州、云南、西藏、陕西、甘肃、青海、宁夏、新疆
Legal authority filter; split on spaces and match any term. Allowed literal values: 宪法、法律、司法解释、行政法规、监察法规、部门规章、党内法规、军事法规规章、立法机关工作文件、行政机关工作文件、行业/团体规范、地方性法规、自治条例和单行条例、地方司法文件、地方政府规章、地方规范性文件、地方律协规定;
Issuing department filter; split on spaces and match any substring
Publication date range start (inclusive), in yyyy-MM-dd format
Publication date range end (inclusive), in yyyy-MM-dd format
Effective date range start (inclusive), in yyyy-MM-dd format
Effective date range end (inclusive), in yyyy-MM-dd format
Maximum number of results; default 10, maximum 50

Sample response

{
  "code": 200,
  "data": [
    {
      "_score": 63.246273,
      "content": "……(keyword 命中时的高亮片段)……",
      "fbbm": "全国人大常委会",
      "fbrq": "2021-01-22",
      "fgmc": "中华人民共和国行政处罚法(2021修订)",
      "fwzh": "中华人民共和国主席令第70号",
      "id": "0c15f68cf89e1339125e9f41d5d31c67",
      "ssrq": "2021-07-15",
      "sxx": "现行有效",
      "title": "中华人民共和国行政处罚法(2021修订)",
      "url": "/zxt/statuteDetail/detailPage/0c15f68cf89e1339125e9f41d5d31c67",
      "xljb_1": "法律",
      "xljb_2": "法律"
    },
    {
      "_score": 60.66238,
      "content": "……(keyword 命中时的高亮片段)……",
      "fbbm": "国家税务总局",
      "fbrq": "1996-06-06",
      "fgmc": "国家税务总局关于贯彻实施《中华人民共和国行政处罚法》的通知",
      "id": "174d6dcbe3762bb197b6481a7515d237",
      "ssrq": "1996-06-06",
      "sxx": "现行有效",
      "title": "国家税务总局关于贯彻实施《中华人民共和国行政处罚法》的通知",
      "url": "/zxt/statuteDetail/detailPage/174d6dcbe3762bb197b6481a7515d237",
      "xljb_1": "部门规章",
      "xljb_2": "部门规范性文件"
    }
  ],
  "message": "请求成功",
  "status": "success"
}

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject[]
    • _scorenumber
    • contentstring
    • fbbmstring
    • fbrqstring
    • fgmcstring
    • fwzhstring
    • idstring
    • ssrqstring
    • sxxstring
    • titlestring
    • urlstring
    • xljb_1string
    • xljb_2string
  • 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 Regulation Keyword Search API with your agent

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