Based on ESCO — European Skills & Occupations taxonomy

EU skills,
made practical.

Translate European occupational data into step-by-step learning routes and concrete work cards — written at B1 level, ready to use on the work floor.

openeyou.eu/routes/route-foundation-bicycle
Bicycle mechanic

Foundation Bicycle Mechanics

BeginnerB1Published
Block 1
Safety & Workspace1 card
Block 2
Tyre & Tube Repairs2 cards
Block 3
Brake Systems2 cards
Block 4
Drivetrain Maintenance1 card
10
occupations
3
routes
12
work cards
96
steps
5
languages

Browse by sector

Occupations classified using ESCO and ISCO codes, covering trades across the EU.

How it works

From raw ESCO data to practical, validated work cards in three steps.

1

ESCO data import

An occupation and its essential skills are imported from the ESCO REST API. Each occupation brings its full skill profile — essential and optional.

2

AI generates routes & cards

Claude AI groups skills into logical learning blocks and writes a work card per skill — at B1 level, with steps, safety notes and evidence requirements.

3

Human review & publish

Every AI-generated card is reviewed by a subject expert before publishing. Status: ai_generated → in_review → validated → published.

Open EYou

The route map

What does someone need to learn? What steps are involved? What should a supervisor check?

  • + Occupations and skills from ESCO
  • + Practical learning routes
  • + Work cards — step by step
  • + Open REST API
  • + NL · DE · FR · AR + more
Bloeiindex

The evidence file

A learner completed this work card. A supervisor checked off the steps. Evidence was added. Hours were registered.

  • + Check off steps with a supervisor
  • + Attach evidence (photo, document)
  • + Register hours per work card
  • + Build a personal practical declaration
bloeiindex.nl →

REST API

All data available via a REST API. Add ?language=nl or set the Accept-Language header for translations.

Supported: ennldefrarplesit

GET/api/v1/occupations
GET/api/v1/occupations/:id
GET/api/v1/routes
GET/api/v1/routes/:id
GET/api/v1/work-cards/:id
GET/api/v1/search?q=electrician

No API key required in development. Set API_SECRET_KEY in production to require authentication via x-api-key header.