Dixit

List what Dixit tracks against one registered stakeholder. One caveat to pass on whenever you report `amendment` results: the link between an amendment and an interest representative is a correspondence **computed by Dixit**, not something either party declared. Attribute it as Dixit's assessment, never as a matter of record. Results come back as entities carrying their numeric `id` and `type`, which you can pass to get_entity for the full record. They come newest-first. An anchor with nothing attached is an empty page, not an error. Pick what to list with `entity_type`, one kind per call: - `amendment`: a single amendment tabled on a text. - `communication`: an institutional or lobbying communication (a press release, position paper…). - `consultation_response`: a contribution to a public consultation (consultation publique) — a response, a lobbying input. - `initiative`: a European Commission initiative (a legislative dossier / text). - `lobbying_activity`: a lobbying activity declared to a transparency register (the HATVP), tied to one reporting exercise.

list_entities_by_stakeholder

List what Dixit tracks against one politician or official. `entity_type="mandate"` lists the offices they hold or have held, and `entity_type="vote"` the recorded votes (scrutins publics) they took part in. Neither can be fetched with get_entity -- what this list returns is all of them Dixit exposes. Everything else is listed on attachment alone, and the capacity is not exposed here: an `amendment` comes back whether they authored or cosigned it, a `document` in whatever capacity they are attached in, and a `procedure` on authorship, cosignature or any of its rapporteur functions. So this answers "what has this person been involved in", never "what is this person rapporteur on" — reporting someone as rapporteur on the strength of this list is an invention, and only a `procedure` has a rapporteur to report at all. Results come back as entities carrying their numeric `id` and `type`, which you can pass to get_entity for the full record — except `mandate` and `vote`, which get_entity does not serve, so for these the entity returned here is everything Dixit exposes. Dated kinds come newest-first; the undated ones (`mandate`, `organ`) in their own fixed order. An anchor with nothing attached is an empty page, not an error. Pick what to list with `entity_type`, one kind per call: - `amendment`: a single amendment tabled on a text. - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `mandate`: one seat or office a person holds in a body — the function, the body, the period and whether it is still active. A person's full set of these is their mandate history. - `organ`: a political body (a committee/commission, an assembly, a directorate-general, a comitology body…). - `procedure`: a legislative procedure — the dossier législatif following one text through both French chambers (navette included), or an EU procedure as tracked in the Parliament's legislative observatory (OEIL). - `question`: a parliamentary written or oral question (question écrite, question au gouvernement). - `speech`: a single speech (intervention) in a parliamentary debate, in séance or commission, with its speaker. - `vote`: a recorded vote (scrutin public) and how it divided — the for, against and abstention counts. Not every division is recorded, so an absence here is not an absence of a vote.

list_entities_by_person

