# Trust Center Compliance Extractor - SOC 2 and ISO API (`changeable_peddler/trust-center-compliance-extractor`) Actor

Extract security, compliance, trust-center, DPA, and subprocessor signals from vendor websites for procurement and vendor-risk workflows.

- **URL**: https://apify.com/changeable_peddler/trust-center-compliance-extractor.md
- **Developed by:** [Sean J](https://apify.com/changeable_peddler) (community)
- **Categories:** Business, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 trust center 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?

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

### What does Trust Center Compliance Extractor do?

Prepare a public vendor-evidence register before requesting private audit documents. This Actor collects trust-centre and security-page references, including available SOC 2, ISO 27001, DPA and subprocessor language. [Open the Actor](https://apify.com/changeable_peddler/trust-center-compliance-extractor) to inspect its input and pricing.

### Start with one website

1. Paste one public URL into the Input tab, preferably the relevant policy or resource page.
2. Keep evidence enabled and set a run spending limit that covers both event fees below.
3. Run the check, then inspect its sources and errors before expanding the list.

Example input with one public source URL checked on 27 October 2026. Current responses and coverage may differ:

```json
{
  "startUrls": [
    {
      "url": "https://www.digitalocean.com/trust"
    }
  ],
  "maxPagesPerSite": 3,
  "concurrency": 1,
  "requestTimeoutSecs": 10,
  "includeEvidence": true
}
```

### Read the evidence

Treat a certification mention as the vendor’s published claim until you inspect an authoritative document. Follow returned trust, DPA and subprocessor sources to confirm their scope and date before recording an assessment.

| Field | How to use it |
|---|---|
| `status`, `confidence` | Signal-detection status and a heuristic score, not a probability of correctness. |
| `findings`, `sourceUrls` | Claim snippets and checked URLs for a reviewer’s evidence register. |
| `findings` | Short source snippets when `includeEvidence` is enabled. |
| `coverage`, `errors` | Request/download limits and problems affecting what was checked. |

Export JSON or CSV with `retrievedAt` and your source notes so a later comparison retains its original context.

### Scope and limits

Phone strings are conservative candidates from visible text or telephone links. Unusual formats and extensions may be omitted; numbers are not verified.

The output does not verify certification, obtain private SOC reports or establish regulatory compliance. Hosted trust portals outside the allowed domain or behind sign-in may not be inspected.

Checks use static public responses, without browser execution or login. Each site is bounded by **20 seconds, 1 MiB downloaded and 4 MiB decoded text**; redirects and failed requests consume `maxPagesPerSite` attempts. Submit at most 100 combined URL/domain entries, including duplicates. An undetected signal is not proof of absence.

### Pricing and spending control

Event fees are **$0.002 per attempt** (`website-processed`) plus **$0.006 per useful report** (`trust-report`): **$0.008** when both apply. Check the Pricing tab for the current rates. The report fee requires `FOUND` or `PARTIAL` with useful detected signals or extracted evidence. Failed or empty resource probes do not qualify; ordinary `NO_SIGNAL`/`FETCH_FAILED` output incurs only the attempt fee.

Budget for both fees before starting a website, and check the Pricing tab for platform terms and plan charges. Review `RUN_SUMMARY` before repeating billing/output uncertainty, because a retry is a new chargeable check.

### Responsible use and support

Use permitted public targets and review their terms. Send a sanitized input through the [Issues tab](https://apify.com/changeable_peddler/trust-center-compliance-extractor/issues) for support or a scope discussion.

# Actor input Schema

## `startUrls` (type: `array`):

Submitted public website URLs. At most 100 entries combined with domains, including duplicates. Checks are limited to public same-domain pages; credentials and nonstandard ports are not accepted.

## `domains` (type: `array`):

Optional public bare domains, one item per company. At most 100 entries combined with startUrls, including duplicates.

## `maxPagesPerSite` (type: `integer`):

Maximum actual HTTP requests per website, including redirects and failed attempts. Work may stop earlier at the shared 20-second deadline, 1 MiB response-body download budget or 4 MiB retained-text budget.

## `concurrency` (type: `integer`):

Number of websites to process in parallel.

## `requestTimeoutSecs` (type: `integer`):

Upper bound in seconds for one request. The remaining overall 20-second website budget can stop it sooner.

## `includeEvidence` (type: `boolean`):

Include source URLs and short snippets explaining detected signals.

## `userAgent` (type: `string`):

HTTP User-Agent used when fetching public website pages.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.digitalocean.com/trust"
    }
  ],
  "domains": [],
  "maxPagesPerSite": 3,
  "concurrency": 1,
  "requestTimeoutSecs": 10,
  "includeEvidence": true,
  "userAgent": "Mozilla/5.0 (compatible; Apify-Website-Intelligence-Actor/1.0; +https://apify.com/)"
}
```

# Actor output Schema

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

One row per input website or domain with signals, evidence, extracted fields, contacts, and risk flags.

## `runSummary` (type: `string`):

Counts for processed, found, partial, failed, and charged events.

# 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 = {
    "startUrls": [
        {
            "url": "https://www.digitalocean.com/trust"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("changeable_peddler/trust-center-compliance-extractor").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 = { "startUrls": [{ "url": "https://www.digitalocean.com/trust" }] }

# Run the Actor and wait for it to finish
run = client.actor("changeable_peddler/trust-center-compliance-extractor").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 '{
  "startUrls": [
    {
      "url": "https://www.digitalocean.com/trust"
    }
  ]
}' |
apify call changeable_peddler/trust-center-compliance-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,changeable_peddler/trust-center-compliance-extractor"
        }
    }
}
```

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/LihcZvQf52ZzzAaKQ/builds/e1dQ26ccwvvLsTihW/openapi.json