# Portugal EV Charging - Dataset Export (`teal_hang/ev-charging-portugal-run`) Actor

Export live Portugal EV charging to a dataset. Set your location and driving time. Get cheapest charge, chargers you can reach, hubs nearby, or one charger by ID. Official status, real card prices, minutes on the road. Not a scraper.

- **URL**: https://apify.com/teal\_hang/ev-charging-portugal-run.md
- **Developed by:** [Daniel Oiteiro](https://apify.com/teal_hang) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 cheapest charges

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

### Portugal EV Charging - Dataset Export

Set where you are. Pick what to export. Start. You get a table of rows. Not a scrape. The network is already loaded.

Same engine as the MCP listing, [`teal_hang/ev-charging-portugal`](https://apify.com/teal_hang/ev-charging-portugal). That one is chat (Cursor, Claude Desktop). This one is a Console export.

#### How to run

1. Open **Input**.
2. Leave the default, or set **Where are you?** as `latitude, longitude` (default is Marques de Pombal, Lisbon: `38.7253, -9.1502`).
3. Set **How far you will drive**. That is time on the road, not a circle on the map. 1 to 15 minutes.
4. Pick **What do you want?**
5. Start. A default cheapest-charge run takes about 2 seconds.

If you pick **Is this site full?** or **Is this charger reliable?**, you must paste a **Charger ID**. Without it the run fails. Copy the `id` column from a previous cheapest-charge or chargers-I-can-reach run, or read the code on the post (example `OER-00069-01`).

Cursor / Claude: use the other Actor. Do not point MCP clients at this one.

#### What to pick

| You want                   | Pick                                         | You must set                                               |
| -------------------------- | -------------------------------------------- | ---------------------------------------------------------- |
| Cheapest stop near me      | Cheapest charge near me                      | Where you are. Optional: kWh and your exact charging card. |
| Every charger I can reach  | Chargers I can reach                         | Where you are.                                             |
| Sites near me, who is busy | Hubs near me right now                       | Where you are.                                             |
| Is this place packed?      | Is this site full? (needs charger ID)        | Charger ID.                                                |
| Can I trust this cable?    | Is this charger reliable? (needs charger ID) | Charger ID.                                                |

A **charger** is one cable. That is the `id` you paste. A **hub** is the place: one lot can have several cables. "Full" means every cable at that place is taken. A street post with one socket is a hub of 1. One car makes it 100% full.

#### What the numbers mean

**€/kWh** is the VoltPass weighted price. Energy plus CEME activation plus operator flat and time, amortized over a basket of batteries. It is not a raw energy-only rate. **est\_total\_eur** is that number times the kWh you set.

The price depends on the card in your wallet. EDP Casa is not EDP UVE. Leave **Any card** to rank the cheapest card per charger. Pick the exact tariff you hold to rank only that card.

**minutes** is driving time on the road network, not crow-flies.

**status** is the official live feed, not a crowd check-in.

Every row has **computed\_at**. Prices and occupancy move. Do not treat an old run as today's price.

#### What you get

The dataset is one row per charger or hub. Same shape on every row. The short sentence in Portuguese and English is also in key-value store `OUTPUT` (`summary_pt`, `summary_en`).

Typical cheapest-charge columns: `id`, `name`, `operator`, `kW`, `status`, `minutes`, `ceme`, `ceme_tariff`, `eur_per_kwh`, `est_total_eur`, `kwh`, `tool`, `computed_at`.

#### Example (Marques de Pombal, 27 Aug 2026)

Default input. Cheapest charge, 30 kWh, 15 minutes, any card.

Pick: `OER-00069-01`, 50 kW, 8 min drive, available, €3.38 for 30 kWh. Card was Moeve App GOW Deco.

Ten uniform rows. About 2 seconds. That euro figure is from that run. Check `computed_at` on yours.

To check that cable, run again, pick **Is this charger reliable?**, paste `OER-00069-01`.

#### Pricing

You pay Apify compute for the run. The lookup itself is one call into the live Portugal index, not a crawl of the public web.

#### What this is not

Not a scraper. Not MCP. Not global. Not a route planner.

# Actor input Schema

## `location` (type: `string`):

Latitude, longitude. Default is Marques de Pombal, Lisbon. Used for cheapest charge, chargers I can reach, and hubs near me.

## `max_minutes` (type: `integer`):

Max driving time from here to the charger. Time on the road, not a circle on the map. 1 to 15. Used for the same three questions.

## `tool` (type: `string`):

One question per run. Cheapest / chargers I can reach / hubs near me use Where are you? above. Is this site full? and Is this charger reliable? need a charger ID below. Without that ID those two fail.

## `kwh` (type: `number`):

Used for cheapest charge. Leave 30 otherwise.

## `ceme` (type: `string`):

Used for cheapest charge. The exact card in your wallet, not the brand. Any card = cheapest across all cards.

## `charging_point_id` (type: `string`):

You must fill this if you asked Is this site full? or Is this charger reliable?. Without it those two fail. Copy the id column from a previous run (example OER-00069-01) or read it on the post. Leave empty for the other questions.

## `limit` (type: `integer`):

Used for chargers I can reach and hubs near me. Max 50.

## `full` (type: `boolean`):

Used for Is this charger reliable? Off = last 7 and 30 days. On = long history.

## Actor input object example

```json
{
  "location": "38.7253, -9.1502",
  "max_minutes": 15,
  "tool": "compare_price",
  "kwh": 30,
  "ceme": "any",
  "limit": 25,
  "full": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (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 = {
    "location": "38.7253, -9.1502",
    "max_minutes": 15,
    "tool": "compare_price",
    "kwh": 30,
    "ceme": "any",
    "limit": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("teal_hang/ev-charging-portugal-run").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 = {
    "location": "38.7253, -9.1502",
    "max_minutes": 15,
    "tool": "compare_price",
    "kwh": 30,
    "ceme": "any",
    "limit": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("teal_hang/ev-charging-portugal-run").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 '{
  "location": "38.7253, -9.1502",
  "max_minutes": 15,
  "tool": "compare_price",
  "kwh": 30,
  "ceme": "any",
  "limit": 25
}' |
apify call teal_hang/ev-charging-portugal-run --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,teal_hang/ev-charging-portugal-run"
        }
    }
}

```

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/0cuhQW9S7HSKGtUIT/builds/5caeCQoNniKEh8yK0/openapi.json