A lot of teams want to test crime data before they commit to a vendor. That is reasonable. You should be able to call an endpoint, inspect the response shape, see how location resolution works, and decide whether the data fits your product.
CrimeScore accounts are free to create and do not require a payment method. Public ZIP/ZCTA profiles and the nationwide map help teams inspect the product before activating API access.
The Starter response is intentionally simple: resolved geography, `safety_score`, `safety_grade`, component scores, and model metadata. That gives teams a stable contract for location-safety workflows and proof-of-concept integrations.
CrimeScore is score-first. Authenticated API calls require a trial or paid plan; there is no public raw incident feed or free API allowance.
That distinction matters for product quality. Raw incident lists can be noisy and hard to compare across cities. A score API gives your application a cleaner signal that can sit inside property search, underwriting support, routing workflows, market analytics, or internal dashboards.
Starter includes `/v1/score/details` with contributor explanations and watermarked map embeds. Pro adds nearby incidents and unwatermarked embeds. Enterprise adds custom volume and dedicated support for larger deployments.
The easiest way to start is to create an account, review public ZIP and map pages, then activate the seven-day monthly Starter trial when you are ready to generate a server-side API key and test real requests.
A useful API trial should support honest evaluation. Test a small number of real locations, compare ZIP and coordinate behavior, read the methodology, and make sure the response is something your users can understand.