API · Companies

Get company profile

Narrative business context — what the company does, customers, geography, strategy, risks.

GET/api/v1/data/companies/{company}/profile

Returns Clarifo's analytical profile: a structured narrative covering overview, products & services, customers, geography, strategy, risks (with materiality classifications), and critical accounting policies.

The profile is LLM-generated from filings — it is qualitative analysis, not raw filing text. The response field source = "clarifo_analytical_profile" makes this explicit so you can distinguish analytical content from filing-grade data.

When to use this

Generating a one-paragraph company description for a UI.
Giving an LLM enough business context before it reasons over the numbers.
Surfacing a quick "what does this company actually do?" tooltip.

For audit-grade citations, pair with content search and the snapshot endpoint.

Path

Field	Type	Description
companyrequired	string	Name or ticker. Fuzzy matching is supported.

Query

Field	Type	Description
locale	string default: en	en \| fi. Falls back to the other locale if requested one is empty.
include_full_text	boolean default: false	false = short previews (smaller token footprint); true = full multi-paragraph narrative.

Example

bash

curl "https://api.clarifo.com/api/v1/data/companies/Fiskars/profile?locale=en" \
  -H "Authorization: Bearer $CLARIFO_API_KEY"

Response

json

{
  "company_name": "Fiskars Oyj Abp",
  "locale": "en",
  "source": "clarifo_analytical_profile",
  "updated_at": "2026-04-01T12:00:00Z",
  "entity": {"name": "Fiskars Oyj Abp", "ticker": "FSKRS"},
  "overview": "Fiskars Group is a Finnish consumer goods company …",
  "products_services": {"text": "…", "tags": ["consumer goods", "premium"]},
  "customers": {"text": "…", "tags": ["…"]},
  "geography": {"text": "…", "tags": ["…"]},
  "strategy": "…",
  "risks": {"text": "…", "tags": ["…"]},
  "accounting": {"text": "…", "tags": ["…"]},
  "structured": {"…": "…"},
  "sources": [
    {
      "company": "Fiskars Oyj Abp",
      "document_type": "company_profile",
      "source_kind": "company_profile",
      "evidence_strength": "model_inference",
      "source_url": "https://…",
      "citation_label": "…",
      "citation_markdown": "[…](https://…)",
      "…": "…"
    }
  ],
  "source_policy": {"citation_mode": "claim_level", "…": "…"}
}

Field	Description
`entity`	The company the identifier resolved to (`name`, plus `ticker` / `cik` when known). Check it to confirm the profile is for the company you meant.
`overview`, `strategy`	Narrative text. Short previews unless `include_full_text=true`.
`products_services`, `customers`, `geography`, `risks`, `accounting`	`{text, tags}` objects.
`structured`	Additional structured profile content (e.g. competitive position, strategic priorities, materiality), when generated. Its shape varies by profile.
`sources`	One evidence card pointing at the company's profile page. It is tagged `source_kind: "company_profile"` and `evidence_strength: "model_inference"`, never as filing evidence.
`source_policy`	How Clarifo expects citations to be rendered.

Sections that were not generated for a company are omitted.

No profile yet

Profiles do not exist for every company yet, especially newer US additions. A miss is HTTP 200 with an error body:

json

{
  "error": "No analytical profile generated yet for this company",
  "failure_kind": "not_found",
  "company": "Palantir",
  "resolved_name": "Palantir Technologies Inc.",
  "cik": "0001321655",
  "ticker": "PLTR",
  "locale": "en",
  "alternatives": ["search_filing_content — search the actual filing text …", "…"],
  "hint": "Analytical profiles are LLM-generated summaries. …"
}

alternatives names Clarifo's MCP tools; over this API, use content search and financials instead.