Offendersearch API
Offendersearch, Inc. operates a REST API that unifies US sex-offender registry data — all 50 states, the District of Columbia, the US territories and NSOPW, 58 registries in all — behind a single authenticated endpoint. One call searches every jurisdiction and returns scored, de-duplicated records in one normalized 76-field schema, each carrying per-source provenance, a deep link back to the originating registry, and its own lastCheckedAt timestamp. Its defining contract is completeness labelling: an incomplete search is reported as partial with per-source status and a closed incompleteReason enum rather than returned as a silently empty result, so a zero from a registry that did not finish reads as UNKNOWN rather than NO MATCH. The API offers synchronous, asynchronous (with signed webhooks and Idempotency-Key retries) and 1,000-row batch/CSV modes, per-request freshness tiers, consolidated timestamped verification-report PDFs with a citation on every record, and a drop-in offenders.io compatibility endpoint. It publishes an OpenAPI 3.1 contract in JSON and YAML, an RFC 9727 api-catalog, an llms.txt, a markdown twin of every documentation page, and a documented (private-beta) MCP server. Pricing is purely metered at $0.15 per call, $0.11 above 2,000 a month. Offendersearch is expressly not a consumer reporting agency and its results are not a consumer report.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Offendersearch API the way a machine reads it — 23 machine-readable artifacts across 16 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Offendersearch API scores 47.8/100 (developing), with a separate agent-readiness read of 55/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from Offendersearch API's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/offendersearch-api/"
title="Offendersearch API on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/offendersearch-api.svg"
alt="Offendersearch API Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/offendersearch-api/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/offendersearch-api/"
title="Offendersearch API on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/offendersearch-api/card.svg"
alt="Offendersearch API Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Offendersearch API
Each block below is one kind of artifact we hold for Offendersearch API. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Offendersearch API Account API
The Account API from Offendersearch API — 1 operation(s) for account.
Offendersearch API Admin API
The Admin API from Offendersearch API — 11 operation(s) for admin.
Offendersearch API Auth API
The Auth API from Offendersearch API — 2 operation(s) for auth.
Offendersearch API Batch API
The Batch API from Offendersearch API — 1 operation(s) for batch.
Offendersearch API Billing API
The Billing API from Offendersearch API — 1 operation(s) for billing.
Offendersearch API Compat API
The Compat API from Offendersearch API — 1 operation(s) for compat.
Offendersearch API Keys API
The Keys API from Offendersearch API — 3 operation(s) for keys.
Offendersearch API Proof Docs API
The Proof Docs API from Offendersearch API — 1 operation(s) for proof docs.
Offendersearch API Records API
The Records API from Offendersearch API — 1 operation(s) for records.
Offendersearch API Report API
The Report API from Offendersearch API — 1 operation(s) for report.
Offendersearch API Search API
The Search API from Offendersearch API — 1 operation(s) for search.
Offendersearch API Searches API
The Searches API from Offendersearch API — 3 operation(s) for searches.
Offendersearch API Sources API
The Sources API from Offendersearch API — 1 operation(s) for sources.
Offendersearch API Support API
The Support API from Offendersearch API — 1 operation(s) for support.
Offendersearch API Team API
The Team API from Offendersearch API — 2 operation(s) for team.
Offendersearch API Usage API
The Usage API from Offendersearch API — 1 operation(s) for usage.
Scroll within the panel for all 16 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Offendersearch Api Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Offendersearch Api Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Offendersearch API — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/offendersearch-api · machine-readable index on apis.io
This is an independent, third-party profile of Offendersearch API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.