Everything you sourced lands in Vincere, on the right record.
Vincere is a recruiting CRM, and one of the 54 tools hyreflow connects to Claude, ChatGPT and other AI assistants. Through hyreflow, an AI agent can run 9 actions: 6 that look something up and 3 that create or change records. Vincere costs no hyreflow credits, and runs on your own Vincere account.
Vincere (vincere.io) is a recruiting CRM. Your agent searches Vincere before it creates anything, so you do not end up with duplicates, then writes the genuinely new ones in. It reads your jobs, companies and contacts as well.
Vincere is the destination. Sourcing and enrichment feed it.
With hyreflow connected, you ask for the outcome in plain language and the assistant runs Vincere for you. For example:
You connect hyreflow once over MCP, and Vincere comes with it, next to the other 53 tools. You do not need to run a separate Vincere MCP server.
In Claude, ChatGPT or any other MCP client, add a custom connector named hyreflow with the server URL https://recruit.hyreflow.ai/api/v2/mcp. The MCP setup guide on hyreflow.ai has the exact steps for each app.
A browser window opens. Sign in, choose the workspace the assistant may act on, and approve. The connection is live.
Vincere runs on your own Vincere account. Connect it on the Integrations page in hyreflow, and hyreflow charges no credits for its calls.
Tell Claude or ChatGPT what you want done with Vincere in plain language. The assistant picks the Vincere action that fits and runs it through hyreflow.
Using Cursor, Claude Code or another client? Every one is covered in the MCP setup guide.
In a hyreflow run, Vincere is most often paired with Apollo, LeadMagic, Fathom and SourceWhale.
source against the roles already live in Vincere
fill the contact gaps on records you already hold
interview debriefs onto the candidate record
outreach shaped the way the desk is measured
Through hyreflow, an AI agent can run 9 Vincere actions: 6 that look something up and 3 that create or change records. Vincere costs no hyreflow credits, and runs on your own Vincere account.
| Vincere action | What it does | Cost through hyreflow |
|---|---|---|
| Search candidates | Looks something up | no hyreflow credits |
| Search companies | Looks something up | no hyreflow credits |
| Search contacts | Looks something up | no hyreflow credits |
| Search jobs | Looks something up | no hyreflow credits |
| Create candidate | Creates or changes a record | no hyreflow credits |
| Create candidates batch | Creates or changes a record | no hyreflow credits |
| Update candidate | Creates or changes a record | no hyreflow credits |
| Get candidate | Looks something up | no hyreflow credits |
| Get job | Looks something up | no hyreflow credits |
One credit is priced on the pricing page. The full price list for every tool is in the pricing tables.
4 hyreflow skills call Vincere as part of the run. A skill is a whole pipeline your agent already knows, end to end.
use whena role comes in and you want to know who you already have before you pay to source anyone new
use whena strong applicant comes in for the wrong job, and your team is working dozens of other roles they might fit
use whenyour database is full of people you have not spoken to in years, and you do not know which of them have been promoted or changed employer since
use whenyou have a finished shortlist or prospect list as a file, and it needs to be in your ATS or CRM without doubling up people you already hold
hyreflow ships a written playbook for Vincere, and the agent loads it before the first call. Auth, rate limits, what each call costs, which actions need your approval, and the mistakes worth avoiding. It is the difference between an agent that knows the tool and one that guesses at it.
Read the Vincere docs →HOW in lib/vincere.py.
https://{tenant}.vincere.io/api/v2 — the tenant is the workspace's own Vincere subdomain.x-api-key AND id-token (1 h TTL). The id-token refreshes automatically once connected — no manual refresh needed.Candidates: search_candidates, get_candidate, create_candidate, update_candidate. Reads: search_jobs, get_job, search_companies, search_contacts. Index: reference/docs/vincere/raw/endpoints.md.
job (NOT position) in v2 — confirmed. Search paths carry a trailing slash (/candidate/search/).fl/sort are matrix params on the path (/candidate/search/fl=id,name;sort=created_date asc?q=...), q is a query param. The client passes fl/q as query params; if a search 400s, report it rather than retrying with a hand-built path.Production ATS writes — pilot one, confirm, then bulk. Watch for id_token expiry (refresh + retry).
ATS write target: enriched candidates → create_candidate.
Call via the CLI: hyreflow tools execute vincere <method> --payload '{...}' (preview with --dry-run; hyreflow tools get vincere <method> returns the live contract + cost). Only the methods listed below are callable.
batch(method: str, calls: list, *, stop_on_error: bool = False) -> dict — Batched get/search/update/create: run one method over many inputs, rate-limited. Each call is a value -> method(value), or {"args": [...], "kwargs": {...}} for multi-arg methods like update_candidate(id, payload). Destructive methods (delete) are refused. See lib/_base.run_ops.create_candidate(payload: dict) -> Any — POST /candidate — create a candidate.create_candidates_batch(payloads: list[dict], *, stop_on_error: bool = False) -> dict — POST /candidate for many records, respecting VINCERE_RATE_LIMIT_RPM.get_candidate(candidate_id: str, *, fields: str | None = None) -> Anyget_job(job_id: str, *, fields: str | None = None) -> Anysearch_candidates(q: str, *, fl: str | None = None, sort: str | None = None, **params) -> Any — GET /candidate/search/ — q uses Vincere's field:terms# syntax; fl=returned fields, sort=e.g. "created_date desc".search_companies(q: str, *, fl: str | None = None, sort: str | None = None, **params) -> Any — GET /company/search/.search_contacts(q: str, *, fl: str | None = None, sort: str | None = None, **params) -> Any — GET /contact/search/.search_jobs(q: str, *, fl: str | None = None, sort: str | None = None, **params) -> Any — GET /job/search/ — jobs are job in Vincere v2 (CONFIRMED — not position).set_id_token(id_token: str) — Swap in a freshly-refreshed id_token (they expire after 1 h).update_candidate(candidate_id: str, payload: dict) -> AnyYes. hyreflow is a connector for Claude, ChatGPT and other AI assistants. Once hyreflow is connected, you ask for the outcome in plain language and the assistant calls Vincere for you. hyreflow exposes 9 Vincere actions this way.
Yes. Vincere runs on your own Vincere account. You connect it to hyreflow once, hyreflow charges no credits for the calls, and Vincere bills you as before.
Vincere costs no hyreflow credits, and runs on your own Vincere account.
Add the hyreflow MCP server to your assistant and sign in. hyreflow calls the Vincere API directly and exposes its actions as tools the assistant can run, so there is no separate Vincere server to install.
Connect hyreflow to Claude or ChatGPT and ask for the outcome. It reads the playbook above before it makes a single call.