Cable
Cable is an automated compliance and financial-crime assurance platform for banks, fintechs, and crypto companies. Based on transaction, customer, screening, risk-assessment, and onboarding data you send it, Cable continuously tests 100% of activity against your regulatory frameworks (US Bank Secrecy Act, UK Money Laundering Regulations, Reg E/B/Z, UDAAP, and others) to detect any single instance of control failure or regulatory breach, replacing manual dip-sampling. The Cable API is primarily a data-ingestion surface: a REST entry point for transferring raw data from your systems into Cable's analysis environment, with resource-oriented URLs, JSON request/response bodies, token-based authentication, and standard HTTP verbs and status codes. Cable is backed by Anthemis and CRV.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Cable the way a machine reads it — 26 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cable scores 53.4/100 (developing), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Cable
Each block below is one kind of artifact we hold for Cable. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cable alerts API
The alerts API from Cable — 1 operation(s) for alerts.
Cable authentication API
The authentication API from Cable — 2 operation(s) for authentication.
Cable business API
The business API from Cable — 9 operation(s) for business.
Cable checks API
The checks API from Cable — 1 operation(s) for checks.
Cable company API
The company API from Cable — 1 operation(s) for company.
Cable customerSar API
The customerSar API from Cable — 1 operation(s) for customersar.
Cable helper API
The helper API from Cable — 1 operation(s) for helper.
Cable identityVerification API
The identityVerification API from Cable — 1 operation(s) for identityverification.
Cable onboardingFlow API
The onboardingFlow API from Cable — 1 operation(s) for onboardingflow.
Cable person API
The person API from Cable — 1 operation(s) for person.
Cable retail API
The retail API from Cable — 8 operation(s) for retail.
Cable riskAssessment API
The riskAssessment API from Cable — 1 operation(s) for riskassessment.
Cable screening API
The screening API from Cable — 2 operation(s) for screening.
Cable suspiciousActivities API
The suspiciousActivities API from Cable — 1 operation(s) for suspiciousactivities.
Cable transactionAlerts API
The transactionAlerts API from Cable — 1 operation(s) for transactionalerts.
Cable transactionChecks API
The transactionChecks API from Cable — 1 operation(s) for transactionchecks.
Cable transactions API
The transactions API from Cable — 4 operation(s) for transactions.
Cable transactionSuspiciousActivities API
The transactionSuspiciousActivities API from Cable — 1 operation(s) for transactionsuspiciousactivities.
Cable upload API
The upload API from Cable — 1 operation(s) for upload.
Cable utilities API
The utilities API from Cable — 1 operation(s) for utilities.
Scroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
cable-mcp.yml
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Cable — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/cable · machine-readable index on apis.io