Company registry timeline
company_historyGet one company's BORME timeline: its published registry events within your plan's window.
Use it once the company is known (a slug from search_companies or company_by_nif); across many companies use search_events. A name is searched too: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}.
Returns JSON {company_slug, total_events, first_seen, last_seen, truncated, next_offset, count, events} (as in search_events), with former_slugs for a merged company (an old slug returns the merged timeline) and plan_window on a limited plan. total_events, first_seen and last_seen cover the whole timeline in your window, not this page. To page, keep limit and order and pass next_offset as offset (at most 10000) until it is null.
Read-only; one request per call. Without an API key (X-API-Key header) only the last 7 days; basic covers 365 days, pro and risk the full history back to 2009. If all its events are outside your window, the refusal counts them.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"company": "<company>"
},
"name": "company_history"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Events per page, integer 1-200, e.g. 20 (default 100). | |
| order | No | "desc" (default, newest first) or "asc" (oldest first), e.g. "asc" to start from the earliest event in your plan's window. | desc |
| offset | No | Events to skip, integer 0-10000 (default 0); pass the previous page's next_offset, e.g. 100. | |
| company | Yes | Company slug, e.g. vaz-metales-sl (from search_companies), or a name of at least 3 letters or digits, e.g. "Mercadona", searched case-insensitively. | |
| include_inferred | No | Optional, default false, e.g. true. true allows an inferred sector on events without a CNAE code: the first act with a non-empty objeto social gets `fields` with `cnae_inferred` (a CNAE-2009 division), `cnae_source` `jev` and `cnae_inference` (`confidence`, `model`, `prompt`, `section`, `note`). Nothing is added if any act has a CNAE code, no act has a non-empty objeto social, or no decision qualifies. It is the output of a language model (TypeSafe Jev, model `typesafe-ai/jev-1.14.0`, prompt ID `two-stage-v1`), not a code published in BORME, and it describes the objeto social, not the company's verified activity. Only decisions whose confidence meets the threshold are returned (default 0.9). Inferred values are included only on request: if you omit `include_inferred` or set it to `false`, there are none. Only acts published from 2024-11-05 have inferred divisions (`note`), so more sector coverage from that date may reflect them and does not, by itself, show market growth. |