Vitally

Vitally is an AI-powered Customer Success platform (CSP) that unifies customer data, health scores, and revenue context with workflow automation — Hubs, automated Playbooks, Docs, Projects, and NPS and custom surveys — plus Vitally AI (Copilot, Summaries, Meeting Recorder). Its public REST API exposes the core Customer Success objects (accounts, organizations, users, tasks, notes, conversations, NPS responses, custom objects) over HTTP Basic auth with cursor pagination and RateLimit headers, and an official remote MCP server (Beta) connects MCP-compatible AI clients to a Vitally workspace.

Vitally is listed with 9 APIs on the APIs.io network, including Accounts API, Admins API, Conversations API, and 6 more. Tagged areas include Company, Customer Success, Software-as-a-Service, CRM, and NPS.

The Vitally catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

61.8/100 strong ▬ flat Agent 56/100 agent ready Front door AI 6/6 dominant Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

9 APIs 1 MCP Servers 3 Agent Skills

Company Customer Success Software-as-a-Service CRM NPS Surveys Analytics Artificial Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 61.8/100 · strong

Contract Quality 4.6 / 19

Developer Ergonomics 8.7 / 15

Access Clarity 13.8 / 15

Operational Transparency 6.9 / 10

Contract Governance 2.9 / 9

Discoverability 6.0 / 8

Regulatory Posture 4.9 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 56/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vitally/"><img src="https://apis.io/badge/vitally/card.svg" alt="Vitally on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter

2 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 24.4 — up to +18.9 composite points
Developer Ergonomics scores 57.7 — up to +8.5 composite points
Contract Governance scores 31.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/vitally/apis.yml: open an issue on github.com/api-evangelist/vitally to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Surveys, Market Research and Experience Management	builds-on	38.8	-	-
Intercom App Store (customer-support, chat and messaging integrations)	builds-on	38.8	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Vitally Accounts API

The Accounts API from Vitally — 3 operation(s) for accounts.

Vitally Admins API

The Admins API from Vitally — 1 operation(s) for admins.

Vitally Conversations API

The Conversations API from Vitally — 1 operation(s) for conversations.

Vitally Custom Objects API

The Custom Objects API from Vitally — 1 operation(s) for custom objects.

Vitally Notes API

The Notes API from Vitally — 2 operation(s) for notes.

Vitally NPS Responses API

The NPS Responses API from Vitally — 2 operation(s) for nps responses.

Vitally Organizations API

The Organizations API from Vitally — 2 operation(s) for organizations.

Vitally Tasks API

The Tasks API from Vitally — 2 operation(s) for tasks.

Vitally Users API

The Users API from Vitally — 3 operation(s) for users.

Scroll for all 9

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Vitally REST Accounts API

OPEN COLLECTION

Vitally REST Accounts Admins API

OPEN COLLECTION

Vitally REST Accounts Conversations API

OPEN COLLECTION

Vitally REST Accounts Custom Objects API

OPEN COLLECTION

Vitally REST Accounts Notes API

OPEN COLLECTION

Vitally REST Accounts NPS Responses API

OPEN COLLECTION

Vitally REST Accounts Organizations API

OPEN COLLECTION

Vitally REST Accounts Tasks API

OPEN COLLECTION

Vitally REST Accounts Users API

OPEN COLLECTION

Scroll for all 9

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Vitally MCP Server

Vitally operates an official remote MCP (Model Context Protocol) server (Beta) that connects any MCP-compatible AI client (Claude, ChatGPT, Cursor) to a Vitally workspace. Authe...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Find at-risk accounts and summarize activity

AGENT SKILL

Log a follow-up task on an account

AGENT SKILL

Sync an account and its users

AGENT SKILL

Vitally API pricing

Prices published by Vitally, read 2026-10-07 from www.vitally.io/pricing.

