Collects a company's stated security and compliance posture: SOC 2, ISO 27001, HIPAA and GDPR claims with the page and quote that state them, its trust center, security.txt, bug-bounty or disclosure policy, DMARC policy and HSTS.
curl -X POST "https://api.primaryapi.com/v1/run/company.trust_profile" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"vercel.com"}'{
"output": {
"found": true,
"data": {
"httpsHomepage": true,
"domain": "example.com",
"trustCenter": {
"platform": "safebase",
"url": "https://trust.example.com/"
},
"claims": [
{
"framework": "iso27001",
"label": "ISO/IEC 27001",
"status": "claimed",
"statedOn": "https://trust.example.com/", …
}, …
], …
}
},
"credits": 1
}Input and output
2 fields
vercel.com.9 fields
Good to know
Claims are reported exactly as the pages state them, never inferred. A framework the pages do not name is simply absent, and an absent claim does not mean the company lacks it (many publish reports only on request).
Trust centers that render only in a browser are reported without claims.
A domain that does not resolve is a free miss. A miss is an answer, not an error, and it costs nothing.
Outputs are stable between runs of an unchanged page (sorted lists, normalised whitespace, no timestamps). So the API can be scheduled as a monitor that fires only when the content changes.
More from Company. Same key, same credits.
The same key and credits work for every API.