VAZ METALES SL. Sociedad unipersonal. Cambio de identidad del socio único: CID SAEZ JESUS MIGUEL. Ceses/Dimisiones. Adm. Unico: VAZ CULEBRAS JOAQUIN. Nombramientos. Adm. Unico: CID SAEZ JESUS MIGUEL. Cambio de domicilio social. C/ SAN JOSE DE CALASANZ 1 Ptl.2 1º C (VILLANUEVA DEL PARDILLO). Datos registrales. S 8 , H M 507991, I/A 2 (23.06.26).
Resolve a company. Reconstruct what was published about it.
BORME API turns Spain’s official company-gazette notices into a maintained intelligence layer: resolve a company, reconstruct its published history, expose officers and brands, monitor changes, and keep the official-source provenance beside every result.
{
"date": "2026-06-30", "borme_id": "BORME-A-2026-123-28",
"act_number": 308560, "province": "MADRID",
"company_name": "VAZ METALES SL.",
"company_slug": "vaz-metales-sl",
"acts": [
{ "act_type": "SOLE_SHAREHOLDER_STATUS", … },
{ "act_type": "SOLE_SHAREHOLDER_CHANGE",
"fields": { "text": "CID SAEZ JESUS MIGUEL." }, … },
{ "act_type": "TERMINATIONS", "roles": [{
"role": "SOLE_DIRECTOR", "role_raw": "Adm. Unico",
"names": ["VAZ CULEBRAS JOAQUIN"] }], … },
{ "act_type": "APPOINTMENTS", "roles": [{
"role": "SOLE_DIRECTOR", "role_raw": "Adm. Unico",
"names": ["CID SAEZ JESUS MIGUEL"] }], … },
{ "act_type": "ADDRESS_CHANGE", "fields": { … }, … }
],
"registral": { "hoja": "M 507991", "seccion": 8,
"inscription": "2", "reg_date": "2026-06-23", … },
…
}
Production baseline as of 24 August 2026: 9,573,786 events, 3,291,829 companies, more than 520,000 NIF mappings and 1,252,115 risk signals. OEPM rights, company links and linked companies are separate counts.
From a published notice to a decision-ready company record
Start with the identity you have; keep the ambiguity when the evidence does not resolve it.
Resolve a company
Use one NIF or one registry sheet (hoja) at a time. NIF mappings expose source and confidence; hoja results preserve the published coordinate and return ambiguity explicitly.
GET /v1/companies/by-nif/A46103834
→ snapshot: officers, status, insolvency
Reconstruct published history
Fold dated acts into a useful timeline or an as-of view, bounded by what the published BORME history showed by that date.
GET /v1/companies/vaz-metales-sl/events?limit=100
→ oldest-first published timeline
Monitor change
Watch companies and receive new published events or risk signals without repeatedly rebuilding the same ingestion pipeline.
POST /v1/watchlists
{"company_slug":"vaz-metales-sl","webhook_url":"https://example.com/borme"}
→ signed delivery after new published events
Expose officers and brands
Move from a person or OEPM brand name to sourced candidates. An OEPM alias is not silently promoted to a tax-ID match.
GET /v1/brands?q=freixenet
→ holder, marks, trading names
Keep the evidence
Every event retains its official-source provenance: gazette issue, act number and source link travel with the normalized record.
GET /v1/companies/vaz-metales-sl?as_of=2022-03-01
→ published BORME history showed by that date
51 emitted act types, one vocabulary
Dense gazette shorthand becomes a closed, documented enum — the same value for the same act since 2009, across every provincial dialect of the gazette.
Auditable by design
Registry data is only useful if you can defend it. Every record retains official-source provenance — the gazette issue, act number and source link — alongside the normalized value. Anything unrecognized remains available as raw text rather than becoming an invented fact.
Official BOE open-data API
Fetched politely from boe.es — the state publisher of BORME. Every event links back to its gazette file and act number.
No LLM in the hot path
A deterministic parser over a closed vocabulary. Identical input yields identical output, byte for byte, on every re-run.
Source before inference
Parse completeness is measured per file. API events retain the publication reference and act number so an uncertain normalization can be checked against the BOE source.
Stable event IDs
event_id is a deterministic hash — deduplicate across re-runs and replays with confidence.
Reconciled against the registry itself
Counted act by act against the Colegio de Registradores' own annual totals for 2016–2025, incorporations and capital reductions are within 1% in all ten years, capital increases in nine and extinctions in eight. How we measured it. Control figures: opendata.registradores.org (ODbL 1.0).
Why pay?
The published facts are public. Payment funds the maintained processing that makes them dependable in a product: ingestion, normalization, entity resolution, historical replay, daily operation and delivery.
Collect and preserve
We follow the official publication stream, retain the source reference and make the dated record queryable.
Make notices usable
A repeatable parser turns provincial gazette shorthand into typed events, roles and fields without hiding the original text.
Show candidates honestly
Name, hoja, NIF and OEPM relationships have different strengths; the API exposes provenance and ambiguity instead of claiming certainty it does not have.
Serve history and change
We maintain replays, snapshots, watchlists and delivery so your team can ask a past question and receive new publication events.
Start today — actor or hosted API
Choose the Actor for an on-demand date-range export. Choose the maintained Hosted API for repeated lookups, derived company state, NIF mappings, history, monitoring, risk and MCP.
Apify actor
- Any date range since 2009, any province
- Filter by event type and company name
- $0.01 per run, plus $1 per 1,000 delivered events
- JSON / CSV / Excel export, API & SDK access
- Agent-friendly: limited permissions, typed output
Hosted API
API tiers
Explore
- 50 requests/day
- 7-day event history
- 2 watchlists
- Daily CSV subscription endpoint, subject to its subscription limits
Resolve
- 5,000 requests/day
- 365-day event history
- 20 watchlists
- Company snapshots; single NIF and hoja resolution; people roles and brands
- Webhooks and email alerts
Reconstruct
- 50,000 requests/day
- Full archive since 2009
- 200 watchlists
- Batch NIF, as-of state, officer network and on-demand bulk CSV dump
Investigate
- 200,000 requests/day
- Full archive since 2009
- 200 watchlists
- Everything in Pro, plus signals and itemized, rule-based risk profiles
- AEAT large-debtor-list cross-reference; not a credit rating or tax-debt check
All plans return the same sourced, typed records; the paid tiers add maintained resolution, replay, monitoring and delivery depth.
What the Hosted API adds
The free event feed lets you inspect recent sourced records. Paid tiers add indexed company resolution, derived state, monitoring, point-in-time history and risk outputs without requiring you to rebuild the publication pipeline.
Confirm your email to get a free key. Your key is shown only in your account.
Quick start
From a free key to your first response in three steps — and an MCP endpoint for AI agents that needs no key at all.
1 · Get a key
Enter your email in your account and open the sign-in link we send you. Your free key is shown once, right after you sign in: copy it then.
2 · Make a request
Send the key in the X-API-Key header. Recent incorporations in Madrid, within the free tier's seven-day window:
curl -G \
-H "X-API-Key: YOUR_KEY" \
-d province=MADRID \
-d act_type=INCORPORATION \
-d limit=5 \
https://api.bormeapi.com/v1/events
3 · Read the docs
Every endpoint, parameter and response schema, with a console to try calls from the browser: api.bormeapi.com/docs. The machine-readable spec is at /openapi.json.
MCP for AI agents
Read-only tools over streamable HTTP at https://mcp.bormeapi.com/mcp. In Claude Code:
claude mcp add --transport http borme https://mcp.bormeapi.com/mcp
In clients configured with JSON, such as Cursor's mcp.json:
{"mcpServers": {"borme": {"url": "https://mcp.bormeapi.com/mcp"}}}
Questions
Is this the official registry?
BORME is Spain's official commercial-registry gazette and publishes notices about appointments, capital changes, insolvency proceedings and other company events. This service normalizes that published history; it is not affiliated with or endorsed by BOE, and it is not a certified registry extract. Verify legal conclusions against the official notice or Registro Mercantil documents.
How fresh is the data?
BORME is normally published Monday to Friday. Events become available after BOE publication and successful ingestion; each processed record carries its publication date, gazette ID and source reference.
How far back does it go?
Coverage starts with the BORME of January 2, 2009. The actor accepts any date range from then on; the hosted API serves the full archive, with company timelines, on the Pro tier.
What about GDPR and personal names?
BORME is public-sector information whose publication is required by Spanish law; director names are part of the official record. We honor documented suppression requests for derived outputs — write to [email protected] and we will mask the affected person going forward.