Lovdata Open Law Datasets (Norwegian Laws and Regulations Packs)
lovdata/list-datasets
Lists the open data packs Lovdata publishes for Norwegian law: current laws (gjeldende-lover), current central regulations (gjeldende-sentrale-forskrifter) and the Norsk Lovtidend part I archives. Each entry has the file name, a Norwegian description, the size in bytes and the time the pack was last rebuilt (packs are rebuilt nightly), so a caller can tell whether the law corpus changed. Takes no input and returns the listing only, not the law texts. Data from Stiftelsen Lovdata under NLOD 2.0, served by Eden Engine; not an official Lovdata product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Source: Lovdata (Stiftelsen Lovdata), api.lovdata.no. The open law datasets are licensed under the Norwegian Licence for Open Government Data (NLOD 2.0), which asks for attribution. Served by Eden Engine; not an official Lovdata product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "lovdata/list-datasets" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "lovdata/list-datasets" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "lovdata/list-datasets", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "lovdata/list-datasets", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 24, 2026
Input and output schemas
Input schema
{
"type": "object",
"properties": {},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"results"
],
"properties": {
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"filename",
"description",
"sizeBytes",
"lastModified"
],
"properties": {
"filename": {
"type": "string",
"description": "Archive file name, for example gjeldende-lover.tar.bz2."
},
"sizeBytes": {
"type": "string",
"description": "Archive size in bytes, as a decimal string."
},
"description": {
"type": "string",
"description": "What the pack holds, in Norwegian."
},
"lastModified": {
"type": "string",
"description": "When the pack was last rebuilt, ISO 8601 UTC."
}
},
"additionalProperties": true
},
"description": "One entry per open data pack."
}
},
"description": "The data packs Lovdata lists, in the order the API returns them.",
"additionalProperties": false
}