Intelligent Legal Search — diff_article_versions

Search for intelligent Legal diff_article_versions with the PKULaw API. Supply an article number and a from version. Sample fields include citations. Use it in a legal research or due diligence workflow. 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
Current article number, e.g. `3` or `第三条` (Article 3). Write Article 17-1 as 17.1 or `第十七条之一`.
Starting version (older version). Accepts a version label, e.g. `2018修正` (amended in 2018), as returned by list_law_versions, or a date YYYY-MM-DD (locates the version effective at that time by its effective date).
Statute name. Full or abbreviated names are accepted, e.g. `公司法` (Company Law), `民法典` (Civil Code), or `上海市生活垃圾管理条例` (Shanghai Municipal Regulations on Domestic Waste Management). Version hints such as `新公司法` (new Company Law), `2023公司法` (2023 Company Law), or `公司法 2023修订` (Company Law, revised in 2023) are also accepted. For long names of judicial interpretations, meeting minutes, and similar documents, supply as much of the full name as possible. Maximum 200 characters.
Ending version (newer version). Uses the same syntax as fromVersion; also accepts current (the version of this statute that remains currently effective; there is no current version if it has been incorporated into another statute).
Optional parameters (1)
Diff format. phraseSummary (default) provides added/deleted phrases and a change level, suitable for paraphrasing; unified provides line-by-line additions/deletions; sideBySide provides a left/right comparison, suitable for legislative amendment comparison tables.
Differences Between Two Article Versions

Sample response

"_meta": {
  "io.modelcontextprotocol/serverInfo": {
    "name": "pkulaw-statute-history",
    "title": "北大法宝·法规与法条沿革",
    "version": "1.0.0"
  },
  "pkulaw/evidence": {
    "confidence": "A",
    "notes": [],
    "origin": "mixed",
    "retrievedAt": "2026-10-28T12:48:18Z",
    "verifiedByApi": true
  },
  "ui": {
    "resourceUri": "ui://pkulaw-statute-history/article-diff.html"
  }
}
content [1]
[0] {}
textString · text preview
content[0].text
《中华人民共和国公司法》第一条:2018修正 → 2023修订,文本变化较大。
删除 1 处短语,新增 5 处短语。
新增:股东;职工和债权人的合法权益;完善中国特色现代企业制度;弘扬企业家精神;根据宪法
删除:股东和债权人的合法权益
增删短语为启发式切分,小标题或标点变化可能导致同一句两侧都出现;实质性改动请以统一 diff 或左右对照为准。
引注:https://www.pkulaw.com/chl/8ba805acd08846d7bdfb.html?way=mcp#tiao_1
"type": "text"
"isError": false
"resultType": "complete"
"structuredContent": {
  "articleLabel": "第一条",
  "articleNumber": "1.0",
  "compareStatus": "compared",
  "diff": {
    "lines": null,
    "phraseSummary": {
      "addedPhrases": [
        "股东",
        "职工和债权人的合法权益",
        "完善中国特色现代企业制度",
        "弘扬企业家精神",
        "根据宪法"
      ],
      "caveat": "本结果仅为基于文本短语和相似度的程序化差异摘要,不构成法律语义、法律效果或法律适用结论;请结合条文全文、上下文和专业判断复核。增删短语按标点启发式切分,小标题或标点变化可能导致同一句同时出现在新增和删除里;判断实质性改动请以统一 diff 或左右对照为准。",
      "heuristicChangeLevel": "majorTextChange",
      "normativeTermsChanged": [],
      "removedPhrases": [
        "股东和债权人的合法权益"
      ],
      "summary": "删除 1 处短语,新增 5 处短语。"
    },
    "rows": null
  },
  "diffStats": {
    "addedPhraseCount": 5,
    "changedLineCount": 0,
    "changedRowCount": 0,
    "heuristicChangeLevel": "majorTextChange",
    "heuristicChangeLevelChinese": "文本变化较大",
    "isTextUnchanged": false,
    "normativeTermChangeCount": 0,
    "removedPhraseCount": 1
  },
  "format": "phraseSummary",
  "fromDateBasis": "label",
  "fromVersion": {
    "articleLabel": "第一条",
    "articleNumber": "1.0",
    "changeType": "unchanged",
    "changeTypeChinese": "未修改",
    "citation": {
      "anchorId": null,
      "articleLabel": "第一条",
      "articleNumber": "1.0",
      "formatBluebook": null,
      "formatChinese": "《中华人民共和国公司法》(2018修正)第一条",
      "lawShort": "公司法",
      "lawTitle": "中华人民共和国公司法",
      "url": "https://www.pkulaw.com/chl/aec0c211a78989e9bdfb.html?way=mcp#tiao_1",
      "versionLabel": "中华人民共和国公司法(2018修正)"
    },
    "coversArticleNumbers": [],
    "implementDate": "2018-10-26",
    "implementDateUnknown": false,
    "isCurrentAnchor": false,
    "issueDate": "2018-10-26",
    "renumbered": false,
    "text": "第一条  为了规范公司的组织和行为,保护公司、股东和债权人的合法权益,维护社会经济秩序,促进社会主义市场经济的发展,制定本法。",
    "textComparison": null,
    "textUnavailable": false,
    "versionRef": "2018修正"
  },
  "lawCitation": {
    "anchorId": null,
    "articleLabel": null,
    "articleNumber": null,
    "formatBluebook": null,
    "formatChinese": "《中华人民共和国公司法》(2023修订)",
    "lawShort": "公司法",
    "lawTitle": "中华人民共和国公司法",
    "url": "https://www.pkulaw.com/chl/8ba805acd08846d7bdfb.html",
    "versionLabel": "2023修订"
  },
  "lawTitle": "中华人民共和国公司法",
  "precededBy": null,
  "rowsDropped": 0,
  "succeededBy": null,
  "toDateBasis": "label",
  "toVersion": {
    "articleLabel": "第一条",
    "articleNumber": "1.0",
    "changeType": "modified",
    "changeTypeChinese": "修改",
    "citation": {
      "anchorId": null,
      "articleLabel": "第一条",
      "articleNumber": "1.0",
      "formatBluebook": null,
      "formatChinese": "《中华人民共和国公司法》(2023修订)第一条",
      "lawShort": "公司法",
      "lawTitle": "中华人民共和国公司法",
      "url": "https://www.pkulaw.com/chl/8ba805acd08846d7bdfb.html?way=mcp#tiao_1",
      "versionLabel": "中华人民共和国公司法(2023修订)"
    },
    "coversArticleNumbers": [],
    "implementDate": "2024-07-01",
    "implementDateUnknown": false,
    "isCurrentAnchor": true,
    "issueDate": "2023-12-29",
    "renumbered": false,
    "text": "第一条  为了规范公司的组织和行为,保护公司、股东、职工和债权人的合法权益,完善中国特色现代企业制度,弘扬企业家精神,维护社会经济秩序,促进社会主义市场经济的发展,根据宪法,制定本法。",
    "textComparison": null,
    "textUnavailable": false,
    "versionRef": "2023修订"
  }
}

