Base Operations
Base Operations provides street-level threat intelligence for corporate, government, and law-enforcement security teams. Its platform validates crime, violence, unrest, and sUAS-incursion data from 25,000+ OSINT sources across 5,000+ global cities (99% of the US) and distills it into BaseScore, a transparent 0-100 risk metric comparable at country, city, district, and sub-mile (0.1 mile) granularity. The Customer API exposes BaseScore ratings, threat summaries, time-series trends, forecasting, change analysis, and saved locations over a REST interface authenticated with an X-API-KEY header, returning JSON so teams can integrate standardized risk scores directly into their own risk models, travel-security, event-security, and site-selection workflows.
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 Base Operations the way a machine reads it — 16 machine-readable artifacts across 12 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 — Base Operations scores 45.2/100 (developing), with a separate agent-readiness read of 51/100 (agent ready). 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-07-27 · rubric v0.5
How we profile Base Operations
Each block below is one kind of artifact we hold for Base Operations. 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 12
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.
Base Operations Analytics API
The Analytics API from Base Operations — 2 operation(s) for analytics.
Base Operations Base Score API
The Base Score API from Base Operations — 9 operation(s) for base score.
Base Operations Change Detection API
The Change Detection API from Base Operations — 13 operation(s) for change detection.
Base Operations Key Takeaways API
The Key Takeaways API from Base Operations — 4 operation(s) for key takeaways.
Base Operations Public Charts API
The Public Charts API from Base Operations — 4 operation(s) for public charts.
Base Operations Radius Charts API
The Radius Charts API from Base Operations — 9 operation(s) for radius charts.
Base Operations Saved Location Charts API
The Saved Location Charts API from Base Operations — 10 operation(s) for saved location charts.
Base Operations Saved Location Radius Charts API
The Saved Location Radius Charts API from Base Operations — 6 operation(s) for saved location radius charts.
Base Operations Saved Locations API
The Saved Locations API from Base Operations — 4 operation(s) for saved locations.
Base Operations Source Categories API
The Source Categories API from Base Operations — 2 operation(s) for source categories.
Base Operations Threat Categories API
The Threat Categories API from Base Operations — 2 operation(s) for threat categories.
Base Operations Threats API
The Threats API from Base Operations — 6 operation(s) for threats.
Scroll within the panel for all 12 ·
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.
base-operations-mcp.yml
MCP SERVERSecurity 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.
Resources
Every other property we hold for Base Operations — 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 3
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 5
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 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/base-operations · machine-readable index on apis.io