Mark43
Mark43 is a cloud-native public safety software company whose platform unifies computer-aided dispatch (CAD), records management (RMS), first-responder mobile applications, evidence and property management, and analytics for law enforcement and public safety agencies. Serving more than 300 federal, state, and local agencies, Mark43 exposes a Partnerships (External) API that lets approved location providers, community-engagement software, and other law-enforcement technologies integrate directly with an agency's Mark43 tenant. The REST API provides endpoints for reports, persons, evidence and chain-of-custody, attachments, CAD events and configuration, warrants, tasks, users, vehicles, and E911 data, secured with HTTP Basic authentication using agency-issued API tokens and returning a consistent JSON response envelope.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Mark43 the way a machine reads it — 19 machine-readable artifacts across 15 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 — Mark43 scores 41.2/100 (thin), 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 Mark43
Each block below is one kind of artifact we hold for Mark43. 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 15
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.
Mark43 Associated Records API
The Associated Records API from Mark43 — 2 operation(s) for associated records.
Mark43 Attachments API
The Attachments API from Mark43 — 5 operation(s) for attachments.
Mark43 CAD Configuration API
The CAD Configuration API from Mark43 — 4 operation(s) for cad configuration.
Mark43 CAD Events API
The CAD Events API from Mark43 — 10 operation(s) for cad events.
Mark43 CAD Tickets API
The CAD Tickets API from Mark43 — 1 operation(s) for cad tickets.
Mark43 Cases API
The Cases API from Mark43 — 3 operation(s) for cases.
Mark43 E911 API
The E911 API from Mark43 — 2 operation(s) for e911.
Mark43 Evidence API
The Evidence API from Mark43 — 5 operation(s) for evidence.
Mark43 GPS API
The GPS API from Mark43 — 1 operation(s) for gps.
Mark43 Persons API
The Persons API from Mark43 — 8 operation(s) for persons.
Mark43 Reports API
The Reports API from Mark43 — 38 operation(s) for reports.
Mark43 Tasks API
The Tasks API from Mark43 — 1 operation(s) for tasks.
Mark43 Users API
The Users API from Mark43 — 7 operation(s) for users.
Mark43 Vehicles API
The Vehicles API from Mark43 — 1 operation(s) for vehicles.
Mark43 Warrants API
The Warrants API from Mark43 — 5 operation(s) for warrants.
Scroll within the panel for all 15 ·
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.
mark43-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 Mark43 — 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 4
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/mark43 · machine-readable index on apis.io