Securities Industry Regulation Keyword Search API
Searches for a list of securities industry regulations. The request body must not be empty, but keyword may be omitted. Without keywords, results are primarily selected using filters such as regulation name, validity status, region, legal authority, publication date, and effective date. An item includes content only when keywords are supplied and a highlighted match is found; content is a snippet, not the full regulation text. Use the regulation detail API for the full text.
- Selected price
- $0 / callPublished pricing
- Providers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Provider | Price / call | Requests · 30d | Performance | Access |
|---|---|---|---|---|
yuandianCurrent Securities Industry Regulation Keyword Search API · POST | $0 / call | — | —successP50— |
Loading...
Statistics use persisted gateway logs from the last 30 days up to now, including today.
Success rate = successful requests / all requests;
P50 = median latency of successful requests.
Prices reflect the published API contract. Contract revision: 2. Price update time: not supplied.
Playground
Run sends a real API request. Charges follow the published API contract.
Request example
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"keyword": "内幕交易",
"search_mode": "AND",
"sxx": "现行有效",
"top_k": 2
}'- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
Request example
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"keyword": "内幕交易",
"search_mode": "AND",
"sxx": "现行有效",
"top_k": 2
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
keyword | JSON request bodybody | string | No | Keywords in regulation text; split on spaces and join with AND/OR according to `search_mode` to form a queryString |
search_mode | JSON request bodybody | string | No | Keyword combination mode; defaults to `AND` and is converted to uppercase (for example, `AND`/`OR`) |
fgmc | JSON request bodybody | string | No | Regulation name filter; split on spaces and require every term to match the regulation title |
sxx | JSON request bodybody | string | No | Validity status filter; split on spaces and match any term. Allowed literal values: 现行有效、失效、已被修改、部分失效、尚未生效 |
dy | JSON request bodybody | string | No | Region filter; split on spaces and match any term. Allowed literal values: 中央、北京、天津、河北、山西、内蒙古、辽宁、吉林、黑龙江、上海、江苏、浙江、安徽、福建、江西、山东、河南、湖北、湖南、广东、广西、海南、重庆、四川、贵州、云南、西藏、陕西、甘肃、青海、宁夏、新疆 |
xljb_1 | JSON request bodybody | string | No | Legal authority filter; split on spaces and match any term. Allowed literal values: 宪法、法律、司法解释、行政法规、监察法规、部门规章、党内法规、军事法规规章、立法机关工作文件、行政机关工作文件、行业/团体规范、地方性法规、自治条例和单行条例、地方司法文件、地方政府规章、地方规范性文件、地方律协规定; |
fbbm | JSON request bodybody | string | No | Issuing department filter; split on spaces and match any substring |
fbrq_start | JSON request bodybody | string | No | Publication date range start (inclusive), in yyyy-MM-dd format |
fbrq_end | JSON request bodybody | string | No | Publication date range end (inclusive), in yyyy-MM-dd format |
ssrq_start | JSON request bodybody | string | No | Effective date range start (inclusive), in yyyy-MM-dd format |
ssrq_end | JSON request bodybody | string | No | Effective date range end (inclusive), in yyyy-MM-dd format |
top_k | JSON request bodybody | number | No | Maximum number of results; default 10, maximum 50 |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Published response example · Configured HTTP 200; actual status is unverified. Published documentation example. Verify the actual response after an approved call.
Doc example (source abbreviated; HTTP status set during import)
{
"code": 200,
"data": [
{
"_score": 70.18538,
"content": "……（keyword 命中时的高亮片段）……",
"dy": "中央",
"fbbm": "深圳证券交易所",
"fbrq": "2026-04-24",
"fgmc": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司 规范运作（2026年修订）》的通知",
"fwzh": "深证上〔2026〕547号",
"id": "85dc0390a623ac12aeeec5460e4bafec",
"ssrq": "2026-04-24",
"sxx": "现行有效",
"title": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司规范运作（2026年修订）》的通知",
"url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/85dc0390a623ac12aeeec5460e4bafec",
"xljb_1": "行业/团体规范",
"xljb_2": "其他规定"
},
{
"_score": 68.467064,
"content": "……（keyword 命中时的高亮片段）……",
"dy": "中央",
"fbbm": "深圳证券交易所",
"fbrq": "2026-04-24",
"fgmc": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）",
"fwzh": "深证上〔2026〕548号",
"id": "b01691fc9ee211539b5d4ace93d4dca6",
"ssrq": "2026-04-24",
"sxx": "现行有效",
"title": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）",
"url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/b01691fc9ee211539b5d4ace93d4dca6",
"xljb_1": "行业/团体规范",
"xljb_2": "其他规定"
}
],
"message": "请求成功",
"status": "success"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
API Markdown
# Securities Industry Regulation Keyword Search API
Searches for a list of securities industry regulations. The request body must not be empty, but keyword may be omitted. Without keywords, results are primarily selected using filters such as regulation name, validity status, region, legal authority, publication date, and effective date. An item includes content only when keywords are supplied and a highlighted match is found; content is a snippet, not the full regulation text. Use the regulation detail API for the full text.
## Available implementations
yuandian · Securities Industry Regulation Keyword Search API: https://openany.si/markets/apis/capabilities/yuandian-securities-industry-regulation-keyword-search-api?offering=c349910c-7a9e-4dd9-aec0-b43849ce9868 · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/yuandian-securities-industry-regulation-keyword-search-api
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search
Price: $0 / call
Provider: yuandian
Contract revision: 2
Price source: selected implementation in the OpenAny public API catalog. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"keyword": "内幕交易",
"search_mode": "AND",
"sxx": "现行有效",
"top_k": 2
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "Securities Industry Regulation Keyword Search API",
"endpoint": "https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Keywords in regulation text; split on spaces and join with AND/OR according to `search_mode` to form a queryString",
"location": "body",
"name": "keyword",
"nullable": false,
"pointer": "/keyword",
"required": false,
"type": "string"
},
{
"description": "Keyword combination mode; defaults to `AND` and is converted to uppercase (for example, `AND`/`OR`)",
"location": "body",
"name": "search_mode",
"nullable": false,
"pointer": "/search_mode",
"required": false,
"type": "string"
},
{
"description": "Regulation name filter; split on spaces and require every term to match the regulation title",
"location": "body",
"name": "fgmc",
"nullable": false,
"pointer": "/fgmc",
"required": false,
"type": "string"
},
{
"description": "Validity status filter; split on spaces and match any term. Allowed literal values: 现行有效、失效、已被修改、部分失效、尚未生效",
"location": "body",
"name": "sxx",
"nullable": false,
"pointer": "/sxx",
"required": false,
"type": "string"
},
{
"description": "Region filter; split on spaces and match any term. Allowed literal values: 中央、北京、天津、河北、山西、内蒙古、辽宁、吉林、黑龙江、上海、江苏、浙江、安徽、福建、江西、山东、河南、湖北、湖南、广东、广西、海南、重庆、四川、贵州、云南、西藏、陕西、甘肃、青海、宁夏、新疆",
"location": "body",
"name": "dy",
"nullable": false,
"pointer": "/dy",
"required": false,
"type": "string"
},
{
"description": "Legal authority filter; split on spaces and match any term. Allowed literal values: 宪法、法律、司法解释、行政法规、监察法规、部门规章、党内法规、军事法规规章、立法机关工作文件、行政机关工作文件、行业/团体规范、地方性法规、自治条例和单行条例、地方司法文件、地方政府规章、地方规范性文件、地方律协规定;",
"location": "body",
"name": "xljb_1",
"nullable": false,
"pointer": "/xljb_1",
"required": false,
"type": "string"
},
{
"description": "Issuing department filter; split on spaces and match any substring",
"location": "body",
"name": "fbbm",
"nullable": false,
"pointer": "/fbbm",
"required": false,
"type": "string"
},
{
"description": "Publication date range start (inclusive), in yyyy-MM-dd format",
"location": "body",
"name": "fbrq_start",
"nullable": false,
"pointer": "/fbrq_start",
"required": false,
"type": "string"
},
{
"description": "Publication date range end (inclusive), in yyyy-MM-dd format",
"location": "body",
"name": "fbrq_end",
"nullable": false,
"pointer": "/fbrq_end",
"required": false,
"type": "string"
},
{
"description": "Effective date range start (inclusive), in yyyy-MM-dd format",
"location": "body",
"name": "ssrq_start",
"nullable": false,
"pointer": "/ssrq_start",
"required": false,
"type": "string"
},
{
"description": "Effective date range end (inclusive), in yyyy-MM-dd format",
"location": "body",
"name": "ssrq_end",
"nullable": false,
"pointer": "/ssrq_end",
"required": false,
"type": "string"
},
{
"description": "Maximum number of results; default 10, maximum 50",
"location": "body",
"name": "top_k",
"nullable": false,
"pointer": "/top_k",
"required": false,
"type": "number"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "0",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Doc example (source abbreviated; HTTP status set during import)",
"request": {
"body": {
"keyword": "内幕交易",
"search_mode": "AND",
"sxx": "现行有效",
"top_k": 2
},
"headers": {},
"path": {},
"query": {}
},
"response_body": {
"code": 200,
"data": [
{
"_score": 70.18538,
"content": "……（keyword 命中时的高亮片段）……",
"dy": "中央",
"fbbm": "深圳证券交易所",
"fbrq": "2026-04-24",
"fgmc": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司规范运作（2026年修订）》的通知",
"fwzh": "深证上〔2026〕547号",
"id": "85dc0390a623ac12aeeec5460e4bafec",
"ssrq": "2026-04-24",
"sxx": "现行有效",
"title": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司规范运作（2026年修订）》的通知",
"url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/85dc0390a623ac12aeeec5460e4bafec",
"xljb_1": "行业/团体规范",
"xljb_2": "其他规定"
},
{
"_score": 68.467064,
"content": "……（keyword 命中时的高亮片段）……",
"dy": "中央",
"fbbm": "深圳证券交易所",
"fbrq": "2026-04-24",
"fgmc": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）",
"fwzh": "深证上〔2026〕548号",
"id": "b01691fc9ee211539b5d4ace93d4dca6",
"ssrq": "2026-04-24",
"sxx": "现行有效",
"title": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）",
"url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/b01691fc9ee211539b5d4ace93d4dca6",
"xljb_1": "行业/团体规范",
"xljb_2": "其他规定"
}
],
"message": "请求成功",
"status": "success"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Doc example (source abbreviated; HTTP status set during import)
Published documentation example. Verify the actual response after an approved call.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 12
Review these request fields before running. Keep the published provider and request method unchanged.
keyword- Keywords in regulation text; split on spaces and join with AND/OR according to `search_mode` to form a queryString
search_mode- Keyword combination mode; defaults to `AND` and is converted to uppercase (for example, `AND`/`OR`)
fgmc- Regulation name filter; split on spaces and require every term to match the regulation title
sxx- Validity status filter; split on spaces and match any term. Allowed literal values: 现行有效、失效、已被修改、部分失效、尚未生效
dy- Region filter; split on spaces and match any term. Allowed literal values: 中央、北京、天津、河北、山西、内蒙古、辽宁、吉林、黑龙江、上海、江苏、浙江、安徽、福建、江西、山东、河南、湖北、湖南、广东、广西、海南、重庆、四川、贵州、云南、西藏、陕西、甘肃、青海、宁夏、新疆
xljb_1- Legal authority filter; split on spaces and match any term. Allowed literal values: 宪法、法律、司法解释、行政法规、监察法规、部门规章、党内法规、军事法规规章、立法机关工作文件、行政机关工作文件、行业/团体规范、地方性法规、自治条例和单行条例、地方司法文件、地方政府规章、地方规范性文件、地方律协规定;
fbbm- Issuing department filter; split on spaces and match any substring
fbrq_start- Publication date range start (inclusive), in yyyy-MM-dd format
fbrq_end- Publication date range end (inclusive), in yyyy-MM-dd format
ssrq_start- Effective date range start (inclusive), in yyyy-MM-dd format
ssrq_end- Effective date range end (inclusive), in yyyy-MM-dd format
top_k- Maximum number of results; default 10, maximum 50
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_zq_search' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ --data-raw '{ "keyword": "内幕交易", "search_mode": "AND", "sxx": "现行有效", "top_k": 2 }'Check the response
Published response example · Configured HTTP 200; actual status is unverified.
Sample response · not a live result{ "code": 200, "data": [ { "_score": 70.18538, "content": "……（keyword 命中时的高亮片段）……", "dy": "中央", "fbbm": "深圳证券交易所", "fbrq": "2026-04-24", "fgmc": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司规范运作（2026年修订）》的通知", "fwzh": "深证上〔2026〕547号", "id": "85dc0390a623ac12aeeec5460e4bafec", "ssrq": "2026-04-24", "sxx": "现行有效", "title": "深圳证券交易所关于发布《深圳证券交易所上市公司自律监管指引第1号——主板上市公司规范运作（2026年修订）》的通知", "url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/85dc0390a623ac12aeeec5460e4bafec", "xljb_1": "行业/团体规范", "xljb_2": "其他规定" }, { "_score": 68.467064, "content": "……（keyword 命中时的高亮片段）……", "dy": "中央", "fbbm": "深圳证券交易所", "fbrq": "2026-04-24", "fgmc": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）", "fwzh": "深证上〔2026〕548号", "id": "b01691fc9ee211539b5d4ace93d4dca6", "ssrq": "2026-04-24", "sxx": "现行有效", "title": "深圳证券交易所上市公司自律监管指引第2号——创业板上市公司规范运作（2026年修订）", "url": "https://ydzk.chineselaw.com/zxt/statuteDetail/detailPage/b01691fc9ee211539b5d4ace93d4dca6", "xljb_1": "行业/团体规范", "xljb_2": "其他规定" } ], "message": "请求成功", "status": "success" }
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.