Complete Criminal Checks API

Name: Complete Criminal Checks API
Brand: Complete Criminal Checks API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey1 EndpointsREST

For Agents

Search US public criminal records by name across arrests, sex-offender, inmate, and most-wanted data sources, charged at one credit per search.

Install Jentic One Beta

Connect the Complete Criminal Checks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Complete Criminal Checks API, 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 | sh

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

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

Capabilities

What an agent can do with Complete Criminal Checks API.

Search public criminal records by full name across multiple US data sources

Filter a search to specific source types such as arrests, sex offenders, inmates, or most wanted

Return matching records with the source that produced each hit

GET STARTED

Start building with Complete Criminal Checks API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Complete Criminal Checks API, keeping it validated and agent-ready. The Complete Criminal Checks API performs name-based searches across publicly available US criminal-record data sources including arrests, sex-offender registries, inmate rosters, and most-wanted lists. It is built around a single search endpoint that consumes one credit per query and returns matching records with the originating source. The API is suited to background-check workflows for housing, gig-platform onboarding, or due diligence where a quick public-records sweep is needed.

Use Cases

Patterns agents use Complete Criminal Checks API for, with concrete tasks.

★ Tenant Screening

Run a public-records criminal sweep against a prospective tenant before signing a lease. The /search.php endpoint accepts a name and returns matches across arrest, sex-offender, inmate, and most-wanted sources, with one credit deducted per call. Independent landlords and small property managers use this as a low-cost first-pass screen before commissioning a full FCRA-compliant report.

Search the name 'John A Smith' across all available sources and return the list of matching records with their source labels

Gig and Volunteer Onboarding

Add a quick public-records check to the onboarding flow for gig workers, contractors, or volunteers. The single-endpoint API is straightforward to wire into an onboarding form and the credit-per-search pricing keeps the cost predictable. This is appropriate for non-FCRA informational screening; for adverse-action decisions a regulated background-check provider should also be used.

For each new sitter applicant in the queue, call /search.php with their name and flag any results from the sex-offender source for human review

Due Diligence Lookups

Add a public-records sweep to a wider due-diligence workflow alongside corporate-register and sanctions data. A single name search returns hits across multiple US datasets, which can be combined with PSC and sanctions results to build a richer picture of a counterparty. The credit-based model makes one-off lookups cheap to integrate.

Take the named directors returned from a Companies House lookup and run each name through /search.php, returning any with non-empty results

Agent-Driven Screening via Jentic

Let an AI assistant trigger a public-records screen as part of an onboarding or research conversation. Through Jentic the agent searches by intent, loads the schema for the single search endpoint, and executes the call without the developer wiring auth or credit tracking. Results are returned in structured form for the agent to summarise to the user.

On the prompt 'check if Jane Doe has any public criminal records', call /search.php with name=Jane Doe and report a one-line summary of any matches

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for complete criminal checks api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/search.php

Search criminal records by name across selected sources

GET

/search.php

Search criminal records by name across selected sources

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Complete Criminal Checks API keys are stored encrypted in the Jentic vault and injected as the X-API-Key header at execution time. The raw key never enters the model context or application logs.

Intent-based discovery

Agents search Jentic with intents like 'search public criminal records' and Jentic returns the GET /search.php operation with its parameter schema, so the agent can submit a name without browsing developer docs.

Time to first call

Direct integration: a couple of hours to wire the header auth and parse the response shape. Through Jentic: under 15 minutes via search, load, execute.

FAQs

Specific to using Complete Criminal Checks API through Jentic.

Why is there no official OpenAPI spec for Complete Criminal Checks API?

Complete Criminal Checks does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Complete Criminal Checks API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Complete Criminal Checks API use?

The API uses an API key passed in the X-API-Key request header. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt or logs. HTTPS is required.

Can I search the sex offender registry with this API?

Yes. Call /search.php with the name parameter and constrain the source filter to the sex-offender dataset. The response lists matches with their originating source so you can separate sex-offender hits from arrest or inmate records.

What are the rate limits and pricing for the Complete Criminal Checks API?

Pricing is credit-based: each call to /search.php costs one credit from your account balance. There is no documented per-second rate limit; high-volume integrations should monitor remaining credits and add backoff if HTTP 429 is returned.

How do I run a criminal record search through Jentic?

Run the Jentic search query 'search public criminal records by name', load the returned operation (GET /search.php), and execute it with the name parameter. The response returns the list of matched records and the data source for each hit.

Is this API FCRA-compliant for employment decisions?

No. Complete Criminal Checks is a public-records search and is not a Consumer Reporting Agency under the US Fair Credit Reporting Act. Do not use it as the sole basis for hiring, tenancy, or credit adverse-action decisions; pair it with an FCRA-regulated provider when an adverse action is on the table.