Company intelligence

GET https://api.logorouter.com/api/intelligence/{domain}

Returns structured company intelligence: industry, sizing hints, inferred technologies, narrative description, etc. Responses are assembled server-side from research-style prompts plus cached normalisation layers.

Authentication

• Requires a secret API key (lm_live_* / lm_test_*) via Authorization: Bearer, x-api-key, or compatible header shapes.
• Publishable keys are rejected for this route — mirror the separation you use elsewhere (browser <img> uses publishable; CRM enrichment uses secrets).

Always call this endpoint server-to-server.

Typical fields

Exact keys evolve minor versions additively (openapi.json lists the authoritative schema).

You will commonly see categories such as:

• Industry — normalised vertical or product category.
• Company size / scale — human-readable buckets or ranges when confidently inferred.
• Founding timeframe — year or coarse decade when attributable.
• Technologies — short list of surfaced stack signals (best-effort, not a SOC2-attested scanner).
• Positioning fields — description, business_model, target_market-style summaries for CRM or enrichment panels.

Treat long-form narratives as UI copy candidates rather than audited financial facts.

Caching & performance

Workers apply multi-tier caches (KV / R2 / edge) keyed by normalized domain plus plan rules. Repeated reads on hot domains amortise latency; first-touch may still incur external model hops.

Prefer ETag‑friendly retries (If-None-Match) once clients support it upstream.

Operational headers

Correlation headers such as x-lr-region pair with dashboards for anomalies. Respect 429 problem responses (Retry-After when emitted).

Combine with CDN logo bytes (img.logorouter.com) plus Brand colors for dashboards that tint cards from live identity data.