# EU Maritime & Port Opportunity Monitor (`dekaz/eu-maritime-port-opportunity-monitor`) Actor

Monitor Spanish and EU public tenders and funded projects for ports, dredging, maritime works, coastal protection, terminals, and decarbonization. Classifies, deduplicates, and tracks lifecycle changes.

- **URL**: https://apify.com/dekaz/eu-maritime-port-opportunity-monitor.md
- **Developed by:** [Progamadores.com](https://apify.com/dekaz) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 monitor scans

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/platform/actors/running/actors-in-store#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 Maritime & Port Opportunity Monitor

An API-first Apify Actor that finds and monitors technically relevant maritime and port
opportunities from official Spanish and European Union data.

This is procurement intelligence for companies bidding for public contracts. It is not a jobs,
vacancies, candidates or employment scraper.

The Actor is designed for marine contractors, engineering consultancies, dredging and coastal
works specialists, port-equipment suppliers, shore-power providers, terminal operators, and
business-development teams. It returns qualified lifecycle events instead of an unfiltered dump of
public notices.

### What it monitors

- Port, harbour, quay, berth, jetty, breakwater and terminal works.
- Dredging, reclamation, coastal protection and marine construction.
- Mooring, fendering, navigation, VTS/VTMS and port-safety systems.
- Shore-side electricity, alternative fuels and port decarbonisation.
- Maritime engineering, geotechnical and environmental services.

The built-in taxonomy combines maritime CPV roots, deterministic Spanish and English terminology,
buyer/authority signals and user-supplied filters. Every result includes the matched rules; the
Actor does not use an LLM or an opaque win-probability score.

### Official sources

| Source | Signals | Interface |
|---|---|---|
| PLACSP | Spanish preliminary consultations, tenders, awards and cancellations | Official Atom/XML open data |
| TED | EU procurement notices and awards | Official Search API v3 |
| EU Funding & Tenders | Calls and funded-project signals that may precede procurement | Official public Search API |

Source documentation: [PLACSP open data](https://contrataciondelestado.es/wps/portal/DatosAbiertos),
[TED Search API](https://docs.ted.europa.eu/api/latest/search.html), and
[Funding & Tenders APIs](https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/support/apis).

### Input

```json
{
  "monitorId": "iberian-port-works",
  "sources": ["placsp", "ted", "funding_tenders"],
  "countries": ["ES", "PT"],
  "regions": [],
  "cpvCodes": ["45241000", "45252124"],
  "keywords": ["dragado", "shore power"],
  "minBudget": 100000,
  "publishedAfter": "2026-07-01",
  "signalTypes": ["PRE_TENDER", "OPEN", "AWARDED", "FUNDED_PROJECT"],
  "maxResults": 100,
  "minRelevanceScore": 0.35
}
```

`monitorId` is stable state, not a display label. Reusing it compares the new scan with the last
successful observation. Use a different ID for a different commercial profile.

When `publishedAfter` is omitted, the Actor queries the previous 30 days. Inputs are bounded to
protect upstream services, run costs and storage.

### Output

Each default Dataset item is a traceable change event:

```json
{
  "recordType": "OPPORTUNITY_EVENT",
  "schemaVersion": "1.0",
  "eventType": "NEW",
  "opportunityId": "ted:123456-2026",
  "projectKey": "sha256:...",
  "source": "ted",
  "sourceRecordId": "123456-2026",
  "title": "Shore-side electricity installation at the port",
  "phase": "OPEN",
  "buyer": "Port Authority",
  "countries": ["ES"],
  "cpvCodes": ["45241600"],
  "budgetValue": 3200000,
  "budgetCurrency": "EUR",
  "deadlineAt": "2026-10-15T12:00:00Z",
  "relevanceScore": 0.84,
  "matchedRules": ["cpv:45241600", "keyword:shore-side electricity"],
  "changedFields": [],
  "sourceUrl": "https://api.ted.europa.eu/...",
  "noticeUrl": "https://ted.europa.eu/...",
  "sourceEvidence": [
    {
      "source": "ted",
      "sourceRecordId": "123456-2026",
      "sourceUrl": "https://api.ted.europa.eu/...",
      "noticeUrl": "https://ted.europa.eu/..."
    }
  ],
  "firstSeenAt": "2026-08-09T10:00:00Z",
  "lastSeenAt": "2026-08-09T10:00:00Z"
}
```

Supported change events are:

- `NEW`: first qualified observation for this monitor.
- `UPDATED`: one or more material fields changed.
- `DEADLINE_CHANGED`: the submission deadline changed.
- `AWARDED`: the source now reports an award.
- `CANCELLED`: the source explicitly reports cancellation.

Absence from a source response is never interpreted as cancellation. Source health and counts are
written to the default Key-Value Store under `RUN_SUMMARY`; historical state and billing markers
live in the named store derived from `monitorId`.

### Pricing contract

The private beta uses two Pay-Per-Event names:

- `monitor-scan`: USD 0.10 after at least one official source completes successfully.
- `qualified-opportunity`: USD 0.01 for each persisted `NEW` or changed qualified opportunity.

Duplicates, irrelevant records and failed sources are not charged as qualified opportunities. The
Actor respects the run spending limit and uses idempotency keys so a restart cannot bill the same
event twice. Event prices must be configured in Apify Console before Store publication; the source
code defines the names and charging behavior.

### Scheduling and integrations

Save the input as an Apify Task and schedule it daily or weekly. The default Dataset can be consumed
through the Apify API, Make, Zapier or a run webhook. Webhook delivery is an Apify platform feature;
this Actor does not send data to arbitrary user-provided URLs.

### Deliberate v1 limits

- No PDF or tender-document interpretation.
- No private, authenticated or paid sources.
- No browser automation or residential proxy.
- No bid recommendation, legal advice or probability of winning.
- No assumption that a missing record was cancelled.
- Published values remain attributable to the official source and should be verified before bidding.

### Development

Runtime: Python 3.13 on `apify/actor-python:3.13`. The code also supports Python 3.12 for local
development.

```powershell
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
.\.venv\Scripts\python.exe -m ruff check src tests scripts
.\.venv\Scripts\python.exe -m mypy src
.\.venv\Scripts\python.exe -m pytest
```

Run the real-source smoke script before a release. Fixtures test parser behavior; the smoke run tests
the assumptions made about the live official services.

```powershell
$env:PYTHONUTF8 = "1"
.\.venv\Scripts\python.exe scripts\smoke_sources.py
```

### Architecture

The code separates source adapters from domain qualification and historical state:

```text
official sources -> normalized source records -> maritime classifier
                 -> cross-source deduplication -> historical diff
                 -> Dataset / RUN_SUMMARY / PPE
```

This separation keeps one upstream schema change from changing the public output contract.

# Actor input Schema

## `monitorId` (type: `string`):

Stable identifier used to compare this recurring monitor across runs.

## `sources` (type: `array`):

Official datasets to query.

## `countries` (type: `array`):

ISO alpha-2 country codes. Spain is selected by default.

## `regions` (type: `array`):

Optional region names or NUTS codes used to narrow the query.

## `cpvCodes` (type: `array`):

Optional CPV roots or complete CPV codes used to filter source queries.

## `keywords` (type: `array`):

Optional Spanish or English terms used to filter source queries.

## `minBudget` (type: `number`):

Require a published budget equal to or above this value; records without a budget are excluded.

## `publishedAfter` (type: `string`):

ISO date. When omitted, the Actor uses the previous 30 days.

## `signalTypes` (type: `array`):

Empty means every supported phase.

## `maxResults` (type: `integer`):

Maximum number of qualified opportunities emitted in one run.

## `minRelevanceScore` (type: `number`):

Minimum deterministic maritime relevance score from 0 to 1.

## `requestTimeoutSeconds` (type: `integer`):

Timeout in seconds for each official-source HTTP request.

## `maxConcurrency` (type: `integer`):

Maximum number of official sources queried concurrently.

## Actor input object example

```json
{
  "sources": [
    "placsp",
    "ted",
    "funding_tenders"
  ],
  "countries": [
    "ES"
  ],
  "regions": [],
  "cpvCodes": [],
  "keywords": [],
  "signalTypes": [],
  "maxResults": 100,
  "minRelevanceScore": 0.35,
  "requestTimeoutSeconds": 30,
  "maxConcurrency": 3
}
```

# Actor output Schema

## `opportunities` (type: `string`):

No description

## `runSummary` (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("dekaz/eu-maritime-port-opportunity-monitor").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("dekaz/eu-maritime-port-opportunity-monitor").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 dekaz/eu-maritime-port-opportunity-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dekaz/eu-maritime-port-opportunity-monitor"
        }
    }
}

```

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/cQe6CfAkFIzKVfQyI/builds/XwpN4jzIFQt5teYlq/openapi.json