Search Administrative Enforcement — search_enforcement

Search for Administrative Enforcement search_enforcement with the PKULaw API. The sample response includes titles. Use it to surface relevant records in a search or discovery tool. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.05 / 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
body* object
Optional parameters (12)
Pass back nextCursor from the previous page unchanged. Leave empty for the first page; do not supply it unless the user requests more results. Keep all other parameters the same as on the previous page when paginating
Issued document / case number, matched as a phrase; separate multiple entries with spaces. Vertical bars do not mean OR. Ignored in semantic mode when queryText is supplied
Publication date to. Accepts 2026.01.01, 2026-01-01, or 2026/01/01; missing zero-padding is added automatically
lawEnforceType array
Enforcement type, e.g. `行政处罚` (administrative penalty), `行政处理` (administrative disposition), `市场禁入` (market entry ban), or `行政检查` (administrative inspection)
lawRegional array
Enforcement region. Accepts only `中央` (central) or a province-level administrative region name, e.g. `广东省` (Guangdong Province); do not supply city or county names
Number of results on this page, e.g. 10; maximum 50. A search can retrieve at most 50 results across 5 pages. Keep this value the same as on the previous page when paginating
punishmentTarget array
Category of penalty recipient: `个人` (individual) or `组织` (organization)
Penalty types, as a string, not an array. Accepts full code-table names or fragments, e.g. `罚款` (fine); separate multiple entries with spaces, Chinese enumeration commas `、`, or commas
Description of case facts or unlawful conduct. In semantic mode, the whole passage is vectorized without splitting on vertical bars; if no case-facts description is supplied in semantic mode, filtering uses the title, document number, and other filters. In keyword mode, used for full-text phrase search: spaces and commas mean AND, | means OR, and the Chinese enumeration comma `、` does not split terms
keyword=search by title, issued document / case number, full text, or filters (default); semantic=find similar documents from case facts supplied in queryText, ignoring title and documentNo
Publication date from. Accepts 2026.01.01, 2026-01-01, or 2026/01/01; missing zero-padding, e.g. 2026.1.1, is added automatically
Document title: phrase matching, not exact equality of the entire text. Spaces and commas mean AND; | means OR. The Chinese enumeration comma does not split terms. Ignored when searchType is semantic and queryText is supplied.
Administrative Enforcement Search

Sample response

"_meta": {
  "io.modelcontextprotocol/serverInfo": {
    "name": "pkulaw-enforcement-doc",
    "title": "北大法宝·行政执法检索",
    "version": "1.0.0"
  },
  "pkulaw/evidence": {
    "confidence": "B",
    "notes": [],
    "origin": "search",
    "retrievedAt": "2026-10-28T12:48:22Z",
    "verifiedByApi": true
  }
}
content [1]
[0] {}
textString · text preview
content[0].text
检索到 1 条行政执法文书,本页 1 条,最多 5 页,一次最多 50 条。召回按相关度排序,引用前请打开 URL 核对原文。
- 1. 财政部行政处罚决定书(财监法〔2026〕193号)(财监法〔2026〕193号,警告、通报批评、罚款、没收违法所得、没收非法财物,中华人民共和国财政部,依据:中华人民共和国注册会计师法(2014修正)第21条第1款、中华人民共和国注册会计师法(2014修正)第21条第2款、中华人民共和国注册会计师法(2014修正)第21条第3款、中华人民共和国注册会计师法(2014修正)第31条、会计师事务所执业许可和监督管理办法(2019修改)第60条第1款、中华人民共和国注册会计师法(2014修正)第39条第1款、会计师事务所执业许可和监督管理办法(2019修改)第67条第1款,2026.07.31)  https://www.pkulaw.com/apy/9445d6e6deb7c9d25469aabb87ec71c0d4d2ea8dab269752bdfb.html?way=mcp
"type": "text"
"isError": false
"resultType": "complete"
"structuredContent": {
  "data": [
    {
      "accordingLaw": [
        "中华人民共和国注册会计师法(2014修正)第21条第1款",
        "中华人民共和国注册会计师法(2014修正)第21条第2款",
        "中华人民共和国注册会计师法(2014修正)第21条第3款",
        "中华人民共和国注册会计师法(2014修正)第31条",
        "会计师事务所执业许可和监督管理办法(2019修改)第60条第1款",
        "中华人民共和国注册会计师法(2014修正)第39条第1款",
        "会计师事务所执业许可和监督管理办法(2019修改)第67条第1款"
      ],
      "category": [
        "财税",
        "会计",
        "审计",
        "招标采购"
      ],
      "documentNo": "财监法〔2026〕193号",
      "enforcementLevel": "中央",
      "lawEnforceType": [
        "行政处罚"
      ],
      "punishOrgan": "中华人民共和国财政部",
      "punishmentDate": "2026.07.31",
      "punishmentTarget": [
        "组织"
      ],
      "punishmentType": [
        "警告、通报批评",
        "罚款、没收违法所得、没收非法财物"
      ],
      "title": "财政部行政处罚决定书(财监法〔2026〕193号)",
      "url": "https://www.pkulaw.com/apy/9445d6e6deb7c9d25469aabb87ec71c0d4d2ea8dab269752bdfb.html?way=mcp"
    }
  ],
  "hasMore": false,
  "message": "查询成功",
  "nextCursor": null,
  "total": 1
}

Response result

Response structure

Inferred from examples
  • _metaobject
    • io.modelcontextprotocol/serverInfoobject
      • namestring
      • titlestring
      • versionstring
    • pkulaw/evidenceobject
      • confidencestring
      • notesunknown[]
      • originstring
      • retrievedAtstring
      • verifiedByApiboolean
  • contentobject[]
    • textstring
    • typestring
  • isErrorboolean
  • resultTypestring
  • structuredContentobject
    • dataobject[]
      • accordingLawstring[]
      • categorystring[]
      • documentNostring
      • enforcementLevelstring
      • lawEnforceTypestring[]
      • punishOrganstring
      • punishmentDatestring
      • punishmentTargetstring[]
      • punishmentTypestring[]
      • titlestring
      • urlstring
    • hasMoreboolean
    • messagestring
    • nextCursornull
    • totalinteger

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 Search Administrative Enforcement — search_enforcement with your agent

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