Skip to content
iLeads
GateKeeperReal-time collateral API · mortgage

Know if the lead can fund before the first call.

A real-time API that fires the moment a lead form is submitted, checks the property behind the name against title-grade public records, and returns a verdict in under a second. Unfundable leads never reach the floor. The ones that can fund stand out, whatever the source.

GateKeeper APILive
POST lead submitted< 1s
collateral checked
Fundable
Title matched
LTV 68%
No Notice of Default
1st lien only
A 291-element property match, resolved at the speed of a lead form.
Wired into the lead flow of national mortgage lenders
Retail lendersWholesaleDirect-to-consumerLead aggregators
Watch it decide

One lead comes in. A verdict goes out. Under a second.

GateKeeper reads the property behind the lead, not the form the prospect filled in. It checks the value, the equity, the liens, and the loan activity against title-grade public records, and answers before your team ever picks up the phone.

  1. 1The lead form submits. GateKeeper fires automatically, in any source you run.
  2. 2The property is matched and read against title-grade records in real time.
  3. 3A verdict returns before the first call: Won’t Fund, Watchlist, or Fundable.
Inbound lead
Lead#6159
PropertyChandler, TX
SourcePaid search form
POST /gatekeeper/score< 1s
Title matchedexact
Estimated value$344,000
Loan-to-value68%
Notice of Defaultnone
Lien position1st only
FundableHELOC · of 60 types
POST /gatekeeper/score< 1s
{  // request  "lead_id": "#6159",  "property": "Chandler, TX",  "loan_amount": 344000,  "property_type": "single_family",  "source": "paid_search_form",  // response  "verdict": "Fundable",  "title_match": "exact",  "ltv": 0.68,  "notice_of_default": null,  "lien_position": 1,  "suggested_loan_type": "HELOC",  "append": "141 property elements"}
Curated from a 291-element property match: the fields that move a funding decision.

One POST in. The whole verdict back.

GateKeeper is a REST API that sits wherever leads enter: your own forms, aggregator feeds, the intake side of your LOS or CRM. Send the lead as it arrives, and the response replaces what the consumer typed with what title records prove.

  • Works in any source. Retail forms, purchased feeds, transfers. If it produces a lead, GateKeeper reads it at submission.
  • Route on the verdict. Three machine-readable values drop into your distribution rules: Won’t Fund is filtered, Watchlist is parked, Fundable goes to the floor.
  • Only the fields that matter. The append is curated from a 291-element property match down to the 141 elements that move a funding decision.

Where it runs

GateKeeper runs on Microsoft Azure, encrypted at rest and in transit. iLeads stores no credit data at rest; credit is accessed per transaction under FCRA permissible purpose.

How data is handled

Client-provided data is held in segregated custody and never resold. Every lead carries its consent record (consent token, IP, timestamp), and deletion requests and DNC suppression run through a documented process with an audit trail.

What happens when you ask

"Get the API" starts a conversation with the team that built the engine: your lead sources, the system the verdict lands in, and the wiring scoped before anything touches your live flow.

Every lead, sorted three ways.

GateKeeper doesn’t just flag the bad ones. It reads the collateral on every lead and routes each to where it belongs, so your floor spends its hours on the loans that can fund.

Lead 4471Lead 4472Lead 4473Lead 4474Lead 4475Lead 4476
GateKeeper sorts
Won't Fund

A structural disqualifier: bad address or title mismatch, active foreclosure, wrong property type. Filtered before it wastes a call.

Title mismatchActive foreclosureRefinanced 30 days ago
Watchlist

Not fundable now, but the collateral is worth watching. Monitored for the change that puts it back in play.

Equity buildingRecent inquiry
Fundable

Passes the collateral checks. Hand it to the floor and work it now.

Clear title, 68% LTV1st lien, no NOD
Under the verdict

What GateKeeper checks, in under a second.

Title data of the quality used to underwrite real mortgages, not a modeled score trained on guesses. GateKeeper runs a 291-element property match on every lead and reads the ten signals that decide whether it can fund.

The checks decide if it can fund. The classification decides what it funds as: every fundable lead comes back tagged with its candidate loan type, one of 60, so your floor pitches the right loan on the first call.

PROPERTY MATCH · lead #6159291 elements read
Address confirmationbad address = no verdict
AVM valuationwhat the home is worth
Loan type & amountwhat's on the property now
Loan-to-value (LTV)room for the new loan
Hidden second liensdebt the form omitted
Notices of Defaultdistress on record
Foreclosure statusstructural disqualifier
Recent loan activity (90 days)already refinanced?
Servicing lenderwho holds it today
FHA / VA indicatorsprogram eligibility
Close the loop

The verdict doesn’t end at the call. It ends at funding.

The watch runs long past the first funding. GateKeeper follows every lead for as long as the borrower stays on title, so you can prove what a verdict was worth, see which fundable leads closed, and find out who won the ones you lost.

And because homeowners borrow again and again, the watch keeps paying: when a borrower comes back around, the same engine that scored them the first time hands them to Recapture.

0s

Verdict returned at submission

Back before the first call.

wk 1

Fundable lead worked by the floor

Routed straight to a loan officer.

mo 4

A lost lead funds elsewhere

GateKeeper reports which competitor won it.

mo 5

Funding confirmed, attributed back

Every verdict measured against what actually closed.

yrs

The borrower comes back around

Watched for as long as they’re on title. The next loan goes to Recapture.

U.S. properties · nationwide coverage

The same engine as Revive, run forward in real time.

One engine powers all three: lien, title, and property records on 150M+ U.S. properties. Revive delivers verified opportunities. Performance shows lenders what the leads they already bought went on to do. And GateKeeper points the same engine at your inbound flow, live.

< 1s
verdict at submission
60
candidate loan types
291-element
property match

The questions every lender asks.

What does mortgage lead verification actually check?

The property itself. Consumers get collateral wrong 50-60% of the time; GateKeeper replaces what they typed with title-grade records: a 291-element property match, curated to the 141 elements that move a funding decision, plus the verdict.

How fast can a mortgage lead be verified at intake?

Under a second at submission. Fast enough to route the lead before anyone dials.

Does lead verification just reject half your leads?

That’s not the point of it. The verdict sorts your flow three ways: Fundable, Watchlist, Won’t Fund. The win isn’t only the bad leads you skip; it’s the fundable loans hiding in leads you’d have discarded. What you do with the information is up to you.

How is mortgage lead verification different from lead scoring?

Lead scoring predicts behavior. GateKeeper reads the collateral record. It doesn’t guess whether the borrower will pick up; it verifies whether the property can fund a loan.

How does a real-time lead-verification API plug into my LOS or CRM?

A real-time API at lead intake: post the lead, get the verdict back with the appended data. Your LOS or CRM routes on it.

How do I know lead verification actually works?

Attribution is built in. Every lead you run stays matched to the title record, so when it funds, with you or anyone else, you see it. The engine watches until the borrower leaves title.

Your next fundable loan is already in your lead flow.

GateKeeper finds it the moment the form submits, and the leads that could never fund don’t reach your floor.