OffenderSearch
Court runner alternative · for screening companies and CRAs

Court runner alternative for county criminal searches

Check the county court itself, live, through one API call, and get back structured records with the court’s link and the time it was checked. Where a court has no online records, the answer says so by county, and that county alone goes to your courthouse researcher.

Get a free API keyTalk to sales25 free calls · no card

Updated November 22, 2026 · API changelog

One county, checked live at its court
POST /v1/criminal/search
{
  "query": { "firstName": "Jordan", "lastName": "Rivera", "dob": "1988-04-12" },
  "geography": { "county": "OH:Franklin" },
  "recordKinds": ["court"],
  "live": { "jurisdictions": [{ "county": "OH:Franklin" }] }
}
The answer names each court system asked, whether it answered, and every county in the request that has no online court source: coverage.geography.countiesWithoutSource.
1,934live jurisdictions a search can name, of 2,131 catalogued as of 2026-11-08
48states with a statewide court source; county courts listed by name
$0.02per court or agency that answered live, $2.00 ceiling a search
$4.95an FCRA order, live re-checks included, no court fees

Court runner services: how a county search works today

A county criminal search ordered from a researcher network is a chain of people. Each link adds time and a fee, and each is a place where the answer can be typed wrong.

A screening company sends the subject’s name, date of birth and county to a wholesaler. The wholesaler assigns the county to a courthouse researcher, often called a court runner or public record retriever. In some courthouses the researcher searches a public terminal; in others they file a request and wait for a clerk to run it. Hits are read off the screen or the file and typed into the wholesaler’s system, checked by a quality team and returned.

The model exists for a good reason: most criminal cases in the US are filed in county courts, and for decades the only reliable way to see a county’s current record was to stand in its courthouse. Turnaround is commonly quoted in business days, the per-county price is a fee per search plus whatever access fee the court charges, and clerk-assisted counties run slower than terminal counties.

A growing share of county and state courts now publish their criminal index online. For those courts the step that needed a person, reading the current record at the source, can be done by software during your request. That is the part of the chain this page replaces. The county criminal records page explains why the county layer is the hard one.

StepCourthouse researcherLive check by API
OrderSent to a wholesaler, queued for a countyOne POST /v1/criminal/search per county or ZIP radius
Reach the courtTravel, terminal time or a clerk requestThe court system is asked during the request
Read the recordRead and typed by a personStructured fields: case, charges, dispositions, dates
Prove itA researcher’s notesources[].recordUrl and lastCheckedAt on each record
No online recordsThe researcher still goesListed in countiesWithoutSource: send it to a runner
Court feesPassed through on topNone on our invoice

Digital court runner: what a live check at the source court does

Four steps, the first three inside one search: the stored answer is the baseline, the live block asks the court again, the response says who answered, and you route what is left.

  • Name the county, not a code. geography takes a county ("OH:Franklin" or a FIPS code), a ZIP and a radius, a city or whole states. The server picks the court, jail and agency systems that cover that area. See search criminal records by place.
  • Ask the court again, live. The same geography object inside live.jurisdictions asks every county, city and regional system in that area that can answer live. Statewide and federal systems are added by their code from the jurisdictions catalog, because every live source is billed.
  • Read who answered. sourceStatus[] has one row per system asked: ok, incomplete and the reason. A record confirmed live carries sources[].live: true and a fresh lastCheckedAt; a record the stored copy holds but the live check did not return is flagged, never silently kept or dropped.
  • Route the rest. coverage.geography.countiesWithoutSource names each asked county with no court source of its own. Those, and any system that did not answer, are the only orders your researcher network still needs.
Live check answerWhat your team does
Court answered, record confirmedReport it with the citation and check time
Court answered, no recordA defensible “not held there” for that court
Stored record not returned liveFlagged: review before anything is reported
Court did not answerincomplete; not billed; retry or route to a runner
County has no online sourceListed in countiesWithoutSource; route to a runner

The status codes and polling: live and async searches. What “complete” means: result completeness.

Court runner vs API: cost, turnaround and evidence

The two models side by side, without vendor names. Our side is the published price list; the runner side is how the industry commonly prices and quotes the work.

Courthouse researcher networkLive court check by API
UnitPer county searched, per namePer search: $0.15, plus $0.02 per system that answered live
Court access feesPassed through, set by each courtNone
TurnaroundCommonly quoted in business days; clerk-assisted counties run longerSame call for up to two in-request systems; a polled job otherwise; on FCRA orders, 90% of criminal checks done in under 30 minutes
What comes backText keyed in by a personJSON: case number, charges, statute, severity, disposition, dates
EvidenceResearcher’s notesThe court’s own link, check time, verification PDF, signed receipt on FCRA orders
GapsImplicit: a clear can mean the court was not reachedExplicit: countiesWithoutSource, sourceStatus[].incomplete
Counties with no online recordsCovered: a person can go to the counterNot covered: listed so you can send a researcher
Certified copies, archived filesAvailableNot offered

