ShotSpotter (SoundThinking)
ShotSpotter is the flagship acoustic gunshot detection service of SoundThinking, Inc. (Nasdaq: SSTI), the public safety technology company formerly named ShotSpotter, Inc. SoundThinking operates a portfolio of law-enforcement and security products including ShotSpotter gunfire detection, SafePointe AI weapons detection, PlateRanger license-plate recognition, CrimeTracer investigative search, CaseBuilder case management, and ResourceRouter patrol analytics. Developers integrate via the SoundThinking developer documentation at docs.soundthinking.com, which publishes REST data APIs for ShotSpotter (incident data, CAD incident ID, ILS) and SafePointe (alert data, line-crossing data), plus NAPI, a webhook/push notification interface that delivers real-time XML alert documents (ShotSpotter IALRT incident presentations and SafePointe SPALRT alerts) to a customer network endpoint, alongside an Applications IT Resource Guide.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles ShotSpotter (SoundThinking) the way a machine reads it — 5 machine-readable artifacts across 2 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 — ShotSpotter (SoundThinking) scores 28.0/100 (emerging), with a separate agent-readiness read of 31/100 (agent aware). 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.
How we profile ShotSpotter (SoundThinking)
Each block below is one kind of artifact we hold for ShotSpotter (SoundThinking). 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 2
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.
ShotSpotter Data APIs
REST data APIs for ShotSpotter gunfire detection — incident data, CAD incident ID lookup, and ILS (Investigative Lead Summary) retrieval.
SafePointe Data APIs
REST data APIs for SafePointe AI weapons detection — alert data and line-crossing data.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
shotspotter-mcp.yml
MCP SERVEREvent 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.
Shotspotter Napi Webhooks
ASYNCAPISecurity Posture 1
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.
Resources
Every other property we hold for ShotSpotter (SoundThinking) — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/shotspotter · machine-readable index on apis.io