canonical: https://jentic.com/apis/microbilt.com/microbilt

# Microbilt US Criminal Reports

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.

## For AI agents

Order a US criminal background report - nationwide database, county, or statewide - and retrieve any previously generated report by its archive ID.

## Scope

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.

## Capabilities

- 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
- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance rather than in the agent's context.

Example prompt: Search Jentic for 'order a US criminal background report', load POST /GetReport, and submit the candidate demographics with ProductID 'USCRMD'.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/GetReport` | Order a new US criminal report by ProductID |
| GET | `/GetArchiveReport` | Retrieve a previously generated report by RqUID |

## Key resources

- **Report** — Order a new US criminal report by submitting subject details and a ProductID
- **Archive** — Retrieve a previously generated report by its RqUID for audit reuse

## Why Jentic

- **Setup:** Wiring US Criminal Reports by hand means running the OAuth 2.0 client-credentials flow against Microbilt's token URL, choosing the test or production host, and refreshing the bearer token yourself. Through Jentic you install once, import US Criminal Reports from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** This API carries the subject demographics in the request body rather than a fixed URL path resource, so limit the agent to the operations it needs, such as reusing an archived report with GetArchiveReport. You choose which operations it may call, so ordering a new report with POST /GetReport is not included unless you add it.
- **Credential handling:** Your Microbilt OAuth client credentials and refreshed bearer tokens are stored once, encrypted, by your own Jentic One instance and applied to the Authorization header at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'order a US criminal background check' or 'retrieve an archived report', and Jentic returns the matching operation with its subject and ProductID schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Onfido** — Identity verification with document checks and global background data
- **Experian** — Credit and consumer data including background screening products
- **Plaid** — Identity and bank account verification

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the US Criminal Reports API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's two operations the agent may call and which credentials it may use. You can allow only GET /GetArchiveReport so the agent reuses a previously generated report by its RqUID, while excluding POST /GetReport so it cannot order and charge for a new nationwide, county, or statewide report. To let the agent place new orders, you add POST /GetReport to its permitted operations.