Elvesora Enrichment

Company data enrichment API

Add company-level context to business records before CRM routing, segmentation, and account workflows depend on them.

Short answer: Elvesora Enrichment is a company data enrichment API for firmographics, official domains, headquarters, descriptions, public business links, and CRM-ready company fields. It is not people-data enrichment or contact discovery.

Get API Key View Pricing View API
Self-serve instant access
No credit card required
Built for serious workflows
Developer-first experience

Enrichment request

POST /api/v1/enrichment/company 200 OK
JSON cURL 
{
  "domain": "acmecorp.com"
}

Input: one business domain

Response: result_type plus company fields

Enrichment result

Enriched CRM-ready fields
Company name
Acme Corporation
Domain
acmecorp.com
Industry
Manufacturing
Headquarters
New York, United States
Employees
1,001-5,000
Description
Acme Corporation designs, manufactures, and distributes industrial components.
Website
https://acmecorp.com
LinkedIn
/company/acmecorp
Result type ENRICHED

Input

Known company context

REST and MCP require a business domain. Bulk lists can start from a domain or business email.

Output

Company profile data

Firmographics, headquarters, descriptions, public business links, and CRM-ready fields.

Boundary

Company-level data only

No people profiles, private contact lists, personal email discovery, or lead generation. Public company contact channels may be returned.

Best before

Routing, scoring, or account workflows

Resolve identity and validate domain first for best results.

How teams run enrichment

API automation, MCP clients, or UI list processing

Use Elvesora Enrichment as a direct API when enrichment belongs in code, call the remote MCP tool from a compatible authenticated client, or use the product UI for one-time and recurring lists.

API automation

Embed enrichment in pipelines

Send business domains from CRM jobs, onboarding flows, and internal tools, then write company-level fields back with your own rules. In the signed-in API screen, create or regenerate a team token, confirm API readiness, and download the OpenAPI and Postman assets. Resolve company names to domains first.

View API ->

Remote MCP

Enrich from compatible MCP clients

Call enrich_company with a business domain and optional idempotency key, then receive structured company and credit data under the same team account. Compatible clients can also discover the Markdown guide and embedded results resource.

View MCP setup ->

UI list processing

Process records without building first

For one-time imports or periodic CRM hygiene lists, paste values or upload CSV, XLS, and XLSX rows. Submission lowercases, normalizes, deduplicates, and classifies entries; invalid rows stay visible without consuming credits, while valid rows start processing immediately.

Create Account ->

Elvesora Enrichment Features

Company-level fields for CRM, analytics, routing, and workflow quality.

Capability What you get Why it matters
Firmographics Industry, employee range, revenue range, company type, year founded, and other core attributes. Power segmentation, scoring, and account qualification with reliable company-level data.
Headquarters context HQ name, city, state or province, country, and address context when available. Improve routing, territory assignment, regional analytics, and reporting.
Company descriptions Short company descriptions sourced from official or trusted public sources. Add context for analytics, reporting, and AI automation use cases.
Public business links Official website, LinkedIn, and other public business profiles. Connect accounts to official online presence without private data or contact discovery.
Public company contact channels Company-level email addresses and phone numbers when returned by source data. Route account records with public business context without person-level profiles or private contact lists.
CRM field mapping Pre-mapped fields for common CRM and account workflows. Drop-in fields reduce transformation work and speed time to value.
Remote MCP integration Authenticated Streamable HTTP access to the enrich_company tool and structured company results. Use the same team token and credit accounting from compatible AI and MCP clients.

Implementation example for Elvesora Enrichment

Simple APIs, clear responses, and predictable company-level data.

Request

POST /api/v1/enrichment/company
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: enrichment-acmecorp-001
Content-Type: application/json

{
  "domain": "acmecorp.com"
}

Response summary

