Datapublica

Use this when the root SQL contract uses modular delivery and an analysis requires this declared data domain or one of its dependencies. Modules cover company registry data, people and ownership, financials and filings, risk and signals, classifications and geography, and capital and investments. Pass the exact schemaVersion from the root contract.

get_sql_contract_module

Use this when the user asks for curated narrative sections from one identified company’s XBRL annual report, covering business and development, risks and material matters, or commitments and security. This is not the complete annual report: boilerplate and cross-scope duplicates are suppressed, contentPlain is capped at 20,000 characters, isTruncated marks excerpts, and there is no pagination. A section’s financialScope can be report_wide; sourceReportUrl can be null; PDF-only filings return no sections; and availableReports[].locked is always false for token-authenticated calls. Supply financialScope when no scoped numeric annual filing can provide a default. Do not use it for numeric financial comparisons or full-report retrieval.

get_company_annual_report_sections

Use this when the user asks about capital increases, reductions, funding events, subscription prices, implied valuations, provenance, or attributed investors for one identified company. Do not use for recent investment activity across many companies; use get_investment_feed instead.

get_company_capital_events

Use this when the user asks how one identified company changed over time, including registry, role, ownership, auditor, and filing events. Do not use for the company’s current profile or cross-company event analysis.

get_company_timeline

Use this when the user asks for chronological registry activity involving one unresolved participant identity. Do not use for the participant’s relationship graph.

get_participant_timeline

Use this when the user asks how a resolved person’s company roles, ownership, or other registry activity changed over time. Do not use for the current relationship graph; use get_person_portfolio instead.

get_person_timeline

Use this to run validated custom, read-only DuckDB SQL that may scan the full active Datapublica dataset and return bounded results. Appropriate for company screening, rankings, comparisons, aggregations, trends, and analyses combining registry, financial, ownership, people, industry, geography, risk, Gazelle, capital, and investment data. Do not use unvalidated SQL, write statements, or repeated entity lookups when one analytical query is more appropriate.

execute_sql

Use this only as a fallback when a complex Danish or English analytical question cannot be converted confidently into SQL from the active contract. It can translate screening, ranking, comparison, aggregation, trend, and multi-domain questions, but consumes natural-language credits and does not execute the result.

translate_to_sql

Use this after authoring or modifying custom DuckDB SQL and before execution. It validates full-dataset analytical queries against the active schema, read-only safety rules, semantic domains, financial scope, currency rules, and plan access without running them.

validate_sql

Use this when you already have a stable identifier for one Danish company and need its complete company profile, including registry details, status, addresses, industries, roles, ownership, filings, financials, and available risk fields. Do not use to find an unknown company or compare multiple companies; use search_companies or SQL instead.

get_company

Use this when you have a stable participant identifier and need the registry bundle for an unresolved participant identity. Do not use for resolved companies or people.

get_participant

Use this when you have a stable resolved-person identifier and need that person’s roles, ownership, auditor relationships, contacts, or related companies. Do not use a display name as the identifier; call search_people first when necessary.

get_person