# Cross-Border Supplier Trust Verifier (`aieast/cross-border-supplier-trust-verifier`) Actor

Turn official supplier websites into source-linked procurement pre-screen reports covering visible business identity, product fit, public contactability, supplier-claimed certifications, export readiness, and red flags.

- **URL**: https://apify.com/aieast/cross-border-supplier-trust-verifier.md
- **Developed by:** [Aden](https://apify.com/aieast) (community)
- **Categories:** E-commerce, Business, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$500.00 / 1,000 evidence-backed supplier risk reports

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Cross-Border Supplier Trust Verifier

Pre-screen supplier websites before sourcing, outreach, or procurement. The Actor turns public supplier-controlled pages into a compact, source-linked risk report covering business identity, contactability, product fit, certification claims, export readiness, and visible red flags.

### What you get

- A 0–100 public-web trust score and lower / medium / higher risk band
- Business identity evidence with the exact source page
- Role-based public business emails displayed by the supplier
- Requested product or capability matches
- Supplier-claimed certifications clearly labelled as unverified claims
- OEM, ODM, MOQ, export, shipping, Incoterms, and manufacturing signals
- Missing-evidence warnings and practical next-step guidance
- Every inspected evidence page listed in the output

### What this is not

This is a fast public-web pre-screen, not official registry, beneficial-ownership, sanctions, legal, financial, or certificate verification. A polished website is never proof of delivery capability. Before placing an order, independently verify the company in the relevant registry, confirm certificates with the issuer, order samples, inspect the facility when proportionate, and use protected payment terms.

### Input

```json
{
  "supplierUrls": ["https://supplier.example"],
  "productKeywords": ["battery", "OEM"],
  "countryHint": "China",
  "requireBusinessIdentity": true,
  "minEvidencePages": 2,
  "maxResults": 10
}
```

### Output

Each paid dataset item is a completed evidence-backed supplier report. Important fields include:

- `trustScore`, `riskLevel`, `confidence`
- `identitySignals`
- `productMatches`
- `publicBusinessEmails`
- `certificationClaims`
- `exportSignals`, `positiveSignals`, `redFlags`
- `evidencePages`, `assessment`, `limitations`

### Pricing and failure policy

The Actor charges once per delivered `supplier-report`. Unreachable sites, non-HTML targets, fetch failures, and targets that do not meet the requested evidence threshold are free. The `maxResults` input is a hard cap on paid reports.

### Privacy and responsible use

The Actor inspects public supplier-controlled pages only. It does not log in, bypass access controls, or collect personal profiles. Public contact extraction is limited to role-based business email evidence. Local, private, and reserved network targets are blocked. Use the output for lawful procurement research and human-reviewed decisions.

# Actor input Schema

## `supplierUrls` (type: `array`):

Official supplier homepages, one per line. Public company pages only; no logins or personal profiles.

## `productKeywords` (type: `array`):

Optional product or capability terms, for example power station, CNC, textile, OEM, or battery. Empty means no product-fit gate.

## `countryHint` (type: `string`):

Optional buyer-provided expectation such as China, Vietnam, Germany, or Mexico. It is reported as a hint, not treated as verified location.

## `requireBusinessIdentity` (type: `boolean`):

When enabled, a paid report requires a legal/company name, registration identifier, structured organization record, or physical business address on the inspected site.

## `minEvidencePages` (type: `integer`):

Minimum number of accessible same-site pages required before a report can be delivered and charged.

## `maxResults` (type: `integer`):

Hard cap on delivered supplier reports. Failed or insufficient-evidence targets are free.

## Actor input object example

```json
{
  "supplierUrls": [
    "https://www.anker-in.com/",
    "https://www.dji.com/"
  ],
  "productKeywords": [],
  "requireBusinessIdentity": true,
  "minEvidencePages": 2,
  "maxResults": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `dataset` (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 = {
    "supplierUrls": [
        "https://www.anker-in.com/",
        "https://www.dji.com/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("aieast/cross-border-supplier-trust-verifier").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 = { "supplierUrls": [
        "https://www.anker-in.com/",
        "https://www.dji.com/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("aieast/cross-border-supplier-trust-verifier").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 '{
  "supplierUrls": [
    "https://www.anker-in.com/",
    "https://www.dji.com/"
  ]
}' |
apify call aieast/cross-border-supplier-trust-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aieast/cross-border-supplier-trust-verifier"
        }
    }
}

```

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/AYa09ZL10hIVXcITU/builds/QVZcLrpTAbyaQ4d5h/openapi.json