{
  "success": true,
  "result_type": "ENRICHED",
  "message": "Successfully enriched",
  "data": {
    "company_name": "Acme Corporation",
    "legal_name": "Acme Corporation",
    "domain": "acmecorp.com",
    "website_url": "https://acmecorp.com",
    "industry": "Manufacturing",
    "employee_count": "1,001-5,000",
    "company_size_band": "1001-5000",
    "hq_city": "New York",
    "hq_region": "NY",
    "hq_country": "US",
    "contacts": {
      "emails": ["info@acmecorp.com"],
      "phones": ["+1-212-555-0100"]
    }
  },
  "credits": {
    "limit": 1000,
    "used": 24,
    "remaining": 976,
    "consumed_by_request": 1
  },
  "remaining": 976,
                "limit": 1000
}

This response summary is intentionally shortened and does not show every possible returned field. Review the full response field dictionary in the API docs.

CRM mapping

Enrichment field Example CRM field
company_name Account Name
legal_name Legal Name
domain Website or Domain
website_url Website
industry Industry
sub_industry Sub Industry
sector Sector
employee_count Employee Count
company_size_band Company Size Band
hq_city Billing City
hq_region Billing State/Province
hq_country Billing Country
routing_region Routing Region
company_description Account Description
data_freshness_date Data Freshness Date
RESTful JSON Streamable HTTP MCP Bearer token auth Idempotency-Key support Credit-aware responses

Identity quality before enrichment

Enrichment is safer when the company identity is already clear. If a row starts with only a company name, run Company Domain Lookup first, store confidence and reasons, and enrich only the accepted domain.

Resolve domains first Domain lookup pricing Compare Clearbit View comparison method

Company-level enrichment, not people-data scraping

Elvesora Enrichment adds company-level context such as firmographics, descriptions, headquarters, public links, and public company contact channels when returned. We do not provide people profiles, private contact lists, personal email discovery, or lead generation. This keeps the product boundary at the company level.

  • Company-level data only
  • No people profiles or private contact lists
  • No email finding or verification
  • No lead lists or lead generation

Methodology and sources

How we scope enrichment claims

Enrichment claims are limited to company-level data, public business context, field coverage, and workflow controls visible in the docs and methodology pages. Public company contact channels can be returned, while people profiles, private contact lists, and personal email discovery remain outside the product boundary.

Publisher: Elvesora. Reviewed by Elvesora product team. Last updated August 2, 2026.

Comparison methodology

Review scope, exclusions, field-comparison policy, and evidence rules.

Enrichment API docs

Inspect REST and MCP requests, response fields, idempotency, credits, and webhook outputs.

Pricing guide

Compare pricing models, record volume planning, and operational cost factors.

CRM cleanup solution

Resolve missing domains first, then enrich accepted company records.

Clearbit alternative guide

Compare company data enrichment, domain lookup, and CRM cleanup workflows.

Firmographic Data API

Review the company-level field set for enrichment and segmentation workflows.

Start with company-level context

Get reliable company data into your workflows in minutes.

Get API Key View Pricing View API

Workflows that need verified company context

Use enrichment where routing, segmentation, analytics, and CRM hygiene all depend on stronger company-level inputs.

Company enrichment workflows

See where verified firmographics fit into intake, routing, and account cleanup jobs.

Firmographic Data API

Review the company-level fields, example response, and API workflow for firmographic enrichment.

Frequently asked questions

Common questions about enriching company records with verified firmographic context for CRM and automation workflows.

What data does Elvesora Enrichment add to a record?

Elvesora Enrichment adds verified firmographic context such as industry, headquarters, employee range, descriptions, public links, and other company-level attributes.

When should enrichment run in a CRM workflow?

Run enrichment after a company domain or company identity has been resolved so records receive cleaner context before routing, segmentation, and reporting.

Is Elvesora Enrichment built for API workflows?

Yes. The product is positioned for API and export workflows that need company-level context at intake, during cleanup, or before automation runs.

Can Elvesora identify company leadership from a domain?

No. Elvesora focuses on company-level data enrichment: official domains, firmographics, company descriptions, industry, headquarters, and CRM-ready company records. It does not provide executive profiles, private contact data, or leadership email lists.

Read more about company enrichment

Use these posts to support firmographic implementation, CRM quality programs, and company-level workflow planning.