Realtor License Roster, New Applicants & Broker Change Delta

Real-estate licensee lead feeds for brokerage recruiters, title companies, and proptech — built directly on official state licensing data. Three feeds in one actor:

Feed	What you get	Why it matters
new_applicants	TREC daily license applications — people who just applied for a Texas real-estate license	Future agents, pre-license. Reach them before they pick a brokerage. No other public feed surfaces this.
delta → newly_licensed	Licenses that appeared since your last run	Brand-new agents, day-one recruiting window
delta → affiliation_change	An agent's sponsoring broker changed (with previous_broker)	THE recruiting/retention signal: who is switching brokerages, from whom, to whom
roster	Bounded slice of the current licensee roster	Bulk enrichment, territory mapping, CRM seeding

Who it's for

• Brokerage recruiters / team leads — daily pipeline of new applicants, newly licensed agents, and agents in motion between brokerages.
• Title, escrow, and mortgage BD teams — new licensees are new relationship targets; affiliation changes reshuffle referral networks.
• Proptech & data teams — clean, normalized licensee records with stable snake_case fields for enrichment pipelines and agent-graph products.

Data sources (verified live 2026-07-23)

• TX — TREC Real Estate License Roster (Socrata, data.texas.gov/resource/s7ft-44qi.json): full roster with license status, type, original license date, county, and the sponsoring-broker relation used for affiliation tracking.
• TX — TREC License Applications (Socrata, data.texas.gov/resource/bf5n-799f.json): daily applications with applicant name, license type, and date received. Powers the unique new_applicants feed.
• FL — DBPR Real Estate weekly extract (regional CSVs from the Real Estate Commission public-records page): full licensee rows including mailing address, city, county, statuses, and dates. Choose regions 1–14 via flRegions (files are large; default is region 1).

Example input

{
  "states": ["TX"],
  "feed": "new_applicants",
  "daysBack": 14,
  "maxResults": 200
}

The daysBack window is anchored to the newest date in the applications dataset, not to today — so the feed never returns empty just because the state paused publishing for a few days.

Other useful inputs:

{ "states": ["TX"], "feed": "delta", "licenseType": "Sales Agent", "maxScan": 20000, "maxResults": 500 }

{ "states": ["FL"], "feed": "roster", "flRegions": ["1"], "county": "Escambia", "maxResults": 200 }

Output fields

Every record uses the same normalized schema: state, feed, licensee_name, license_type, license_number, license_status, county, city (FL), mailing_address (FL), sponsoring_broker_name, sponsoring_broker_license, original_license_date, application_date, event_type (new_applicant | newly_licensed | affiliation_change | roster), previous_broker (on affiliation changes), source, source_url.

How the delta works

• The first delta run seeds a baseline (license number → status + sponsoring broker) in the actor's key-value store and emits no events — that's honest delta semantics, not a bug.
• Every later run compares the freshest maxScan roster records (TX is scanned most-recently-updated first) against the baseline and emits newly_licensed and affiliation_change events, then updates the baseline. Schedule it daily or weekly.
• Scanned records are not billed — only emitted events are.

Honest notes / limitations

• Contact fields: public licensing files contain no email or phone. TX gives you name + license + county; FL gives you name + full mailing address. This is a licensing-signal feed you enrich, not a contact list.
• FL has no public application feed, so new_applicants is TX-only (FL is skipped with a warning for that feed). FL supports roster and delta.
• FL sponsoring-broker columns are mapped best-effort from the weekly extract layout; TX affiliation data comes from the verified related_license_* roster columns.
• TX roster county is frequently blank at the source.

Use as an MCP tool

This actor is callable by AI agents (Claude, Cursor, etc.) via mcp.apify.com — the normalized field-level output schema makes it easy to chain into enrichment or CRM workflows.

FAQ

How do I find newly licensed real estate agents in Texas? Run feed: "delta" on a schedule; after the first baseline run, every run emits newly_licensed events. For an even earlier signal, feed: "new_applicants" lists people who only just applied.

How do I know when an agent switches brokerages? Scheduled delta runs emit affiliation_change events with the new sponsoring broker and the previous_broker they left.

Does this include agent emails or phone numbers? No — state licensing files don't publish them. You get name, license, status, county (TX) and mailing address (FL) to feed your enrichment stack.

Which states are covered? Texas (roster + daily applications + delta, live) and Florida (weekly roster + delta). More states can be added as config blocks — request one.

Why was my first delta run empty? By design: it seeds the baseline. The second run onward emits events.

Pricing

Pay per result: you are billed only for the licensee records actually emitted (cap with maxResults). Records scanned to build a delta baseline are not billed. Runs that match nothing cost only the actor start.

Related actors

Actor	What it adds
RIA Registration Delta Monitor	The same new-registration / affiliation-change pattern for SEC investment advisers
NYC Landlord Registry Lead List	Property-manager and landlord contacts for the agents you recruit
Absentee Owner Lead List Builder	Listing-side seller leads to hand new agents on day one