Velaris
Velaris is an AI-native Customer Success platform for mid-market and enterprise B2B SaaS teams, centralizing customer data, health scoring, churn and expansion signals, and lifecycle automation with AI agents and a Copilot workspace assistant. Its Public API (developers.velaris.io) exposes organizations, accounts, contacts, opportunities, risks, custom objects, activities, notes, tickets, tasks, users, surveys, currencies, and lifecycle stages over REST with user-scoped bearer tokens. Velaris is a Battery Ventures portfolio company.
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 Velaris the way a machine reads it — 19 machine-readable artifacts across 14 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 — Velaris scores 50.6/100 (developing), with a separate agent-readiness read of 51/100 (agent ready). 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 Velaris
Each block below is one kind of artifact we hold for Velaris. 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 14
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.
Velaris Activity API
The Activity API from Velaris — 4 operation(s) for activity.
Velaris Attribute Change Log API
The Attribute Change Log API from Velaris — 1 operation(s) for attribute change log.
Velaris Currencies API
The Currencies API from Velaris — 3 operation(s) for currencies.
Velaris Custom Objects API
The Custom Objects API from Velaris — 15 operation(s) for custom objects.
Velaris Entity Management V1 API
The Entity Management V1 API from Velaris — 24 operation(s) for entity management v1.
Velaris Entity Management V2 API
The Entity Management V2 API from Velaris — 11 operation(s) for entity management v2.
Velaris Field Definitions API
The Field Definitions API from Velaris — 2 operation(s) for field definitions.
Velaris Integrations API
The Integrations API from Velaris — 1 operation(s) for integrations.
Velaris Lifecycles API
The Lifecycles API from Velaris — 1 operation(s) for lifecycles.
Velaris Notes API
The Notes API from Velaris — 2 operation(s) for notes.
Velaris Surveys API
The Surveys API from Velaris — 1 operation(s) for surveys.
Velaris Tasks API
The Tasks API from Velaris — 3 operation(s) for tasks.
Velaris Ticketing API
The Ticketing API from Velaris — 6 operation(s) for ticketing.
Velaris Users API
The Users API from Velaris — 2 operation(s) for users.
Scroll within the panel for all 14 ·
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.
velaris-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.
Resources
Every other property we hold for Velaris — 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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
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 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/velaris · machine-readable index on apis.io