Follow a procurement

Public procurement is published at every step, but the steps sit in separate registers. Asked as one question, the notice that opened a tender, the contract that closed it and the payments that followed line up as a single story.

Ask your agent

Show me the contracts my municipality awarded this year over 50,000 euro, and what has actually been paid against them.

How it answers.

The model picks the tools and the order itself. This is the path it takes, and the tools are named as they go over the wire. Each one is in the catalogue, with its arguments and an example it ships with.

  1. Find the contracting authority

    The authority is the thread every later step hangs on. One search fixes which municipality, ministry or agency the rest of the answer is about.

    kimdis_search_organizations

  2. Start at the tender

    The notice says what was asked for, under which procedure and for how much: the estimate an award is later measured against.

    kimdis_search_notices

  3. Take the award

    Who won, for what sum, and under which CPV. Filtering by authority, date and value is the whole of most procurement questions.

    kimdis_search_contracts

  4. Then what was paid

    An award is a promise; the payment register is what happened. The gap between the two is usually the point of the question.

    kimdis_search_payments

The registries behind it.

Official publishers, unmodified. Each answer carries the licence and the attribution its registry asks for, and every tool above is listed on the source's own page.

KIMDISDiavgeia

Ask it yourself.

Connect your clientOne command or one config entry, then ask in your own words.Try a call in the browserPick a tool, edit the arguments, read the real response.