Company Enrichment

Build a company profile from a domain, email or name, read from its website: industry, size estimate, headquarters, description, social links and tech stack.

Pay by wallet (x402) AI-generated company-enrich

Example

Input
{
  "domain": "google.com"
}
Answer
{
  "website": "https://google.com",
  "industry": "Technology",
  "tech_stack": [
    "Gemini",
    "Google AI",
    "Google Cloud",
    "Google DeepMind"
  ],
  "description": "Google is a multinational technology company that develops and provides a wide range of products and services including search, cloud computing, artificial intelligence, productivity software (Google Workspace), and maps.",
  "hq_location": "Mountain View, United States",
  "company_name": "Google",
  "founded_year": 1998,
  "social_links": {
    "github": null,
    "twitter": null,
    "linkedin": null
  },
  "employee_estimate": "1000+"
}

Inputs

FieldTypeRequiredWhat it is
domainstringYesCompany domain (e.g. spotify.com), email, or name

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
industrystringAlways (present in every successful answer)
tech_stackarrayAlways (present in every successful answer)
descriptionstringAlways (present in every successful answer)
hq_locationstringAlways (present in every successful answer)
company_namestringAlways (present in every successful answer)
employee_estimatestringAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "company-enrich",
    "inputs": {
      "domain": "google.com"
    },
    "max_price_cents": 50
  }'

Limitations

  • Some company details can be inferred

    Enrichment combines multiple web sources via AI — some data points may be inferred rather than directly verified

    What to do instead: Check the data_sources field in the response and independently verify critical data points against the listed sources