# Business Website Enricher (`eichan/business-website-enricher`) Actor

- **URL**: https://apify.com/eichan/business-website-enricher.md
- **Developed by:** [Eichan Jolly](https://apify.com/eichan) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Business Website Enricher

### What it does

Enriches **one user-provided official public business domain** from its homepage. It extracts an organization name, description, and (if explicitly declared) company logo URL using schema.org Organization/LocalBusiness JSON-LD, Open Graph metadata, HTML description, and page title. It does **not** discover leads, search engines, people, or additional pages.

### Who it is for

B2B sales ops, CRM data quality teams, and market researchers updating basic company profiles from official sources.

### Input example (one domain)

```json
{"domain":"example.com"}
```

The Apify input form prefills only `example.com`. Production use should substitute the official business's domain. Bare domains and domain-only `https://` URLs work; paths, ports, IP addresses, and logins do not.

### Output example

This example illustrates the *field structure* and is not a claim that the example domain contains this data.

```json
{
  "domain": "sample-business.example",
  "company_name": "Sample Business",
  "description": "Sample Business provides commercial building services.",
  "logo_url": "https://sample-business.example/assets/logo.png",
  "source_url": "https://sample-business.example/",
  "status": "ok",
  "error": null
}
```

Missing fields are `null`, not guesses. `status` is `ok` if any profile field is found or `no_data` if none is found. Input/network/robots errors produce a plain-language log message with nonzero exit code and **no result item**; tracebacks are suppressed.

### Limits and source policy

- **One domain, one homepage** per run; up to 1 MB of HTML, three same-site redirects, and nine seconds per HTTP request.
- Official public pages only: no login, LinkedIn, personal-data collection, search engine use, headless browser, or JavaScript rendering.
- HTTPS first; HTTP is attempted only if HTTPS fails at the connection layer. Apex/`www` redirects only. Private/non-public DNS addresses, IP literals, unusual ports, off-site redirects, and non-HTML pages are blocked.
- `robots.txt` is checked before homepage retrieval; if it disallows access or cannot be checked (except 404/410), retrieval stops. DNS is checked before requests, but this is not a hardened network-isolation boundary against DNS rebinding; deploy with network egress restrictions when processing untrusted domains.
- Structured data can be missing, inaccurate, or outdated. `logo_url` is recorded only from explicit JSON-LD `logo`, never inferred from a generic image. No human review or company identity verification is performed.
- Captures corporate fields only, not personal email addresses or individual contacts. Does not crawl subpages.

### Apify configuration and dataset

This folder is an independently deployable Actor project. `.actor/actor.json` references the root `input_schema.json`. The main script uses the **Apify REST API** directly (no SDK) to read `INPUT` from the run's default key-value store and push one JSON record to the default dataset. It honors `APIFY_API_BASE_URL`, `APIFY_INPUT_KEY`, `APIFY_DEFAULT_KEY_VALUE_STORE_ID`, `APIFY_DEFAULT_DATASET_ID`, and `APIFY_TOKEN` when `APIFY_IS_AT_HOME=true`. Authorization is sent by bearer header, not in URLs.

For local testing, create `storage/key_value_stores/default/INPUT.json` with the input above, then run:

```bash
python src/main.py
```

Or use `ACTOR_INPUT_JSON='{"domain":"example.com"}' python src/main.py`. Local results are appended to `storage/datasets/default/000000001.json` (or the next available numeric file). In Docker, mount the `storage` directory at `/usr/src/app/storage` for local testing. The `storage` directory is not included in this source deliverable.

### Store placement and suggested pricing

**Suggested Apify Store categories (max 3):** Generate leads · Enrich company profiles · Company research. These are placement recommendations, not unsupported properties in `actor.json`; Apify is transitioning to platform-assigned category classification.

**Suggested monetization:** Pay per event (PPE), synthetic `apify-default-dataset-item`, **$0.004 per emitted dataset item** (~**$4 per 1,000 items**), plus an optional small actor-start fee if needed to cover run overhead. Set pricing in the Apify Console: this source package does not activate monetization. Each successful/no-data row is an item; errors emit no item. At one item per run, verify economics against actual run costs before Store publication. Do not assume this is a published or live rate.

# Actor input Schema

## `domain` (type: `string`):

Exactly one public company domain; no login, paths, IPs, credentials, or custom ports.

## Actor input object example

```json
{
  "domain": "example.com"
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset containing the Actor's result items

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domain": "example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("eichan/business-website-enricher").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domain": "example.com" }

# Run the Actor and wait for it to finish
run = client.actor("eichan/business-website-enricher").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domain": "example.com"
}' |
apify call eichan/business-website-enricher --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eichan/business-website-enricher"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/c6um8CrZ6AuTXPd66/builds/AfZeRG0WQhLjodiox/openapi.json