git:20260813.48597a3 to git:20260908.495293d

5 added, 5 removed. Audit A to A.

---

name: data-enrichment

description: "Enrich any entity — companies, domains, emails, or people — with verified data from multiple sources. Combines Apollo, Strale, LinkedIn, and Akta data to fill gaps in your CRM, lead databases, or research datasets with production-quality enrichment."

---

# Data Enrichment

Enrich any entity — companies, domains, emails, or people — with verified data from multiple sources. Combines Apollo, Strale, LinkedIn, and Akta data to fill gaps in your CRM, lead databases, or research datasets with production-quality enrichment. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

- For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`.

+ Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

- ## Available Tools

+ ## Capability identifiers

- `apollo_company_enrich`

- `strale_company_enrich`

- `strale_email_validate`

- `strale_whois_lookup`

- `linkedin_web_v2_company_profile`

- `akta_company_enrichment`

## Workflow

1. Understand the user's research question, target, and context.

- 2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema.

- 3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments.

+ 2. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.

+ 3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.

4. Synthesize findings into a clear, evidence-backed answer.

5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- - Always call `sandbase_describe_tool` before using any capability.

+ - Always call `sandbase_inspect` before using any capability.

- Cite sources and preserve attribution (URLs, usernames, dates, metrics).

- Separate factual observations from analysis and recommendations.

- If data is unavailable, note the gap and continue with available evidence.

- Read-only research only. Never take actions on platforms.