VCV
VCV is a recruitment-automation platform offering video interviews, candidate screening, assessments, and chatbot pre-screening for high-volume, graduate, and professional hiring, used by enterprises like PwC, PepsiCo, and Danone. Its VCV Open API v3 is a bearer-token REST API covering vacancies, candidate responses, video interviews, tests, surveys, invites, tags, users, and company webhooks, documented via Swagger UI at developer.vcv.ru.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles VCV the way a machine reads it — 21 machine-readable artifacts across 17 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 — VCV scores 42.7/100 (thin), with a separate agent-readiness read of 57/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile VCV
Each block below is one kind of artifact we hold for VCV. 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 17
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.
VCV chatbot API
The chatbot API from VCV — 2 operation(s) for chatbot.
VCV companies API
The companies API from VCV — 1 operation(s) for companies.
VCV countries API
The countries API from VCV — 2 operation(s) for countries.
VCV enumeration API
The enumeration API from VCV — 3 operation(s) for enumeration.
VCV integration API
The integration API from VCV — 7 operation(s) for integration.
VCV interview API
The interview API from VCV — 3 operation(s) for interview.
VCV invite API
The invite API from VCV — 2 operation(s) for invite.
VCV Languages API
The Languages API from VCV — 1 operation(s) for languages.
VCV limits API
The limits API from VCV — 1 operation(s) for limits.
VCV response API
The response API from VCV — 12 operation(s) for response.
VCV survey API
The survey API from VCV — 4 operation(s) for survey.
VCV tags API
The tags API from VCV — 4 operation(s) for tags.
VCV test API
The test API from VCV — 4 operation(s) for test.
VCV users API
The users API from VCV — 2 operation(s) for users.
VCV vacancy API
The vacancy API from VCV — 23 operation(s) for vacancy.
VCV videointerview API
The videointerview API from VCV — 4 operation(s) for videointerview.
VCV webhook API
The webhook API from VCV — 2 operation(s) for webhook.
Scroll within the panel for all 17 ·
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.
vcv-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
VCV Webhooks
VCV delivers outbound webhooks for recruitment events. Subscriptions are managed via the Open API v3 company-webhooks endpoints (create/list/get/ update/delete), each carrying a...
ASYNCAPISecurity Posture 2
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 VCV — 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 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
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/vcv · machine-readable index on apis.io