When you’re adding sex offender registry data to a product, you need to decide how your application will access and use it. Will it request records during individual lookups, or will your team need the data in its own environment for processing, analysis, and custom searches? The same question can come up later, when an existing API integration no longer covers everything you want to build.
Nannostomus offers sex offender registry data through an API and CSV delivery. Choosing between them involves search requirements, costs, and ongoing engineering work.
This guide compares those trade-offs and explains when each model fits.
Sex Offender API vs CSV Dataset: At a Glance
Nannostomus API and CSV delivery use the same sex offender registry dataset, refreshed monthly. The main differences are how you access records, which queries you can run, and what your team maintains.
| Comparison point | Sex offender API | Sex offender CSV dataset |
|---|---|---|
| Data access | Retrieve matching records through API requests. | Receive files to load and query in your own systems / load from our S3. |
| Coverage | Nationwide; each lookup requires a state. | Nationwide or selected states. |
| Search and matching | Exact matching; first name, last name, and state required. | Your team builds queries and matching logic. |
| Bulk processing | Individual requests; no batch endpoint. | Process lists, join data, and run dataset-wide analysis locally. |
| Your team manages | API integration and request handling. | Data ingestion, storage, queries, and loading updates. |
| Pricing | Usage-based, with 100 free requests per month. | Quoted for the agreed scope and delivery arrangements. |
What Stays the Same Across the Sex Offender API and CSV Dataset?
Nannostomus API access and CSV delivery share the same underlying dataset. Whether you’re choosing your first access model or reviewing an existing integration, these data characteristics apply to both:
- Source coverage. Nationwide data is available through either model. CSV customers can also request selected states.
- Monthly refresh. Both use the same monthly update cycle. An API request queries the available dataset; it does not trigger a fresh search of source registries.
- Data processing. The same normalization rules apply before records become available through API or CSV.
- State-level deduplication. Records are deduplicated within each state. A person registered in multiple states may appear in multiple records; nationwide deduplication is not performed.
- Data limitations. Missing source fields, registry outages, and delays in source updates can affect records available through either model.
Neither access model provides inherently fresher or more complete source data. The choice determines how your product retrieves and processes records. Search results can differ depending on the coverage you select and the matching rules you use. For details on data sourcing, processing, limitations, and intended use, visit the Nannostomus Trust Center.
For more context on what the records contain and how to interpret them, see our guide to sex offender registry data.
When to Choose a Sex Offender API
A sex offender API fits products that need registry records during individual lookups and can work with the provider’s search rules. Your application requests matching records, while Nannostomus hosts and updates the underlying dataset.
For example, a public-record product could retrieve registry records when a user searches by name and state. The team can integrate those responses without building a database to store and search the full nationwide dataset. This approach can support both a new product and an established service with recurring lookup needs.
You can try the Nannostomus sex offender API using the public test key in the API documentation, without registering. This shared key provides limited test access to inspect requests and responses. To evaluate the full production environment, create an account at Intsurfing API platform, complete setup, activate the service, and generate your own production key. Production access includes 100 free requests each month, with usage-based billing beyond that allowance.
Check whether the API supports your search inputs
The Nannostomus sex offender API requires first name, last name, and state. City, ZIP code, and date of birth are optional filters. Matching is exact, and supplied search fields are combined with AND logic: a returned record must satisfy all of them.
These rules matter when designing your search flow. If your product collects only a name, the required state is missing. If you need to accommodate misspellings or name variations, the standard API does not provide fuzzy matching. Adding filters narrows results, but can also exclude relevant records when source values are missing or differ from your inputs.
If the standard search parameters do not fit your workflow, contact Nannostomus and describe the inputs you have and the search behavior you need. We can assess whether custom search parameters can be supported.
Retrieve records without operating the full dataset
The API returns JSON responses with pagination. Your team handles requests, processes the responses, and presents the information within your product.
Your integration still needs to handle errors, timeouts, and paginated results. Lookups depend on network connectivity and API availability, so consider how your product should behave when a request cannot be completed.
Make sure individual requests fit your workload
The Nannostomus API has no batch endpoint. Processing a list requires individual lookup requests, with request volume, processing time, and usage charges considered together.
API access remains a reasonable choice as usage grows if its search rules, costs, and availability fit your product. CSV becomes worth evaluating when you need dataset-wide analysis, bulk processing within your own infrastructure, or search logic your team wants to build and maintain itself.
When to Choose a Sex Offender CSV Dataset
A sex offender CSV dataset fits products that need registry data in their own environment for bulk processing, analysis, or custom searches. Your team receives the files, loads them into its systems, and controls how records are queried and used.
For example, a public-record data company might load registry records into a warehouse, join them with other datasets, and build a search layer for its product. CSV can support that workflow from the start or become an option as an existing integration’s requirements grow.
To inspect real records, visit the sex offender dataset page and click Load sample data. The downloadable sample lets you review the file structure, field names, and example values before deciding whether CSV delivery fits your workflow.
Bulk processing and dataset-wide analysis
CSV lets your team process a list against the delivered dataset without sending an API request for each lookup. You can also run queries across the data, group records by available attributes, and calculate aggregate statistics.
These workflows require processing logic in your environment. The files provide structured records; your team builds the joins, matching rules, and analysis. Our U.S. sex offender report and sex offenders per capita by state analysis illustrate how registry data can support aggregate research and comparisons across states.
Custom search and matching logic
With CSV, your team defines the search inputs, filters, and matching rules. Depending on your implementation, you could search across states, accommodate name variations, or combine several fields to identify candidate matches.
That flexibility comes with responsibility for testing the results. Broader matching can retrieve additional candidates while also increasing false matches. Missing or inconsistent source values still affect what your search can find.
If you only need an adjustment to the standard API’s search parameters, contact Nannostomus first. We can assess whether a custom API configuration could support your workflow.
Nationwide or selected-state delivery
The Nannostomus sex offender CSV dataset is available with nationwide coverage or selected states. Coverage, delivery method, and delivery schedule are agreed around your requirements. Your delivery arrangements determine when you receive files, while your ingestion process determines when those records become available within your product.
Data ingestion and ongoing maintenance
Your team manages file ingestion, storage, relationships between tables, indexing, and recurring updates. If the dataset powers a customer-facing search feature, you also maintain the application logic and infrastructure that serve those queries.
Once loaded, local queries depend on your systems. Keeping the data current still requires receiving and successfully loading subsequent deliveries.
CSV is a good fit when this control supports your workflow and your team can maintain the required infrastructure. Compare those responsibilities alongside the data access price when deciding between API and CSV.
Which Access Model Fits Your Workflow?
Start with what your product needs to do with sex offender registry data. The scenarios below apply whether you’re choosing an access model for the first time or reassessing an existing integration.
| Requirement | Suitable model | Reason |
|---|---|---|
| Retrieve records during individual name-and-state searches | API | Your application requests matching records without hosting the full dataset. |
| Add registry lookups with limited data infrastructure | API | Nannostomus hosts and updates the dataset; your team maintains the integration. |
| Regularly process large lists of people | CSV | Your team can match lists against locally loaded records instead of making individual API requests. |
| Join registry records with other data in a warehouse | CSV | The delivered records can be queried alongside your existing tables using your own join logic. |
| Calculate statistics across states or the full dataset | CSV | Local processing supports dataset-wide queries, grouping, and aggregation. |
| Search with missing inputs, name variations, or additional filters | Custom API, if feasible, or CSV | Nannostomus can assess custom search requirements. CSV lets your team build and maintain its own search logic. |
| Maintain a shared internal registry database for several systems | CSV | Multiple applications can query the same internally managed data store. |
| Reduce a growing API bill | Compare both | Compare actual API charges with a CSV quote, including ingestion, storage, and ongoing maintenance costs. |
A higher API request volume alone does not determine the choice. With CSV, the total cost includes data access, developer time to build and maintain ingestion and search logic, and infrastructure for storage, processing, and backups. Recurring updates, monitoring, and troubleshooting also require ongoing work, even when you already have the tools and infrastructure. Depending on your workflow, these costs can outweigh the savings on API requests.
If API access fits your workflow and you’re also comparing providers, see our sex offender registry API comparison for 2026.
Sex Offender API vs CSV: Pricing and Total Cost
Nannostomus API pricing depends on monthly request volume. CSV pricing is available on request for your coverage and delivery requirements. Comparing the two also means accounting for development, infrastructure, and maintenance.
How much does the sex offender API cost?
The sex offender API includes 100 free production requests each month, followed by usage-based billing. Standard per-request rates decrease across higher usage tiers. See the API pricing to estimate your monthly charges.
- 100 requests: $0
- 300 requests: $30
- 1,000 requests: $100
- 3,000 requests: $300
- 10,000 requests: $650
- 30,000 requests: $1,250
- 50,000 requests: $1,450
- 100,000 requests: $1,950
For requirements beyond standard access, Custom Enterprise options can include volume discounts, faster response-time options, and custom search parameters. Contact Nannostomus with your expected volume and technical requirements so we can assess feasibility and provide a quote.
How much does CSV access cost?
CSV pricing depends on the agreed scope and delivery arrangements, including nationwide or selected-state coverage. Request CSV pricing and describe the coverage you need, your intended workflow, and your delivery requirements.
What to include in the cost comparison
| Cost component | API access | CSV delivery |
|---|---|---|
| Data access | Usage-based charges or a Custom Enterprise quote. | Quote for the agreed coverage and delivery. |
| Initial development | Integrate requests, responses, pagination, and error handling. | Build ingestion, table relationships, indexes, and query or matching logic. |
| Infrastructure | Resources used by your application to make requests and process responses. | Storage, processing, backups, and any database or search infrastructure you operate. |
| Ongoing maintenance | Monitor the integration and handle request failures or integration changes. | Load updates, validate ingestion, maintain queries, monitor systems, and troubleshoot failures. |
A higher request volume alone does not determine the choice. With CSV, the total cost includes data access, developer time to build and maintain ingestion and search logic, and infrastructure for storage, processing, and backups. Recurring updates, monitoring, and troubleshooting also require ongoing work, even when you already have the tools and infrastructure. Depending on your workflow, these costs can outweigh the savings on API requests.
Getting Started with API Access or CSV Delivery
Both access models let you inspect the data before purchasing. Try the free demo on the sex offender API page or use the public test key in the API documentation.
Getting started with the sex offender API
- Register and complete your account details. Provide your contact and billing information.
- Add a payment card. We accept Visa and Mastercard.
- Activate the sex offender API service. Accept the applicable terms and generate your production API key.
- Start making requests. Production access includes 100 free requests each month, followed by usage-based charges.
API usage is billed on the first day of each month for the previous month’s use. For example, September usage is billed on October 1.
Getting started with CSV delivery
- Agree on scope and delivery. Contact Nannostomus to discuss nationwide or selected-state coverage, pricing, delivery method, and schedule.
- Sign the agreement and pay the invoice. We sign an electronic copy of the agreement, send it for bank verification, and send you an invoice.
- Receive the dataset. Nannostomus delivers the files through the agreed method, with subsequent deliveries following your arrangements.
The underlying dataset refreshes monthly. Your team loads each delivery into its own environment and makes the updated records available to your product.
Conclusion
Nannostomus API and CSV provide two ways to access the same sex offender registry data. Choose API for supported on-demand lookups, or CSV for bulk processing and search logic managed in your own environment. Compare the full operating cost alongside your product’s requirements.
Start with the API demo or CSV sample. If neither standard option fully fits, tell us what you need so we can assess a custom arrangement.
Frequently Asked Questions
Does the sex offender API provide fresher data than the CSV dataset?
No. Nannostomus API and CSV access use the same underlying dataset, refreshed monthly. An API request retrieves records from the available dataset; it does not trigger a new search of source registries. With CSV, freshness within your product also depends on when your team loads the latest delivery.
Is a sex offender CSV dataset cheaper than API access?
It depends on your request volume, coverage, and internal operating costs. API access includes 100 free production requests each month, followed by usage-based charges. CSV pricing is available on request and should be evaluated alongside development, storage, processing, and maintenance costs. There is no universal request-volume threshold at which CSV becomes cheaper.
Can I use the sex offender API for batch lookups?
The standard Nannostomus API has no batch endpoint. Processing a list requires individual lookup requests. CSV lets your team process lists against locally loaded data, using matching logic you build and maintain.
Can I search sex offender records without knowing the state?
The standard Nannostomus API requires first name, last name, and state. With nationwide CSV data, your team can build searches across states without requiring a state as input. You can also contact Nannostomus to assess whether custom API search parameters could support your requirements.
Does the sex offender CSV dataset include fuzzy matching?
CSV delivery provides structured records. Your team can implement fuzzy matching, name-variation handling, and other search logic using those fields. These capabilities require development and testing; they are not a ready-made matching engine included with the files.
Can I get a sex offender CSV dataset for selected states?
Yes. Nannostomus offers nationwide CSV coverage or selected-state delivery. Coverage, pricing, delivery method, and schedule are agreed before payment.
Can I try the sex offender API and CSV dataset before purchasing?
Yes. Use the free API demo or public test key to inspect requests and responses without registering. For full production access, complete account setup and generate your own key, which includes 100 free requests each month. To inspect CSV records and file structure, click **Load sample data** on the dataset page.
