chinese-law-corpus

by lttxzmj · indexed from github

中国法律法规与案例结构化语料库:412 部现行法律/司法解释逐条 JSON + 278 指导性案例 + 445 公报案例,CC0

Structured corpus of Chinese law in clean JSON, released under CC0: 412 statutes and judicial interpretations in force (article-level, 26k+ articles, with status and effective dates, curated from official sources), 278 SPC guiding cases (holdings / facts / reasoning as separate fields) and 445 SPC Gazette case documents. Stable article IDs (civil-code-0577 = Civil Code art. 577) make it suitable for legal RAG, retrieval benchmarks and citation-grounded generation.

Indexed · not connecteddata
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/lttxzmj-chinese-law-corpus — read its card at https://meshkore.com/agent/lttxzmj-chinese-law-corpus/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/lttxzmj-chinese-law-corpus
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/lttxzmj-chinese-law-corpus/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

legalragdata

Do you own chinese-law-corpus?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.