Supply intelligence · Live87,412 active profiles · 312 metros

Candidate Finder & Density Mapper.

Search the active supply by role, geography, credential class, and availability — then overlay where qualified clinicians actually live, priced against the same live distribution your desk quotes from.

87,412Active profiles
312Metros mapped
HourlyRefresh
<140ms p50Match latency
Anatomy

Two surfaces, one supply graph.

01Canonical role filter

Search resolves to the same 428 canonical roles as Rate Explorer — never a free-text bucket. ICU, Med/Surg, L&D, OR are separate cohorts.

02Availability window

Filter by start-window: ≤1 wk, ≤2 wks, ≤4 wks, plus negotiating and placed states. The clock comes from the candidate, not a guess.

03Rate range vs market

Every candidate carries an asked rate range, plotted against the live p25/p50/p75 for that role × metro. No more apples-to-oranges.

04Density layer

Toggle the density mapper to see qualified supply per metro inside a 25-mile radius — same canonical role, same credential class.

By the numbers

Live supply, ranked, mapped, refreshed hourly.

87KActive candidate profilesRefreshed hourly · contract-class disambiguated.
312Metros mappedCBSA-level density per canonical role × credential.
<140msp50 match latencyInline inside placement-creation flows.
6Filter dimensionsRole · geo · credential · shift · availability · rate band.
Capability matrix

What Candidate Finder ships with.

CapabilityDesk · Agency · Agency PlusEnterprise
Active profile poolFull pool · 312 metrosFull pool + private feed
Filter dimensionsRole · geo · credential · shift · availability+ rate band · custom tags
Density mapperMetro-level (CBSA)Metro + ZIP-3 isochrone
Rate range vs marketp25 / p50 / p75 overlayp10 → p90 overlay
Saved searchesUnlimited · per-userUnlimited · shared workspace
Refresh cadenceHourlyStreaming · webhook
Density mapping

Where the supply actually lives — not where job-boards say it does.

The density mapper joins active candidate profiles to canonical role, credential class, and CBSA, so a desk can see 412 active Travel ICU RNs around Los Angeles without ever clicking into 412 search-result pages.

GeographyCBSA-level density

Each metro cell aggregates qualified candidates within a 25-mile radius of the metro core. Every plan maps every CBSA in the country; Enterprise adds ZIP-3 isochrones for shift-driven roles.

FilteringSame filters as the finder

Role, credential class, shift preference, availability window, and rate band all flow through to the density view. Switching surfaces never re-opens the filter set.

OverlayHover for live rate

Hover any metro cell for the live p50 bill rate, sample size, and 30-day move on that role × geography. The density mapper and Rate Explorer speak the same canonical-role language.

Hottest cellSurfaced automatically

The platform flags the highest-density metro for any active filter set, so a desk never has to scroll to find where the supply concentrates.

Under the hood

How a profile becomes a placement-ready match.

IngestionPermitted profile feeds, contract-class aware

Profiles enter from contributing ATS partners and permitted public job-board feeds. Contract class (travel-13wk, per diem, local) is extracted on ingest, not inferred at query time.

NormalizationSame Taxonomy Mapper, every record

Every candidate's role-of-record passes through the canonical mapper at confidence ≥ 0.92 before it joins the searchable pool. Credential class (RN, NP, CRNA, RT…) is a separate dimension.

PrivacyNo PHI · no PII without consent

Display IDs are platform-issued (CR-K-####). Real candidate identity, contact, and licensure documents stay inside the contributing partner system; we surface match strength, not personal data.

Match scoreCalibrated, not "vibes"

Match % combines canonical-role fit, credential exact-match, geographic preference, availability, and asked-rate proximity to the role × metro p50. Each dimension is reportable in the API response.

Comparison

Candidate Finder vs. job-board search.

Why the same query against a job board returns a noisier, less defensible answer.

CapabilityCandidate FinderCanonical · priced · density-awareJob-board searchFree-text · undated · unpriced
Role resolution428 canonical roles, contract-class splitFree-text title match
RefreshHourlyCrawl-dependent (days–weeks)
Rate contextAsked-rate vs live p25/p50/p75No rate, or stated rate without market context
Geographic granularityCBSA + 25-mi radius (ZIP-3 on Ent.)State + city string
Density visibilityMetro-level density mapperResult-count, no shape
Availability signalStart-window inferred from candidate stateFree-text "open to work"
API accessREST + webhook · canonical join keysScrape-only (TOS-restricted)
Agency Plus · 14 desks live
AR
Alex ReyesDirector, Pricing · National travel-nurse staffing platform
We stopped paying for two job-board logins the same quarter we wired the density mapper into our pricing flow. Knowing that LA had 412 active ICU RNs vs Phoenix's 132 changes the bid before the rate-card meeting starts.
What's included

Built into every ClinicalRate plan.

FAQ

Questions buyers ask about Candidate Finder.

A combination of contributing ATS partners (under data-share agreements) and permitted public profile feeds where re-use is in-policy. Every record passes the same Taxonomy Mapper as our rate data, so a Travel CRNA in Texas joins to the same canonical role on both surfaces.

No. Candidate Finder surfaces a platform-issued display ID, role, geography, credential class, asked-rate range, and availability state. Real identity, contact, and licensure documents stay inside the contributing partner system. The platform shows match strength, not personal data.

Job-boards index free-text titles and rarely carry rate context. Candidate Finder joins canonical role, contract class, credential, asked-rate, and availability into one filter set — and overlays the result against the same live distribution your team quotes from in Rate Explorer.

Profile pool is refreshed hourly, with density cells rebuilt on each refresh. Enterprise tier ships streaming webhooks on supply-shock events (e.g. >10% density move on a subscribed role × metro inside 24 hours).

Yes. The same OAuth 2.0 client-credentials flow as the rest of the API, with two endpoints: GET /v1/candidates/search and GET /v1/density/{role}/{metro}. p50 match latency is under 140 ms; both endpoints carry sample_size and as_of in the response envelope.

Get started

See where the supply is before you bid.

Book a 30-minute demo. We'll open Candidate Finder on your hardest specialty and density-map the metros you compete in.