Vincere logo vincere.io

Live

Vincere API and MCP server

Vincere gives API keys only to partners and has no API for shortlists, LiveLists, comments or tasks that you can use without a partner deal. Sign in to Vincere once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Vincere.

Vincere has no API for this. So we run one for you.

Vincere's own API, a GitHub MCP server and Cotlet compared
What you need Vincere's APIGitHub MCP serverCotlet
Shortlists, LiveLists, comments, tasks No No Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Vincere changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 22, 2026. Sources: Vincere Help: Understanding and requesting API keys · Vincere Help: Set up and use the Zapier integration · Vincere on Zapier: triggers and actions · Vincere Help: Candidate Actions

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Vincere in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Vincere to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Vincere and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/vincere with its own method and path, such as POST /api/v1/vincere/jobs/{job_id}/candidates/shortlist, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Vincere API and MCP server do?

13 tools on your own Vincere account. Agents call them as operations of the MCP tools vincere_read and vincere_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Vincere tools in Cotlet's MCP server and REST API
Tool What it does Access
list_jobs Jobs of your agency with company, contact, owner, status and sourcing dates. read
get_job One job with its details, public and internal description and brief notes. read
list_candidates Candidates of your agency or of one Talent Pool, with title, company and owner. read
get_candidate One candidate with title, company, owner, Talent Pools and applications with their stage. read
list_job_applications Candidates on one job with their pipeline stage. read
list_tasks Vincere tasks assigned to you, created by you or followed by you, with due date and status. read
list_activities Comments, meetings and tasks logged on a candidate or a job, with who added them and when. read
add_comment Log a comment on a candidate with an Action, such as a connected call, and notes. writeasks first
add_task Create a Vincere task with subject, type, due date and assignee. writeasks first
shortlist_candidates Shortlist candidates to an open job. writeasks first
send_candidates_to_client Email candidates to the client as a LiveList for a job and move them to Sent. writeasks first
send_job_list_to_candidates Email a list of jobs to candidates, who can accept or decline each role. writeasks first
move_application_stage Move a candidate to the next stage of a job without sending an email. writeasks first

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All Vincere use cases

Is it safe to connect Vincere?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Vincere API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Vincere is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Vincere have an API?

Vincere has an API, but only partners can get a key (checked 22 Oct 2026). Vincere issues API keys only to partners with a formal agreement, and it has no official MCP server. The Zapier app is the one open connection: 9 triggers and 6 actions, mostly new-record events and VinnyChat messages.

How do I get access?

Sign up free, open Vincere under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Vincere yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Vincere sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: add_comment, add_task, shortlist_candidates, send_candidates_to_client, send_job_list_to_candidates, move_application_stage wait for your OK by default. You can switch that off per tool for scheduled runs.

Which Vincere role does my account need?

Cotlet works in your own Vincere login and sees what you see. Shortlisting needs a user account with the permission for it, and a company that is compliant, according to Vincere's Help Center, which names no role. Logging a call as a comment needs the call Action activated in Settings > Goal Console, and an admin with access to Settings and Goal Console does that.

Which tools send email?

Two do: send_candidates_to_client emails the client a LiveList, and send_job_list_to_candidates emails candidates a job list. Vincere limits an email action to 100 recipients, and a job-list send to 10 jobs and 100 candidates. shortlist_candidates and move_application_stage send nothing. Each write waits for your OK by default.

What does it not cover?

Placements stay in Vincere: Place opens the placement details page and Vincere runs compliance checks on it. A candidate cannot be moved back a stage, merged, archived or removed from a job through these tools, and Float to Contact for a role with no open job is not built. Comments and tasks cannot be deleted through Cotlet. Vincere also limits a candidate to 1,000 position associations.

Should I use a Vincere MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Vincere changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Vincere?

No. Cotlet is independent and not affiliated with Vincere.

Give your agent access to Vincere.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free