Plan	Price
Tech-Touch	Request Pricing Includes: Designed for scaling with one-to-many & PLG Customer Success.
Hybrid-Touch	Request Pricing Includes: Designed for scaling with any model of Customer Success.
High-Touch	Request Pricing Includes: Designed for scaling with one-to-one Customer Success. UNLIMITED FULL SEATS

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Vitally Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Vitally Rate Limits

1 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Vitally

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Vitally Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Vitally Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Vitally API Rules

58 rules · 55 errors 1 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Vitally Rest Overlay

3 actions · update · vitally-rest-openapi.yml

DERIVED

Security Posture 4

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

Vitally Authentication

http · 1 scheme

SECURITY

Vitally Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Vitally Vulnerability Disclosure

no policy recorded

SECURITY

Vitally Trust Center

SOC 2, GDPR

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Vitally Agentic Access

31 operations · 14 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

AgenticAccess

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Components

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

Packages

Packages

SDKs

SDKs

Access & Security 6

Authentication, authorization, and security posture

Authentication

Compliance

Security

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: vitally
name: Vitally
description: Vitally is an AI-powered Customer Success platform (CSP) that unifies customer data, health scores, and revenue
  context with workflow automation — Hubs, automated Playbooks, Docs, Projects, and NPS and custom surveys — plus Vitally
  AI (Copilot, Summaries, Meeting Recorder). Its public REST API exposes the core Customer Success objects (accounts, organizations,
  users, tasks, notes, conversations, NPS responses, custom objects) over HTTP Basic auth with cursor pagination and RateLimit
  headers, and an official remote MCP server (Beta) connects MCP-compatible AI clients to a Vitally workspace.
url: https://raw.githubusercontent.com/api-evangelist/vitally/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/63d3e5f547ca0a274b2e07e1/65456c4b07c63e23bfaedbea_logo-vitally.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- techstars
x-tier: enriched
x-tier-reason: portfolio-lead
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 4
  pass: local-v1
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Customer Success
- Software-as-a-Service
- CRM
- NPS
- Surveys
- Analytics
- Artificial Intelligence
tags_raw:
- Company
- Customer Success
- SaaS
- CRM
- NPS
- Surveys
- Analytics
- Artificial Intelligence
apis:
- aid: vitally:vitally-accounts-api
  name: Vitally Accounts API
  description: The Accounts API from Vitally — 3 operation(s) for accounts.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/vitally-accounts-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-admins-api
  name: Vitally Admins API
  description: The Admins API from Vitally — 1 operation(s) for admins.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Admins
  properties:
  - type: OpenAPI
    url: openapi/vitally-admins-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-conversations-api
  name: Vitally Conversations API
  description: The Conversations API from Vitally — 1 operation(s) for conversations.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Conversations
  properties:
  - type: OpenAPI
    url: openapi/vitally-conversations-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-custom-objects-api
  name: Vitally Custom Objects API
  description: The Custom Objects API from Vitally — 1 operation(s) for custom objects.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Custom Objects
  properties:
  - type: OpenAPI
    url: openapi/vitally-custom-objects-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-notes-api
  name: Vitally Notes API
  description: The Notes API from Vitally — 2 operation(s) for notes.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Notes
  properties:
  - type: OpenAPI
    url: openapi/vitally-notes-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-nps-responses-api
  name: Vitally NPS Responses API
  description: The NPS Responses API from Vitally — 2 operation(s) for nps responses.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - NPS Responses
  properties:
  - type: OpenAPI
    url: openapi/vitally-nps-responses-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-organizations-api
  name: Vitally Organizations API
  description: The Organizations API from Vitally — 2 operation(s) for organizations.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Organization
  tags_raw:
  - Organizations
  properties:
  - type: OpenAPI
    url: openapi/vitally-organizations-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-tasks-api
  name: Vitally Tasks API
  description: The Tasks API from Vitally — 2 operation(s) for tasks.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - Task
  tags_raw:
  - Tasks
  properties:
  - type: OpenAPI
    url: openapi/vitally-tasks-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- aid: vitally:vitally-users-api
  name: Vitally Users API
  description: The Users API from Vitally — 3 operation(s) for users.
  humanURL: https://docs.vitally.io/en/articles/9880649-rest-api-overview
  baseURL: https://rest.vitally.io/resources
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/vitally-users-api-openapi.yml
  - type: Documentation
    url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/vitally/overview
