All filters optional. Dates are YYYY-MM-DD (coverage starts 2009).
provinces: BORME province names, accent-insensitive (MADRID, CADIZ...).
act_types: normalized enums, e.g. INCORPORATION, APPOINTMENTS, TERMINATIONS,
CAPITAL_INCREASE, DISSOLUTION, INSOLVENCY_STATUS (see list_act_types).
Returns newest first, at most `limit` (<=200) events as JSON.

`company` is a company slug (e.g. vaz-metales-sl) or an exact-ish name;
if no slug matches, falls back to case-insensitive name search and, when
several companies match, returns the list of candidate slugs instead.

BORME itself prints no tax IDs — this mapping is cross-referenced from
open official sources (GLEIF, BDNS subsidies register, AEAT) and covers
a growing subset (~232k companies). A miss means "not matched yet",
not "does not exist". On a hit, follow up with company_history using
the returned slug.

This is a teaser feed — the full historical signals firehose lives in the
hosted API's risk tier (https://bormeapi.com/#pricing).

Returns a JSON object with: total_events (approximate count, planner
estimate), total_companies, date_range (first and latest publication day
covered, YYYY-MM-DD), and recent parse completeness (share of gazette text
successfully structured over the last publication days, e.g. 0.9987).

Use this to answer "how much data is there?", "how fresh is it?" and
"can I trust date filters for period X?" before running searches. Takes
no arguments; counts are estimates (fast reads), not exact tallies.