Response result

Response structure

Inferred from examples
  • _metaobject
    • io.modelcontextprotocol/serverInfoobject
      • namestring
      • titlestring
      • versionstring
    • pkulaw/evidenceobject
      • confidencestring
      • notesunknown[]
      • originstring
      • retrievedAtstring
      • verifiedByApiboolean
    • uiobject
      • resourceUristring
  • contentobject[]
    • textstring
    • typestring
  • isErrorboolean
  • resultTypestring
  • structuredContentobject
    • articleLabelstring
    • articleNumberstring
    • compareStatusstring
    • diffobject
      • linesnull
      • phraseSummaryobject
        • addedPhrasesstring[]
        • caveatstring
        • heuristicChangeLevelstring
        • normativeTermsChangedunknown[]
        • removedPhrasesstring[]
        • summarystring
      • rowsnull
    • diffStatsobject
      • addedPhraseCountinteger
      • changedLineCountinteger
      • changedRowCountinteger
      • heuristicChangeLevelstring
      • heuristicChangeLevelChinesestring
      • isTextUnchangedboolean
      • normativeTermChangeCountinteger
      • removedPhraseCountinteger
    • formatstring
    • fromDateBasisstring
    • fromVersionobject
      • articleLabelstring
      • articleNumberstring
      • changeTypestring
      • changeTypeChinesestring
      • citationobject
        • anchorIdnull
        • articleLabelstring
        • articleNumberstring
        • formatBluebooknull
        • formatChinesestring
        • lawShortstring
        • lawTitlestring
        • urlstring
        • versionLabelstring
      • coversArticleNumbersunknown[]
      • implementDatestring
      • implementDateUnknownboolean
      • isCurrentAnchorboolean
      • issueDatestring
      • renumberedboolean
      • textstring
      • textComparisonnull
      • textUnavailableboolean
      • versionRefstring
    • lawCitationobject
      • anchorIdnull
      • articleLabelnull
      • articleNumbernull
      • formatBluebooknull
      • formatChinesestring
      • lawShortstring
      • lawTitlestring
      • urlstring
      • versionLabelstring
    • lawTitlestring
    • precededBynull
    • rowsDroppedinteger
    • succeededBynull
    • toDateBasisstring
    • toVersionobject
      • articleLabelstring
      • articleNumberstring
      • changeTypestring
      • changeTypeChinesestring
      • citationobject
        • anchorIdnull
        • articleLabelstring
        • articleNumberstring
        • formatBluebooknull
        • formatChinesestring
        • lawShortstring
        • lawTitlestring
        • urlstring
        • versionLabelstring
      • coversArticleNumbersunknown[]
      • implementDatestring
      • implementDateUnknownboolean
      • isCurrentAnchorboolean
      • issueDatestring
      • renumberedboolean
      • textstring
      • textComparisonnull
      • textUnavailableboolean
      • versionRefstring

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 Intelligent Legal Search — diff_article_versions with your agent

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