2020 Police Brutality

This repository accumulates and contextualizes evidence of police brutality during the 2020 George Floyd protests. The goal is to assist journalists, politicians, prosecutors, activists and concerned individuals who can use the evidence accumulated here for political campaigns, news reporting, public education and prosecution of criminal police officers.

2020 Police Brutality is listed with 1 API on the APIs.io network: Incidents API. Tagged areas include Brutality, Civil Rights, Policing, and Public Data.

The 2020 Police Brutality catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

2020 Police Brutality’s developer surface includes documentation and 12 more developer resources.

📡 Profile data on GitHub

24.0/100 emerging ▬ flat Agent 25/100 agent aware Heartbeat 0/100 dormant self hosted · MIT Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 API 6 Features 6 Use Cases

BrutalityCivil RightsPolicingPublic Data

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 24.0/100 · emerging

Contract Quality 5.0 / 19

Developer Ergonomics 1.4 / 15

Access Clarity 1.2 / 15

Operational Transparency 2.6 / 10

Contract Governance 2.5 / 9

Discoverability 4.3 / 8

Regulatory Posture 0.7 / 15

Open Source Surface 5.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/2020-police-brutality/"><img src="https://apis.io/badge/2020-police-brutality/card.svg" alt="2020 Police Brutality on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 7.9 — up to +18.4 composite points
Contract Quality scores 26.7 — up to +18.3 composite points
Developer Ergonomics scores 9.5 — up to +18.1 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/2020-police-brutality/apis.yml: open an issue on github.com/api-evangelist/2020-police-brutality to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

2020 Police Brutality Incidents API

Police brutality incident records from the 2020 George Floyd protests

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

2020 Police Brutality Incidents API

OPEN COLLECTION

2020 Police Brutality API

OPEN COLLECTION

2020 Police Brutality API pricing

Not yet checked against 2020 Police Brutality's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against 2020 Police Brutality's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

2020 Police Brutality Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

2020 Police Brutality Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

2020 Police Brutality

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

2020 Police Brutality Finops

FINOPS

Features 6

Notable capabilities this provider offers.

Incident Documentation

Documented evidence of police brutality with descriptions, dates, locations, and source links

Location Data

GPS geolocation coordinates for each incident, enabling geographic analysis

Tag Classification

Categorical tags classifying incident types (foam-bullet, tear-gas, pepper-spray, etc.)

Multiple Data Formats

Data available in JSON (v1 and v2) and CSV formats for different use cases

Source Verification

Each incident includes links to source documentation for verification

Open Data

MIT licensed open dataset available for public use

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

2020 Police Brutality Context

5 classes · 11 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

2020 Police Brutality — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

2020 Police Brutality API Rules

23 rules · 11 errors 10 warnings 2 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

IncidentCollection

4 properties

JSON SCHEMA

Incident

11 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

2020 Police Brutality Incident Collection Structure

4 properties

JSON STRUCTURE

2020 Police Brutality Incident Structure

11 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

2020 Police Brutality Incident Collection Example

4 fields

EXAMPLE

2020 Police Brutality Incident Example

11 fields

EXAMPLE

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

2020 Police Brutality Agentic Access

3 operations

3 operations · 0 acting

AGENTIC

Use Cases 6

What developers build with this provider.

Journalism and Reporting

Investigative journalists use incident data for news reporting on police conduct

Legal Proceedings

Prosecutors and civil rights attorneys use evidence for criminal and civil cases

Academic Research

Researchers study patterns in police use of force during protests

Policy Advocacy

Activists and policymakers use data to support police reform campaigns

Public Education

Organizations use the data to educate the public about police brutality

Geographic Analysis

Researchers map incidents by location to identify geographic patterns

Resources

Documentation 2

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

IssueTracker

IssueTracker

Releases

Releases

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Source (apis.yml)

aid: 2020-police-brutality
url: https://raw.githubusercontent.com/api-evangelist/2020-police-brutality/refs/heads/main/apis.yml
name: 2020 Police Brutality
type: Index
deliveryModel:
  model: self-hosted
  license: MIT
  open_source: true
  commercial: false
  callable_host: true
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/2020-police-brutality.png
tags:
- Brutality
- Civil Rights
- Policing
- Public Data
description: This repository accumulates and contextualizes evidence of police brutality during the 2020 George Floyd protests.
  The goal is to assist journalists, politicians, prosecutors, activists and concerned individuals who can use the evidence
  accumulated here for political campaigns, news reporting, public education and prosecution of criminal police officers.
