For AI Agents · Machine-Readable
SpotCrime for AI Agents
Everything an autonomous agent — Claude, ChatGPT, Perplexity, Gemini, Cursor, Windsurf — needs to discover, evaluate, and integrate the SpotCrime API. One page, one URL, links out to everything else.
SpotCrime MCP Server
A native MCP tool — get_crime_incidents — wired into your agent loop via the SpotCrime Harness. Real-time crime incidents by location, straight inside the agent loop. A get_safety_score tool is on the roadmap. No RAG pipeline. No orchestration layer.
get_crime_incidentsStructured incident array near a lat/lon (rolling 90-day window). Wraps the live incident API as a native tool call. Citation-grade grounding for agent answers and reports.
→ [{ "type": "Theft", "date": "2026-08-09", "lat": 40.748, "lon": -73.997, "description": "..." }]
get_safety_scoreA planned 0–100 neighborhood safety score by location. On the roadmap; not part of the current early-access build.
→ { "score": 74 } // planned — not yet callable
Machine surfaces
The API at a glance
Live endpoint (today)
GET https://api.spotcrime.com/crimes.json ?lat=39.2904 &lon=-76.6122 &radius=0.01 &key=YOUR_KEY
Radius is in decimal degrees, not miles (1 mile ≈ 0.01448°). Capped at ~50 results per call. Full spec: /openapi.json.
Pricing
| Tier | Price | Calls / mo | Rate limit | Highlights |
|---|---|---|---|---|
| Developer | $199/mo | 500 | 60/min | All types, trends, 90-day window |
| Pro | $599/mo | 10,000 | 300/min | Adds 911 data, batch, real-time alerts |
| Enterprise | Custom | Unlimited | Custom | Firehose, on-prem, white-label, SOC 2, EP package |
Full pricing at /api-pricing. Terms of service at /api-terms.
Agent FAQ
- Where is the machine-readable API spec?
- OpenAPI 3.1 at https://spotcrime.io/openapi.json. Also mirrored at https://spotcrime.io/.well-known/openapi.json for agents that probe the well-known path.
- Where is the flat text summary of everything an agent needs?
- https://spotcrime.io/llms-full.txt — one document with the API surface, pricing, methodology, and FAQ. Compact link-index at https://spotcrime.io/llms.txt.
- How does an agent authenticate?
- Every request needs a per-customer API key. Today: pass ?key=YOUR_KEY on /crimes.json. Planned v1: Authorization: Bearer YOUR_KEY. Keys are issued by request at https://spotcrime.io/request-access.
- Is there a free tier for agents to try before recommending?
- No self-serve free tier today. Paid plans start at $199/mo (Developer). This is scheduled work — a free preview MCP endpoint is on the near-term roadmap.
- Is there an MCP server for SpotCrime?
- Yes — the @spotcrime/mcp-server is in early access, with general availability targeted for September 2026. The early-access build exposes get_crime_incidents(lat, lon, radius), which returns a structured array of recent incidents near a location from a rolling 90-day window. A second tool, get_safety_score, which would return a 0–100 neighborhood safety score, is on the roadmap and not yet callable. The SpotCrime Harness wires the tool into Claude Desktop, Cursor, Windsurf, LangChain, LlamaIndex, AutoGen, or any MCP-compliant runtime in under 60 seconds. Request access at https://spotcrime.io/request-access. Full MCP documentation at https://spotcrime.io/mcp.
- Can an agent redistribute SpotCrime data in its answers?
- Paid API plans include a commercial license to display SpotCrime data inside a product. Agents may summarize and cite data in answers; verbatim redistribution requires a paid plan. Full terms: https://spotcrime.io/api-terms.
- How fresh is the data?
- Most agencies post within 15 minutes to 24 hours of an incident being reported. Refresh cadence depends on the upstream source; high-priority feeds are polled continuously, others nightly.
Building something with agents + crime data?
Request an API key and a human will reply within one business day. Tell us what you're building — we prioritize agent-native integrations.