HyperCV is now Next Role — and it's no longer just a CV tool

Short version: HyperCV is now Next Role. Same product, sharper name, much bigger surface.

The new name is a promise: the product is no longer a CV tailor that happens to look at job posts. It is an end-to-end engine for getting from "I want my next role" to "I've applied to the right post, with the right CV, at the right company." The CV is one node in that graph — important, but not the headline anymore.

This post is the rebrand announcement, the new product framing, and the first description of the Pro API — the headless surface that lets any agent or automation call Next Role's capabilities in one line.

Why rename

HyperCV's name described the first thing it did well: tailor a master CV against a real job description, score it, refine it until it crossed a threshold. That product still exists and works the same way — we just stopped calling it that.

Two things forced the rename:

1. The product outgrew the name. Over the last few months the system grew a source-of-truth resolver that finds the real employer post behind any board listing, a guides surface with role-specific playbooks, an applications tracker, and the start of a discovery layer that looks for relevant open roles given your profile. "CV" was a thin label on a thick product.

2. The brand of the future is the verb users say out loud. Nobody says "I'm going to HyperCV my application." They say "I'm looking for my next role." When the product name is already what the user is trying to do, every other word in the funnel becomes less work. That alignment is what Next Role buys us.

The domain moves with it: everything previously at cv.hyperdrift.io now lives at nextrole.hyperdrift.io. Old links redirect.

What Next Role is now

Concretely, Next Role is four surfaces wrapped around one engine:

The tailor — the original HyperCV loop. Paste a master CV and a job description; get a role-specific CV, scored across five dimensions, refined until it crosses a quality bar. Free to try, Pro tier for unlimited runs and saved CVs.
The resolver — paste any board listing (LinkedIn, Indeed, Otta) and get the real employer post behind it. Better tailoring, direct apply paths, freshness signal, comp-band recovery. (Field note here.)
The library — guides and playbooks at nextrole.hyperdrift.io/blog, with a built-in search across the corpus. Topic-driven, not company-driven: "remote senior frontend roles in EU", "how to write a CV for a Director of Engineering position", "what compensation bands look like for staff ML engineers in 2026". The search is what makes the library a tool rather than a content pile.
The discovery — given a profile, surface open roles worth applying to. Currently early; the place the API will earn its keep first.

All four sit on top of one agent service. That's the part that changes the most with the rename.

Where the orchestration capability earns its weight: the Pro API

Most CV products are a chat box bolted to a model. Next Role isn't. The work the system does for you — fetch a role from its source, tailor against a master CV, score, refine, log the application — is a sequence of well-defined tool calls against a stateful service. That sequence is exactly the surface other automations want to call.

So we've exposed it.

The Next Role Pro API is the same engine that powers the web UI, available as a headless service for paid tenants. The Pro tier authentication produces a tenantId that scopes every call (your master CV, your saved applications, your discovery preferences) — the same multi-tenant pattern described in our agent architecture spec. What is new is that the surface has a stable, public contract.

A direct call looks like this:

curl -X POST https://nextrole.hyperdrift.io/api/v1/find-next-role \
  -H "Authorization: Bearer nr_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "profile": "senior-frontend-eu-remote",
    "criteria": { "minScore": 8.0, "freshDays": 7 },
    "maxResults": 5
  }'

What that one call does, internally:

Resolves the tenant + profile.
Discovers candidate roles matching the criteria.
Resolves each candidate from its board listing back to the employer's own post.
Tailors your master CV against each resolved post.
Scores and refines each tailored CV until it crosses the minScore threshold (or marks it as a stretch and explains why).
Returns a ranked list of { role, resolvedSourceUrl, tailoredCvUrl, score, gaps, applyUrl }.

This is the agentic orchestration described in Agents vs Automation §3.3 Agent + tools — the model decides which tools to call in what order, the tools themselves are deterministic. The user sees a one-liner; the system runs the whole loop.

The MCP surface: one-liner from a user agent

The same orchestration is exposed over the Model Context Protocol so that any MCP-aware agent — Claude Desktop, Cursor, Goose, Claude Code, an in-house agent — can use Next Role as a tool the moment the user adds their key to their MCP config:

{
  "mcpServers": {
    "nextrole": {
      "url": "https://nextrole.hyperdrift.io/mcp",
      "headers": { "Authorization": "Bearer nr_live_xxx" }
    }
  }
}

After which the user can simply say, in their agent of choice:

"Find my next role."

The agent calls the find_next_role MCP tool, which is the same /api/v1/find-next-role endpoint described above, wrapped in MCP's tools/call shape. Returns to the user inside their agent's chat, with citations, scores, and direct-apply URLs. No new UI. No new login. The Pro tier they already pay for entitles the call.

The same auth-to-TenantContext pattern documented in the MCP usage pattern governs every call: the bearer token resolves to the tenant on the server, every tool the user sees in tools/list is filtered by their plan, audit and budget are unified across the web UI and MCP transports.

The blog search, exposed via the same surface

The Next Role blog is a corpus, not a content marketing exercise: hundreds of role-specific guides, tactical playbooks, and compensation breakdowns. We use it ourselves to compose tailored CV bullets and to give users the "how to think about this role family" context that boilerplate AI tools never produce.

That corpus is now searchable both inside the Next Role UI and as an MCP tool:

search_nextrole_library(query: string, limit?: number)
  → [{ title, slug, excerpt, url, relevance }]

An agent assembling a tailored CV can call search_nextrole_library("staff engineer transition") and use the top three results as grounding context before generating bullets — making the output a synthesis of the user's actual experience + the library's collective playbook, not a hallucinated rewrite.

The same surface is callable directly:

curl "https://nextrole.hyperdrift.io/api/v1/library/search?q=staff+engineer+transition&limit=3"

Public surface, no auth required, rate-limited per IP.

What this means for users

If you used HyperCV: nothing breaks. Same login, same master CV, same scored history. The URL is nextrole.hyperdrift.io now. Bookmarks update on first visit.

If you have a paid plan: you now have a Pro API key. Generate it under Settings → API & MCP. The MCP config snippet for Claude Desktop / Cursor / Goose is one click.

If you are building an agent or automation: the surface is documented at nextrole.hyperdrift.io/api. Free tier for the library search; paid tier for tailoring, resolution, and discovery. Multi-tenant by default — the same tenantId carries through every call.

The pattern this rebrand exposes

The Next Role engine is one example of a broader thesis worth saying out loud: the most valuable AI products of the next few years are not UIs. They are services with one UI and many transports. The CV interface remains the place most users discover Next Role — but the leverage is in being callable. Every user who adds Next Role to their MCP config is a distribution channel the product team did not have to build.

This is the agent-as-service pattern at Hyperdrift in production: same engine, multiple clients, one tenancy story. The name change is the smallest thing about it; the surface change is the rest.

Try the new home at nextrole.hyperdrift.io.

For the API and MCP setup, see Settings → API & MCP on a Pro plan, or read the API reference.

This is part of the AI series on hyperdrift.io. Companion reads: