Legal Provision Detail API

Retrieve details of a single legal provision with the Yuandian API. The sample response includes titles. Use it in a legal research or due diligence workflow. The POST request schema also lists id, fgmc, ftnum.

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
ID of the detail target.
Regulation name (required when `id` is empty)
Provision number/name (required when `id` is empty)
Reference date used to determine the laws and regulations effective at that time; if omitted, uses the currently effective version. Format: yyyy-MM-dd

Sample response

"code": 200
data {}
contentString · text preview
data.content
 【前科报告制度】依法受过刑事处罚的人,在入伍、就业的时候,应当如实向有关单位报告自己曾受过刑事处罚,不得隐瞒。
犯罪的时候不满十八周岁被判处五年有期徒刑以下刑罚的人,免除前款规定的报告义务。
"fbrq": "2023-12-29"
"fgid": "aecabfbe6b0843642509a7f1ff865413"
"fgmc": "中华人民共和国刑法(2023修正)"
"ft_num": "第一百条"
"ftmc": "中华人民共和国刑法(2023修正)第一百条"
"id": "aecabfbe6b0843642509a7f1ff865413_100"
"ssrq": "2024-03-01"
"sxx": "现行有效"
"tid": "100"
"title": "中华人民共和国刑法(2023修正)第一百条"
"type": "法条"
"url": "/zxt/statuteDetail/detailPage/aecabfbe6b0843642509a7f1ff865413?text=100"
"xljb_1": "法律"
"xljb_2": "法律"
"message": "请求成功"
"status": "success"

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • contentstring
    • fbrqstring
    • fgidstring
    • fgmcstring
    • ft_numstring
    • ftmcstring
    • idstring
    • ssrqstring
    • sxxstring
    • tidstring
    • titlestring
    • typestring
    • 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 Legal Provision Detail API with your agent

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