The honest reading: an API wins wherever a court publishes its criminal index online, and a researcher is still the only answer where it does not. Most programs end up with both, and the API decides which county goes where. Turnaround is compared on the how long does a background check take page.

When a courthouse researcher is still the right call

Five situations an API cannot reach. Each one is visible in the response, so none of them is a silent miss.

  • A court with no online criminal index. Some counties keep their index on a courthouse terminal or behind the counter. The county is listed in countiesWithoutSource; only a person can search it.
  • Records a court does not publish. Sealed, expunged and juvenile matters, and anything the court withholds from its public index, are not returned. That is the correct outcome for a report as well.
  • Files that exist only on paper. Older cases that predate a court’s electronic index, and the case file behind an index entry, are a clerk request.
  • Certified copies. A certified disposition for an adjudicator or a dispute is a courthouse product.
  • A court that did not answer. A system that timed out or refused is incomplete in sourceStatus and is not billed; retry it, or route it to a researcher if your deadline is today.

Live coverage is built jurisdiction by jurisdiction, so the list of counties in the API lane grows. The current list is in the criminal coverage reference and, by state, on the criminal records by state pages.

Court record retrieval routing: API first, runner by exception

A router your fulfilment system can run per order: one county search per address-history county, and a runner order only for counties the API cannot answer.

# Route each county in the address history: API first, a researcher only for the gaps.
import os, time, requests

BASE = "https://api.offendersearch.app"   # an os_test_ key: https://sandbox.offendersearch.app
H = {"X-API-Key": os.environ["OFFENDERSEARCH_KEY"]}

def county_search(person, county):
    body = {
        "query": person,
        "geography": {"county": county},          # "OH:Franklin" or a 5-digit FIPS
        "recordKinds": ["court"],
        "live": {"jurisdictions": [{"county": county}]},
    }
    r = requests.post(f"{BASE}/v1/criminal/search", json=body, headers=H, timeout=60)
    data = r.json()
    poll = data.get("poll")
    while r.status_code == 202:                  # most live checks run as a job
        time.sleep(5)
        r = requests.get(f"{BASE}{poll}", headers=H, timeout=60)
        data = r.json()
        if r.status_code == 200:
            data = data["result"]
    return data

def route(person, counties):
    for county in counties:
        res = county_search(person, county)
        geo = res["coverage"]["geography"]
        gaps = {c["fips"] for c in geo["countiesWithoutSource"]}
        incomplete = [s for s in res["sourceStatus"] if s.get("incomplete")]
        if gaps or incomplete:
            yield county, "runner", res            # no online court record, or it did not answer
        else:
            yield county, "api", res

The router reads two fields. countiesWithoutSource is the list of asked counties with no court source of their own; sourceStatus[] says whether each system asked live answered. A county with neither problem is done in the API lane. Anything else becomes a runner order, with the API answer attached as the starting point.

Keep the two lanes in one audit trail: the API response carries the searchId, and a verification report can be rendered from it later. The step-by-step build is in the court records API tutorial, and the matching rules a reviewer needs are in criminal matching and date of birth.

Wholesale volume? Bulk criminal record search runs a list in one call against the stored answer; the live check is per search, so send the rows that must be confirmed one at a time.

Court runner alternative coverage by state

Statewide court sources, county jail rosters, prison systems and warrant systems by state. A live jurisdiction answers a search today.

The twelve states with the most live jurisdictions. Each state links to its criminal records by state page; the statewide criminal search page covers the state tier.

StateCourtsCounty jail rosters (live / catalogued)Prison systemWarrants
KentuckyStatewide119 / 121Statewide—
TexasStatewide84 / 104StatewideStatewide
OhioStatewide82 / 86StatewideStatewide
South CarolinaStatewide72 / 73StatewideStatewide
IndianaStatewide70 / 74Statewide—
PennsylvaniaStatewide69 / 71StatewideStatewide
CaliforniaStatewide66 / 71StatewideStatewide
New YorkStatewide65 / 67StatewideStatewide
MissouriStatewide66 / 68Statewide—
MontanaStatewide61 / 72Statewide—
VirginiaStatewide60 / 62StatewideStatewide
FloridaStatewide57 / 63StatewideStatewide

Jurisdictions in our catalogue as of 2026-11-08; a live jurisdiction answers a search today. Approximate, not an official figure. Showing the 12 states with the most live jurisdictions; the full list is in the criminal coverage reference.

Depth varies by state and by county. Read the list for the counties you order most before you move them, and keep a researcher for the ones it does not name.

Court runner alternative pricing

A call, the live checks that answered, and nothing for the ones that did not. No court fees, no minimum.

ItemPriceUnit
County criminal search (stored answer)$0.15per call, the first 2,000 in a calendar month
Live re-verification+$0.02per completed live source, $2.00 ceiling per search; a source that did not answer is not billed
Volume rate$0.11per call past 2,000 in a calendar month
Free to start25 callsonce per account, on production data, no card
Sandbox$060 calls a minute and 2,000 a day per test key
FCRA order$4.95per order; sex offender and criminal court search included, with no court fees or extra charges

