EUR-Lex (EU law, consolidated)
Reads named EU acts from EUR-Lex in their latest consolidated version: the text that applies today, with every amendment folded in. The Publications Office’s public SPARQL endpoint says which consolidation is newest; an act is read again only when a new one appears.
At a glance
Section titled “At a glance”| Collector | EUR-Lex (EU law, consolidated), version 1.0.0 |
|---|---|
| Reads | Publications Office of the European Union: EUR-Lex and the Cellar SPARQL endpoint (the vendor's documentation) |
| Family | Regulation |
| Kind | Regulation |
| Ways to connect | None (no credential) |
| Scopes |
|
| Read only | Yes |
| Vendor's API can move money | No |
| Personal data | None |
| Hosts it may contact | publications.europa.eu, eur-lex.europa.eu |
| Vendor API versions | Cellar SPARQL 1.1 (CDM ontology), EUR-Lex legal-content HTML |
| Lowest engine version | 0.45.0 |
What it reads
Section titled “What it reads”- The acts you name by CELEX number (for example
32012R0965, the EU air operations regulation). - For each act: the full text of its newest consolidated version, in the language you choose (English by default), with its title, its date and a link to it on eur-lex.europa.eu. An act that has never been consolidated is read as adopted.
How to connect
Section titled “How to connect”- In LightHouse, open Connectors and choose EUR-Lex.
- Name the acts by CELEX number. EUR-Lex shows it on every act’s page.
- Choose a language (a two-letter code,
ENby default), a label (normallyregulation) and how often to read. A daily or weekly read costs one query when nothing has changed.
No credential is needed.
Permissions
Section titled “Permissions”None. The collector sends only GET requests, without credentials, to
publications.europa.eu (the SPARQL query, sent as a GET) and
eur-lex.europa.eu (the text). Its read-only test proves it on every
change, and the certification run recorded every request it made against
the live services.
Limits
Section titled “Limits”- The consolidated text is the Publications Office’s convenience version, not the authentic text published in the Official Journal. Each record says so in its metadata, and an answer that quotes it can say so too.
- Each act is one document, however long: the consolidated air operations regulation is over a million characters.
- Requests are paced (one second apart by default) and back off when the
service asks (
Retry-After).
Data handling
Section titled “Data handling”- The text is public: © European Union, reused under Commission Decision 2011/833/EU. It carries no personal data.
- The raw HTML is cached in your deployment, named by its SHA-256, so any passage can be traced to what was served.
- Nothing leaves your deployment: the collector runs inside it, and only the counts of acts read reach LightHouse.
Troubleshooting
Section titled “Troubleshooting”| What you see | What it means | What to do |
|---|---|---|
not CELEX numbers of acts |
A number is not an act’s CELEX number | Copy it from the act’s EUR-Lex page, for example 32018R1139 |
not a language code |
The language is not two capital letters | Use EN, FR, DE and so on |
HTTPStatusError 503 |
EUR-Lex or the SPARQL endpoint is busy | It retries by itself; read again later |
| Read succeeded, 0 written | No act has a newer consolidation since the last read | Nothing to do |
Certification
Section titled “Certification”Each entry is a run by Atlantic Agentic Labs, newest first. Only a run against the vendor’s sandbox or a client environment certifies a collector; a certification lasts six months, or less if the vendor publishes an API version the collector does not list. See How collectors are certified.
| Date | Collector | Engine | Vendor API | Method | Expires |
|---|---|---|---|---|---|
| 7 November 2026 | 1.0.0 | 0.45.0 | Cellar SPARQL 1.1 (CDM ontology); EUR-Lex legal-content HTML | Vendor's sandbox (a real run) | 7 May 2027 |
| 7 November 2026 | 1.0.0 | 0.45.0 | Cellar SPARQL 1.1 (CDM ontology); EUR-Lex legal-content HTML | Fixtures only: built, not certified | Not applicable |
Security posture
Section titled “Security posture”From the collector’s last scan on the default branch. What each line means, and what blocks a release: Security posture.
| Last scanned | 10 November 2026 |
|---|---|
| Critical findings | 0 |
| High findings | 0 |
| Medium findings | 0 |
| Low findings | 0 |
| Info findings | 0 |
| Release blocked | No |
| Network allow-list check | Pass |
| Read-only behavioural test | Pass |
| SBOM (CycloneDX) | Produced |
| Dependency licences | Pass |
| Scanners | bandit 1.9.4, semgrep 1.181.1, pip-audit 2.10.1, osv-scanner 2.7.0, cyclonedx-py 7.5.0, pip-licenses 5.5.5, gitleaks repository job aal-secrets, hosts_check tools/hosts_check.py, read-only test pytest -m read_only |