Company research with evidence

Build company records that a person can check. Keep public website observations, contact sources and missing information explicit.

curl -X POST https://api.luni.gg/v1/company \
  -H "Authorization: Bearer $LUNI_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: example-company-0f5fb0306a51" \
  -d '{
  "url": "https://example.com",
  "maxPages": 10
}'

Begin with the company's website

Provide a public company URL and a page budget. The invite-only enterprise company endpoint builds a bounded profile from website evidence. It is useful for a research queue, directory review or an account-research workflow where a person needs to see the source behind a field.

For an application with its own extraction logic, map the site and scrape the selected about, product or contact pages instead. Choose the API based on whether you need a profile or the underlying documents.

Preserve provenance and uncertainty

Store source URLs and observation time alongside the values you accept. Treat missing fields as missing. A contact copied from a website is harvested rather than independently verified, and an email address alone does not establish deliverability or consent to outreach.

Build your own review rules before writing values into a CRM or directory. Luni does not provide a built-in CRM connector, authenticated social scraping or access to private company databases.

Evaluate enterprise access

Company research is enterprise-only and must be enabled for your invited workspace. Each successful profile costs 40 credits and can examine up to 20 pages; a failed profile consumes zero profile credits. Start with a small sample that reflects the kinds of sites you actually research.

Measure which fields are useful and how often a reviewer accepts them. A page budget and a saved source trail make the workflow inspectable, but they do not guarantee a complete or verified company record.