Dapper
Use cases

Political intelligence, delivered as infrastructure

How companies, public institutions, and product teams turn Latin America's regulatory and legislative activity into monitoring systems, risk models, and AI copilots.

Who builds on Dapper

The same API powers compliance desks, public-sector observatories, and venture-backed products.

Medium & large companies

Compliance, legal, strategy, and public affairs teams in banking, energy, healthcare, telecom, and tech — monitoring the rules that move their markets across 12 countries without maintaining scrapers.

Government & public sector

Ministries, regulatory agencies, embassies, and multilateral organizations — tracking neighboring legislation, benchmarking regulation across the region, and briefing decision-makers with sourced data.

Product, data & AI teams

Consultancies, RegTech and GovTech builders, and research groups embedding structured political data into their own products, models, dashboards, and agents.

What teams ship with the API

Every use case below runs on documented public endpoints — the examples are real requests you can adapt.

Companies
Regulatory change monitoring

Poll new decrees, resolutions, and rulemaking consultations by country, entity, and date, and alert the affected business line the day something changes. Filter by the issuing regulator you already know (SHCP, CRC, CMF…).

GET /v1/regulations?country_code=MX&since=2026-07-01
GET /v1/consultations?country_code=MX&since=2026-07-01
Companies · Government
Legislative tracking & government affairs

Follow every bill from filing through committees to the plenary: authors, status changes (tramitaciones), agenda events, and final votes — the raw material of a public affairs practice, structured.

GET /v1/bills?country_code=CL&since=2026-06-01
GET /v1/bills/8421/updates
Companies
Political risk & market intelligence

Feed risk models and country reports with historized, cross-country regulatory activity, news, and voting behavior. One query spans several countries with the same response shape.

GET /v1/regulations?country_code=BR,CO,MX&since=2026-06-01
Companies · Government
Voting analytics & accountability

Reconstruct how each legislator and party voted, session by session. Power scorecards, coalition analysis, and data journalism with roll-call records linked to actors, parties, and bills.

GET /v1/actors/512/votes
GET /v1/parties?country_code=AR
Companies
Public consultation response

Catch open comment periods before they close. Consultations come with start and end dates and the issuing entity, so your regulatory affairs team never misses a window to participate.

GET /v1/consultations?country_code=CO&since=2026-06-15
Government
Cross-country regulatory benchmarking

Compare how 12 countries regulate the same topic — instrument types, issuing entities, and timing — from one API. Built for public-sector observatories, multilaterals, and policy research units.

GET /v1/regulations?country_code=CL,PE,EC&since=2026-01-01
GET /v1/regulation-types
Companies · Government
AI copilots & policy assistants

Connect Claude, ChatGPT, or your in-house agent to the MCP server and every endpoint becomes a tool. Analysts ask questions in plain language; answers cite real official records.

"Which AI bills moved in Brazil this week?"
→ MCP: https://api.dapperglobal.com/mcp
Companies · Government
Data pipelines & research datasets

Bulk-sync any domain with stable cursor pagination that never skips or duplicates rows, and gate your pipeline on the public freshness endpoint before each run.

GET /v1/bills?country_code=BR&limit=500&cursor=eyJpZCI6…
GET /v1/health

Built for production teams

The operational guarantees procurement and platform teams ask about, on by default.

Scoped API keys

Restrict each key to specific countries and data domains — clean governance for large teams, vendors, and agencies.

Zero-downtime key rotation

Rotate credentials with a grace window so running integrations keep working while you swap secrets.

Transparent rate limits

Every response carries X-RateLimit-* headers, and 429s include Retry-After — no guessing, no surprise cutoffs.

Public freshness SLAs

GET /v1/health publishes the last update per country and domain, with explicit ok/warning/stale thresholds — verify recency before you buy.

Stable cursor pagination

Keyset cursors stay consistent while new records land — built for bulk syncs and long-running exports.

Machine-readable errors

Every error has a stable code (RATE_LIMITED, FORBIDDEN_COUNTRY…) your automation can branch on.

Frequently asked questions

What is the Dapper Public API?

A REST API with read-only data for political and regulatory intelligence in Latin America. It serves regulations, bills, roll-call votes, political actors, public consultations, legislative agendas, news, and documents from official sources across 12 countries, normalized behind one consistent interface.

Which countries does the API cover?

Argentina, Brazil, Chile, Colombia, Costa Rica, the Dominican Republic, Ecuador, Guatemala, Mexico, Panama, Peru, and Venezuela. Countries are addressed by ISO code (e.g. /v1/bills?country_code=BR), and GET /v1/countries lists live coverage per data domain.

What data does the API include?

Eight domains: regulations (official gazette acts), bills with full legislative tracking, roll-call votes, political actors, public consultations, legislative agendas, political news, and searchable documents. Reference catalogs of entities, commissions, and parties make everything joinable.

How fresh is the data, and how can I verify it?

Each domain has an update SLA — news within hours, regulations and bills daily. GET /v1/health is public and shows the last update time and status for every country and domain, so you can verify freshness before and after integrating.

Can I use the API with Claude, ChatGPT, or my own AI agent?

Yes. The MCP server at /mcp exposes every endpoint as a tool for Claude, ChatGPT, Cursor, and any MCP-compatible client, with browser OAuth login or an API key (as a header, as a bearer token, or via OAuth client credentials). The API also publishes llms.txt, a machine-readable guide agents use to navigate it.

Is the API suitable for enterprise and government procurement?

It is designed for it: read-only data, API keys scoped per country and domain, zero-downtime key rotation, explicit rate-limit headers, machine-readable error codes, per-key usage reporting, and a public freshness SLA per data domain.

How do I get access?

Public endpoints like /v1/health and /v1/countries need no key. For data endpoints, request an API key from the Dapper team, then pass it in the X-API-Key header — the quickstart on the home page takes you from zero to a first authenticated request in five steps.

Bring your use case to the data

Start with the live coverage matrix, or get a key and run your first query in minutes.

Use Cases — Regulatory Monitoring, Legislative Tracking & Political Risk · Dapper