Trust Center Compliance Extractor - SOC 2 and ISO API
Pricing
from $6.00 / 1,000 trust center reports
Trust Center Compliance Extractor - SOC 2 and ISO API
Extract security, compliance, trust-center, DPA, and subprocessor signals from vendor websites for procurement and vendor-risk workflows.
Pricing
from $6.00 / 1,000 trust center reports
Rating
0.0
(0)
Developer
Sean J
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
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 to inspect its input and pricing.
Start with one website
- Paste one public URL into the Input tab, preferably the relevant policy or resource page.
- Keep evidence enabled and set a run spending limit that covers both event fees below.
- 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:
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 for support or a scope discussion.