No minimum on search. The Map API has its own $300 monthly minimum. No seats, no platform fee, no per-state fee; a batch row is billed as one call.

Worked example: one county search in which two court systems answer live costs $0.15 + $0.04 = $0.19 if both answer. Volume pricing is on the pricing page and the background check API pricing breakdown.

Worked examples by volume: background check API pricing · every rate: pricing.

Court runner alternative questions

What operations and compliance teams ask before they move a county out of the runner queue.

Is this a replacement for every court runner we use?

No. It replaces the runner for the counties whose court records can be checked online, and it tells you, county by county, which ones those are. A county whose court publishes nothing online, or only on a courthouse terminal, still needs a researcher. Every response lists those counties in coverage.geography.countiesWithoutSource, so the hand-off is a field, not a guess.

How fast is a live court check compared with a courthouse search?

Up to two systems that can answer inside a request return in the same call (200). More systems, or a system that cannot answer in-request, run as a job you poll (202). On FCRA orders, 90% of criminal checks done in under 30 minutes. A courthouse search is commonly quoted in business days.

Are there court access fees on top?

Not on our side. The data API bills $0.15 a call and $0.02 per live source that answered, never more than $2.00 of live checks on one search. An FCRA order is $4.95 all in, with no court fees.

What does a runner return that the API does not?

Things that live only on paper or at the counter: a file a clerk pulls from storage, a certified copy, an answer from a court with no online index, and a clerk’s reading of an identifier the online index does not show. The API returns what the court publishes online, structured, with the court’s own link and the time it was checked.

What if the database copy shows a record the live check no longer returns?

The record is flagged as not returned by the live check (liveResult "not_found_live"), so your reviewer sees the disagreement instead of a silent drop. Inside an FCRA order the rule is stricter: a record is furnished only when the live check confirms it, and one the court no longer shows is withheld as not_current_at_source.

Can we start with a few counties?

Yes. Send the counties you route most often, read countiesWithoutSource and sourceStatus on each answer, and move a county out of the runner queue once its answers come back complete. The sandbox is free with an os_test_ key, and 25 production calls are free with no card.

Is a search on the data API a consumer report?

No. The standard key returns a public-records lookup and the response says so. A result that will be used for a hiring, tenant, credit or insurance decision runs as an order through FCRA Partner Access, which runs the live checks, the controls and the evidence as part of the order.

County criminal search and FCRA 613 pages

The two pages beside this one: the search request itself, and the compliance reason it is ordered.

County criminal search API

The request, the response and the coverage block for a county search, field by field.

County criminal search API ›

FCRA 613 compliance

Strict procedures for public records: verify a database hit at its source court before it is reported.

FCRA 613 compliance ›

Criminal record verification API

The live block on any search, what it bills and the provenance on each record.

Criminal record verification API ›

Learn the API by example

Runnable guides that use this endpoint as the worked example.

Court records API tutorial ›Cases, charges and dispositions, and how to read a case that holds both a conviction and a dismissal.
Criminal records by name and date of birth ›Why the date of birth decides whether a hit is an identification or a lead.
No-match and multiple-match results ›The three shapes of "nothing", possibles, and a decision table per matchState.
FCRA adverse action with an API ›Adverse items, the pre-adverse notice, the waiting period and the post-adverse notice, endpoint by endpoint.
Bulk background checks from a CSV ›The batch endpoint, 1,000 rows a call, results in input order, billed per row.
Rate limits, retries and idempotency ›429 semantics, backoff that honours Retry-After, and why a repeated POST is a second search.

All guides: Learn APIs by example · reference: developer docs · packages: SDKs and CLI.

Related court record API pages

The rest of the developer surface, one anchor per page.

Background check API ›Criminal records and 58 US sex offender registries on one key, per call.
Criminal records API ›Court cases, jail bookings, prison custody and warrants as JSON.
Sex offender API ›One POST across 58 US registries, scored and cited.
Free background check API ›25 free calls on real data, no card, plus the free sandbox.
Employment screening API ›The public-records stage of a hiring pipeline, and the FCRA path for the decision.
Tenant screening API ›The registry and criminal layer behind a rental application.
Inmate search API ›State prison and county jail custody records.
Background check API pricing ›Costs from 100 to 100,000 searches a month.
Public API for testing ›A free sandbox with documented test people in the production shape.
SDKs: Python, Node, CLI ›Client status and the method surface, one per endpoint.
Postman collection ›Every endpoint with sandbox bodies pre-filled.
MCP server ›Registry and criminal lookups as tools for Claude, Cursor and agents.

Test a court runner alternative on your own counties

Send the counties you order most with a live block, read countiesWithoutSource, and see which ones leave the runner queue. The sandbox is free.