- type: Plans
  url: plans/vitally-plans-pricing.yml
- type: Overlay
  url: overlays/vitally-rest-overlay.yaml
- type: Website
  url: https://vitally.io/
- type: Documentation
  url: https://docs.vitally.io/
- type: APIReference
  url: https://docs.vitally.io/en/articles/9880649-rest-api-overview
- type: GettingStarted
  url: https://docs.vitally.io/en/articles/11048953-getting-started-with-vitally-as-an-admin
- type: Support
  url: https://docs.vitally.io/
- type: Blog
  url: https://www.vitally.io/blog
- type: Pricing
  url: https://www.vitally.io/pricing
- type: SignUp
  url: https://www.vitally.io/demo-request
- type: Login
  url: https://login.vitally.io
- type: TermsOfService
  url: https://www.vitally.io/terms-conditions
- type: PrivacyPolicy
  url: https://www.vitally.io/privacy-policy
- type: StatusPage
  url: https://vitally.statuspage.io
- type: ChangeLog
  url: changelog/vitally-changelog.yml
- type: MCPServer
  url: mcp/vitally-mcp.yml
- type: LLMsTxt
  url: llms/vitally-llms.txt
- type: Authentication
  url: authentication/vitally-authentication.yml
- type: RateLimits
  url: rate-limits/vitally-rate-limits.yml
- type: Conventions
  url: conventions/vitally-conventions.yml
- type: ErrorCatalog
  url: errors/vitally-problem-types.yml
- type: Lifecycle
  url: lifecycle/vitally-lifecycle.yml
- type: Conformance
  url: conformance/vitally-conformance.yml
- type: Compliance
  url: https://www.vitally.io/security
- type: Security
  url: https://www.vitally.io/security
- type: TrustCenter
  url: security/vitally-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/vitally-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/vitally-domain-security.yml
- type: AgenticAccess
  url: agentic-access/vitally-agentic-access.yml
- type: DataModel
  url: data-model/vitally-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Packages
  url: packages/vitally-packages.yml
- type: SDKs
  url: packages/vitally-packages.yml
- type: Webhooks
  url: asyncapi/vitally-webhooks.yml
- type: Components
  url: components/vitally-components.yml

Vitally API — frequently asked questions

Does Vitally have an API?

Yes. APIs.io lists 9 APIs from Vitally, including Vitally Accounts API, Vitally Admins API and Vitally Conversations API, and 6 more.

Is there an OpenAPI specification for the Vitally API?

Yes. APIs.io indexes 9 OpenAPI specifications for Vitally, each linked for download from this page.

How do I authenticate with the Vitally API?

Vitally documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Vitally Authentication.

How much does the Vitally API cost?

Vitally publishes its prices; its Tech-Touch plan is Request Pricing as of 2026-10-07. APIs.io lists 3 pricing plans for Vitally, with each plan's price, limits and inclusions under Pricing on this page.

Does Vitally have an MCP server?

Yes. APIs.io lists 1 MCP server for Vitally: Vitally operates an official remote MCP (Model Context Protocol) server (Beta) that connects any MCP-compatible AI client (Claude, ChatGPT, Cursor) to a Vitally workspace. Authentication is a standard

Is the Vitally API ready for AI agents?

Vitally has a Kin Score of 61.8 out of 100 (strong) and an Agent Readiness score of 56.2 (agent-ready), scored by API Evangelist on 2026-11-06.

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/vitally"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/vitally/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/vitally/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.