For agents and developers

This page describes Attendit so that programs and AI agents can read it. It is the documentation for anyone who submits a tender on behalf of a person.

What we do

We sum up a tender on 1 to 2 pages: the documents and declarations to submit, the deadlines, and the award criteria with weights. Each item has a quote, a section and a page. Free of charge, in 1 working day, by email. A reading aid, not legal advice. The contracting authority's documents prevail.

Format of the summary

The summary arrives as text by email. Its structure is described in a JSON schema. The example is invented and shows the target format (draft). It is derived from the typed findings of the pipeline. Here is an excerpt:

{
  "required_documents": [
    {
      "id": "d2",
      "title": {
        "de": "Gewerbeberechtigung nachweisen",
        "en": "Prove the trade licence"
      },
      "quote_de": "Der Bieter hat die erforderliche Gewerbeberechtigung durch einen Auszug aus dem Gewerberegister nachzuweisen. Der Auszug darf nicht älter als drei Monate sein.",
      "translation_en": "The bidder must prove the required trade licence with an extract from the trade register. The extract must not be older than three months.",
      "source": {
        "section": {
          "de": "Eignung",
          "en": "Suitability"
        },
        "page": 8
      },
      "when": {
        "de": "auf Aufforderung",
        "en": "on request"
      }
    }
  ],
  "deadlines": [
    {
      "id": "f2",
      "title": {
        "de": "Ende der Angebotsfrist",
        "en": "Bid deadline"
      },
      "when": {
        "de": "12.03.2027, 10.00 Uhr",
        "en": "12 Mar 2027, 10:00"
      },
      "quote_de": "Das Angebot muss bis 12.03.2027, 10.00 Uhr im Vergabeportal einlangen.",
      "translation_en": "The bid must arrive in the procurement portal by 12 Mar 2027, 10:00.",
      "source": {
        "section": {
          "de": "Angebotsbestimmungen",
          "en": "Bid rules"
        },
        "page": 14
      },
      "iso": "2027-03-12T10:00"
    }
  ],
  "award_criteria": [
    {
      "id": "a1",
      "name": {
        "de": "Preis",
        "en": "Price"
      },
      "weight_percent": 70,
      "quote_de": "Preis: 70 Prozent",
      "translation_en": "Price: 70 percent",
      "source": {
        "section": {
          "de": "Zuschlagskriterien",
          "en": "Award criteria"
        },
        "page": 15
      }
    }
  ]
}

• Example as JSON (invented)
• JSON schema
• Example as a page

How an agent requests a summary

1. The person the agent acts for reads the privacy notice and gives the consent themselves. The box stays empty without their instruction.
2. The agent opens the form (link below) and fills it in with the details in the table. Without the form, an email with the link to the tender also works.
3. The summary arrives by email at the address given.

Form: Request a summary. Email: [email protected].

Rules for agents

• Only the person gives the consent.
• Send only documents the person may pass on. No drafts of their own bid, no internal files.
• Do not quote a price. There is none.
• Do not state numbers on speed or accuracy that are not on this page.
• The data is processed in the EU.

Connections: what exists today

Do you need one of these connections? Tell us through the demo request, interest "a connection for software or AI agents". Go to the demo request

Roadmap

No dates and no promises. We build what demand, feasibility and data protection show. Tell us what you need.

How the MCP App could look

See more concepts: full screen, roles, agent

Machine readable

• llms.txt
• sitemap.xml
• robots.txt