# Company Contact Proof — Website Email & Contact API (`hadi.kanj/company-contact-proof`) Actor

Extract public business emails, phone links and social profiles with source-page evidence. Review contacts before CRM import. Up to five same-origin pages; no guessed emails or mailbox verification. Demo: https://market-data-gateway-production-2084.up.railway.app/launch/company-contact-proof

- **URL**: https://apify.com/hadi.kanj/company-contact-proof.md
- **Developed by:** [Hadi Kanj](https://apify.com/hadi.kanj) (community)
- **Categories:** Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 scanned domains

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

## Company Contact Proof

Extract public business emails, phones and social profiles with page evidence.

### Start here

```json
{
  "urls": [
    "https://crawlee.dev"
  ],
  "maxPages": 3,
  "stateKey": "my-monitor"
}
```

Run once, inspect the dataset and SUMMARY, then schedule repeat checks using the same monitor name.

### Supported scope

Up to five same-origin contact/about pages, including supplied hints. Explicit \[at]/\[dot] decoding, role inboxes, affiliation labels and optional MX DNS checks. No guessed addresses, SMTP tests, image OCR or owner identification.

Every row carries source evidence and observedAt. Publisher evidence is not a guarantee of real-world correctness. Blocked, failed, capped and malformed sources are explicit, not silently fabricated results. HTTP-only: JavaScript-only facts may be absent. Source data and image URLs are not a grant of republication rights.

### Monitoring

FIRST_OBSERVATION, NEW_RECORD and UPDATED describe observed records. Changes include before-values and changedFields; SEO includes newly introduced issues. Technology disappearance needs two successful checks and only confirms missing signals, not uninstallation. Event and TED histories preserve up to 5,000 observed identities; disappearance from a finite source window is not deletion. Revision links require the same official notice identifier, not merely a similar title or procedure. Partial/failed/budget-stopped scans never replace the baseline. Don't overlap runs of the same named monitor.

### Cost

$0.005 per run start plus $0.003 per observed domain ($3/1,000), platform usage included under Apify PPE. Unchanged observed records count even with onlyChanges enabled. Failed sources have no record charge. Readable contacts/technology pages with no matches are still observed records; an event page containing no structured event produces no event charge. Configure max run cost; budget-stopped runs preserve history.

### API integration

POST https://api.apify.com/v2/acts/hadi.kanj~company-contact-proof/runs with your own Authorization: Bearer APIFY_TOKEN and JSON body. Poll /v2/actor-runs/{id}, retrieve /v2/datasets/{defaultDatasetId}/items and /v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY. Use /run-sync-get-dataset-items for short runs; asynchronous runs are safer for bulk inputs.

Export JSON for nested evidence, or CSV/Excel for tables. Use Apify schedules, webhooks, Make or n8n to retrieve completed results. No outbound email or messages are sent by this Actor.

### Status and limits

complete describes the requested fetched source scope, not the entire internet or all company pages. Inspect errors, pagesFetched/requests and observedRecords. Public HTTP(S) only, ordinary ports, protected DNS and redirects, robots rules and crawl delay, two MB HTML and eight MB TED response limits. Up to 100 URLs per Actor run, five contact pages/domain and 1,000 events/notices per source.

### Support

Open an Actor issue with a public source URL, expected field and run link. Never post API keys or private client data.

# Actor input Schema

## `stateKey` (type: `string`):

Repeat this name for account-isolated history. Failed, partial and budget-stopped scans do not replace history.

## `onlyChanges` (type: `boolean`):

All observed records are still billed; suppressed unchanged output does not avoid charges.

## `urls` (type: `array`):

1–100 public HTTP URLs. No authenticated or blocked content bypass.

## `maxPages` (type: `integer`):

Prioritize linked contact/about pages; the cap is reported in completeness.

## `contactHints` (type: `array`):

Same-origin URLs, prioritized after the home page.

## `checkMx` (type: `boolean`):

DNS presence only, not mailbox deliverability.

## Actor input object example

```json
{
  "stateKey": "default",
  "onlyChanges": false,
  "urls": [
    "https://crawlee.dev"
  ],
  "maxPages": 5,
  "checkMx": false
}
```

# Actor output Schema

## `records` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {
    "urls": [
        "https://crawlee.dev"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hadi.kanj/company-contact-proof").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 = { "urls": ["https://crawlee.dev"] }

# Run the Actor and wait for it to finish
run = client.actor("hadi.kanj/company-contact-proof").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 '{
  "urls": [
    "https://crawlee.dev"
  ]
}' |
apify call hadi.kanj/company-contact-proof --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hadi.kanj/company-contact-proof"
        }
    }
}
```

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/SYwIi8jFDtLETl5q7/builds/ZAaw79RCgVkDPjoZN/openapi.json