# Spanish Company Formations (BORME) (`neburlabs/my-actor`) Actor

Extract structured Spanish company incorporation notices from official BOE BORME OpenData by date, province, and keyword.

- **URL**: https://apify.com/neburlabs/my-actor.md
- **Developed by:** [RKM](https://apify.com/neburlabs) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Spanish Company Formations (BORME)

Extract structured company incorporation notices from the official BOE BORME OpenData API. Choose a publication date range and optionally filter by exact province or keywords. Output is one JSON record per constitution notice.

### Input

- `dateFrom`, `dateTo`: publication dates (`YYYY-MM-DD`); defaults to today / start date.
- `provinces`: optional exact BORME province names.
- `keywords`: optional case-insensitive company-name or objeto-social terms.
- `includeAdministrators`: opt in to names published in BORME; off by default.
- `maxCompanies`: 1-10,000 records; default 500.

See the exact customer examples in `STORE_LISTING.md`.

### Output

Each record includes `companyName`, `publicationDate`, `province`, `municipality`, `objectPurpose`, `capitalEur`, optional `administrators`, derived `sectorTag`, `officialActId`, official XML/PDF links, attribution, and parser version. Use `officialActId` for downstream deduplication.

### Date-range product, not a monitor

Version 1 does not retain cross-run customer state and does not claim “only new since last run.” For repeat schedules, supply the intended one-day range and deduplicate on `officialActId` in the receiving system. This avoids shared-state leakage, accidental cross-filter suppression, state resets, and ambiguous behavior when users backfill or change filters.

### Source, attribution, and status

The Actor calls `https://www.boe.es/datosabiertos/api/borme/sumario/{YYYYMMDD}` and the official Section A XML links returned by that API. No browser scraping is used.

**Basado en datos de la Agencia Estatal Boletín Oficial del Estado.** Source: https://www.boe.es

This is an independent, derived data extractor. It is not an official BOE/AEBOE product and is not endorsed by them. Parsed JSON is non-official; the signed PDF linked in each record is authoritative. `municipality` is inferred from notice text. `sectorTag` is a deterministic, non-official heuristic. Either may be null or imperfect.

### Operational limits

The Actor is sequential and waits 150 ms between province documents. Weekends and holidays with no issue are skipped. Administrator names are opt-in and users remain responsible for lawful personal-data reuse.

### Pricing

$0.05 per Actor start plus $0.0015 per result (Result is the primary event; Apify platform usage is included). This is experimental launch pricing for the first 30-60 days, not permanent pricing.

### Local validation

```bash
npm ci
npm test
node test/validate-store-package.js
```

# Actor input Schema

## `dateFrom` (type: `string`):

First BORME publication date to read, in YYYY-MM-DD format. Defaults to today.

## `dateTo` (type: `string`):

Last BORME publication date to read, in YYYY-MM-DD format. Defaults to the start date.

## `provinces` (type: `array`):

Optional exact BORME province names, for example MADRID or BARCELONA.

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

Optional case-insensitive keywords matched against the company name and objeto social.

## `includeAdministrators` (type: `boolean`):

Off by default. Names come from the official publication and remain subject to applicable data-protection duties.

## `maxCompanies` (type: `integer`):

Safety limit for records emitted by one run.

## Actor input object example

```json
{
  "includeAdministrators": false,
  "maxCompanies": 500
}
```

# Actor output Schema

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

Default dataset containing one record per parsed company incorporation.

# 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("neburlabs/my-actor").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("neburlabs/my-actor").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 neburlabs/my-actor --silent --output-dataset

```

## MCP server setup

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

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/penluMw5hlI0vqNwN/builds/m7eTaXC2HAAoEdLxG/openapi.json