Cable · Trust Center

Cable Trust Center

Trust center

Cable maintains a public trust center documenting SOC 2 Type I compliance.

CompanyComplianceFinancial CrimeRegTechAnti-Money LaunderingTransaction MonitoringScreeningRisk AssessmentBankingFintech
Trust center: https://cable.tech/security

Certifications & Compliance

SOC 2 Type I

Source

Trust Center

Raw ↑ 
generated: '2026-07-18'
method: searched
probe: true
source: https://cable.tech/security
url: https://cable.tech/security
certifications:
- SOC 2 Type I
compliance_frameworks_supported:
- US Bank Secrecy Act
- UK Money Laundering Regulations
- Bermuda Financial Crime Regulations
- Ireland Criminal Justice Act
- Reg E (EFTA)
- Reg B (ECOA)
- Reg Z (TILA)
- UDAAP
notes: >-
  Cable states it is SOC 2 Type I certified on its security page. No ISO 27001, PCI DSS,
  HIPAA, or FedRAMP certification is claimed, and GDPR is not asserted as a held certification.
  The regulatory frameworks listed are the compliance frameworks Cable's product tests customer
  activity against, not certifications held by Cable itself.
evidence:
- source: https://cable.tech/security
  keywords:
  - soc 2 type i

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/cable-trust-center"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.