Fetch full detail for a single Dixit entity. Pass the `entity_type` and numeric `entity_id` of a result returned by the search tools — for example `entity_type="procedure", entity_id=512`. Returns the human-readable essentials (title, description, `resource` link for citation) plus the small per-type set of extra fields, or, with `response_format="full"`, the text itself: its pages, sections, articles, or a transcript's speeches, in reading order. Supported types: - `agenda`: a meeting agenda (ordre du jour). - `amendment`: a single amendment tabled on a text. - `communication`: an institutional or lobbying communication (a press release, position paper…). - `consultation_response`: a contribution to a public consultation (consultation publique) — a response, a lobbying input. - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `initiative`: a European Commission initiative (a legislative dossier / text). - `legal_act`: a published legal act (a French act published in the Journal officiel — JO/JORF — or an EU act). - `lobbying_activity`: a lobbying activity declared to a transparency register (the HATVP), tied to one reporting exercise. - `meeting`: a meeting (séance publique, réunion de commission, comitology meeting…). - `organ`: a political body (a committee/commission, an assembly, a directorate-general, a comitology body…). - `person`: a politician or official Dixit tracks (député, sénateur, MEP, ministre, senior civil servant…). - `procedure`: a legislative procedure — the dossier législatif following one text through both French chambers (navette included), or an EU procedure as tracked in the Parliament's legislative observatory (OEIL). - `question`: a parliamentary written or oral question (question écrite, question au gouvernement). - `social_post`: a social-media post by a tracked politician or official. - `speech`: a single speech (intervention) in a parliamentary debate, in séance or commission, with its speaker. - `stakeholder`: an interest representative (représentant d'intérêts) listed on a lobbying transparency register — the HATVP or the EU Transparency Register. - `transcript`: the minutes / verbatim record of a meeting (compte rendu).

get_entity

List the entities delivered in one of your keyword alerts (for policy briefs). Returns each entity Dixit delivered for that alert, with the date it was sent, ready to fetch in full with get_entity. Only keyword alerts deliver items here: the ids of the other alert kinds list_alerts returns are not accepted. Each call lists one delivered kind, so call once per kind — the alert's `counts` in list_alerts say which kinds hold anything. Results are newest-first by send date, with the items not sent yet first when `sent_only=false`. Accepted kinds: - `agenda`: a meeting agenda (ordre du jour). - `amendment`: a single amendment tabled on a text. - `communication`: an institutional or lobbying communication (a press release, position paper…). - `consultation_response`: a contribution to a public consultation (consultation publique) — a response, a lobbying input. - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `initiative`: a European Commission initiative (a legislative dossier / text). - `legal_act`: a published legal act (a French act published in the Journal officiel — JO/JORF — or an EU act). - `lobbying_activity`: a lobbying activity declared to a transparency register (the HATVP), tied to one reporting exercise. - `meeting`: a meeting (séance publique, réunion de commission, comitology meeting…). - `procedure`: a legislative procedure — the dossier législatif following one text through both French chambers (navette included), or an EU procedure as tracked in the Parliament's legislative observatory (OEIL). - `question`: a parliamentary written or oral question (question écrite, question au gouvernement). - `social_post`: a social-media post by a tracked politician or official. - `speech`: a single speech (intervention) in a parliamentary debate, in séance or commission, with its speaker. - `transcript`: the minutes / verbatim record of a meeting (compte rendu).

list_entities_from_alert

List your alerts (in French: une alerte, une veille) across every alert type. Returns each alert as an entity: `type` is the alert kind, `id` its numeric id, `title` its name (keyword alerts) or the watched subject (the others), and `attributes` its `frequency` plus, for keyword alerts, delivered-item `counts` by kind. Keyword alerts come first, then the follows of a procedure, body, person or initiative, then the follows of a single amendment, question or meeting — newest first within each. Pass a `keyword_alert`'s `id` to list_entities_from_alert to retrieve the items delivered in it — only keyword alerts deliver items there, so the other kinds' ids are not accepted. Alert kinds: - `amendment_alert`: an alert watching the amendments tabled on a text. - `initiative_alert`: an alert watching a European Commission initiative. - `keyword_alert`: a saved keyword search that delivers matching items (in French: une alerte, une veille). - `meeting_alert`: an alert watching a meeting and its transcript. - `organ_alert`: an alert watching a political body's activity. - `person_alert`: an alert watching a politician or official's activity. - `procedure_alert`: an alert watching a legislative procedure, French or EU. - `question_alert`: an alert watching a parliamentary question and its answer.

list_alerts

List what Dixit tracks against one legislative initiative. This is the way to enumerate a consultation's responses. A free-text search finds only the responses whose words match its query, so a count taken from search results understates them badly — where the initiative's own `contribution_count` disagrees with what you have gathered, this list is the one to trust and that count is the total to page towards. Consultation responses are EU records, so a caller entitled only to France gets an empty page here rather than an error. Results come back as entities carrying their numeric `id` and `type`, which you can pass to get_entity for the full record. They come newest-first. An anchor with nothing attached is an empty page, not an error. Pick what to list with `entity_type`, one kind per call: - `consultation_response`: a contribution to a public consultation (consultation publique) — a response, a lobbying input.

list_entities_by_initiative

Search Dixit's tracked European and French entities by free text. One search covers one region, the one `scope` names: to cover a question spanning both, search each in turn and say which region each result came from. Search in the language the sources are written in — largely English for the European sources and French for the French sources. Matching is lexical, with no translation step, so a term rendered into another language searches for words that are not in the text and comes back empty on a subject Dixit covers well. Keep the caller's own wording in the query, and translate only in the answer you write back. A French question carries French terms of art, and those are what the French corpus holds: search navette, projet de loi, saisine, question écrite — never "shuttle", "bill", "referral". Returns the matching entities, each with its `type` and numeric `id` (pass both to `get_entity` for the full record). Some kinds exist in one region only: `agenda`, `consultation_response`, `initiative` only in the European sources (`scope="eu"`). A `person` search finds members of the Assemblée nationale and the Sénat (`fr`) and of the European Parliament (`eu`); an `initiative` search finds delegated and implementing acts. To list what hangs off one entity you already have the id of — a person's amendments, a committee's documents, a procedure's amendments — use the list_entities_by_person / _organ / _procedure / _stakeholder / _initiative tools instead of searching. Dated kinds: - `agenda`: a meeting agenda (ordre du jour). - `amendment`: a single amendment tabled on a text. - `communication`: an institutional or lobbying communication (a press release, position paper…). - `consultation_response`: a contribution to a public consultation (consultation publique) — a response, a lobbying input. - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `initiative`: a European Commission initiative (a legislative dossier / text). - `legal_act`: a published legal act (a French act published in the Journal officiel — JO/JORF — or an EU act). - `lobbying_activity`: a lobbying activity declared to a transparency register (the HATVP), tied to one reporting exercise. - `meeting`: a meeting (séance publique, réunion de commission, comitology meeting…). - `procedure`: a legislative procedure — the dossier législatif following one text through both French chambers (navette included), or an EU procedure as tracked in the Parliament's legislative observatory (OEIL). - `question`: a parliamentary written or oral question (question écrite, question au gouvernement). - `speech`: a single speech (intervention) in a parliamentary debate, in séance or commission, with its speaker. - `transcript`: the minutes / verbatim record of a meeting (compte rendu). Reference kinds: - `organ`: a political body (a committee/commission, an assembly, a directorate-general, a comitology body…). - `person`: a politician or official Dixit tracks (député, sénateur, MEP, ministre, senior civil servant…). - `stakeholder`: an interest representative (représentant d'intérêts) listed on a lobbying transparency register — the HATVP or the EU Transparency Register.

search_entities

List what Dixit tracks against one legislative procedure. One procedure is the whole dossier législatif, navette included, so its `document` and `amendment` lists span every reading in both chambers rather than one stage — a text's readings are not separate procedures to be gathered. It must be a `procedure`: an `initiative` is the European Commission's own dossier, a different kind of record, and passing its id here returns an empty page rather than its documents. Results come back as entities carrying their numeric `id` and `type`, which you can pass to get_entity for the full record — except `vote`, which get_entity does not serve, so for this the entity returned here is everything Dixit exposes. They come newest-first. An anchor with nothing attached is an empty page, not an error. Pick what to list with `entity_type`, one kind per call: - `amendment`: a single amendment tabled on a text. - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `meeting`: a meeting (séance publique, réunion de commission, comitology meeting…). - `vote`: a recorded vote (scrutin public) and how it divided — the for, against and abstention counts. Not every division is recorded, so an absence here is not an absence of a vote.

list_entities_by_procedure

List what Dixit tracks against one political organ. Two different relations are covered, depending on the kind: a `document`, `agenda`, `meeting`, `transcript`, `speech`, `legal_act`, `communication` or `initiative` is listed when it belongs to the organ, while an `amendment`, `question`, `procedure` or `person` is listed when the organ is the committee seized (saisie) — the filter does not separate saisine au fond from saisine pour avis, so both come back together and neither can be reported as one or the other. `entity_type="organ"` reads the hierarchy instead, listing the bodies that sit under a directorate-general — so it answers for a DG and comes back empty for a committee. Results come back as entities carrying their numeric `id` and `type`, which you can pass to get_entity for the full record — except `mandate`, which get_entity does not serve, so for this the entity returned here is everything Dixit exposes. Dated kinds come newest-first; the undated ones (`mandate`, `organ`, `person`) in their own fixed order, people by name. An anchor with nothing attached is an empty page, not an error. Pick what to list with `entity_type`, one kind per call: - `agenda`: a meeting agenda (ordre du jour). - `amendment`: a single amendment tabled on a text. - `communication`: an institutional or lobbying communication (a press release, position paper…). - `document`: a legislative document (a bill — projet de loi/PJL or proposition de loi/PPL —, a report/rapport, an annex…). - `initiative`: a European Commission initiative (a legislative dossier / text). - `legal_act`: a published legal act (a French act published in the Journal officiel — JO/JORF — or an EU act). - `mandate`: one seat or office a person holds in a body — the function, the body, the period and whether it is still active. A person's full set of these is their mandate history. - `meeting`: a meeting (séance publique, réunion de commission, comitology meeting…). - `organ`: a political body (a committee/commission, an assembly, a directorate-general, a comitology body…). - `person`: a politician or official Dixit tracks (député, sénateur, MEP, ministre, senior civil servant…). - `procedure`: a legislative procedure — the dossier législatif following one text through both French chambers (navette included), or an EU procedure as tracked in the Parliament's legislative observatory (OEIL). - `question`: a parliamentary written or oral question (question écrite, question au gouvernement). - `speech`: a single speech (intervention) in a parliamentary debate, in séance or commission, with its speaker. - `transcript`: the minutes / verbatim record of a meeting (compte rendu).

list_entities_by_organ