Regulation Detail API
Retrieves regulation details. The request body must not be empty, and at least one of id or fgmc must be supplied. refer_date can be used to locate the version effective on a specified date; if omitted, returns details related to the currently effective version. Returns basic regulation information, validity status, publication and effective dates, issuing departments, attachments, and regulation content.
- Selected price
- $0 / callPublished pricing
- Providers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Provider | Price / call | Requests · 30d | Performance | Access |
|---|---|---|---|---|
yuandianCurrent Regulation Detail API · POST | $0 / call | — | —successP50— |
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.
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"fgmc": "中华人民共和国刑法",
"refer_date": "2025-01-01"
}'- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"fgmc": "中华人民共和国刑法",
"refer_date": "2025-01-01"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
id | JSON request bodybody | string | No | ID of the detail target. |
fgmc | JSON request bodybody | string | No | Regulation name (required when `id` is empty) |
refer_date | JSON request bodybody | string | No | Reference date used to determine the laws and regulations effective at that time; if omitted, uses the currently effective version. Format: yyyy-MM-dd |
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.
{
"code": 200,
"data": {
"content": "……",
"fbrq": "2023-12-29",
"fgid": "aecabfbe6b0843642509a7f1ff865413",
"fgmc": "中华人民共和国刑法(2023修正)",
"id": "aecabfbe6b0843642509a7f1ff865413",
"ssrq": "2024-03-01",
"sxx": "现行有效",
"title": "中华人民共和国刑法(2023修正)",
"type": "法规",
"url": "/zxt/statuteDetail/detailPage/aecabfbe6b0843642509a7f1ff865413",
"xljb_1": "法律",
"xljb_2": "法律"
},
"message": "请求成功",
"status": "success"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Regulation Detail API
Retrieves regulation details. The request body must not be empty, and at least one of id or fgmc must be supplied. refer_date can be used to locate the version effective on a specified date; if omitted, returns details related to the currently effective version. Returns basic regulation information, validity status, publication and effective dates, issuing departments, attachments, and regulation content.
## Available implementations
yuandian · Regulation Detail API: https://openany.si/markets/apis/capabilities/yuandian-regulation-detail-api?offering=f7db3081-1506-4608-9975-8e3055e6254a · $0 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/yuandian-regulation-detail-api
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail
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_detail' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"fgmc": "中华人民共和国刑法",
"refer_date": "2025-01-01"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "Regulation Detail API",
"endpoint": "https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "ID of the detail target.",
"location": "body",
"name": "id",
"nullable": false,
"pointer": "/id",
"required": false,
"type": "string"
},
{
"description": "Regulation name (required when `id` is empty)",
"location": "body",
"name": "fgmc",
"nullable": false,
"pointer": "/fgmc",
"required": false,
"type": "string"
},
{
"description": "Reference date used to determine the laws and regulations effective at that time; if omitted, uses the currently effective version. Format: yyyy-MM-dd",
"location": "body",
"name": "refer_date",
"nullable": false,
"pointer": "/refer_date",
"required": false,
"type": "string"
}
],
"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": {
"fgmc": "中华人民共和国刑法",
"refer_date": "2025-01-01"
},
"headers": {},
"path": {},
"query": {}
},
"response_body": {
"code": 200,
"data": {
"content": "……",
"fbrq": "2023-12-29",
"fgid": "aecabfbe6b0843642509a7f1ff865413",
"fgmc": "中华人民共和国刑法(2023修正)",
"id": "aecabfbe6b0843642509a7f1ff865413",
"ssrq": "2024-03-01",
"sxx": "现行有效",
"title": "中华人民共和国刑法(2023修正)",
"type": "法规",
"url": "/zxt/statuteDetail/detailPage/aecabfbe6b0843642509a7f1ff865413",
"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 3
Review these request fields before running. Keep the published provider and request method unchanged.
id- ID of the detail target.
fgmc- Regulation name (required when `id` is empty)
refer_date- Reference date used to determine the laws and regulations effective at that time; if omitted, uses the currently effective version. Format: yyyy-MM-dd
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/yuandian/open/rh_fg_detail' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ --data-raw '{ "fgmc": "中华人民共和国刑法", "refer_date": "2025-01-01" }'Check the response
Published response example · Configured HTTP 200; actual status is unverified.
Sample response · not a live result{ "code": 200, "data": { "content": "……", "fbrq": "2023-12-29", "fgid": "aecabfbe6b0843642509a7f1ff865413", "fgmc": "中华人民共和国刑法(2023修正)", "id": "aecabfbe6b0843642509a7f1ff865413", "ssrq": "2024-03-01", "sxx": "现行有效", "title": "中华人民共和国刑法(2023修正)", "type": "法规", "url": "/zxt/statuteDetail/detailPage/aecabfbe6b0843642509a7f1ff865413", "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.