Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

The EU data catalogue

The catalogue gives away what makes us citable: 32 acts and 1 798 articles with address, identity, reading date, hash and a ready citation string. Four files under the same terms as the rest of the open layer, no key, no rate limit, never a payment demand. The article text itself is not included.

Share this page

NovaCopilot · ExploreWorld Legal

European and Nordic law as verifiable data, with source, reading date and checksum on every row.

Publisher
NovaCopilot, ExploreWorld Legal
Corpus version
legal-2026-10-02
Read at
2026-08-31
Freshness
84/100

Four files

  • /api/public/v1/open/eu, the catalogue: which surfaces exist, the terms and the corpus version.
  • /api/public/v1/open/eu/acts, every act: id, title, short name, CELEX, address, reading date, hash and article count.
  • /api/public/v1/open/eu/articles, the articles: act, number, heading, address, reading date and hash, paginated with limit and offset.
  • /api/public/v1/open/eu/citations, a ready citation string per act and article, with canonical link and reading date.
  • /api/public/v1/open/eu/freshness, the freshness index per act and for the EU layer as a whole.

How to fetch without wasting calls

  • Every response carries ETag and Last-Modified. Send If-None-Match and we answer 304 when nothing changed.
  • The x-next-check header says when it is worth coming back. The catalogue updates daily.
  • OPTIONS answers 204 with CORS, so a browser client can read the files directly.

The boundary, stated

  • Free: address, act, article number, heading, reading date, hash, citation string and freshness.
  • Priced: the article text, the reasoning answers, bulk extraction and the agent surfaces.
  • Terms: use, cite, index and cache. No resale of the dataset as such. Attribution: Source: NovaCopilot with the canonical URL.

EU rules and EU data

  • The AI Act in practice

    The regulation sorts systems by risk and puts the requirements on roles, not on companies. The same company can be a provider in one system and a deployer in another. This page goes through the roles, the requirements and the dates, and every row points at the article in the register.

  • Data protection in the EU

    Data protection rests on three questions that return in every audit: who decides the purpose, where does the data end up, and who supervises. This page goes through all three, with a path to the articles in the register.

  • Data and data governance in the EU

    The two acts treat the same matter from opposite ends: the Data Act decides who gets data out of a product or a service, the Data Governance Act organises sharing where data is not free. This page goes through the duties and the roles.

  • Cybersecurity in the EU

    Three regimes reach the same company from different directions. NIS2 addresses the entity, DORA the financial sector and its IT suppliers, the Cyber Resilience Act the product. This page separates them so the right duty lands on the right desk.

  • Sustainability in EU law

    The sustainability rules connect in three steps: the taxonomy defines what counts, reporting requires it to be disclosed, and due diligence requires something to be done about what is disclosed. This page takes the steps one at a time.

  • Digital services and digital markets

    The two acts split the work: the DSA is about what happens inside the service, the DMA about what happens in the market around it. This page goes through the duties on both sides and points at the articles in the register.

  • Copyright and AI in the EU

    Training on protected material is lawful in the EU under an exception, not without conditions. This page collects the three rules that settle the question: the text and data mining exception, the reservation a rightholder may make, and the obligations the AI Act places on anyone releasing a general-purpose model.

  • Product safety and liability

    When software becomes part of the product, liability moves with it. Three frameworks govern the question in the EU: the general product safety regulation, the machinery regulation for machines with control systems, and the revised product liability directive, which expressly counts software as a product.

  • Digital consumer protection

    Selling digital content or a digital service to consumers in the EU means meeting four layers: contract law in the digital content and sale of goods directives, the information duties of the consumer rights directive, the ban on unfair practices, and the specific design rules in the Digital Services Act.

  • Procuring AI

    A public body buying AI is usually a deployer under the AI Act, sometimes a provider. That difference decides the requirements. This page sets out what belongs in the tender, which clauses are commonly used, and which evidence can actually be checked.

  • Market surveillance and CE marking

    Rules mean little without someone testing them. The market surveillance regulation gives authorities their powers, notified bodies handle assessment in some cases, and the penalty rules decide what a failure costs. This page sets out the chain.

  • The timeline

    The hard part of EU law is rarely what applies, but when. Entry into force and application are two different things, and several acts arrive in stages. This page gathers the dates that drive planning and links to the act behind each line.

  • EU recitals as open data

    Recitals explain why an article reads the way it does, and they are cited daily in questions of interpretation. Here they sit as an open surface: every recital has a number, a heading, an address, a hash and a reading date, enough to cite correctly and to notice when something changed.

  • EU timelines as open data

    A requirement that does not apply yet is planned differently from one that applies today. This surface gives the dates: when each part of an act starts to apply, which article carries the date, and where it is published.

  • EU obligations as open data

    The same act places different duties on different roles. This surface makes that searchable: each row is one duty, tied to a role, an act and an article, with the address where the requirement is published.

The NovaCopilot models

The decision model

In: A role, a legal act and the situation in plain words.

Out: The obligations that reach the role, the article behind them and what remains.

When: When the question is whether a requirement applies to you, and why.

The difference model

In: A checksum already used and the date of the last reading.

Out: What changed since then: checksum, reading date, passed deadline and rows to revisit.

When: When earlier work is reused and has to be checked first.

The obligation model

In: A legal act or an article, with or without a role filter.

Out: The obligation in the register's wording, the role it reaches, canonical address and reading date.

When: When the answer has to be citable article by article.

Example for an agent

curl -s "https://legal.exploreworldai.com/novacopilot/eu-data?format=agent"
  • canonical, the address to cite
  • node_hash, the checksum for the next comparison
  • corpus_version, the corpus version that answered
  • freshness.read_at, the reading date of the row
  • freshness.next_check, when a new check is reasonable
  • citation.string, the finished citation
  • agent.receipt, the receipt of the call, without a key

Metadata

Canonical address
https://legal.exploreworldai.com/novacopilot/eu-data
Layer
index
Read at
2026-08-31
Freshness
84/100
Checksum
b62b210ce6ad5881
Corpus version
legal-2026-10-02
Next check
-
License
https://legal.exploreworldai.com/revision

How to cite this page

NovaCopilot (ExploreWorld Legal, Valkiv Ventures AB), https://legal.exploreworldai.com/novacopilot/eu-data, read 2026-08-31, checksum b62b210ce6ad5881, corpus version legal-2026-10-02, license https://legal.exploreworldai.com/revision

Owner
Valkiv Ventures AB
License
https://legal.exploreworldai.com/revision
Checksum
b62b210ce6ad5881
Fingerprint
ewai:eu:108865
Terms
Use, cite, index and cache. The register as such is not resold.

Source registers

The same material as registers, with read date and source on every row.

Édition française

FAQ

Do I need a key?
No. The four files are open and never return a payment demand. A key is needed only for article text, reasoning and agent surfaces.
How fresh is the data?
The EU layer was re-read on 2026-08-31. Every row carries its own reading date and the freshness file shows the index per act.
May I use the catalogue commercially?
Yes. Use, cite, index and cache are permitted, including in commercial products. The only restriction is resale of the dataset as such.

Next step

Three ways to put the register to work in your own practice.

Start with your task