created: '2024-11-13'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: 2020-police-brutality:2020-police-brutality-incidents-api
  name: 2020 Police Brutality Incidents API
  description: Police brutality incident records from the 2020 George Floyd protests
  humanURL: https://github.com/2020PB/police-brutality/tree/data_build
  baseURL: https://raw.githubusercontent.com/2020PB/police-brutality/data_build
  tags:
  - Incidents
  properties:
  - type: OpenAPI
    url: openapi/2020-police-brutality-incidents-api-openapi.yml
  - type: Documentation
    url: https://github.com/2020PB/police-brutality/tree/data_build
  - type: JSONSchema
    url: json-schema/2020-police-brutality-incident-schema.json
  - type: JSONSchema
    url: json-schema/2020-police-brutality-incident-collection-schema.json
  - type: JSONLD
    url: json-ld/2020-police-brutality-context.jsonld
common:
- type: Plans
  url: plans/2020-police-brutality-plans-pricing.yml
- type: RateLimits
  url: rate-limits/2020-police-brutality-rate-limits.yml
- type: FinOps
  url: finops/2020-police-brutality-finops.yml
- type: IssueTracker
  url: https://github.com/2020PB/police-brutality/issues
- type: Releases
  url: https://github.com/2020PB/police-brutality/releases
- type: ContributionGuide
  url: https://github.com/2020PB/police-brutality/blob/main/CONTRIBUTING.md
- type: License
  name: MIT
  url: https://github.com/2020PB/police-brutality/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/2020-police-brutality-agentic-access.yml
- type: GitHubOrganization
  url: https://github.com/2020PB
- type: GitHubRepository
  url: https://github.com/2020PB/police-brutality
- type: Documentation
  url: https://github.com/2020PB/police-brutality/blob/main/README.md
- type: SpectralRules
  url: rules/2020-police-brutality-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/2020-police-brutality-vocabulary.yaml
- type: Features
  data:
  - name: Incident Documentation
    description: Documented evidence of police brutality with descriptions, dates, locations, and source links
  - name: Location Data
    description: GPS geolocation coordinates for each incident, enabling geographic analysis
  - name: Tag Classification
    description: Categorical tags classifying incident types (foam-bullet, tear-gas, pepper-spray, etc.)
  - name: Multiple Data Formats
    description: Data available in JSON (v1 and v2) and CSV formats for different use cases
  - name: Source Verification
    description: Each incident includes links to source documentation for verification
  - name: Open Data
    description: MIT licensed open dataset available for public use
- type: UseCases
  data:
  - name: Journalism and Reporting
    description: Investigative journalists use incident data for news reporting on police conduct
  - name: Legal Proceedings
    description: Prosecutors and civil rights attorneys use evidence for criminal and civil cases
  - name: Academic Research
    description: Researchers study patterns in police use of force during protests
  - name: Policy Advocacy
    description: Activists and policymakers use data to support police reform campaigns
  - name: Public Education
    description: Organizations use the data to educate the public about police brutality
  - name: Geographic Analysis
    description: Researchers map incidents by location to identify geographic patterns
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

2020 Police Brutality API — frequently asked questions

Does 2020 Police Brutality have an API?

Yes. APIs.io lists 1 API from 2020 Police Brutality, including 2020 Police Brutality Incidents API.

Is there an OpenAPI specification for the 2020 Police Brutality API?

Yes. APIs.io indexes 1 OpenAPI specification for 2020 Police Brutality, each linked for download from this page.

How much does the 2020 Police Brutality API cost?

APIs.io lists 3 pricing plans for 2020 Police Brutality, with each plan's price, limits and inclusions under Pricing on this page.

Is the 2020 Police Brutality API ready for AI agents?

2020 Police Brutality has a Kin Score of 24.0 out of 100 (emerging) and an Agent Readiness score of 24.5 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/2020-police-brutality"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/2020-police-brutality/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/2020-police-brutality/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.