For Agents
Order a US criminal background report — nationwide database, county, or statewide — and retrieve any previously generated report by its archive ID.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the US Criminal Reports, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with US Criminal Reports API.
Order a US Criminal Database Report (ProductID USCRMD) for nationwide aggregated coverage
Order a US Criminal County Report (ProductID USCRMC) for manual county court searches
Order a US Criminal Statewide Report (ProductID USCRMS) for direct statewide repository searches
GET STARTED
Use for: I need to order a nationwide criminal background check for a candidate, Run a county-level criminal record search for a specific subject, Retrieve a previously generated criminal report by its RqUID, Get statewide criminal records for a candidate moving across jurisdictions
Not supported: Does not handle credit reports, employment verification, international background checks, or identity document verification — use for US criminal record retrieval and archived report reuse only.
Microbilt's US Criminal Reports API provides programmatic access to three criminal background report products: a nationwide aggregated database, a manual county court search, and a manual statewide search. Each product is selected via a ProductID in the request payload and returns felony, misdemeanour, sex offender registry, incarceration, and traffic violation records subject to jurisdictional coverage. The two-endpoint API uses OAuth 2.0 and supports retrieving a previously generated report by its RqUID for audit reuse.
Submit a single POST /GetReport request with subject demographics and product selection
Retrieve a previously generated report by RqUID via GET /GetArchiveReport for audit and reuse
Patterns agents use US Criminal Reports API for, with concrete tasks.
★ Pre-Employment Background Screening
HR teams running pre-employment screening submit a candidate's demographics to POST /GetReport with ProductID USCRMD for a nationwide database sweep, then run USCRMC searches against counties tied to the subject's residence history for direct court coverage. The combination meets reasonable background check practices for many roles and integrates with any ATS that can call REST.
Submit POST /GetReport with subject demographics and ProductID 'USCRMD' for a nationwide database report and capture the returned RqUID.
Tenant and Vendor Risk Screening
Property managers and procurement teams reduce exposure by running USCRMD reports on prospective tenants or vendors before signing. The API returns felony convictions without date restrictions and up to seven years of misdemeanours, arrest records, and traffic violations, giving the screener a defensible basis for a decision.
Order a USCRMC county report for a prospective tenant scoped to their last two counties of residence and return any felony hits.
Audit Reuse of Existing Reports
Compliance teams responding to audits or applicant disputes often need to retrieve the exact report that was used for a prior decision. GET /GetArchiveReport with the original RqUID returns the cached report, supporting defensible record-keeping without re-running and re-charging for a fresh search.
Call GET /GetArchiveReport with RqUID 'abc-123' and return the original criminal report payload.
Agent-Assisted Background Checks
An AI agent guiding a recruiter through a hiring workflow can call Microbilt through Jentic to order a background report and parse hits. The agent searches by intent, loads the POST /GetReport schema, and executes — with the OAuth 2.0 token managed inside the Jentic vault rather than in the agent's context.
Search Jentic for 'order a US criminal background report', load POST /GetReport, and submit the candidate demographics with ProductID 'USCRMD'.
2 endpoints — microbilt's us criminal reports api provides programmatic access to three criminal background report products: a nationwide aggregated database, a manual county court search, and a manual statewide search.
METHOD
PATH
DESCRIPTION
/GetReport
Order a new US criminal report by ProductID
/GetArchiveReport
Retrieve a previously generated report by RqUID
/GetReport
Order a new US criminal report by ProductID
/GetArchiveReport
Retrieve a previously generated report by RqUID
Three things that make agents converge on Jentic-routed access.
Credential isolation
Microbilt's OAuth 2.0 client credentials and refreshed bearer tokens live in the encrypted Jentic vault. Agents request operations and Jentic adds the Authorization header at execution time, so the token never enters the model's context — important when handling subject PII.
Intent-based discovery
Agents search Jentic with intents like 'order a US criminal background check' and Jentic returns the matching POST /GetReport operation with the subject demographics and ProductID schema, so the agent does not parse Microbilt's documentation.
Time to first call
Direct Microbilt integration: 1-3 days for OAuth setup, payload construction, and ProductID handling. Through Jentic: under 1 hour — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using US Criminal Reports API through Jentic.
What authentication does the Microbilt US Criminal Reports API use?
Microbilt uses OAuth 2.0 — your client obtains an access token from Microbilt's authorisation server and presents it on each request. Through Jentic the OAuth credentials and refreshed tokens are stored encrypted in the vault and applied at execution time.
Can I order all three criminal report types from one endpoint?
Yes — POST /GetReport accepts a ProductID field set to USCRMD, USCRMC, or USCRMS. The response payload structure differs by product but the request shape is consistent.
What are the rate limits for the Microbilt API?
Limits are governed by your Microbilt service agreement rather than the OpenAPI spec, and county and statewide manual searches have longer turnaround times because they involve human researchers. Plan throughput accordingly and use /GetArchiveReport to avoid duplicate orders.
How do I retrieve an archived report through Jentic?
Search Jentic for 'get an archived Microbilt report', load GET /GetArchiveReport, and execute with the original RqUID. Jentic adds the OAuth bearer token from your stored credential.
Is the Microbilt API free?
No — Microbilt's criminal reports are billable per search under your account agreement, with separate pricing for database, county, and statewide products. Use the archive endpoint to reuse an existing report rather than re-ordering when a recent result already exists.
Does this API cover non-US jurisdictions?
No — the US Criminal Reports API is scoped to United States federal, state, and county records. International background checks require separate Microbilt products that are not part of these two endpoints.