Repère
AGEC · REP · ADEME register

Check a supplier's REP registration. Keep the proof.

One call tells you what the official ADEME register says about a French supplier — which streams, which identifier, on which date. We keep that answer dated, so you can still produce it for an auditor next year.

Check the register for a supplier now — free, no account.

No identifier to hand? Start from the company name.

3 free checks per connection in any 24 hours. A name search counts as one of them, and reading the company you then pick counts as another. What you enter is sent in the form, never in the page address.

No credit card. Cancel any month. Built on the official ADEME open data, cited in every response.

DECATHLON 500 569 405 03239
Electrical & electronic (EEE) Registered
Household packaging (EMB) Registered
Tyres (PNEU) Not in the register
Observed 2026-09-28 · ADEME / SYDEREP · archived, so you can cite it later
Why Repère

What a one-off lookup will not give you

Anyone can read today's register. What you need on audit day is what it said back then — and to hear about it the morning a supplier drops off it.

Evidence you can still produce in two years

ADEME publishes today's register and nothing else: a withdrawn registration is deleted from it. We take a dated snapshot every day, so you can show what the register said in March — which nobody can reconstruct after the fact.

You hear about a withdrawal before your auditor does

A supplier losing their IDU is the one event that leaves you exposed. We compare every snapshot and raise it the morning it happens, by webhook or by email.

No guesses dressed up as answers

Foreign producers have no SIRET. When a name match is ambiguous we hand you ranked candidates and say so, rather than picking one and letting you discover it later.

For your developers

One endpoint. That is the whole integration.

A REST call in, a dated record out. No SDK to adopt, no portal for your team to log into, no monthly file to import by hand.

# Ask about a SIRET
curl -X POST https://repere.tech/v1/verify \
  -H "X-API-Key: *** \
  -d '{"siret": "50056940503239"}'

# Get back what the register said, and when
{
  "query":    { "siret": "50056940503239" },
  "observed_at": "2026-09-28T06:00:00Z",
  "source":   "ADEME / SYDEREP",
  "findings": [
    { "filiere": "EEE", "status": "found_active",
      "identifiant_unique": "FR...", "raison_sociale": "DECATHLON" },
    { "filiere": "PNEU", "status": "not_found" }
  ]
}

No compliant: true anywhere in that response — and there never will be. Compliance is a legal conclusion; we give you the facts it rests on.

Monitoring

Know the morning a supplier drops off the register

Register the suppliers you buy from once. Every morning we compare the new register against yesterday's and raise an event for anything that moved — so a registration that lapses quietly does not stay quiet.

1

1. Register your suppliers

POST /v1/watch with a SIRET or SIREN, optionally narrowed to the REP streams you care about. Free to create, and listing or cancelling a watch never costs a call.

2

2. We diff the register daily

ADEME refreshes around 05:30 UTC; we snapshot after that and diff only your watched suppliers. A withdrawal is matched against the separate withdrawn register, so the event carries the end date and the motive.

3

3. You read the events

GET /v1/events returns the changes on your suppliers, newest first, each stamped with the two snapshots it was detected between. One real change is one event, even if a job retries.

What raises an event

  • Withdrawn — the IDU left the active register and a withdrawal was published, with its date and motive.
  • Disappeared — the registration is gone with no withdrawal record, so the source states no reason. Reported as what it is rather than guessed at.
  • Registered — a new active IDU, so you can tell when a supplier has put things right.

Pushed to you, or polled

Register a destination and every event is pushed to it: an HTTPS webhook signed with HMAC-SHA256 so you can prove it came from us, or a plain-text email. Polling GET /v1/events keeps working either way — push is an addition, never the only copy. GET /v1/destinations shows you whether delivery is actually succeeding, including the last error, so a silently broken endpoint is visible to you rather than only to us.

Suppliers you can monitor

Monitoring is included in every plan up to a ceiling: free 5, starter 100, growth 1 000, scale 10 000. GET /v1/watch always tells you how much headroom is left.

What we do not promise

Detection is daily, not real-time — the source only changes daily, so a faster poll would just re-read yesterday's file. Delivery is best-effort with retries: we attempt a webhook 5 times over about 2 h 36 min, then park it and keep the event readable on the API, so a missed push is never a lost event. And monitoring needs a SIRET or SIREN: we refuse name-only watches, because matching a name is a guess and a guess raises false alarms.

See the events API

The obligation behind it

The AGEC obligation, in one API call

Article L. 541-10-13 du Code de l'environnement requires every producer to hold a unique identifier (IDU) for each REP stream. When one of your suppliers lets theirs lapse, the exposure lands on you — quietly, and usually at the worst moment. Repère turns that into one call and a record you can file.

Check your first supplier today

Create an account, get a key, make the call. Nothing to install, no card to enter, and the free allowance is enough to wire Repère into your own systems before you decide.