canonical: https://jentic.com/apis/gunpolicy.org/gun-policy

# GunPolicy.org API

The GunPolicy.org API provides comparative data on armed violence and firearm regulation across countries and regions. List the regions it covers, read a region's profile, or pull a specific measure such as firearm deaths, gun ownership, or a point of law for one region. A compare endpoint returns the same measure across several regions side by side, and supporting endpoints list the available measures and a glossary that defines each term. Every endpoint is public and read-only, so the API is for pulling reference statistics into research, dashboards, and reports.

## For AI agents

Pull comparative armed-violence and firearm-regulation data from GunPolicy.org: list regions, read region profiles, fetch a measure, compare measures across regions, and read the measures list and glossary.

## Scope

Covers reading comparative firearm and armed-violence measures, region profiles, the measures list, and the glossary. It is a read-only reference dataset and does not report live incidents or accept submissions.

## Capabilities

- List the regions and countries the dataset covers
- Read a single region's armed-violence and firearm profile
- Fetch a specific measure such as firearm deaths or ownership for a region
- Compare one measure across several regions side by side
- List the available measures the API reports
- Read the glossary that defines each measure and term

## Use cases

### AI Agent for Armed-Violence Research

A research or journalism agent answers questions comparing firearm statistics between countries. Through Jentic it lists regions, fetches the requested measure, and calls the compare endpoint to line up several countries, then reads the glossary so its answer defines each term correctly. The agent discovers the data and compare operations by intent, so it grounds its answer in the source dataset without a developer wiring the HTTP calls.

Example prompt: Fetch the firearm death rate for three countries using the compare endpoint and summarize the differences with each term defined from the glossary

### Country Firearm Profile Dashboard

A dashboard shows a firearm profile for a chosen country. It reads the region profile and pulls several measures, laying out ownership, deaths, and relevant points of law. Because the data is public and read-only, the dashboard can refresh directly from the API without managing any access setup.

Example prompt: Read a region's profile and its key measures, then render an ownership, deaths, and law summary for that country

### Cross-Country Comparison Reports

An analyst builds reports that rank regions on a measure. The workflow lists the available measures, uses the compare endpoint to gather one measure across a set of regions, and orders the results. The measures list and glossary keep the report labelled with the dataset's own definitions.

Example prompt: Pick a measure, compare it across a chosen set of regions, and produce a ranked table labelled with glossary definitions

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/region` | List the covered regions |
| GET | `/region/{region_id}` | Read one region's profile |
| GET | `/data/{measure}` | Fetch a measure's value for a region |
| GET | `/compare/{region_ids}/{measure}` | Compare a measure across regions |
| GET | `/measures` | List the available measures |
| GET | `/glossary` | Read the glossary of terms |

## Key resources

- **Regions** — The list of covered regions and each region's profile
- **Data** — A specific measure's value for a region
- **Compare** — The same measure across several regions side by side
- **Measures** — The list of measures the dataset reports
- **Glossary** — Definitions for each measure and term

## Why Jentic

- **Setup:** Using the GunPolicy.org API by hand means learning its region ids, measure names, and the compare path format, then joining values to the glossary yourself. Through Jentic you install once, import the API from the Directory, and your agent calls the right endpoint with the correct region and measure.
- **Permission scoping:** The GunPolicy.org API is read-only, so you allow only the endpoints a task needs, such as GET `/data/{measure}` and GET `/compare/{region_ids}/{measure}`, and leave the rest out of the allowed set. Rules run on your own instance and every call the agent makes is logged.
- **Credential handling:** The GunPolicy.org API needs no API key or token, so there is nothing to store; requests run from your own Jentic One instance straight to the public endpoints, and the agent never handles any secret.
- **Discovery method:** Agents search Jentic by intent such as 'compare firearm deaths across countries' or 'get a region's firearm profile', and Jentic returns the matching GunPolicy.org operation with its input schema so the agent calls the right endpoint without reading reference docs.

## Related APIs

- **Data.gov API** — Catalog of open US government datasets across many topics
- **US Census Bureau API** — Population and demographic data by geography
- **openFDA API** — Public health and safety datasets from the US FDA

## FAQ

### What authentication does the GunPolicy.org API use?

None. Per its OpenAPI spec every endpoint is public and requires no API key or token, so there is nothing to configure before calling it. Through Jentic the agent simply calls the public endpoints directly.

### What data does the GunPolicy.org API provide?

It provides comparative data on armed violence and firearm regulation by region: measures such as firearm deaths and gun ownership, points of law, region profiles, and a glossary that defines each term. It is a reference dataset for research and reporting, not a live incident feed.

### How do I compare firearm data across countries with the GunPolicy.org API?

Call GET `/compare/{region_ids}/{measure}` with the regions and the measure you want, and it returns that measure for each region side by side. Use GET /measures to see what you can compare and GET /glossary to label each value. Through Jentic you search for the intent 'compare a measure across regions' and the agent gets the operation and its input schema.

### How do I read a single region's firearm profile?

Call GET /region to list the covered regions, then GET `/region/{region_id}` for a region's profile, and GET `/data/{measure}` to pull a specific measure for it. Together these build a country firearm profile without any setup.

### What are the rate limits for the GunPolicy.org API?

The OpenAPI spec does not define numeric rate limits. Because the data is reference statistics that change infrequently, cache responses and refresh them occasionally, and check https://www.gunpolicy.org for current guidance.

### Can I limit what my agent is allowed to do with the GunPolicy.org API?

Yes. The API is read-only, so you allow only the endpoints a task needs, such as GET `/data/{measure}` and GET `/compare/{region_ids}/{measure}`, and leave the rest out of the allowed set. Through Jentic these rules run on your own instance and every call is logged.

### Is there a GunPolicy.org MCP server?

You don't need a separate MCP server to give your agent the GunPolicy.org API. Jentic connects it directly from the API Directory: import the API and your agent reads and compares firearm data on demand without loading another server's tool definitions into its context.