Company Enrichment — Website Metadata

Turn one company domain into source-backed website metadata candidates for CRM review, research queues, and automation workflows. The Actor returns only a validated result produced from a successful website scrape. It does not return authoritative registry data and does not make eligibility, credit, compliance, or outreach decisions.

Quick start

{
  "domain": "example.com"
}

Use one bare domain without a scheme, port, path, credentials, wildcard, or spaces. Batch input, email lookup, arbitrary actions, and nested payloads are intentionally unsupported.

Output

A successful run writes exactly one item to the default dataset:

{
  "success": true,
  "domain": "example.com",
  "website": "https://example.com/",
  "nameCandidate": "Example Domain",
  "description": "Example website metadata when available",
  "industryCandidate": null,
  "provenance": {
    "method": "website_metadata_scrape",
    "sourceUrl": "https://example.com/",
    "caveat": "Candidate fields are not authoritative registry data."
  },
  "integrationSource": "apify-store",
  "observedAt": "2026-07-28T00:00:00.000Z"
}

Treat nameCandidate and industryCandidate as review candidates, not verified facts. Recheck important fields against an authoritative source before writing to a production CRM.

Data truth boundary

Current builds do not generate simulated company size, location, founding year, financial, social, or technology fields. Builds before 1.1.1 may have returned estimated fields and should not be used as evidence. Every successful current result must identify website_metadata_scrape, its public source URL, and the candidate-data caveat in provenance; the dataset schema rejects output that does not satisfy that contract.

If the website cannot be scraped, the upstream response is unauthenticated, invalid, estimated-only, too large, or unsuccessful, the run fails and writes no dataset item. The Actor performs one upstream request and never retries an ambiguous failure automatically.

Pricing and cost control

The current Store price is US$0.005 per valid dataset result. Apify also lists a small Actor-start event. A failed run can therefore have a platform start charge even though this Actor does not write or charge a result item. Always check the live Pricing tab because Store pricing is the source of truth.

For synchronous REST calls, keep the Apify token in a secret manager and cap the response and total run charge:

curl --request POST \
  'https://api.apify.com/v2/acts/vivid_astronaut~company-enrichment/run-sync-get-dataset-items?maxItems=1&maxTotalChargeUsd=0.02' \
  --header 'Authorization: Bearer YOUR_SCOPED_APIFY_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{"domain":"example.com"}'

Attribution labels

Published Brainiall integrations send one of these fixed labels:

• apify-store — direct Store or API use; this is the default.
• apify-mcp — Apify MCP use.
• daggerverse-c9 — Brainiall Dagger module.
• github-action-c9 — Brainiall GitHub Action.
• n8n-github-c9 — Brainiall n8n workflow.
• kestra-c19 — Brainiall Kestra blueprint.
• apify-task-c19 — public Apify Task example.

The label is caller-supplied telemetry. It distinguishes integration routes but does not establish buyer identity, payment, payout, settlement, or revenue.

MCP setup

Apify exposes the Actor through its hosted Streamable HTTP MCP server:

{
  "mcpServers": {
    "brainiallCompanyMetadata": {
      "url": "https://mcp.apify.com/?tools=vivid_astronaut/company-enrichment",
      "headers": {
        "Authorization": "Bearer YOUR_SCOPED_APIFY_TOKEN"
      }
    }
  }
}

Keep the token in the MCP client's secret storage. Actor and Apify charges can apply to MCP runs.

Ready-made integrations

• GitHub Action and n8n workflow
• Dagger module

Security behavior

• One top-level domain per run; unknown fields are rejected.
• A dedicated encrypted Actor environment variable authenticates the upstream.
• Credentials are sent only to a fixed HTTPS origin and redirects are rejected.
• The Actor runtime logs event names, timing, and the integration label only; it does not log inputs, domains, upstream bodies, results, or credentials.
• Responses are size-bounded and schema-checked before any dataset write.
• Failures write zero dataset items; only a validated source-backed result is eligible for the result event.
• The public dataset view exposes only website-derived candidates and their observation context; it does not expose or recreate the removed estimates.

Support

Open an Actor issue with the run ID and the stable error code. Do not include an Apify token, upstream credential, customer record, or private company data.