ClientSuccess

ClientSuccess provides a comprehensive customer success platform that helps businesses reduce churn, increase revenue, and deliver world‑class customer experiences. The SaaS solution combines AI‑driven insights, automation, and a unified portal for onboarding, journey management, and analytics, enabling teams to act on real‑time health scores, NPS, and product feedback. It integrates with major CRMs and support tools, offering a scalable, data‑driven approach to customer lifecycle management.

ClientSuccess is profiled on the APIs.io network. Tagged areas include Customer Success, SaaS, AI, Analytics, and Integration.

ClientSuccess’ developer surface includes signup flow, documentation, API reference, getting-started guide, support, engineering blog, pricing, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub
28.6/100 thin Agent 3/100 human only Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0
0 APIs
Customer SuccessSaaSAIAnalyticsIntegration

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0
Composite quality — 28.6/100 · thin
Contract Quality 0.0 / 21
Developer Ergonomics 6.9 / 17
Access Clarity 10.3 / 17
Operational Transparency 0.6 / 11
Contract Governance 1.7 / 10
Discoverability 4.1 / 9
Regulatory Posture 3.3 / 15
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/clientsuccess: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Clientsuccess Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Clientsuccess Trust Center

SOC 2, ISO 27001, HIPAA, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp
SignUp
 GettingStarted
GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Postman
Postman

Access & Security 4

Authentication, authorization, and security posture

Compliance
Compliance
 SecurityTxt
SecurityTxt
 TrustCenter
TrustCenter
 DomainSecurity
DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support
Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 2

Properties that don't map to a standard resource type

Hosts
Hosts
 Vendors
Vendors

Source (apis.yml)

apis.yml Raw ↑ 
aid: clientsuccess
name: ClientSuccess
image: https://www.clientsuccess.com/images/cs-og-image.jpg
description: ClientSuccess provides a comprehensive customer success platform that helps businesses reduce churn, increase
  revenue, and deliver world‑class customer experiences. The SaaS solution combines AI‑driven insights, automation, and a
  unified portal for onboarding, journey management, and analytics, enabling teams to act on real‑time health scores, NPS,
  and product feedback. It integrates with major CRMs and support tools, offering a scalable, data‑driven approach to customer
  lifecycle management.
url: https://raw.githubusercontent.com/api-evangelist/clientsuccess/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-09 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-08'
modified: '2026-10-08'
tags:
- Customer Success
- SaaS
- AI
- Analytics
- Integration
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Compliance
  url: https://www.clientsuccess.com/security-compliance
- type: Conformance
  url: conformance/clientsuccess-conformance.yml
- type: LLMsTxt
  url: llms/clientsuccess-llms.txt
- type: SecurityTxt
  url: well-known/clientsuccess-help-security.txt
- type: WellKnown
  url: well-known/clientsuccess-well-known.yml
- type: Hosts
  url: hosts/clientsuccess-hosts.yml
- type: Vendors
  url: vendors/clientsuccess-vendors.yml
- type: SignUp
  url: https://www.clientsuccess.com/resources/sign-up-to-win-a-duffel-bag
- type: GitHubOrganization
  url: https://github.com/ClientSuccess
- type: TrustCenter
  url: security/clientsuccess-trust-center.yml
- type: DomainSecurity
  url: security/clientsuccess-domain-security.yml
- type: Website
  url: https://www.clientsuccess.com/
- type: Documentation
  url: https://www.clientsuccess.com/platform/insights-and-analytics
- type: APIReference
  url: https://www.clientsuccess.com/mcp
- type: GettingStarted
  url: https://www.clientsuccess.com/get-started
- type: Support
  url: https://www.clientsuccess.com/contact
- type: Blog
  url: https://www.clientsuccess.com/categories/blog
- type: Pricing
  url: https://www.clientsuccess.com/pricing
- type: TermsOfService
  url: https://www.clientsuccess.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.clientsuccess.com/privacy-policy
- type: Postman
  url: https://www.postman.com/clientsuccess/workspace
apis: []
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Provider docs at https://www.clientsuccess.com/mcp return HTML with no machine‑readable OpenAPI or other contract.
  evidence:
  - url: https://www.clientsuccess.com/mcp
    status: 200
  checked: '2026-10-09'
x-enrichment:
  date: '2026-10-09'
  status: enriched
  artifacts_added: 11
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider 
curl "https://apis.io/api/v1/providers/clientsuccess"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/clientsuccess/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/clientsuccess/evidence"

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.