OpenChainGraph Suite · ART-354 · UNCITRAL MLETR · Trade Finance

MLETR Jurisdiction-Adoption Lookup

Pick an origin and destination jurisdiction and look up the UNCITRAL MLETR (Model Law on Electronic Transferable Records) adoption status for each — statute, scope, and effective date, cited and data_version stamped — plus a corridor verdict for whether an electronic bill of lading (eBL) is legally effective end-to-end across that corridor. Static citation table, update-on-touch, not live data. Answers the "is an eBL faster paper in corridor X→Y" practitioner question that sits upstream of the MLETR control-evidence chain (OpenChainGraph Suite).

UNCITRAL MLETR Static Citation Table Corridor Verdict Not Legal Advice
🔒 All lookup runs locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Corridor
Jurisdiction where the eBL originates (e.g. the shipper's jurisdiction).
Jurisdiction where the eBL is presented (e.g. the consignee/bank's jurisdiction).
Origin jurisdiction
Destination jurisdiction
Data version
data_version
Execution Hash (SHA-256)

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `lookup_mletr_jurisdiction_adoption`. Task: Static citation-table lookup of UNCITRAL MLETR (Model Law on Electronic Transferable Records) adoption status per jurisdiction -- statute, scope, and effective date, data_version stamped -- and a corridor verdict for whether an electronic bill of lading (eBL) is legally effective end-to-end between an origin and destination jurisdiction (UK, Singapore, UAE, Bahrain, France, Japan, India, US, Germany at this data_version).
Call it with arguments: {"policy_parameters":{"origin_jurisdiction":"UK","destination_jurisdiction":"Singapore"}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-354-mletr-jurisdiction-adoption-lookup.html#p=v1.H4sIAAAAAAAA_wFDALz_eyJvcmlnaW5fanVyaXNkaWN0aW9uIjoiVUsiLCJkZXN0aW5hdGlvbl9qdXJpc2RpY3Rpb24iOiJTaW5nYXBvcmUifRJdbcZDAAAA