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 (VILLANUEVA DEL PARDILLO). Datos registrales. S 8, H M 507991, I/A 2 (23.06.26).
Spain's commercial registry, in English, as JSON.
Every act published in BORME — Spain's official company-registry gazette — parsed the same morning into typed, auditable events: incorporations, director changes, capital moves, insolvencies. Straight from the official BOE source.
{
"company_name": "VAZ METALES SL.",
"date": "2026-06-30", "province": "MADRID",
"acts": [
{ "act_type": "SOLE_SHAREHOLDER_CHANGE",
"payload": "CID SAEZ JESUS MIGUEL" },
{ "act_type": "TERMINATIONS", "roles": [{
"role": "SOLE_DIRECTOR",
"names": ["VAZ CULEBRAS JOAQUIN"] }] },
{ "act_type": "APPOINTMENTS", "roles": [{
"role": "SOLE_DIRECTOR",
"names": ["CID SAEZ JESUS MIGUEL"] }] },
{ "act_type": "ADDRESS_CHANGE" }
],
"registral": { "hoja": "M 507991", "inscription": "2" }
}
Built for the questions you actually ask
One normalized event stream, three ways to use it.
KYC & onboarding
Start from the NIF you already hold. Who runs this company today? Any insolvency before you sign?
GET /v1/companies/by-nif/A46103834
→ snapshot: officers, status, insolvency
Risk monitoring
One call, one explainable score — insolvency, AEAT debt, phoenix officers, mass exits, each factor itemized.
GET /v1/companies/{slug}/risk
→ score 0–100 + factors[]
Sales intelligence
Fresh incorporations by province, every morning. Leadership changes as buying signals.
provinces = ["MADRID"]
act_types = ["INCORPORATION"] # ~120/day
Audit & point-in-time
What did this company look like the day you onboarded it? Rewind the registry to any past date — officers, status, capital as of then.
GET /v1/companies/acme-sl?as_of=2022-03-01
→ state as the registry knew it then
52 event kinds, 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 carries its own paper trail — and every quality claim on this page is a measured number, not an adjective: completeness is computed per file, reliability was audited against an independently built reference database over 31 publication days (100% match), and identical inputs always produce identical outputs.
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.
Nothing silently dropped
Parse completeness is measured per file. Anything unrecognized ships verbatim in unparsed_spans and raw_text.
Stable event IDs
event_id is a deterministic hash — deduplicate across re-runs and replays with confidence.
Start today — actor or hosted API
Both are live: the pay-per-event actor on Apify, and the hosted API with a free tier — history queries, watchlists, webhooks, MCP.
Apify actor
- Any date range since 2009, any province
- Filter by event type and company name
- Pay only for delivered events
- JSON / CSV / Excel export, API & SDK access
- Agent-friendly: limited permissions, typed output
Hosted API
| Free | €0 | 50 req/day · last 7 days of events |
|---|---|---|
| Basic | €19/mo | 5,000 req/day · 365-day lookback · watchlists, webhooks & email alerts |
| Pro | €49/mo | 50,000 req/day · full archive since 2009 · company timelines · NIF lookup (232k companies) · point-in-time (state as of any past date) · batch NIF lookup · officer network graphs · bulk CSV dumps |
| Risk | €149/mo | 200,000 req/day · everything in Pro · signals feed: insolvency filings, accordion recaps, mass exits, phoenix companies, mass-domiciliation clusters, AEAT large debtors · one-call risk profiles with itemized factors |
- Same typed JSON on every tier; upgrade only changes depth & volume
- NIF cross-reference — BORME prints no tax IDs; we map 232,300 companies from official open sources (GLEIF, BDNS, AEAT), each with source & confidence declared
- Watchlists with HMAC-signed webhooks and email alerts — live
- MCP server for AI agents — live:
mcp.bormeapi.com/mcp(free, read-only, now with NIF lookup)
Questions
Is this the official registry?
BORME is the official gazette of Spain's Registro Mercantil: every registrable act — appointments, capital changes, insolvency proceedings — must be published in it. This service republishes and normalizes that public data; it is not affiliated with or endorsed by BOE. For full deeds and annual accounts you still need the registry itself; for screening and monitoring, BORME is the canonical public source.
How fresh is the data?
BORME is published Monday to Friday in the morning (Europe/Madrid). Events are available the same morning; each record carries its publication date and gazette file ID.
How far back does it go?
To the first digital BORME issue, January 2, 2009. The actor accepts any date range; 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.