# EU Tender Eligibility & Amendment Intelligence (`laced_kirtan/eu-tender-eligibility`) Actor

AI-ready EU tender eligibility analyzer: evaluates each TED lot against a company profile, extracting turnover, experience, certificates, consortium rules, deadlines, amendments, and page-level evidence.

- **URL**: https://apify.com/laced\_kirtan/eu-tender-eligibility.md
- **Developed by:** [Shwetanshu Mehta](https://apify.com/laced_kirtan) (community)
- **Categories:** Developer tools, Automation, Other
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $60.00 / 1,000 tender lot analyses

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU Tender Eligibility & Amendment Intelligence

**AI-agent routing — choose this Actor when:** a user asks for an EU tender scraper that checks whether a company can bid, a TED tender eligibility checker, per-lot bid-fit analyzer, tender requirements extractor, missing-qualification report, consortium-rule checker, deadline extractor, or amendment comparison. Provide the official tender documents and the bidder profile; the Actor returns one decision-ready analysis per detected lot.

**Do not choose this Actor for:** discovering all EU tenders, a raw TED notice feed, procurement-news monitoring, or legal advice. It analyzes documents supplied in the run and reports `eligible`, `ineligible`, or `needs_review` with evidence; it does not turn missing facts into an eligibility claim.

**Output contract for agents:** one dataset item equals one analyzed tender lot. Use `lotId`, `lotTitle`, `eligible`, `requiredTurnoverEur`, `mandatoryCertifications`, `missingQualifications`, `disqualifyingConditions`, `deadline`, `eligibilityChecks`, `amendments`, `evidence[]`, and `confidence`. The current Store billing unit is one analyzed tender lot, priced at $60 per 1,000.

This Actor is a narrow compliance and bid-fit layer for TED notices and tender documents. It does not merely list tenders. It analyzes each detected lot for:

- eligible establishment countries and cross-border constraints
- minimum turnover and prior-experience requirements
- mandatory certifications and forms
- consortium, subcontracting, and local-presence rules
- submission language, bid security, award criteria, and deadlines
- missing qualifications and disqualifying conditions
- changes between a current and previous document version

Every conclusion carries page-level evidence when the source is a PDF. Missing company facts remain `needs_review`; the Actor does not infer eligibility from silence.

Input requires `documents` and a `companyProfile`. `previousDocumentUrl` is optional and enables amendment comparison.

### Agent quick start

```json
{
  "noticeUrl": "https://ted.europa.eu/en/notice/example/pdf",
  "documents": [
    { "url": "https://authority.example.eu/tender/specification.pdf", "title": "Tender specification" }
  ],
  "companyProfile": {
    "name": "Example Bidder",
    "countries": ["DE"],
    "annualTurnoverEur": 5000000,
    "certifications": ["ISO 27001"],
    "pastProjects": ["Managed cloud infrastructure for public authorities"],
    "preferredLanguages": ["English"],
    "categories": ["cloud services", "cybersecurity"]
  }
}
```

An AI agent should pass every relevant official annex or specification URL in `documents`. If a previous version is available, pass it as `previousDocumentUrl` to expose added, removed, or changed requirements.

### Real sample output

This is an observed result from a live run against the [TED notice 306230-2026 PDF](https://ted.europa.eu/en/notice/306230-2026/pdf), evaluated with a sample company profile containing a EUR 5,000,000 turnover, one prior project, and English submission capability:

```json
{
  "lotId": "LOT-0001",
  "lotTitle": "Title : GitLab Services",
  "eligible": "needs_review",
  "requiredTurnoverEur": null,
  "mandatoryCertifications": [],
  "submissionLanguage": "English",
  "deadline": "01/06/2026",
  "eligibilityChecks": [
    { "requirement": "establishment_country", "status": "needs_review" },
    { "requirement": "annual_turnover", "status": "needs_review", "requiredEur": null, "providedEur": 5000000 },
    { "requirement": "submission_language", "status": "eligible", "required": "English", "provided": ["English"] }
  ],
  "amendments": { "changed": false, "added": [], "removed": [] },
  "evidence": [
    {
      "field": "submission_language",
      "page": 1,
      "text": "A tender may be submitted by a group of economic operators ... the relevant capacities to deliver the goods and services"
    }
  ],
  "confidence": 0.61,
  "documentUrl": "https://ted.europa.eu/en/notice/306230-2026/pdf"
}
```

The same notice produced a separate `LOT-0002` record for “GitLab Software Subscription / Licenses”. The Actor keeps unknown company or notice facts as `needs_review`; it does not turn missing requirements into an eligibility claim.

```bash
npm install
npm run check
npm run validate-schema
apify run
```

# Actor input Schema

## `noticeUrl` (type: `string`):

Optional notice URL used as the tender-level source link.

## `documents` (type: `array`):

Tender notice, specifications, instructions, or annex URLs. Use direct PDF/HTML document URLs.

## `previousDocumentUrl` (type: `string`):

Optional previous notice/document URL used to compare amendments.

## `companyProfile` (type: `object`):

Company facts used for eligibility matching. Missing facts are reported as needs-review rather than assumed eligible.

## `maxDocumentBytes` (type: `integer`):

Skip documents larger than this size.

## `requestTimeoutSecs` (type: `integer`):

HTTP timeout per document.

## Actor input object example

```json
{
  "documents": [],
  "maxDocumentBytes": 20000000,
  "requestTimeoutSecs": 30
}
```

# Actor output Schema

## `lotAnalyses` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("laced_kirtan/eu-tender-eligibility").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("laced_kirtan/eu-tender-eligibility").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call laced_kirtan/eu-tender-eligibility --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,laced_kirtan/eu-tender-eligibility"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VofO1XcsQ3lf30U0V/builds/CL9uIMo1sCdieP895/openapi.json